Lol. Let’s ban accountability, refactoring, and debugging, never work alone, never coordinate, avoid productivity, and refuse ownership—then scream when things break, don’t integrate, and fall behind schedule.

"This is all your fault!" built-in. Why didn't you intuitively know what myX is supposed to do and how it's used?

Provocation just for "engagement" really. 102 comments so, to some degree, it works.

E: Guys, it's satire. Lol.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

I don’t see any ban of accountability, refactoring or debugging, coordination, or endorsement of screaming.

I recognize most of these as specific antipatterns that get adopted because some manager read a blog or no one actually had a clue was “agile” meant.

[–] [email protected] 4 points 1 week ago (1 children)

I recognize most of these as specific antipatterns that get adopted because some manager read a blog

Go ahead. Point out the anti-pattern baggage.

There are enough coders on here from before the post-dot-com made mentors extinct that I'm sure they'd love your specificity.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

Check my top level comment and several other replies on this post.

One I’ll mention here is “Tasks for testing and refactoring”. “Task” is the key word - testing and refactoring isn’t a backlog item that the product manager gets to deprioritize. (haha, like the product manager even realizes they are supposed to manage the backlog). It’s part of ongoing continuous codebase improvement and done whenever and wherever it’s needed.

I’ve been a software developer since 1997, I’d love to have a beer and shoot the shit with them!

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

Let’s ban

overshot your mark. maybe you misunderstood what you read and that's why you're so needlessly het up.