Oopsie 🙄

Interviewer: Can you explain OOP to a six year old?

Applicant: About the 6yo, are you referring to a client or you?

🤦‍♂️🤦‍♂️🤦‍♂️

This is how I handle bad requests.

Was literally about to release a test version of the url shortener when I did some more testing and found some security vulnerabilities, let's fix those first tomorrow 😅

💙💛 oopsie

Hey Root, remember that super high-priority ticket that we ignored for five months before demanding you rewrite it a specific way in one day?

Yeah, the new approach we made you use broke the expected usecases, and now the page is completely useless to the support team and they're freaking out. Drop everything you're doing and go fix it! Code-complete for this release is tonight! -- This right after "impacting our business flow" while being collapsed on the fucking floor.

Jesus FUCKING christ, what the fuck is wrong with these people?

If I dropped the ball on a high-priority ticket for two weeks, I'd get fired, let alone for five fucking months.

If I was a manager and demanded a one-day rewrite I can only imagine the amount of chewing out I'd receive, especially on something high-priority.

And let's not forget product ownership: imagine if I screwed up feature planning for someone so badly I made them break a support tool in production. I'd never hear the end of it.

Fucking double standards.

And while I'm at it. Some of the code I've seen in this codebase is awful. Uncommented spaghetti, or an unreadable mess with single-letter variables, super-tightly coupled modules so updates are nearly impossible, typos in freaking constants added across sixty+ files, obviously-incorrect comments, ... . I'll have to start posting snippets to show them off. But could I get away with any of it? ha. Hell no. My code must be absolutely perfect. I hear about any and every flaw, doesn't matter how minor, and nothing can go out until everything is just so.

Hell, I even hear about flaws in other peoples' code during my code reviews. Why? Because I should have fixed it, that's why. But if I do, I get yelled at for "muddying the waters."

Just. JESUS FUCKING CHRIST.

It's like playing a shell game where no matter which shell I pick (or point to their goddamn sleeve where they're clearly hiding it), I get insulted for being so consistently useless, and god damn, how can I never find the fucking pea or follow the damned rules? I'm so terrible and this is why "nobody trusts me." Fuck you.

I'll tell you why I can't find your damned pea: IT'S RATTLING INSIDE YOUR FUCKING HEADS, you ASSHOLE FUCKING IMBECILES.

That's right: one pea among the lot of them.

goddamn I am fucking pissed off.

Just found a humongous bug in production. The customer relation number, which should have been unique was shared by ten customers.
So instead of 400,000 relation numbers we only had 40,000 unique numbers.

The system is live for 3 weeks now, and we just fixed it on a friday at 5:30PM

If we had found out a week later every customer would have gotten a plastic card with the wrong number, because the cards will be printed in four days...

> I didn't brought any condoms
> Just pull out Anon, we'll buy some later

You could say I went straight to production and now I'm considered "legacy"

Going through the list of projects:

Nope...

Absolutely nope ...

Burn it Nope.

Nononono.

Don't touch this.

It's so fluffy, I will die.

Wow. If this was a fungus, it could talk by now.

What the hell was that...?

Uh. Ehm. So old it's already done. Oopsie.

...

2 hours later...

...

Well. Backlog is sorted.

Conclusion: I just don't work anymore.

-.

I think it's time to add a field "pain level" to Jira.

And I doubt that the backlog contains any ticket less than pain level 8 / 10. -.-

But yey. I ordered beer.

Always quadruplecheck your qoutes kids. Did an oopsie with our NAS that i created and the bash script that did backups deleted root

I once made an oopsie in an API for a logistics provider (one of the biggest in Germany...).

To understand the oopsie...

Based on input data a string must be created containing several hex / string / formatted values.

Think of ...

$return .= sprintf("%02X", ...)

I think there were around 15 to 20 lines, although more complicated.

The bug happened because I had a brainfart.

