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
-
fancy and clever serve to prevent code from breaking and making deliverables faster to complete. if they're not serving these ends then it's bike shedding instead of the reason why fancy and clever was invented in the first place
when I left a place, a month later I had an exit interview with 2 managers I worked with. they said the new guy they hired to replace me said my code quality was really good. nobody at that company cared about code quality, nobody ever looked, but the senior staff guy kept estimating tasks would take me x5 as long as they did and the CEO, who was an angry Italian guy who was never happy, memed I was perfect for a couple months once so I'd say code quality does make business happy, or at least the results of it which is the codebase is easier to work with and consequently meets business needs better -
To be fair and honest, many of the teams I worked with didn't care enough about code quality. As you rightly said, people mostly care whether it works and if the end user/client is happy
However, when something breaks especially in production, everyone jumps onto a bridge and tries to dissect the code as if they are the Fathers of Programming and spews whatever nonsense they come up with
This is how one of our junior devs solved a merge conflict
Your code is your karma 😅
How do I code....
Has anyone ever resumed at a new place and was impressed by the code inherited from their predecessor? If yes, did you see any need to communicate this information to the admin or the superiors he left behind?
For as long as I delved into code quality, I've taken great pride in my work and have been enthusiastic to show it off to anyone who cares to listen. I'm morbidly afraid of a colleague berating my work over something I didn't do correctly or don't know. But none of those I've worked with have that kind of time for pedagogy. The only thing I've witnessed them care about is how much your code breaks, to what extent your endpoints break, etc
Does this make code quality practically an overrated metric? All your fancy oop patterns and clever algorithms or business logic basically goes unnoticed. The business cares about output and your colleagues are more concerned about implementing their deliverables.
Is this just my experience or a more general situation of things?
question
code quality