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
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
mundo0349116yThe answer is not on google.
You are being written up by a purely subjective rule.
Code quality is indeed objective, but each person, therefore each company, has subjective ideas on the topic and they will try to force them on you.
So, your only option is to learn the ways of this company.
But, if you lack basic knowledge on the patterns used in there, do google that, buy a book, face them and tell them if they are doing something wrong too. -
MrCush1226yCould you elaborate on what they feel your not doing well in? You say code quality, but that’s a broad area. Is it the naming conventions, lack of comments, choosing to nest multiple loops instead of thinking of better solutions, buggy code, etc? We’d love to help.
-
More information would help.
Om of the general methods which help teams would be code reviews where you collaboratively share, learn and improve your knowledge and code base
Another would be to do some pair programming. This particularly helps learning when there is a senior and junior combo. It also helps keep standards up
You should also use code analysers and formatters. Not sure what languages you use, sonar cube would be good for most programming languages. On frontend, eslint, tslint are helpful with consisntency checks
Related Rants
I guess it's my third or the fourth company that am currently changing.
I have the will to improve and write better code quality level up. But sometimes i guess i have the lack to find the how to do these stuff and how to practice and who is going to tell me that i have to change these lines of code so you can improve am just in a big mess and i feel so bad about it.
Now i had just received a new warning at my current company that i either improve or i get fired. So i have been searching over google and internet how to improve as well i had just created a new project for the will to practice and become better.
Can someone tell me what i should do?
How to fix everything and let my colleagues gain my trust in my code commits ?
Because literally i feel so bad about everything and you can't imagine how miserable i feel.
rant
code
want to succeed and improve
become better
hard times
sad
bad