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
-
If we compare our work to plumbing.
It's mostly under the floors, in the walls, unseen by those who use it. They make sure things move around in the pipes. If a plumber did not take pride in his work they may not do a great job in the connections, leave mess under the floorboards, etc. They will leave this for the next plumber.
Don't leave a mess for the next person. Take pride in your work. -
What you are describing is called micromanagement, and it only creates problems.
For me, writing clean code is a matter of my pride. I take that effort because i like my code to have that footmark positively, that someone should recognize that this must have been written by this guy since it is properly indented and etc. Infact like someone else said above, your pride should double if the company doesnt enforce your practices, but you still do it. -
@Fast-Nop this!
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
What was your most disappointing moment as a software developer?
Mine was the realization that when you're working for someone, all they want to see is the final product. The people paying you don't give a shit whether you put your braces on a new line, your domain model doesn't call a database directly or if you're applying the best practices. Your teammates do, but the people paying you don't.
People hire you to get the job done, and that job is to solve a problem for someone. Not in the way that's best for you, but in the most effective way for them. Since I realized this, I lost some pride in my work.
question
career
rant
disappointment
software development