hackerm0nkey

I've installed it and I felt the same as what you mentioned :)

Then I saw Goyo Vim plugin

that's exactly what I said and it's sadly not a joke :(

I've always wondered, how did it come to this? isn't having a standup every day a 'process'?

ooh yeah, the industry is dogmatic about ill thought about so called agile principles. Nobody dare to question them it baffles me.

I've been consulting for over 10 years, how come I've never encountered a useful scrum master if they do exist

that's exactly my reluctance to question Agile processes, because people will think I am pushing it too far.

or do it from a plank position

I can't agree with this strongly enough also with the parent comment.

I think it's the constant conflict between the 'maker schedule' and the 'manager schedule'

I firmly believe that I can be way more productive when having no standups and when I control my time rather than satisfy an ill thought about ritual, but more often than not you can't change much about it. When I can, I always do.

interesting to see this becoming part of the tools.

In 2012, I was on project were we used a physical board, and we would make a black circle for everyday on the board and once we started exceeding the initial estimate (it was done in days as opposed to complexity for some reason) we make that in red, then we started discussing the reds

it absolutely makes no difference to me to have standups, yet still we participate in them...

- To see who's working on what, I just look at the board. - To seek help when I get blocked, I send a message on Slack (or whatever) at the point that I need that help, not only at 9:30 AM - To know who's blocked on what, just tune to Slack

Given the above and if you have the team discipline to make sure that tickets reflect the state of work. Why do we need standups then?

That time can be more targeted towards a meaningful discussion, but the industry seem to be blindly just doing that without giving it much deeper thought. It baffles me.

The anti-pattern in play here is that “the decision is in the hand of the least-informed”

I believe technical decisions should be delegated by the “aware” manager to the team to make or to the most-informed. But then if the manager in question is not the aware or if ego is at play then we start getting the type of decisions that are useless at best.

I get it wrong every damn time. 16 years and counting.

Not really referring to these type of decisions, but things like "should we extract this into a service, instead of having it to live in the monolith?", "should we use this type of tech to X" type of decisions that in most organisation is left in the hands of the multi-layer above hands-off manager that don't see the code, don't deal with it yet unable to see the disastrous implications of not addressing things. IMHO, organisations are better off leaving tech decisions to the people who _actively_ deal with that tech or at least give a higher weight to their take on the matter