Very good points about why elegance matters in code. It's definitely something I try to keep in mind in code reviews. One has to be careful not to use too obscure features of the language though. For instance, you're mostly fine in Python where what it considered idiomatic is somewhat well defined, you're much more in trouble in C++ which isn't as cohesive.
This is actually a good list. Clearly doesn't try to invalidate YAGNI at all, focuses more on this infrastructure things you need on most projects anyway either for debug purpose or because they allow you to change the system easily later which in fact... supports YAGNI.
Very interesting and insightful point of view... I think this hits the nail on the head: "we talk about conspiracy theories in order to avoid talking about conspiracy practices, which are often too daunting, too threatening, too total".
Interesting approach. Nice to see several coops and non-coops forge an alliance like this for a better all encompassing offering.
Looks like an interesting tool for testing when a HTTP server is involved.
If it wasn't clear that Microsoft never abandoned it's Palladium plans but merely went for a detour after the backslash... now it's getting very clear with Windows 11. They're clearly back at it and this could become a problem to install something else than Windows on PCs...
Seeing the bad practices of Amazon with its Android AppStore, it really feels like another supply chain mess in the making with Windows 11 Android support...
This looks like an interesting full system profiler.
Obviously I'm convinced it's necessary for students to learn how to contribute as soon as possible. That being said, this leave unanswered the very important question of not burning out project maintainers. Indeed, it needs to be structured in some way, most projects can't cope up with swarm of students dropping potential contributions on them.
It is indeed important that serious research and conversation arise on this topic. The bomb is ticking.
Lots of good advice in there. Per usual quite some of it also makes sense in non-remote teams. Not sure I'd do everything exactly in the same way but that gives a good overall idea of the important points.
Very good rant which explains nicely why rewriting some software from scratch is almost never the right answer.
A good reminder of why you don't want to mess too much with the VCS history for systems with long term maintenance and several stable releases.
Interesting product, and it's fully Open Source, even the hardware.
Self-censorship is indeed the worst type of censorship. It's also the one the power that be prefer, it's better when peoples just stay quiet, less work to control them this way.
At last some interesting tooling for profiling memory usage of web frontends. Clearly this is very early days though, this will get more interesting as the tooling makes progress. Some of the numbers in the benchmarks they came up with in this article are very scary though.
Interesting coaching approach for teams. It's indeed hard to get teams to stick to some of the difficult development practices... By mixing several approaches, this looks like she's onto something here.
Neat introduction to how SSDs work.
Interesting exploration on the amount of legacy a platform can accumulate over time.
Clearly that's a big "if"... I don't think we'll ever see the Scrum Alliance really care about developers.