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
-
@knuppelsmurf people don't even write for loops they just copy the code hundreds of times
-
@iSwimInTheC Yep, thats what happens. Optimized for money instead of readability or maintainability
-
Not having issues with committing regularly. When the part of the work is meaningful, you should commit it.
That's my take but not applying it everywhere.
But measuring by how much commits I make is ridiculous! There's script for that that commits to the repo automatically.
Garbage job has garbage metrics!
Got together with my old dev team (5) who all left the same company at the same time almost two years ago. (Thats a whole other story).
One of them told us he left and went to a new company that measured performance by the amount of commits a dev would to per day. Of course he didn't know that when he signed on.
Three months into the job he had a week where his first commit wasn't until a wednesday and he got called in by the manager to explain his lack of commits and how he was going to improve.
He quit on the spot. Had a new job in less than a week.
Other devs at the company were fixing typo's and just commiting them one at a time to create a lot of commits.
rant