Hacker News new | past | comments | ask | show | jobs | submit login

What I learn from this is, they key to being a 10x developer is to work on problems that have 10x impact and not necessarily writing 10x more code.



That's the right lesson. The difference is actually even more stark than that: if you extend it out to picking the right project in the right company in the right industry, there're positions where you can be easily 1000x more productive. Project selection probably determines more of your productivity than almost any day-to-day coding decision.


I'm sure Larry and Sergey would agree.

The what-to-build skill trumps the how-to-build-it skill every time!


And in fact, writing scads of dumb code is often the sign of a poor developer. It often follows from the "never turn back" mentality, that leads them to follow an initial poor choice of solution through to the bitter end.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: