More likely, your &quot;type B&quot; programmer will build a half-assed MVP with 20% of the initial features that will break every 5 seconds and thus the &quot;million dollars paying startup&quot; will lose their customers to the saner competition.<p>I will also very much question your visionaries&#x2F;maintenance distinction. Many dynamic languages today are influenced by technology developed in academia. This is because the &quot;type B coder&quot; you are speaking of lacks the theoretical foundation to  build sound abstractions that are proven to not break.<p>I would describe myself very much as a &quot;type B&quot; personality - I&#x27;m completely disorganized, messy and lazy. I&#x27;ve event gotten into (physical) fights with flatmates over this.<p>And <i>precisely</i> because of this, I&#x27;m choosing technology that takes away all the rigid bookkeeping and context switching that is needed when writing anything more complex than a basic Bootstrap&#x2F;Angular&#x2F;whatever bullshit CRUD app.<p>This is because refactoring is a lot harder in a language without structure. I would never dare rip out the base data structures and replace them with something completely different in a project with more than 2kloc in a language without types. While in a logically sound language I do that daily and don&#x27;t even care - a perfect fit for my &quot;type B&quot; personality.