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

You don't want to be in a career where people who have been doing it for two years can be as effective as people who have been doing it for twenty—your rate of learning should always be high.

I'm having trouble reconciling this point. How can you continuously increase your effectiveness exponentially in a particular role? Take being a developer for example. Seems like the progression of skill is usually linear (with some variability). Is Sam saying that investing in becoming a great engineer ins't effective if your ultimate goal is to be extremely successful? I feel like this is overly reductionist. Maybe being an engineer for your entire career isn't going to lead to that massive success, but spending part of your career cultivating that skill does provide indirect benefits that can help you become super successful. For example, being able to rapidly prototype an MVP when you are testing product ideas. Building a business is the high-leverage action that could lead to massive success, but the years you spent cultivating your technical ability could be what enabled you to be able to build the MVP in the first place. Or maybe it allowed you to recognize good technical talent if your first engineering hires. I think exclusively focusing on tasks that provide orders of magnitude improvement is too direct and superficial of an answer. I'd be interested in hearing people's thoughts.




I think the "career" you're talking about is entrepreneur, built upon the "skill" of programmer. On the other hand, if your "career" is programmer, you're limited by salary, and competing (largely) on skill, which a talented recent graduate could beat you at. If your "career" is entrepreneur, then you get a bunch of multipliers (as Sam calls them) which make your core skills more valuable.

For example, 10 years into your career as an entrepreneur, you'll have a network (and possibly financial assets, and possibly an existing successful business, plus vague intangibles like 'wisdom' and industry insight) which all lets you be vastly more effective than someone who is equally skilled but still in their first couple years.

I don't think Sam is telling you not to build any particular skill, but rather to put yourself on a path where, 10 years down the line, you'll be able to use those skills in a way that other folks can't compete with, thanks to the other assets/resources/multipliers you've built up for yourself, and the fact that you're playing in an area where there is a) the potential for scale and b) you own the upside if it works.

Caveat: I have no idea, just my interpretation of the article.


I'd probably argue that in the majority of cases, technical abilities tend to grow exponentially at the start, and sub-linearly after a point. I've worked with a whole lot of people who have been software developers for a long time, but a given a fresh grad and a couple years experience, the fresh grad would be caught up.

For me, I've put a lot of effort into both breadth and depth, and that's where, for me, a (maybe not exponential but) super-linear growth comes from. When you dive deep on a broad set of topics, you start seeing relationships between them that others don't see. But that takes a lot of dedication to diving into a diverse set of things, and go deep on it.


This quote actually captures the sort of issue/gripe I have with being a developer (let's say you don't ascend high into management) for the rest of your career. No matter how good you are, you still have to write individual lines of code out, one-by-one. You'd be a glorified factory worker, albeit a very efficient one (years of experience would make your solution more efficient and architecturally sound from the get go).

Not to mention some very keen, obsessed younger developer could easily replicate what you're doing.




Applications are open for YC Summer 2019

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

Search: