[l33t233372]

To me it seems like the author is saying “An important decision is a nonlinear one, where a nonlinear decision is one that might have a big impacts.”

So this whole post boils down to something like: “only debate decisions that might have big impacts.” I don’t really see what’s interesting about that idea.

[civilized]

Tech writing could do with less "this is technical" signaling and more actual precision. Use ordinary words to express ordinary concepts ("big impact") and technical words for technical concepts ("nonlinear", "exponential"). Don't use technical words to fluff up ordinary ideas.

[blt]

Sadly, it seems that people absolutely love doing this.

[svnt]

The author stops at an intuitive leap before developing the idea into something easily put into practice.

Actually doing what the author describes is often impossible except in an intuitive way. How could you know a priori which decisions might have big impacts? On a project of any complexity you need either deep specific experience or a very accurate working model of the entire project. You aren’t likely to have either.

This has been previously covered in depth, even in software, although of course it could possibly be improved.

Painting the bikeshed is one example: http://phk.freebsd.dk/sagas/bikeshed/

[haimez]

It’s not only uninteresting- it’s wrong. Linear costs of bad decisions can kill a business in so many ways.

[nextaccountic]

> So this whole post boils down to something like: “only debate decisions that might have big impacts.” I don’t really see what’s interesting about that idea.

And yet, many people might agree with it but still debate trivial matters

[nvader]

Yes, but when you say "trivial", I think you actually mean "pedantic". This is an important distinction because...

Click to read more (28 min read)