DEV Community

Cover image for new Developer(you); // How not to suck as a new developer
Matt Eland
Matt Eland

Posted on • Updated on

new Developer(you); // How not to suck as a new developer

Everyone has to start somewhere and with how broad the field of software development is, it's impossible to know everything you need to know at the start of your career - even in a very narrow area such as a single language or framework.

So how can you possibly perform well in this type of environment - either right out of college, boot camp, or even potentially self-taught?

Well, the good news is that we do not expect you to know everything day one. Expectations on junior team levels are fairly narrow:

  • We expect you to know the basics of software development
  • We expect you to know common program flow and components (if statements, loops, functions, classes, etc)
  • We expect you to be able to build and run code using the editor of choice for the organization

That's pretty simple, right? Most educations will prepare you for this level of competence. However, on top of that we also expect some things that may not be obvious:

  • We expect you to ask questions when you don't understand something (technical or business-related)
  • We expect you to work hard
  • We expect you to continually learn and grow to the point where you can contribute more
  • We expect you to tell us how you want to grow and improve
  • We expect you to bring us problems after working through them yourself
  • We expect you to not spend hours on trying to work through a blocking issue someone could spend 10 minutes helping you with
  • We expect you to show up on time and be responsible
  • We expect you to be professional and respectful
  • We expect you to be honest when you mess up (and you will - we all do)
  • We expect you to be open to feedback

If an organization has hired a developer at the beginning of their career, the organization realizes that the dev is going to need some investment, mentoring, and time to become a solid contributor to the team. That's okay, but we do expect that developer to work hard to continue to contribute.

And if you get that job and don't feel like a developer? That's okay, impostor syndrome is real, but the best antidote to it is just to keep working and learning.

Keep learning, keep growing, be reliable, honest, respectful, and a hard worker, and you're going to get better and get more and more opportunities to shine. Read technical books, watch learning videos on YouTube, Pluralsight, LinkedIn Learning, or other platforms, ask questions, attend user groups and/or conferences, but just keep getting better.

Discussion (6)

kaynguyen profile image
Kay N.

Thank you for those very practical pieces of advice! Will definitely follow through!

eerian profile image
Erion Pali

Thanks for the tips.

peeyalk profile image
Khondokar Hashibul Islam Peeyal (PK)

Thank you very much for the information. As a Jr. software engineer I shall definitely follow this instructions.

integerman profile image
Matt Eland Author

No problem. At it's core, I'm just saying simply, be responsible, keep getting better, and get help when appropriate. Don't put a lot of pressure on yourself, but be a great team player, have fun, and try to never make the same mistake twice/ find new ways to fail.

tcgronk profile image

awesome, thanks!

tehseenlgtm profile image

I'd never seen such a concise and to the point post before. Great job Matt and big thank you for sharing with us.