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

You’re correct. I was confusing the two cities

Your username sounds like a way to become very caffeinated

For that to work, one must pronounce SQL as an acronym, not an initialism

Some people will be constitutionally unable to make that tune work

I’m a scrum master. Drinking now. A lot

Gotta stay at the Ballmer peak

Southern Italy is better at pizza. Florence is about the best

IBM is so good and so bad. Their machines are so open. Their software is not.

“I don’t recall” is a reasonable response

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)

You can have your own machine do DNS lookups, a Linux box with BIND, and any other of your computers can have the DNS resolver set to that machine

You need to forward port 53 from your router (usually a wifi router) to the machine running the DNS

You’re right on. We have some good expertise left over from our previous methodology which was both waterfall and siloed so bad feature documents don’t cause too much problem, but once our expertise retires (and we’re not makeing new experts as the silos were removed) the features will need to great to get decent products

And bad management is the biggest thing to make a job miserable

I don’t take it as mocking or anything, I know that some devs in my team preferred waterfall. I’m just saying there are aspects of agile I really enjoy

Waterfall makes higher quality software in many circumstances. It’s optimised for quality.

Agile is optimised for speed explicitly at the expense of quality. Whatever methodology you can only pick two between development speed, cost, and quality

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