Good thing I didn't say or imply either of those then. I said don't abuse language features. That is a far cry from writing perfect code. Non perfect code is

Good thing I didn't say or imply either of those then. I said don't abuse language features. That is a far cry from writing perfect code. Non perfect code is expected early in a startup, I'm just saying don't confuse your non perfect code with a language failure. I'd also like to say if you've never seen "hire perfect developers" scale passed one you've been optimising for the wrong thing. I've seen a team go from technical debt hell and dread to a powerhouse team where everyone commits daily. It doesn't take much, and it doesn't take perfect developers, and it certainly doesn't have anything to do with the language. It had everything to do with honest and healthy code review. It had everything to do with people feeling comfortable enough to say, your solution is a hack, why are you taking this shortcut. That isn't write perfect code, or hire the right people. That is hire pretty much whoever will take the job. That is prioritising and optimising for quality. We still had a legacy code base, it still made us money, and it gave us the time opportunity to do things right, but you still need to take the time.