Hacker News Reader

hef19898

>> I think some of the root issue is the annoying micromanagement and lack of trust from non technical stakeholders. They need to chill out, but it's in their nature to be dicks somehow.

Sure. And now imagine that one of those people encounters your proverbial, arrogant, software solves it all developer. The results, if there are any to begin with, are glorious (gloriously unusable).

View on HN

Arguing in extremes helps no one. Do a better job in your selection process and setting up proper paper trails and agreements.

It's absurd how this extreme is used to justify micromanagement without recognizing how things have exploded despite micromanagement being the status quo. Haven't seen a single stereotype micromanagement scrum shop care enough about the consequences of letting a few cowboys loose only to have trouble hiring devs to fix the mess later (because no self-respecting developer wants to fix old code with near zero documentation for a pittance).

I'd love my post to be an argument in extremes for arguments sake. It is, unfortunately, half of my daily work at the moment...

If I recall correctly, "Working software over comprehensive documentation" is part of the Agile Manifesto.

I have seen this transformed into "We don't need documentation, just work on a new feature".

Reply on news.ycombinator.com