darq

Brainworms.

Eyyy

I would have thought that such a feature would be completely uncontroversial. Really weird that some people seem resistant to it.

I have my complaints about Agile, but a bit different from this list. Teams I’ve worked in have generally tried to spec in quality control measures into story points, to prevent some of the issues mentioned, for example.

My issue is almost always just that the top half of the organisation does not, and will never, conceptualise a software project like agile demands. Business will always want X scope within Y time. And Agile demands that at least one of those to be variable. The backlog represents scope organised by time. Want X features complete? Check the backlog to see when they’ll be done. Want to deliver after Y time? Check the backlog to see what features will likely be ready by that time.

But business will not accept that. They have scope requirements and deadlines to deliver within.

I tried a couple of times to get Docker running rootlessly on my local machine, without just granting root-like permissions to the user. Spent a few hours reading just the worst documentation that tells you to do things with absolutely no explanation of why, feeling like an idiot.

Then I installed Podman. It worked more-or-less out of the box, and I got on with the rest of my project.

I’ve always wondered why some people tout “forcing a consistent appearance across environments” as a pro for spaces. That’s a bad thing.

To be honest I’m surprised code format converters aren’t ubiquitous. Let the repo have it’s master format, enforced on commit. Then converters translate into each developer’s preferred standard dialect on checkout and back again on commit.