Ahh, so that’s why companies want you to be “aligned with their mission” so badly.
Right. Between search costs, orientation time on the codebase and business, mentor/team lead time spent teaching, inevitable moderate fuck-ups, and general odds and sods, a good junior developer at a pure software company is accruing negative value their first year, and is net negative until nearly their second. A bad junior developer is negative EV until you can figure that out and fire him, which can easily take over a year. Additionally, junior developers will, more often than not, leave around year four, due to desire to learn something best learned elsewhere, vesting cliffs, or just life’s inevitable changes. If this sounds like a horrible investment, the upside is senior developers. In the right business they’re pure money-spinning machines, and they need junior developers around. The most valuable thing a junior developer can produce is their future selves as a senior.
The difference between a one-year and a two-year dropout is material (decreasing the flight risk), but diligent and productive time spent as founder will certainly fix that. Don’t half-ass that. Even if your startup fails (which as you note is likely), you need to end up with connections, skills, and stories.
Do ace your Calculus III, though. If the pandemic has taught us anything it’s that most of humanity fundamentally doesn’t get differential equations and as such can barely think about a large range of situations. You certainly don’t want to be one of those folk.
Do ace your Calculus III, though. If the pandemic has taught us anything it’s that most of humanity fundamentally doesn’t get differential equations and as such can barely think about a large range of situations.
I want to highlight this extremely good object-level advice. There are a number of topics that are much easier to learn with the structure of college-level classes than on your own. I don’t know current curricula well enough to know if “ace the class” is a good proxy for “internalize the topic”, but make sure you do the latter. As long as you’re there, get the best value you can from it.
Right. Between search costs, orientation time on the codebase and business, mentor/team lead time spent teaching, inevitable moderate fuck-ups, and general odds and sods, a good junior developer at a pure software company is accruing negative value their first year, and is net negative until nearly their second. A bad junior developer is negative EV until you can figure that out and fire him, which can easily take over a year. Additionally, junior developers will, more often than not, leave around year four, due to desire to learn something best learned elsewhere, vesting cliffs, or just life’s inevitable changes. If this sounds like a horrible investment, the upside is senior developers. In the right business they’re pure money-spinning machines, and they need junior developers around. The most valuable thing a junior developer can produce is their future selves as a senior.
The difference between a one-year and a two-year dropout is material (decreasing the flight risk), but diligent and productive time spent as founder will certainly fix that. Don’t half-ass that. Even if your startup fails (which as you note is likely), you need to end up with connections, skills, and stories.
Do ace your Calculus III, though. If the pandemic has taught us anything it’s that most of humanity fundamentally doesn’t get differential equations and as such can barely think about a large range of situations. You certainly don’t want to be one of those folk.
I want to highlight this extremely good object-level advice. There are a number of topics that are much easier to learn with the structure of college-level classes than on your own. I don’t know current curricula well enough to know if “ace the class” is a good proxy for “internalize the topic”, but make sure you do the latter. As long as you’re there, get the best value you can from it.