63 private links
A bit too high on the "positive caricature scale" to my taste. That said there's a kernel of truth there, focusing on the developer experience will lead to improved impact.
Those principles are old now, but they really captured the zeitgeist of the time.
This is a good list of guidelines to produce a service which is less of a pain to test locally, deploy and operate. Of course, don't take everything at face value (not all of it aged well) but it's a good source for inspiration.
It's indeed tempting to conflate the two (at least for marketing purposes apparently, I see you LLM vendors...). Even if tempting, developer experience is definitely not equivalent to productivity.
A single tool to manage your environment and dev tools across projects? Seems a bit young and needs a proper community still. I'm surely tempted to give it a spin though.
uv keeps showing promise to make development easier. It makes everything very much self contained.
It's tempting to use uv. It's probably fine on the developer workstation at this point. It looks a bit early to use it in production though, it's a bit young for that and carries questions regarding supply chain security still.
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.
Interesting preprint review. Not sure I got it all in depth, will definitely need to revisit it at some point.
Another example of enforcing conventions using automated checks. This time using Python and Django tricks.
Nice writeup about the benefits of homogeneity in an engineering organization. It also shows how it is a balancing act though, since you need experiments to happen in a controlled way for evolution to still happen.
It's indeed important to hone your tools as well. Even though most things are not blocked due to tools, the right ones when well designed can make things easier.
Interesting framework. I wouldn't take everything at face value, but this looks like a good source of inspiration to design your own.
Definitely looks interesting. Might be a good way to uniformize developer environment management across projects.
Looks like an interesting tool to manage developer environments.
Interesting new tool for easily setting up dev environments. The real added value to previous such tools is it's open source nature and the fact that you can fully control on which infrastructure the environments will be created.
Definitely this. This is an interesting talk, most thing shouldn't be shiny. It's not about stagnating of course, but you should think more than twice before adding a new technology to your stack. Mastery is when you know everything that's wrong with a piece of tech, before that keep in mind the amount of unknown unknowns and the cost of exploiting something new.
Very important topic. Nice to see more such teams appearing and thinking now focusing on how to structure them.