Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Managers won’t understand the importance of clean code.
They only understand the importance of bug free and low-maintenance products.
Which happen to be written with clean code.
Sounds like you need to be an entrepreneur!!!
Fast-Nop3225230dUnpopular opinion: they're somewhat right. Shipping is your most important product feature. Long-term benefits of clean code don't matter if a competitor occupies the market first.
Customers complain about bugs and shit, but by and large, they have voted with their money to favour quick and dirty over quality.
That's why safety relevant domains have regulations where you need to demonstrate process compliance in order to be able to ship. The point is to prevent a race to the bottom.
Devnergy614730dBusiness is business. Don't care about clean code as long as you ship fast and it works. Optimization, scalability, clean code and bug fixing will come on later.
All that matters is that you get paid. If the tech debt piles up then they will need to pay the developer.
Believe me. I have worked on lots of internal system and only few of it have clean code. Mostly are just grunt work.
You're primary objective is to make money for the company. That might involve clean code or crappy code depending on the situation
mundo0348461dRemember, that is what agile is for: release fast, fix later.
The problem with most organizations: they forget the part about fixing later and documentation, so they only release and increase the tech debt.
So it is all about balance.