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
-
A bug is a reference.
A reference for the VCS, for tracking time, for anything...
This "just pop it in this ticket i was already working on" would be in a database a unique constraint violation for obvious reasons.
I want to do a lot of gruesome devs ignoring these rules.
Nothing makes more fun than trying to decipher what has really happened in a ticket that became a bukkake gangbang porn because of lazy devs.
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.
Just finished a defect fix, and turns out there's another unrelated but harder bug in the codebase. We are in the last few days of the release.
I told my tech leads that it was an unrelated problem and showed them in detail. I told them I was starting work on it now, but there should probably be a new defect entered for it.
They actually said for me to piggyback the old defect and let this go under the radar. Actually laughed it off like it was no big deal. Like WTF! I don't think its very unreasonable for devs to want separate defects for separate bugs. They're worried about analytics and shit, but I'm the one left holding the rug, looking like I spent a week on a trivial defect.
rant
management
defects