[JamesBarney]

I think you're getting at something very important about the article.

> The first couple hundred lines of code of your project will have a much larger impact than the last few thousand lines of code ever will.

This is true of impact on functionality, not necessarily impact on the world.

If I write my own todo app it might be useful to one person, but as I continue to work on it, eventually 2 people will find it useful. Then 3. I could be up to 3x less productive per hour and still have the same impact per hour due the increased number of users.

Impact on the world is (functionality) * (# of users). If you're working on a useful project the number of users will more than make up for the diminishing functionality returns per hour.

[MaxBarraclough]

To rephrase this then: your additional work may improve your product only a little, but it may be enough that it can now compete in the market. If it's a winner-takes-all market, a slight improvement in quality may be especially consequential.

edit I think this might model the success of Slack. Which chat program should we use? There are lots of free ones and they're all about the same, but Slack has slightly better polish than the rest and is easy to set up. Let's use that. If that conversation happens in tens of thousands of organisations, you take over the world.