What was previously one line with... Many many many many variables, I had to split into multiple lines since internal stuff changed and it was impossible to change this oneliner of hell with >50 formatting codes.

Of course we didn't test everything.
XD

What we didn't test was - funnily enough - wether the casting was correct in all cases.

I misplaced a formatting code.

And we had a major brainfart because we tested integer, but not double / float values....

We sent for a long time packages much cheaper than allowed (took thw logistics provider nearly 3-4 months to realize this :) ).

Spot the difference:

@highlight
print sprintf("%01.2s", $money).PHP_EOL;

print sprintf("%01.2f", $money).PHP_EOL;

I fucking hate environnement configuration so much that I prefer to debug 8 hours straight rather than lose my time and shit for 2 hours on idiotic configuration problems and jump from page to page like a dumbass

"Hey you want that module, download it here !"
"Oopsie, starting from X version of the JDK/JRE this is no longer standalone and directly embedded in"
"Can't find it ? Well I just forgot to tell you that starting from Y version this is COMPLETELY removed from what I just told you to search in and now in another standalone package"
"So now you added your package as dependency for you project, your IDE detects everything well but can't run your code ? That's because it doesn't work anyway, use another method found on the dedicated Github issue which makes little sense and that you have to apply everytime, then sacrifice your inexistent newborn to connect to the 9th circle of hell where Java resides so everything will work"

I knew I couldn't get away using fucking Java and JavaFX

5k lines of code and some long days in and it turns out UI and I (backend) had an oopsie in our communication so it was all for nothing. Back to 0😖

My new passion in life is to spend a whole morning trying to figure out why I can't create a thumbnail with node-imagemagick, only to discover that I forgot an 's' to the output directory.

FUCK. ME.

MFW I worked longer than 8 hours because of a weird bug that turned out to be caused by lack of typing in a third-party library. Was supposed to be a number but I was giving it a string 🤦‍♀️Need more sleep.

The funniest part is the library was written in Typescript. HmmMMMMmm...

Throw a `parseInt` or warning for wrong type in there for me, fellow devs! Save consumers of your library a headache!!

I did an oopsie.

I accidentally accepted a job/project through a friend and realized later that I would have to use wordpress which I have absolutely 0 experience with.
The thing is it's a website for swimming club and at first I was like sure let me just recycle this old school project. But then I've realized they are gonna need something dynamic (to update their schedules etc.) and that they will need something user friendly.
Later I found out that their previous website uses wordpress and that they like it and wanna keep that.
So here I am, thinking if I should just back off or try the dangerous way of learning it while creating the website (it probably wouldn't be worth the money since they won't pay much).
Honestly, how did I even get to this point.

I became familiar with basics after my mom bought a PC and disc with software which included FirstPage. She wasn't *that* angry getting a $100 receipt for the month of Internet I trafficked - oopsie, thatta large price, even after inflation.

Bit of a stupid oopsie I had today that someone might appreciate.

We’re working on a microservice project in Spring Boot, running in a docker swarm. Past few days I get a Spring Cloud config server going in separate stack, create an overlay network, and get CI deployments to use the right profiles etc. It’s looking great, and the first component is working spectacularly.

Now just to do the other 6. Move config files to the Git repo, tweak CI, all the other faffing and hoohas; and deploy. Health checks keep failing, the containers are murdering themselves and resurrecting ad infinitum. They’re doing this so quickly that by the time I get the container ID to exec in and curl health, it’s no longer running. Cue frustration, increased caffeine and nicotine consumption; my sanity is slipping.

No errors in the logs, because from experience the Cloud Config errors ar at debug level. Whhhyyyy?? Some time later (way longer than it should have been) I realize I had never actually included the Spring Cloud Config starter. Boot 101, get your starter!
Since config client is just additional setup in properties.yml, there’s no issue of the dep isn’t there, it just doesn’t try to get the config.

The containers are still unhealthy, I can hear them screaming. But now at least it’s about something else...