>The type A programmers are right that correctness and uniformity is important for building robust, maintainable software. The type B programmers are right that

>The type A programmers are right that correctness and uniformity is important for building robust, maintainable software. The type B programmers are right that a tight feedback loop and experimentation is important for building simple, innovative software. Almost early on in any startup phase, you want a type B to quickly build MVP without drama and then hiring type A to refactor it. I've seen a startup get all worked up about structures, spacings, unit tests when they don't even have a customer yet, can't ship fast enough because of all these bottlenecks introduced by Type A architect. In large corporation Type A would thrive where as the Type B wouldn't so I just don't see why you take what I said to the heart.