Re:Fixing Scrum (2019)
by bobm_kite9 on Sunday March 08, 2020 @06:54AM
(#22517426)
Author here: nice comment. Absolutely the way to success isn't about avoiding all risk. As you point out, this is the way to mediocrity and tedium.
Life (and software) should be about taking risks - I've written a bunch of articles about this on the site[1] about how development is about making bets.
I could understand the author's idea with absolute clarity (regardless of his merit).
I don't have the slightest idea of what I've just read in your comment.
> I don't have the slightest idea of what I've just read in your comment.
Easy. Not having your way does not mean that you're building the wrong thing, and feeling bad because your idea didn't prevailed is not a technical problem nor a sign that everyone else is incompetent or that the process is faulty. In fact, it just mean that the complainer is unprofessional and immature.
Ok, how about this:
We spend so much time claiming to fight against perfectionism, and then we invite it right back in by framing important questions badly.
Go, be wrong, and then be less wrong as quickly as you can.
I had an immediate histamine reaction to this statement. With a site title like Risk First, it’s like he’s standing right next to the solution but looking the other way. I suppose we’ll see in the next article if he’s being coy setting up a scenario so he can make a dramatic turn or not. I’m worried he’s instead being sincere.
But that question? It’s so much the wrong question. We know from surveys that couching questions the wrong way invites certain answers and precludes others. So I have some questions of my own, that are biased toward my agenda.
Who cares if you built the wrong thing? Or more informatively, why do you care that you built the wrong thing? Is it because you were wrong? Oh boo boo. This is a trap intellectuals set for themselves all the time.
You want to know the stuff I recall from school? It’s often the stuff I got wrong on the test. I get it. It’s a bad feeling. But bad feelings aren’t automatically bad. There are worse things in life and software than bad feelings. Like hollowness. A grey heckscape of empty mediocrity teaches you almost nothing and doesn’t even leave you with a story to tell. Nothing happened at all, and it was horrible.
How do we, as software developers, minimise our investment (time, energy, mindshare) in building the wrong thing? That’s a much better question. And some times it means steering toward the stupid, or the crazy, instead of just being averse. Steering past it, not away from it.