Get a good engineer notebook or any notebook and take notes when someone is teaching/training you.
It looks really bad if you have to go ask them something they have already told you.
Ask HN: Advice for my first day as a developer tomorrow
21–30 of 44 posts
Re: Ask HN: Advice for my first day as a developer tomorrow
#22Listen. Talk very little. Good luck!
Re: Ask HN: Advice for my first day as a developer tomorrow
#23Don't be afraid of asking (what you think might be) stupid questions.
Re: Ask HN: Advice for my first day as a developer tomorrow
#24Don't send an embarrassing company-wide email about how someone ate your lunch. I'm still working there after 6 years, but I get reminded about it now and then. But seriously, focus on learning from your peers as much as possible. Don't worry about what others think of you or your code. You shouldn't take code reviews personally. Seek objectively simple solutions to problems. Good luck and may you find fulfillment in…
Also don't just do what code review comments tell you to.
If you disagree, state that and tell them why. Maybe you know something they don't about why you did something the way you did. Maybe they are just wrong. Maybe there's some business requirement you know that they don't or vice versa.
Also the other bit of not making changes just because they tell you to is this, you need to understand why you're making the change. This way you won't make the mistake again and you'll learn. You may stop doing the thing again if they comment it enough times and you internalize it, but that's not understanding, that's pattern recognition and won't help you be a better dev.
Code reviews are a two way street and a great learning opportunity. Use them to your advantage! :D
Re: Ask HN: Advice for my first day as a developer tomorrow
#25* Don’t be smart ass or know it all type - even if you’re indeed the smartest in the room.
* Sit back and learn the culture before you start stepping on toes.
* Value mentorship - learning why things are the way they’re will give you insights into the evolution of the company.
Re: Ask HN: Advice for my first day as a developer tomorrow
#26Don't send an embarrassing company-wide email about how someone ate your lunch. I'm still working there after 6 years, but I get reminded about it now and then. But seriously, focus on learning from your peers as much as possible. Don't worry about what others think of you or your code. You shouldn't take code reviews personally. Seek objectively simple solutions to problems. Good luck and may you find fulfillment in…
Embarrassment? That's your lunch! At some point you have to take a stand and defend yourself against these animals that knowingly eat another persons lunch. What's next? First it's lunch, then it's your car, your identity, then your 3pm snack!?
Re: Ask HN: Advice for my first day as a developer tomorrow
#27Find your go-to rotation of music and podcasts so you can immediately plug in when you want to get in the zone. I highly recommend checking out https://brain.fm. I pay like $6.99/mo (about same as my Spotify subscription) and it has been an absolute gamechanger for me. Piano music, lo-fi, classical music are also great places to start if you have Spotify.
For podcasts, which aren't always great since they can be distracting, I've been enjoying Bill Burr's Monday Morning Podcast lately. It's absolutely hysterical hearing him rant for a few hours every week.
Re: Ask HN: Advice for my first day as a developer tomorrow
#28measure twice, cut once.
day-to-day programming is a lot more like carpentry than science...
Re: Ask HN: Advice for my first day as a developer tomorrow
#29If you have the opportunity to socialize with your coworkers, especially if alcohol is involved, be more careful than you would with friends.
Avoid obscene language or crude humor. Most people tend to smile and laugh even when they feel uncomfortable.
Re: Ask HN: Advice for my first day as a developer tomorrow
#30- continually challenge yourself
- once you are there for a few months, take ownership of something (a part of the product, some piece of tooling, an area of support, etc) and become the go-to guy for that. You will be rewarded for it
- ask a lot of questions and don't be afraid to look stupid. People are often relieved when you ask the "dumb" question because they didn't know the answer either
- along the lines of don't be afraid to look stupid, if something is going poorly or isn't going to meet a deadline you have set, ask for help as soon as possible
- take ownership of your own career. no one will give you a raise or a promotion without you asking. Occasionally someone who is an absolute standout will get recognition like this, but it's rare
Good luck