Yesterday, there's a discussion (here at dev.to) on "What is your best advise to a junior software developer".
I responded with 15-item, somewhat, tounge-in-cheek, list. Apparently, some people liked it. So, here it is now in post form, shareable and all.
If I have Doc Brown's DeLorean, this is what I would advise my younger self
- Keep your head down during code reviews. Humility goes a long way. They're not criticizing you, it's your code they're after. It's not personal
- Do the required reading before you get knee-deep in the code. You have a propensity to shoot from the hip, curb that enthusiasm. Don't read the manual only when you're in trouble
- Design patterns are nice, but you don't have to use all of them, all the time in every code you write
- Learn Python early. Get to the Python REPL and type
import this. Learn it by heart, then read no. 3 (above) again
- Coffee, pizza and chips are nice now, but 20 years from now, you're gonna wish you didn't eat those
- In a couple of years, social media is gonna be big. Stay out of it
- Those math subjects you hated, better get more comfortable with them. There's gonna be a thing called "machine learning", it's gonna be big, you're gonna need them maths
- Stop wondering when you will graduate from being a junior, you'll know it when you're out of it. When you start making technical choices and you recognize that there are choices to be made; then you're not so junior anymore
- Be polite when asking questions. If you don't want to get the RTFM response (a lot), read Eric Raymond's guide on how to ask smart questions
- When you go to a meeting, always bring a pen and paper. Write your notes
- If it's taking you more than 3 hours to figure out something, ask for help, tell your tech lead what's eating you up (but make sure that before you do this, you've read no. 9 above)
- If you promised your tech lead (client, coworker or boss) you will deliver the thing on Friday, and you're not gonna make it, tell them early. Don't tell them on Friday
- Exercise. You're brain (and your blood pressure) will love you for it
- When the book "Pragmatic programmer, journeyman to master" comes out. Read it
- From time to time, write a program in LOLCODE, don't lose your humor
There's a lot more, but these are my big ones
Don't forget to visit the original post by Sergio Tapia, there are other comments in there; it's still going, I think.
In this article, we’re going to explore why young programming languages with modern features can’t be adopted quickly. Additionally, we’re going to take a look at one exceptional example that got specific parameters right to be both young, modern and mature, just ready for adoption at small and big scale.