You recognize who I am speaking about proper? It is that entity/being that makes positive that your code doesn’t operate the identical manner in your native, improvement and manufacturing environments. Properly, he is a gnome and known as Bob Stinkycode.
I think about he appears to be like one thing like this after he is messed with you:
Let’s examine an instance: you have been engaged on a function for some time, you have examined and every part works completely. Then the code is deployed to an actual setting and a few a part of the function that labored and had been examined extensively earlier than doesn’t work. You examine and double examine and crap, theoretically it ought to work, you’ll be able to’t clarify why the hell it is failing… and naturally your code is ideal and the one posible rationalization is that the Bob has carried out it once more, he’s messing together with your code…
It is a exhausting downside to resolve, as Bob decides when to let the code work and when to mess with it. For those who search for him you’ll not discover him, he has 1000s of traces of code, 100s of folders and 10s of companies and processes to cover…
The one resolution is to just accept it, and let him get drained, as soon as he get’s bored your code will work once more… Do not waste your time making an attempt to resolve it xD
One other instance: A consumer studies a bug, we have now screenshots, studies in Sentry, and once we strive replicating it, it by no means occurs once more. That is additionally Bob’s fault.
Jokes apart, I feel Bob is only a metaphor of the ego and/or delight of a developer. Typically it is simpler to swallow, than to just accept your code has flaws. I am responsible of this, however attempt to at all times inform myself that bob is simply uncertainty and ignorance a few bug.
That is it for me, hope you loved the fast learn. Do you could have expertise with Bob Stinkycode? How do you name him?
