DEV Community

Discussion on: From senior to junior in one day - looking back at my first days as a professional developer

Collapse
 
dougaws profile image
Doug

And don't forget, as you matriculate from junior to senior, document your steps! Even if all you do is create a personal text file, you'll be able to later go back and perform some of those steps without having to wade through whatever information you used to get you up to speed previously--"oh yeah, to set up the VPN I had to 1, 2, ...".

I will also help you mentor newer junior engineers when they join your team, making you even more valuable. I keep a number cheat sheets for new team members: day one, week one, month one, month three. After three months, if they aren't up to speed, either I've done something wrong or we've massively over-estimated the new person's qualifications.

Collapse
 
kethmars profile image
kethmars

That's great advice Doug! I personally haven't done that consistently, but have seen it done by some of my teammates, who through their documented knowledge have been able to answer many questions in a quick manner.

I guess into the same category goes an advice of "write down one thing you've learned today".