pull down to refresh

The Gas Town article you pointed to says it all:

The focus is throughput: creation and correction at the speed of thought.

And while this is cool [1] it is not a process that delivers work fit for production. Just like most humans should absolutely be banned from ever delivering production work (as all this crap I'm letting my NPU go through is evidence for.)

Classically we run projects over time, cost AND durable quality. Not just time and cost. And quality is the #1 missing factor in the now-hyped strategy. Gaslighting your investors into giving you more money by hiding the actual slop - fine, they'll learn. Your customers though - hah!

  1. I use this for building tooling that I need to solve really nasty problems, like building REST APIs and UIs that allow me to HitL an analysis of the impact of hundreds-of-docs to an existing set of thousands-of-docs improvement program comparing 2 disparate passes of document restructuring (from scanned binders filled with shit people thought up in the 1980s to incoherent word docs to email archives), to name an example of "things that you really don't want to do manually"