A bit of a rambling, there's something interesting in it though. Splitting small functions early will do more harm than good if they're not reused. Don't assume they automatically make things easier to read.

OK, this is a very bleak view... maybe a bit over the top I'm unsure. There seems to be some truth to it though.

This is a sound advice. In other words, don't commit too early, only when you got enough information. Of course monitor to make sure you don't miss said information.

Lays out the ethical problems with the current trend of AI system very well. They're definitely not neutral tools and currently suffer from major issues.

Good reasoning, multi-page applications should be the default choice for web frontends architecture. The single page applications come at a cost.

A good reminder that depending what happens in the kernel, the I/O time you were expecting might turn out to be purely CPU time.

Looks like the morbid fascination for microservices is fading. This is very welcome. This piece is a good criticism of this particular fad and gives an interesting theory of why it came to be.

Interesting, "state of the union" regarding local-first we frontend. Lots of pointers towards other resources too.

Good process for fixing bug. Definitely similar to how I approach it as well.

Interesting caching strategy. Looks somewhat simple to put in place as well.

Interesting conservation work. Video games being part of our culture, especially indie ones, it's important for such work to happen and be funded.

Think of the typography and fonts if you don't want to have text jumping around in your GUI.

Now this is a very good article highlighting the pros and cons of large language models for natural language processing tasks. It can help on some things but definitely shouldn't be relied on for longer term systems.

I didn't read it since it's basically a whole book. Still from the outline it looks like a very good resource for beginners or to dog deeper on some lower level topics.

If you're still using Chrome, maybe you shouldn't... They're clearly making it easier to overcome ad blocker and the tracking won't be a third party thing anymore, this browser will directly report on your behavior.

Good list of things to keep in mind when thinking about performances. Of course, always measure using a profiler when you want to be really sure.

More details are surfacing regarding async and Rust... definitely not a match in heaven it seems.

Interesting way to approximate how loaded a system is.

Really cool and fun experiment. Surprisingly relaxing I find.

Interesting tale and exploration on how a change in includes impacted cache misses. This is sneaky (and solved with more recent compilers).