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
-
@Dollique probably useless comments like
// increment i with 1
i++;
Instead of explaining why i is incremented. I cant imagine someone having such non descriptive commits making good comments. -
"late night changes" and "laste changes" should be an insta-firing unless ashish is working on The Sims 5 "Late Night". There's already a field for the time when the commit was made, so if that's all they mean, the commit messages might as well be blank.
"After testing"??? What the fuck? "Token things fixed" is one of the better commit messages and that's pretty pathetic. What token? -
I'm not done either -- "last changes done" and yet there's a commit after that? Liar. Hang him.
I hope for your sake that this is some shitty outsourcer that you can more easily politick out of your workplace and not a direct coworker. -
@HollowKitty "laste changes" is last changes I assumed, you though that was late changes?
But Ive heard he quit, so no need to fire anyone. -
A lot of my commit messages are shit, but then we squash changes when we PR and have a better message at that point, although the PR will be based on the work item which has the full description anyway.
-
And I don't think shitty commit messages count if they're personal projects or projects you do with your drinking buddies. I'm assuming this is a Real Project of some kind, either for work or serious OSS.
-
devpit4716y“Something done”
This kid is going places.
Honestly though, on personal projects, this is exactly what my commit messages look like âšī¸ -
What if you do :
$git commit -m "No commit message"
instead of :
$git commit --allow-empty-message -m " " -
@HollowKitty This is a project in production. Our recruitment team called him a promising candidate while hiring. I wish I could fire him!
-
I do. Because I'm the only one in my fucked up team who writes comments and I'm the only one who reads them too.
-
Funny ...not really
The good thing is that this is very easy to train people; not everyone was born with their perfect commit messaged
Instead of “firing” or just passive aggressively reporting it on devRant, please teach them how to write better commit messages, amend or squash them etc
This is something that your team should have a coherent guide/code style on so it’s easy to search for in the future
Just my humbled opinion -
@rusty-hacker Any guesses why this is called dev rant?
You do have a point there, not everyone has the innate sense of making things easy for fellow developers. -
@rusty-hacker No dude, but specifically why posts here are called rants. I look at this as a place to rant about things which you cannot in actual world. Obviously I asked him politely to commit better messages.
Ps. I edited my comment. You might want to read.
Related Rants
Who the fuck commits with such comments?
rant
git
stupidcolleague
commit