The timing of this article and the submission seems to coincide (and possibly a reaction) to the other story on HN frontpage: Working quickly is more important than it seems (2015) (jsomers.net)
To clarify, some are misunderstanding James Somers to be advocating sloppy low quality work, as if he's recommending speed>quality. He's saying something else: remove latencies and delays to shorten feedback loops. Faster feedback cycles leads to more repetitions which leads to higher quality.
"slowness being a virtue" is not the opposite of Somer's recommendation about "working quickly".
To clarify, some are misunderstanding James Somers to be advocating sloppy low quality work, as if he's recommending speed>quality. He's saying something else: remove latencies and delays to shorten feedback loops. Faster feedback cycles leads to more repetitions which leads to higher quality.
"slowness being a virtue" is not the opposite of Somer's recommendation about "working quickly".