|
Geoffroy Couprie
@
gcouprie
Nantes, France
|
|
systems restartability engineer, weird projects @clever_cloud: sozu proxy, nom parsers, biscuit token - crypto, safe and fast protocols in Rust - he/him
|
|
|
70.149
Tweetovi
|
1.518
Pratim
|
4.309
Osobe koje vas prate
|
| Tweetovi |
|
Geoffroy Couprie
@gcouprie
|
6 min |
|
You can shorten computer as "put" or "ter" (should be obvious in context which object it is) then the keyboard is "push ter" and the screen is "show ter"
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
8 min |
|
Yes, but you need to rely on context to understand bar or baz because they both sound like bah
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
23 min |
|
My 2 year old solved the naming problem in programming. We do not need new words, we just need to combine barely intelligible 1 syllable words that are obvious in context.
I'll start renaming: cable and wifi networks are now tube bytes and air bytes
|
||
|
|
||
| Geoffroy Couprie proslijedio/la je tweet | ||
|
Rob Napier
@cocoaphony
|
3. velj |
|
Periodic Reminder: When debugging, you must first accept that something you believe is true is not true. If everything you believed about this system were true, it would work. It doesn't, so you're wrong about something.
This is a surprisingly common stumbling block for devs.
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
11 h |
|
Well, yes 😁
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
11 h |
|
Too much of my work boils down to:
- write in a buffer
- make a stream of things from that buffer
- free parts of the buffer as I consume the stream
- write in free parts
And every step of it is annoying
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
13 h |
|
1. Nobody respects foodies
2. Bringing oysters to work is a power move though but expect to share them at least
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
16 h |
|
It's mostly ready and handling production traffic 😉
I'm preparing a new major version with an improved router
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
16 h |
|
It's production ready, and we're currently working on integration in our systems. There still might be some changes as we're learning how to deploy it, but most of the work is done
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
20 h |
|
Looking at gamozolabs.github.io/fuzzing/2018/1… and wondering how impractical it would be to adapt that to handling http requests in parallel 😁
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
21 h |
|
ugh looks like I'll have to write that article twitter.com/gcouprie/statu…
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
21 h |
|
No. You can have something for which usage is well documented, but when new users discover it they can't even decide if it's for them.
Stop trying to separate them. Marketing, documentation and support have to work closely
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
21 h |
|
Relentlessly tell people "I'm working on X" because even among people you talk to every day some will not even know what you do.
Only after that you start outreach on mailing lists, forums, conferences, etc
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
21 h |
|
Here's how to market your project without feeling like a liar:
- write a good readme that tells people what it does, what problem it solves, for whom, provide examples, and shows who uses it
- talk to potential users, understand their issues and vocabulary, put that in your soft
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
21 h |
|
There's no guarantee you'll find those. Lots of good code will stay forgotten because the author never made any effort to tell people about it
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
22 h |
|
Sorry, no. that only works when you're reasonably well known from potential users, or when some users start advocating your software, doing the marketing in your place
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
4. velj |
|
Same. Usually if the original info did not bubble up it's not worth looking into. But this was a big one
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
3. velj |
|
|
||
|
Geoffroy Couprie
@gcouprie
|
3. velj |
|
Yes, and I decided that reverting that commit github.com/chronotope/chr… to fix the padding bug without allocations was more work that I cared to spend on a crate that I used just for formatting one date
|
||
|
|
||
|
Geoffroy Couprie
@gcouprie
|
3. velj |
|
For my use I really don't need much. Formatting a date and calculating durations are enough
|
||
|
|
||