Just chatted with CEO looking for a CTO. His notion of MVP was that it should be throwaway trash. No testing. No structure. No architecture. Written in a random language. His (many) MVPs were spaghetti thrown at the wall, searching for a product. 1/
Because of that, he actively resisted testing, code reviews, and sustainable pace in general. "We’re a startup!” 2/
He effectively told me that he didn’t have time to be Agile. 3/
To me, that’s all self defeating. Code built properly (w/ tests and a reasonable structure) goes together *faster*. When you’re thinking about architecture, your code will be built to scale when the need arises. Don’t do it now, but make it possible. 4/
“Faster” is not a good reason to be agile (I hate @jeffsutherland’s “Twice the work in half the time” shouldn’t be your main motivation, but that’s a nice code effect to doing things right! 5/5
@jeffsutherland Side effect, not code effect. I hate autocorrect.
