Definitely required more preparation work than brainstorming. That said it's a nice alternative, maybe easier to get right.
Indeed, people getting into lean processes tend to obsess over "eliminating waste". Sure there might be some waste to clean up but it's pretty much useless if you don't focus on the flow of work.
Pipelines are very widespread nowadays, still I don't see them used much. Having a few refactoring ideas under our belt to replace loops with such pipelines might help.
Where are acceptance tests coming from? They're generally the result of a conversation.
It's not the only factor leading to troublesome architectures of course. Still, if state and thus data is wrongly handled, you're indeed on the wrong track.
There are just too many of those cameras deployed. The fact that they are badly secured are compounding the negative effects.
Interesting historical work. It indeed went through a fast paced evolution cycle.
Martin Fowler obviously wrote a lot on the topic. This is a nice guide pointing to some of the most interesting resources on his blog around the agil topic.
Another explanation for the rule of zero in C++. We should definitely stick to it.
Always hated this notarization with a passion when I had to target Macs... One reason being that it felt fairly useless, and it's confirmed: it is pretty much useless.
An oldie now but still the best way to create a passphrase.
The definition of legacy code is ambiguous enough. We generally mean "bad code" (the wrong definition to me...). What about seeing things differently and trying to leave a great legacy behind us?
Nice list of ideas for stories estimations. I applied some of that with nice success.
This is very true. It's not like whoever produced bad code is particularly stupid, in most cases it's the context around which breaks the people.
When teams grow the usual standup/daily meeting format doesn't work anymore. What's proposed here is a nice alternative.
Lots of good advice on how to improve your logs.
A nice little primer on what systems thinking is about.
A good list of characteristics to aim for. Gives clue about the quality of your software architecture.
This is pretty much where I'm at as well regarding Firefox... Sad state of affairs.
Add to this how generative AI is used in the totally wrong context... and then I feel like I could have written this piece. I definitely agree with all that.