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
-
JsonC1136278yLol, this literally happened to me the other day. I did learn about a couple of new method calls in the process however, so I don't mind so much.
-
That's better than an average day for me:
1. Start working on feature
2. Customer IM - they do not understand a process; must explain
3. Tries to get back to feature
4. Customer call - new group coming on board, need meeting to set them up and draw them a roadmap
5. Tries to get back to feature
6. Impromptu mtg - need to give a demo to potential new customers
7. Tries to get back to feature
8. Trouble ticket - user is stuck and world is crashing; need to help them immediately
9. Customer stuff
10. Customer stuff
......
22. Customer stuff
*end of day*
Me: "Well, I read the specifications of that feature, maybe I can actually start working on it tomorrow...." -
Fabian10137y7 hours? It was a week for me last time. And it was 2 changed characters, I think. But maybe not, because the wrong result changed into other wrong results while trying to fix it.
Related Rants
-
ObsidianBlk2Me (6yo): Whatcha doing? Dad: Programming. Me: ??? Dad: If I type this on the screen and hit this key *color a...
-
luckyc7And now i'm feeling guilty every time i call new Guid().
-
silly-symphony9I was a freshman in highschool when I encountered the book entitled "Teach Yourself Visual Basic 6 in 21 Days"...
An average day:
1. Start working on feature
2. Finish feature
3. Feature doesn't work
4. Spend 7 hours refactoring and fixing imaginary bugs
5. Add the 3 characters that were missing
6. Laugh and cry, laugh and cry...
undefined
wk49