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
Search - "problem is between chair and keyboard"
-
When you've had a long ass 14 hour day and you're getting nowhere with a problem so you finally accept its time to go to bed...
You lie there for 45 minutes doing nothing but thinking up awesome solutions to the problem you went to bed over....4 -
Will try to keep that one short.
So we have internal system for active QR codes, nothing really special, as you could imagine. I wrote it when I was beginner but it works and is heavly battle-tested.
Today JBOG (just bunch of guys) come in and try to BS me that something is showing up wrongly for someone.
I check things up, nothing looks out of the order, I go there, everything looks fine too, and they say that yeah but this printed certificate's QR dosen't match what some QR with this name is within the system...
Short invastigation. TL;DR, someone who was rendering/printing these certificates had bunch of these codes with names like
30. ABC
31. ABC
32. ABC
And just casually missclicked...
And to come to that conclusion they need fucking backend dev to confirm that code last 1.5 year didnt magically change, and to destroy their magical belief that it's code's fault.
No, someone fucking missclicked. Whole magic. Usually problem is between chair and keyboard, get fucking used to it. Now, having that settled, let me get back to my work. -
I've just received an urgent bug report email saying something like:
Stop sending [item] to destination. This should have been taken care of in the initial work, but we forgot to say so.
... The work they requested was that [item] gets sent to destination if the user checks a checkbox. If I wasn't supposed to build this, then what did they want me to build in the first place?!1 -
Customer Service(cs): clients complaining our site crashes on their computer
Support: they dont have enough resources, its their computer
CS: customers still complaining, how do we fix this?
Support: tell them to get a better computer
CS: lets borrow their information and see whats going on
Support: reluctantly moves customer data over
CS: I dont see anything wrong here. It works just fine
Support: ... ... ...