Excellent resource for keeping an eye on performance issues in your codebase. It's very C++ oriented but most of the insights can be generalised to other ecosystems.
Things went too far with the cloud monoculture. It's time to remember that it doesn't always makes sense, and in the case of databases maybe it's rarely worth it to go for fully managed options.
I definitely agree there. It looks like a missed opportunity to improve the API and nudge people in the right direction.
Interesting research. Can it give insights on the pervasive views of the time?
This is definitely a useful idiom. A bit like the immediately invoked lambdas in C++ but less verbose. This is nice to control intermediate variables locality and mutability like this.
A good justification of why you want to slice your stories finely. It definitely helps steering the project and reduces chances of bottlenecks.
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.