Python at Scale: Strict Modules
This is yet another example of the divide between wizarding and engineering[1]. When you&#x27;re a small startup, what matters is the expressiveness of your language, and the ability do do a lot of things very very quickly. Type safety, performance, readability, those things don&#x27;t matter. You&#x27;re just a bunch of engineers who know the whole codebase inside out, you&#x27;re pretty certain of what you&#x27;re doing. In short, you&#x27;re wizarding. If you grow big enough, this approach slows you down greatly, and you need to switch to engineering. You sacrifice some speed for making the codebase more understandable to a larger group of people, you can no longer assume everyone knows all the code, you write unit tests, need types and dislike metaprogramming because of the confusion it creates. This is why languages like Python, Ruby, Lisp or Smalltalk are amazing for small startups, but Java is what enterprises use. They&#x27;re different ends of the wizarding&#x2F;engineering spectrum. I wish there was a language that let you move gradually from one end to the other, exactly when you need to.<p>[1] <a href="https:&#x2F;&#x2F;www.tedinski.com&#x2F;2018&#x2F;03&#x2F;20&#x2F;wizarding-vs-engineering.html" rel="nofollow">https:&#x2F;&#x2F;www.tedinski.com&#x2F;2018&#x2F;03&#x2F;20&#x2F;wizarding-vs-engineering...</a>