We're still struggling about how to modularize our code. Sometimes we should go back to the basics, this paper by Parnas from 1972 basically gave us the code insights needs to modularize programs properly.

A good reminder of what agile is about from the product management perspective. If you can regularly demo your work you ensure a feeling of progress.

An old one now, but since I keep giving this advice it seems relevant still. If you're using raw loops at least that no again, there is likely a good alternative in the STL.

A good reminder that genericity can help fight against the rigidity one can accumulate using purely object oriented couplings... but it comes at a price in terms of complexity.

Good points, this is indeed often where we are struggling when we move to a leadership role. This changes the nature of the work at least in part and we need to adjust to it.

Indeed, it is often overlooked that TDD can really help finding a state of flow. Unlike other addictive activities presented in this article it requires a non negligible initial effort though, that's why I wouldn't describe it as an addiction though.

An important white paper which probably went unnoticed. It gives a nice overview of the strategies one can build around Open Source components.

Obviously I agree with this. It's time people stop jumping on chromium based browsers.

Nice principle for a search in a sorted list when you don't know the upper bound.