Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Great question! When I hopped on to my first programming job I was in charge of developing code standards for a language I barely knew. Then I was responsible for defining the code review process. Which I was then in charge of doing. I was code reviewing senior devs code.
Create some code standards for yourself and follow some basic principles. Single Responsibility, Separation of Concerns, and avoid code duplication. Ensure you are doing proper documentation, and following naming conventions.
Ensure you are following your own standards to keep up. I thoroughly enjoyed the book called Clean Code. -
unknown18395yIt's always good to do some self-reflection by asking yourself this kind of questions.
-
And if they cry about what you did to your future employer when they check your referees the answer can simply be:
I warned i was a junior dev and that i needed some supervision. They said yes and provided NO supervision.
Honesty, sometimes can go a long a way.
Related Rants
Being an unsupervised junior developer, I wonder how shitty the code I write is, and how being unsupervised will affect my future in this career.
rant
jobs
career
junior developer's life