Ask HN: Advice for Your Self as a New Engineer | Hacker News Reader

Ask HN: Advice for Your Self as a New Engineer

8 pointschrisdevs7 comments

Here's what I, now a Staff Engineer, would tell my self on day one of my first software engineering job:

1. Slow down. You're building a foundation, focus on learning.

2. Be OK with not knowing. Nobody has it completely figured out, ask questions, embrace the discomfort.

3. Build relationships. You're going to see these people again, I promise.

4. Be kind. When you're kind and helpful to others they will be kind and helpful to you, and you're going to need help from time to time.

5. Take care of yourself. Life is more than work, take time for the things that need time.

6. Don't put Slack on your phone.

What would you say?

View on HN

This business and these business people that you're taking very seriously all have no idea what they're doing. You'll understand this in about 5 years from now.

That's information to research/inquire about before the interview(s) & at interview(s) before accepting a position.

Result of inquires determine what the job seeker should request be put in writing before accepting an offer.

FWIW, the business I'm talking about was a fortune 500 with many well educated people. They still had no idea what they were doing.

I've worked for four businesses now and in that time I've seen a lot of people with no understanding of the software industry. Very well paid people.

I'm still not a senior, thanks to my horizontal/vertical moving across the organizations.

I'd just tell my young self to concentrate on the fundamentals and go as deep as possible. Be someone who does NOT need to suck up and "network" and can still find a job even in a recession. Be PURE technical; Don't be afraid to not get a hold on business; Abstract yourself away from business because that's something you are bad at. Maximize what you are good at instead of trying to be an all-round bucket.

Oh and not to get a kid when you are busy advancing your career. Maybe just not get married at all.

Be lucky to work on a greenfield project with endless opportunity instead of a monolithic codebase with its own rules and strict parameters and no possibility for play.

7a) Write it down! -> Pre/Post doc are not just university certifications <-

   Insufficient information to write down? -> see numbers #2 through #6 above.

7b) in fix isn't what happens after using git to update code after a bux fix. see documentaion. See 7a

7c) * 90% time on 10% of code may be a thing; but 90% of the project should not be typing/debugging code. see 7a

1. To glimpse at the future look at your current peers both inside and outside your current employment. Determine the baselines of acceptable behavior, delivery, and product quality. If you are not commonly seeing world class results abandon that line of work.

Reply on news.ycombinator.com