A good justification of why you want to slice your stories finely. It definitely helps steering the project and reduces chances of bottlenecks.

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).

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.

Indeed, having generalists in teams is definitely what you want. Having only specialists will reduce the project efficiency.

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.

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.

Lots of insight and advice in here. Are you sure you're having enough sleep? Of high enough quality?

Definitely quite some nice resources in the Rust world for people interested by development for embedded systems.