Basically the title, I was finally able to get an entry level job doing .NET development at a medium sized software company. I thought everything about the interview process went great except I was a little shaky during the coding challenge. As I can feel the imposter syndrome already starting is there anything I can do to set myself up for success starting day one? I've worked around software, but never actually done any development with others which is where I think I'll need to learn the most initially. Is there anything that comes to mind, either specific to .NET or development in general that I can refresh on before next week so I don't make a fool of myself day one? Thanks again everyone for any assistance.
#Anything I can prep for leading up to starting my first dev job
languid ruin
pearl marsh
good communication is something that a lot of engineers lack (including me!), learn how to ask good, well-researched questions that people will be happy to help you with. If you ask questions where the answer is 'google' it, that says something about your skills. If you ask a question and you say 'I tried X, Y and Z already', that says that you take initiative.
Question asking is a skill which you'll never let go unused.
vapid jackal
I'll piggyback on above, been on both sides recently.
When you're new I'd suggest being open to people offering help and documents and tips they've learned in your particular setting. Also especially if you get some sort of mentor who would be working with you.
As always communicate what you're thinking and what's going on.
Congratulations on your new role!
languid ruin
Thank you both so much. I think that's something I'll need to work on for sure. I'm constantly caught between being anxious about asking a question initially and then not asking later because I feel like I've missed my chance. Maybe that comes from prior experience with management, but I'll definitely do my best to unlearn that here. I've never worked directly on a team that uses Agile or Scrum, is there any value in trying to get a solid understanding of that before starting or is it something that is easy enough to pick up as a newcomer?
vapid jackal
Well everyone does agile different and wrong. So maybe read up on the idea then try to pick up on whatever flavor your team is doing