Indeed, having generalists in teams is definitely what you want. Having only specialists will reduce the project efficiency.
The other advantage of not relying only on specialists. You actually get teams better at solving problems due to the extra context and communication channels the generalists will bring.
It still something I don't see happening often. I think it is unfortunate.
This is an interesting way to frame the conversation around pair programming (and TDD even if only alluded to here).
This is really a big problem that those companies created for Free Software communities. Due to the lack of regulation they're going around distributing copyright removal machines and profiting from them. They should have been barred from ingesting copyleft material in the first place.
Indeed, we might want to use dev containers more widely in the profession. If you're developing something for the desktop you're out of luck though.
Definitely quite some nice resources in the Rust world for people interested by development for embedded systems.
Looks like a fun way to introduce the next generation to computer science basics.
It's indeed not just about the label. It's more about behaviour.
This is a good introduction to what product management really entails.
Interesting method to split stories which are proving difficult to split.
Was it all going to end up as a management fad? I'd say yes. It's not to say the values and principles in the manifesto are useless... but if something gets successful you'd better have guardrails on how it'll be warped. It didn't happen here.
This is something I've definitely seen indeed. There are clearly a threshold effect in the amount of code you have to manage. Solutions working at smaller amounts don't work anymore a couple of order of magnitudes higher, and vice versa.
Such a nice business model... not. There's really a lack of regulation in this space.
Nice little intro of the various components you need for graphics drivers. It's very much geared toward how it's organised on Linux.
They produced Apertus, and now this for the inference. There's really interesting work getting out of EPFL lately. It all helps toward more ethical and frugal production (and use) of LLMs. Those efforts are definitely welcome.
This is definitely an exciting new option for Python development.
Use the log levels responsibly in your applications. Indeed, what are at most warnings are too often reported as errors.
Finding the right level of abstraction for the tests is important indeed. It helps keep them useful longer. Scope and complexity are linked and can help find the right balance of tests.
For technical tasks, the user stories common structure (the "Connextra format") is not adequate. We can indeed take inspiration from other long forgotten agile approaches for alternatives. I particularly like this one, and it works for user stories as well in my opinion.