Hacker News new | ask | show | jobs
by glaugh 2200 days ago
Few random thoughts:

1. Most people’s answers to questions like this tend towards “Here’s what I did, you should do it, too”

2. If you want to have a family in your 30s, you might feel a strong pull to optimize for money then. So optimize for learning and fun and risk in your 20s.

3. Working at (effective) larger organizations is nice training of best practices, process, communication, and professionalism

4. Working at a larger organization yields a big network that you can pull on for the rest of your career for interesting opportunities

5. Working at small startups is nice training for hustling, getting stuff done, and learning a lot by dint of doing a lot

6. Doing your own startup is #4, only moreso.

7. The best financial return is generally a pre-IPO that looks very likely to go public or reach liquidity soon. They tend to pay closer to market salaries and hand out equity relatively generously (ymmv)

1 comments

This is all solid advice, I would probably add though that in your 20s you might want to set a time limit of a year and half to any one job, as soon as things get comfortable you should be looking for something new.

I had a lot of different jobs in my 20s and they all helped me become a better engineer, if I had stayed at one of the first ones (which was probably the most fun I had at work) then I wouldn't be where I am now..

Alt; land a gig at a consultancy or something doing some presales engineering stuff, you'll do an insane amount of weird things there for lots of different clients but have the security of a longer term position I guess.

Curious about your experiences as an early developer myself, any way to contact you?
Not really, I like to keep my HN account sep from reality. Happy to reply on here though :)
No problem.

What different roles did you do? I'm a software engineer (new grad), and have been thinking of switching roles to learn more, i.e sales engineering. How did you make the transition?

I started out as a C dev, then moved to ops, then consulting (infra, etc -- pre cloud), then devops style work (embedded with dev, cloud ops, automation etc), spent a while doing presales for a consultancy setting up CI/CD stuff POCs..