If you haven't launched yet, working on scaling issues is a huge mistake.
If you have fewer than 1,000 users, working on scaling issues is a huge mistake.
If you have a million users, working on scaling issues is a critical necessity...but that's a high-class problem.
This ratio changes my model of how the world can work. I'm not sure how, yet. I have to give it time to sink in.
It's actually better than that. Individuals can build things that everyone uses. If you don't divide # users / # developers, but look at median users affected foreach developer, the numbers will be far higher. Note that this also means you can break shit for hundreds of millions of people :)
If you get sued the lawyer could make the difference between the company existing or not.
If you have your head down all the time writing code, you may be oblivious to the need to cut certain corners in order to get to market before the money runs out. The manager might save your ass in that case.
Also, let me add marketer since a lot of engineers notoriously hate marketing. If you don't have marketing you may have a great product, but have no clue how to get the word out or position it so people will actually sign up. In that case all your code is worth exactly nothing.
This is pretty incredible, any way you spin it.