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?

When teams grow the usual standup/daily meeting format doesn't work anymore. What's proposed here is a nice alternative.

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.

Lots of good advice on how to improve your logs.