Chronic flow in an engaging project. Start on a Saturday morning, feel like a coffee since you’re a bit sleepy, notice it’s Sunday

I had a team of contractors working on some code. They had learnt in their previous jobs to document everything in the work wiki (aside from the design documents which have their own repository)

And it was good they did, since the project was put on hold due to too much mismatch between backend and front, and all the contractors were fired (a day before Xmas) leaving the useless doco as the best reference for whoever needs to resurrect our code

Hmm. I use 1, 2, 4, 8, 16 (I seldom need to count beyond 31 (and have up to five more bits if needed), or to zero)

I loved agile as an analyst, we used to use waterfall and you’d hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs

Also I absolutely love the job of scrum master which had no equivalent in waterfall