It's sometimes extremely difficult to get to the original source of a scientific claim. Our corpus of science is so large and complex now that finding where a claim comes from can be a daunting task.

I very much agree with this. The relationship between developers and their frameworks is rarely healthy. I think the author misses an important advice though: read the code of your frameworks. When stuck invest sometime stepping into the frameworks with the debugger. Developers too often treat those as a black box.

Another good set of advices. They're not all technical which is to be expected.

Definitely this. Our cognitive capacity is limited, we'd better not deplete it due to complexity before we even reach the core of the problem at hand.

I tend to side on the "boring tech" side, but indeed this is a good reminder that what we want is finding the right balance.

Excellent point, we made the web too complex for regular users. This is actually an issue in term of access and democracy for people to write content there.

A good list to design HTML forms. The bar is indeed high and there's value in simplicity.

Or why anticipating too much is merely a gamble. You can be lucky, but how often will you be? Also I agree that in such cases the performance will be impacted longer term leading to a death by thousands of paper cuts.

Definitely not as fashionable as the kubernetes craze. This gives very interesting properties that multi-tenant applications can't really provide. The article is nice as it lays out properly the pros and cons, helps make the choice depending on the context.

Interesting musing about the "software crisis" which was declared in the late 60s. We're coping with it by piling levels of abstractions but clearly we're still not out of it. Our craft still needs to grow.

Nice return on experience of using a simple stack to serve loads of web requests.

It might not look like a lot from the outside, but "just implementation details" in fact hides quite some work and complexity.

Very nice piece about the various types of complexities we encounter in our trade, and what we can or should do about it.

Some problems are indeed tackled faster by having a simulation allowing to explore potential solutions. It's tempting to go very formal and theoretical but it'd require more effort and be more error prone.

Shows well why you likely don't want to use GraphQL. The chances you need the extra complexity and caveats are very slim.

Since this particular fad apparently doesn't want to die... this is a good reminder about why you want to do something simpler.

Definitely this. We tend to like complexity too much as a profession and field. It's also a good reminder that the complexity of the problem and the complexity of the solution shouldn't be conflated.

Keep things as simple as possible, they might turn out to be robust too.

With some tuning SQLite can go a long way, even for server type workloads. There are still a few caveats but in some case this can reduce complexity and cost quite a bit.

This is about a Rust library but equally applies to any ecosystem which allows to easily pull a dependency. As soon as you pull them, you need to monitor their health for the sake of your own project.