←back to thread

Software Friction

(www.hillelwayne.com)
141 points saikatsg | 1 comments | | HN request time: 0.201s | source
Show context
hnthrow289570 ◴[] No.40718979[source]
>The requirements are unclear, or a client changes what they want during development. A client changes what they want after development.

Agile supports some uncertainty, but often a mile is taken when an inch is given.

You have to take it in stride though. Developers stay employed for shipping bad or happy-path-only code all the time.

>Is friction important to individuals? Do I benefit from thinking about friction on a project, even if nobody else on my team does?

Even if you were to eliminate a lot of friction, the profit would go to the business anyway.

The military has different incentives, of course.

replies(2): >>40719897 #>>40721217 #
1. lloeki ◴[] No.40719897[source]
> Agile supports some uncertainty, but often a mile is taken when an inch is given.

An inch or a mile, over time and with local information only it has you running around in an ant mill pattern[0]. I've seen my share of such projects going nowhere fast.

[0]: https://en.wikipedia.org/wiki/Ant_mill