121

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...

Comments
  • 1
    Lol, 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.
  • 3
    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...."
  • 0
    What 3 characters? What language?
  • 0
    7 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.
Add Comment