Ask HN: Advice for first days/weeks/months at first dev job?
5 comments
Small list:
* Learn to take orders
* Listen, (so many people dont listen)
* Ask Questions
* Learn as much as you can
* Dont turn up late
* Dont be the first one to leave at the end of the day, wait for one person to go before you pack up.
* Follow requirements
* If you find problems pop your project manager an email (and keep a copy).
* Dont drop production database
* Learn to take orders
* Listen, (so many people dont listen)
* Ask Questions
* Learn as much as you can
* Dont turn up late
* Dont be the first one to leave at the end of the day, wait for one person to go before you pack up.
* Follow requirements
* If you find problems pop your project manager an email (and keep a copy).
* Dont drop production database
Ask questions. Ask lots of questions. The thing that makes the saddest is to watch a new person flounder and waste days trying to figure out something on their own which I could have easily helped them out with.
That reminds me of a HN thread a few days ago about someone getting fired after two weeks since he asked too many questions.
It's OK to say I don't know but I can find out. It's better to over-communicate status. As much as everyone talks about working smart over hard people still appreciate hard work.
Make sure you fully understand how the system is intended to work. Its all well and good knowing the stack, but equally important is knowing what you're meant to develop or fix. Also make sure you know the processes.
My advice is to ask your boss this exact question.
They know I'm junior and seem to know it's going to take a bit for me to spin up, but I was hoping HN could share advice for how to make my early days count for the most.