[john-tells-all]

Strongly agree. We need to put out a constant stream of low-quality products, and iterate quickly to achieve our goals.

I used to do the opposite: write high-quality well-tested code, but very often the results weren't useful to the business by the time I was done. It would have been much better to produce a couple "sketches" of the feature first, then the business could kill or refine it as they want. Everyone wins!

(disclaimer: writing a book, featuring feedback loops)

[wruza]

Isn’t most of our business code just glue, forms and api? I appreciate the quick way, but also believe that our tools at hand have a plenty of room to improve. Sometimes I drop a project because it induces “ah, here we go again” mood. Quick mudballs that could be bricks that could be panels, but there’s nowhere to order them. The worst part is when the idea actually works so that mudball becomes your home.

[quickthrower2]

That is quite nuanced. It is good to be clear when you are building a POC or a production ready feature. Often the POC becomes the POS. But https://www.explainxkcd.com/wiki/index.php/2730:_Code_Lifesp...