nirvanis

Hi, OP here. Thanks for this.

I don’t seem to have cracked the Hacker News writing formula yet. A few years ago I got similar feedback, but for the opposite reason: people complained that my English felt awkward because I’m not a native speaker. This time I asked an LLM to smooth out the wording, and it seems I accidentally outsourced my personality too.

The content and research are mine. I spent a few hours trying to collect all the moving pieces into something I wish I’d had as someone returning to frontend after many years away. It was just meant to save a few fellow dinosaurs from opening 47 tabs and wondering why they suddenly need seven package managers.

> Key Limitations [...] > Perfect adherence to schedules in public transport, unlike real-world variation

LOL

Somewhat related tip: prepend LANG=C to many console commands such as grep to speed up many tools processing large files, as they will assume ASCII input (which is probably what you have in most cases)

It's more common than we imagine. That's usually the start of many of the historical network incidents. The important part, as usual, is to make sure the remediations of such incidents focus on how to limit blast radius of small changes, and how to accomplish that without imposing artificial gatekeeping and bureaucracy into the change process.

I have around 18 hours per week of prebooked meeting time (1:1s, team meetings, planning, 1:1 with manager, sync meetings with different cross initiatives, interviews, candidate screening, etc).

I have observed that my biggest productivity killer are not those meetings (I try to make them useful for me and I try to make sure they are useful for everyone). The biggest problem comes when the time around them is very fragmented. For me, a week with 30 hours of meetings can be more productive than a week with 15 hours if I manage to defragment the time around them.

I have recently worked with my team and other peers to put an effort to defragment my calendar by batching predictable meetings together (this is a process I repeat every 6-12 months) and I feel an immediate boost in focus.

My rule of thumb is trying to make sure I get daily focus slots as close as possible to length X where X is:

X = ( (40 hours) - (prebooked hours in meetings) / (5 weekdays) )

In my case (40-18)/5 = 4.4 hours. I currently have two 4-hour slots monday and tuesday, a 5 hour slot on wednesday and a 3 hour slot on thursdays. Not bad. But that degrades quickly!