🔖 Understanding Legacy Code
A bunch of reading material and notes on how to manage legacy projects and code
A bunch of reading material and notes on how to manage legacy projects and code
A ton of links on Engineering Management
It's more accurate to call it a bunch of software engineering advice, as most of it is about engineering practices, particularly on large, team-based projects.
All unhappy agile teams are alike. Each happy agile team is happy in its own way
Being better about asking for the right thing to the right person at the right time
At the risk of it including a line like "Being a massive sook arsehole is a-ok."
Part 2 of a response to the McKinsey developer productivity idea
I predict this article being very useful to me by the end of the year in order to fend off the McKinsey thing being applied to me
I pick stupid large projects with no scope and no idea what I am trying to achieve and then starting smaller yak-shaving projects as I go and never really finish any of them :-)
I haven't had many experiences where I really needed this, but when I did, I really did.