Just say ‘no’. It’s harder than it sounds, but it is indeed often the best choice.
(I think the Google-killing-products point is misplaced - that’s not saying “no”, it’s saying “yes” and regretting it later).
Just say ‘no’. It’s harder than it sounds, but it is indeed often the best choice.
(I think the Google-killing-products point is misplaced - that’s not saying “no”, it’s saying “yes” and regretting it later).
Interesting long post on the backstory behind Mirai.
Amusing in-office auto-replies (as opposed to OoO).
Interesting intro to Sentry’s work to have multiple regions. I worked on similar projects a couple of times, and it’s much more complex than you might first think.
(If you are small, just host everything in Germany).
Got around to watching the Humane Pin intro and understand why people have panned it so much. Hard to understand how this could get released - it would never have been approved anywhere I’ve worked. (The marketing, not the device).
I feel so seen 😂
Good, long, summary of why you should not be directly invoking setup.py.
An excellent update to Spolsky’s famous Unicode primer.
Good post on opting off the career ladder. Closely reflects the journey I recently went through. I think more people need to do this, but also, it’s really hard/scary.
Truly excellent write up of handling database migratons. The only thing I would add is that you want to ensure that moving off dual-write gets priority in your backlog - too often I’ve seen the urgency drop at that point and code stuck with dual writing for ages. via
This post doesn’t really do what is claims: explaining scaling with minimal engineers but it’s an interesting walkthrough of simple techniques to build a service like (OG) Instagram.
Not sure if I saw this post on Instagram’s approach to IDs & sharding back at the time.
We originally used Flickr’s technique that the Instagram post also links to. We eventually scaled it out a bit differently, reserving some of the bits for the shard ID (like Instagram). We also had slightly different requirements (e.g. 64 bits was a hard max, because we had to use the IDs with SphinxSearch).
It’s such a weird quirk of history that tlds belong to countries but are used in other ways. It is cool that, other than Italy, these are generally very small places that can get money (for a while at least) from it. Note that there’s a whole backstory on .io that isn’t mentioned here.
I also wonder what will happen with .nz when we finally change to Aotearoa.
Detailed post on how platform teams get stuff done - particularly interesting at the moment since I’ve recently moved from a platform consumer to platform provider.
How CPython uses Bloom filters in strings.
Interesting stats on security report volume and response frequency for PyPI
I don’t really agree on the linear trend being used on the response time chart. Eyeballing it, it looks like linear upwards until May (the suspension weekend), then a flat period for a while, then a new linear upwards trend from late June.
My thoughts on return styles triggered by some work today.
I wrote up my experience at Kiwi PyCon over the last weekend - in short: since I’m not hugely into the social/networking aspects, it was pretty disappointing - not enough talks of the nature that I’d enjoy.
(Some other people seemed to be having a great time, although that also seemed a little clique-y).
Good tips for beginning programmers. I especially like “More languages isn’t better … Don’t measure your progress in number of languages. More important is to learn new techniques (database, web, testing,concurrency, etc.) in the same-old language”.
Interesting use of LLM in teaching history that relies on the generated text being inaccurate.
Nice summary of the state and some of the history of (email) feedback loops.
Public (and more extensive) post about the problems with review sites that I posted about (when it was in a member-only post) last week.
Good summary of what CNAMEs are, and why they often cause trouble. I’ve seen people have mail issues due to CNAMEs many times.