My top reasons for you to not become a dev are:
- You don't like stress
- You like to overengineer but you want to "take your time"
- You hate bug-detective work
- You are impatient
- You want to overcome your virginity
- You are an overly social person

Probably a must read for QA!

I would love to see someone referencing this book in their application 😂

So we have this really annoying bug in our system that customers keep complaining about. I've explained in detail, multiple times, why the part they think is a bug is not a bug and the workaround they keep asking me to apply doesn't make sense, won't fix the issue, and won't even stick (the system will notice that the record they want me to delete has been removed and it will repopulate itself, by design).

I've told them what we need to do as an actual workaround (change a field on the record) and what we need to do to properly fix the bug (change the default value on the record and give proper controls to change this value through the UI). We've had this conversation at least three times now over a period of several months. There is a user story in the backlog to apply the actual fix, but it just keeps getting deprioritized because these people don't care about bug fixes, only new features, new projects, new new new, shiny shiny new.

Today another developer received yet another report of this bug, and offered the suggested workaround of deleting the record. The nontechnical manager pings everyone to let them know that the correct workaround is to delete the record and to thank the other developer for his amazing detective work. I ping the developer in a private channel to let him know why this workaround doesn't work, and he brushes it off, saying that it's not an issue in this case because nobody will ever try to access the record (which is what would trigger it being regenerated).

A couple hours later, we get a report from support that one of the deleted records has been regenerated, and people are complaining about it.

🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄

Finding a bug that wont trigger an error but will deliver incorrect results, but only in certain circumstances and has only come apparent after the site has bern live for 6 months.

You turn in to a detective trying to determine what triggered the wrong result, what the client changed/added/edited in the cms and work from there.

After much investigation it dawns on you, you then find the bit responsible in your shit code and fix it.

Then feel extremely elated at how cool you are, but no-one gives a shit.

Back to work.

That’s why I play bass guitar, do some cool licks on stage and its instant gratification, glad I have that... and devRant community.

maybe I should learn how to code properly as well.

which type are you ??

**Manager:** Hey, we've got a little hiccup in the production environment. I know it's Friday evening and you're probably daydreaming about pizza, but could you give it a peek?

**Type 1:** Man, this is like finding a needle in a haystack while wearing sunglasses at night. Might take me a few hours... or days. But hey, wish me luck and have an epic weekend!

**Type 2:** Eureka! Found the gremlin. It looks like XYZ person tried to be a bit too creative on commit number 2234324. Maybe they had too much caffeine? Anyway, could you have a chat with them? And oh, may your weekend be as smooth as a fresh jar of peanut butter.

**Type 3:** Detective mode activated! Found the sneaky bug. It was XYZ person's "masterpiece" in commit number 2234324. But fear not! I've put on my superhero cape and fixed it in commit number 345453345.

**Type 4:** This issue again? It's like a recurring bad dream about forgetting your pants! I've revamped the whole thing so we don't have to relive this nightmare. If someone tries to pull this off again, our CI/CD will roast them like a marshmallow over a campfire.

**Type 5:** Ta-da! Fixed the glitch, jazzed up the design, and sprinkled in some extra logging magic. Now, troubleshooting will be as easy as pie. Speaking of which, I've got time for a coffee and maybe a slice of pie before heading out. Cheers!
Type 6 **Gloomy**: Oh, the digital clouds have gathered again. This issue is like a never-ending rain on a Monday morning. I've peered into the abyss of our code, and it's... well, it's deep and dark. I'll need some time, a flashlight, and maybe a comforting blanket. If you don't hear from me in a few hours, send in a search party with some hot cocoa.

Alright, fellow DevRanters, gather 'round for a tale of woe and frustration. 🙄

I was knee-deep in my code, chasing down a bug that had me stumped for hours. I thought I was on the verge of a breakthrough, but then it happened—the code disappeared! Poof! Vanished into the digital abyss without a trace. 😱

I mean, it's one thing to wrestle with bugs and errors, but it's a whole new level of insanity when your code decides to pull a disappearing act on you. I scoured my directories, I even questioned my own sanity. But nope, my code was just playing hide and seek.

So, here I am, feeling like a detective in a coding noir thriller. 🕵️‍♂️ The hunt for the vanishing code continues, but I'm not giving up. This bug won't escape me! 💪

Has anyone else had their code pull a vanishing act when you needed it the most? Share your tales of coding mystery and mayhem below! 🕵️‍♀️👇

I Thought My Nest Egg Was Immobile Permanently! Overseas travel is glamorous until you are at 37,000 feet, trying to cope with different time zones, airport security queues, and dodgy Wi-Fi that cannot even open an email, never mind providing your future funding. I had stashed $890,000 of Bitcoin away as my retirement nest egg, a nest egg made of decades of hard work. That sense of security evaporated in thin air when I replaced my phone and forgot to update the two-factor authentication settings on my wallet.
Somewhere across the Atlantic, turbulence rattled the plane, but the real storm was the panic in my chest when I realized that I could not access my wallet. Tired and flustered, I arrived with the dread realization that my virtual fortune was now as out of reach as the stars in the sky. The frustration mounted as I hopscotched from airport to airport. Customer service droids, robot call centers, and half-baked solutions had me addressing vending machines instead of human beings. That was before a layover in Singapore where, bleary-eyed and clutching my third cup of coffee, I chanced upon a travel vlogger's YouTube video raving about Tech Cyber Force Recovery.
With nothing to lose, I called. From the first message itself, it was different. These were actual people, smart, caring, and willing to work around my insane schedule. They scheduled calls during my layovers and adjusted to the chaos of traveling overseas like pros.
Their engineers delved deep into my issue, analyzing time-stamped authentication records. It was as if watching a digital detective movie, minus the stakes: my future. For over 14 hair-on-end days, they weathered the 2FA bug like pilots navigating through turbulence. Then the message came: Access restored. All the Bitcoins were present. I almost cried into my airport ramen. That weight was lifted from my shoulders, and the feeling that all those years of careful planning weren't wasted, was indescribable.

telegram +1 561 726 36 97
WhatsApp +1 561 726 36 97