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
Related Rants
Found this ancient, forgotten task that was basically a QOL improvement.
Given that the feature would shorten the time of testing from some 10-15 minutes to 2, I left a comment mentioning that it would be immensely helpful.
!too long after, the report started seeing some traffic && the feature got actually implemented.
Checked the implementation as soon as I could.
- Speedup worked well regardless of platform.
- Slowdown /* which was never actually mentioned in the task as it wasn't crucial */ was also implemented, but the mobile phones were omitted, since the implementation would be too complex for the time allowed for the feature implementation. I was perfectly fine w/ it, as this wasn't actually necessary for those.
I left a proper comment, thanking for the feature implementation.
...then the lead tester chimes in, bitching about the lack of implementation of the slowdown on mobiles.
Got the same explanation as I mentioned earlier - too complex for the time allowed. Plus, the feature had other platforms in mind. Having it working on mobiles was just gravy.
Good call, lead, now - ask for another favor.
I'm sure it'll go well, since you can't be satisfied w/ getting what you need. You need that special pampering, too.
/s
rant
bad leadership
debug
retards
qa
test monkeys
testers
feature