Read on Twitter
If a new software engineer were to ask me for basic career advice, here's what I'd tell them.
1. Pair program often.
Learning by osmosis. See how experienced devs tackle challenging problems. And it's not one-sided. Because no one knows everything, you have things to teach them no matter your level. And you can expose gaps in documentation/process.
Learning by osmosis. See how experienced devs tackle challenging problems. And it's not one-sided. Because no one knows everything, you have things to teach them no matter your level. And you can expose gaps in documentation/process.
2. Treat code reviews as the best part of the day.
This is your opportunity to get quick feedback on how to grow. Let people be picky. Keep an open mind. You're not your code. What you write will one day be re-written or deleted by others and you will do the same to them.
This is your opportunity to get quick feedback on how to grow. Let people be picky. Keep an open mind. You're not your code. What you write will one day be re-written or deleted by others and you will do the same to them.
3. Know it's ok to not learn something until you need it.
I burned out because I thought I had to learn all the new frameworks/languages. The greatest gift I was given was the truth it's ok to only learn something when a task requires it. And then just enough to be dangerous.
I burned out because I thought I had to learn all the new frameworks/languages. The greatest gift I was given was the truth it's ok to only learn something when a task requires it. And then just enough to be dangerous.
4. Take notes on everything.
Your questions. Solutions to those questions. How your features work. What was said in standup and other meetings. Anything your managers say to you.
Your questions. Solutions to those questions. How your features work. What was said in standup and other meetings. Anything your managers say to you.
5. Pro-actively talk to stakeholders.
Who needs your feature? Why do they need it? The most valuable developers are ones who can:
- Understand the business value underlying what they're working on
- Clearly communicate technical concepts to non-technical people
Who needs your feature? Why do they need it? The most valuable developers are ones who can:
- Understand the business value underlying what they're working on
- Clearly communicate technical concepts to non-technical people
6. Always be learning and building, but not at the expense of mental health and good sleep.
Growth is pointless without those two things.
Growth is pointless without those two things.
7. Speak up for yourself.
You must see yourself as your biggest advocate. If you need more support, ask for it. Your manager can't read your mind.
You must see yourself as your biggest advocate. If you need more support, ask for it. Your manager can't read your mind.
8. Start mentoring others now.
You don't have to wait until you're a mid-level or senior to teach others. The moment you learn something new, you're qualified to share it with someone else. Plus, you still remember what it's like to be completely new at this.
You don't have to wait until you're a mid-level or senior to teach others. The moment you learn something new, you're qualified to share it with someone else. Plus, you still remember what it's like to be completely new at this.
4. Devour technical books.
Articles are great, but I'd argue that books are superior for learning many technical concepts. Your technical brain is a muscle, and skimming an article doesn't work it the way tracing an author's argument from start to finish in a book does.
Articles are great, but I'd argue that books are superior for learning many technical concepts. Your technical brain is a muscle, and skimming an article doesn't work it the way tracing an author's argument from start to finish in a book does.
10. Embrace empathy
Imagining yourself in other's shoes is one of the best ways to not be a crappy human being (besides going to therapy).
Will others understand what my code is doing?
Will this feature serve ALL my users well?
Would this action or comment make ME feel safe?
Imagining yourself in other's shoes is one of the best ways to not be a crappy human being (besides going to therapy).
Will others understand what my code is doing?
Will this feature serve ALL my users well?
Would this action or comment make ME feel safe?
What advice would you give a developer just starting out?
