Some good points in this list although I'm not in full agreement with everything (especially the one about the lack of usefulness for TDD). The importance and the impacts of the tooling is often underestimated indeed. The last two random opinions about mocking and overtesting are very much true as well.
Very interesting piece. Goes in length about the UNIX history and the evolution of POSIX. It also highlight its limitations and where the design needs to evolve.
In our industry, we obsess too much over individual performance. In turn it means that the systems we put in place within or around our teams get neglected... this is a problem because it is what has the biggest impact on quality and performance.
This has some interesting promises in terms of performance using Python. Looks a bit like a CUDA for Python... to be seen how it fares in practice.
Indeed, React is a bit too much of the default choice right now while clearly it shouldn't be that way. Let's hope it'll change and something else with more merit will take its place.
Python is making progress regarding portable binaries and it is welcome.
A good list of tricks to ease the pain with email hosting. I use some of it to deal with the delivery pain.
The sad state of self-hosting emails.
Looks like a good cheatsheet to navigate the maze of the USB marketing terms...
Lots of good insight for a long career as a programmer. Definitely a few things I live by and a few... I tend to loose sight of. More progress to be made.
Sounds like a potentially interesting tool to estimate web applications CO2 impact. Looks far from perfect but this is better than nothing.
Indeed a good list of attributes. Not sure if that's the only attributes you want in a team but that's definitely must haves in at least one person.
Unfortunately seems to subscribe to the 10x programmer myth at least partly while trying to debunk another one... apart from that, it was very insightful, shows well how it's a team sport and how you want people to complete each other. The whole "rockstar developer" thing is a recruitment marketing scheme.
This mistakes are indeed widespread too much for my taste.
Still controversial in the Python community, this post shows a balanced view on where it makes sense and where it doesn't.
It's at least nice to see people paying attention to this and fixing their applications accordingly.
More elements on why we should all be concerned about Visual Studio Code and the state of development tools overall. It's clearly moving more and more proprietary. Visual Studio Code's ecosystem is a very well designed trap. I see it more and more around me (even tried it for a little while to see what it was all about). What can I say... Go Kate Go! And also we clearly need many more LSP servers.
I'd lie if I said I'm not slightly fascinated by what you can do with Stable Diffusion...
Interesting first exploration of a tiny part of the data set. If you read closely, this shows some of the potential biases in there.
Wise words, if you're always too busy and overloading your team, it's a sign of something... but what? It's important to know since it's what will drive the necessary conversation you need to have.