I know I should not be naming names but WalmartLabs Hackfest 2016 was actually a fuckfest. It was supposed to be a 14 day online hackathon followed by an offline event for top teams. I got in top 6 among the 4350 participants.

In the offline event:

1. They didn't allow us to give live demo of the project. Instead they asked us to present a ppt. The HR idiot even asked me to take screenshots of my cli app and put that in instead.

2. 4 out of the 6 teams actually presented their startup products. It was supposed to be a 14 day hackathon for fucks sake. How can you present some shit that you were working on for the last 1.5 years! This one team literally had "Copyright 2015" mentioned on their product page. This another team had 100,000+ downloads on his app already. Of course Walmart didn't care about it. They didn't listen to my complaint. I wish I had created a scene there :( Another team was boasting on stage about how they got selected in the FB startup accelerator and how they won 3 more hackathon (evidently equally shit) using their shit. This was met with praises from the judges.

3. The results were declared after 3 fucking months! Don't organize this shit next time if you don't have any interest, bitch.

4. The code was supposedly never checked. Other teams kept working on their shit for the 3 months in between. In the live presentation, this guy even had photoshopped a feature which wasn't even present there (and he boasted about it later on).

5. Hackerearth (platform for the hackathon) was equally incompetent in this mishap of a hackathon. One of the teams which won had one the previous hackathon (Pluralsight hackathon) as well on Hackerearth using the same fucking product. What pieces of shit >.<

6. The hackathon was supposed to be tech based and all the categories were like that. Instead the teams presented business models and shit like that and judges focused more on that. They were not concerned about the technical aspects at all. The more noise you made, the more lies you told, the better chance you had to win it.

7. They were supposed to give prizes in 4 categories but silently reduced it to 3 on the event day. They still publicised it as 4 prizes until now.

All of the above is true and I am willing to testify if someone asks for it. I am going to write a nice blog post about it and post it to their idiot HR.

Hackathon: WalmartLabs Hackfest 2016
Team name: psyduck (which is just me)

Sorry for being too salty but it was indeed a fuckfest.

I have one! Once upon a time (about a year ago) my mom went online shopping on her own. Her husband was out of town and so she had no assistance. At about 10.30 pm she called me, freaking the fuck out that she entered her credit card details on a sketchy site and they charged her for more than she ordered. She was in hysterics, didn't know what to do. Superwoman to the rescue, I tell her to go and deactivate her card and jump on a train back home (she was crying on the phone she was so scared, couldn't just leave it until morning) fast forward an hour, I'm in my hometown, she picks me up and we head home to check out the situation, and... She had just received the email invoice twice. They hadn't charged her twice, just some email mishap made the email appear twice and she never thought to check her bank account before summoning me home 🙄😂 we laughed for a while and I got a home cooked meal so it's all good but Jesus christ mom. What would you honestly do without dad?

Okay so I have been a consumer of devRant for a while now but never posted anything. This is my first.

So yesterday I modified an existing method(some very minor changes!!). Today after coming to the office I see that I have comments from Sonarqube stating
"Reduce cognitive complexity from ** to 15.

I get that it is a good measure to maintain readability but this refactoring is not part of my change at all and any mishap can break the whole code base!!!.

My code even won't build because of this company restriction that there should not be any issues from Sonarqube.

I really want to bash my head against the wall right now.

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!

Okay, I'm feeling a bit better now.
How to stop being a lil bitch? Why does it seem like everyone got the "don't give a shit" patch except me? I'm working hard on getting my shit together, I've made MASSIVE progress, but everytime I'm feeling good and confident and ready to take the world head-on, I just kinda crumble again with the slightest mishap. This needs to stop. I'm really trying SO hard not to snap. Fucking hell, being aware of all this makes it even worse! It's like I'm two people, one is a downer and REALLY good in draining my brain power, the other is the guy who's typing this and knows that life shouldn't be taken this seriously, but doesn't stay in the cockpit for too long. I'm extremely tired and mad. I just fucking hate this.

A random story that just popped back into my head while reading another rant:

Long ago, we developed our own webmail platform at the request of clients. After it was finished, it was never updated and eventually turned into an outdated insecure steaming pile of crap. Up until ~2015, it looked like the first iteration of AOL Mail from the 1990s (and it functioned as such too.) Years, we decided to sunset the platform, and allotted 6-months or so to transition all the active users off the platform and over to an alternative email provider. We had to call each client multiple times and send multiple emails with a deadline detailing when the service would be shut down, and we'd explain that if they didn't transition over to a new service and transfer all their emails before that date, then the emails would be lost forever. Lo and behold, a handful of clients ignored our repeated contact attempts, and we shut down their email service (as we told them that we would.) Of course, they called screaming and panicking "OUR EMAIL IS DOWN OUR EMAIL IS DOWN WE'RE LOSING MONEY FIX IT NOW!!!!," and we told them "We attempted to contact you multiple times, and you neglected to return our numerous calls or emails. We're happy to help you transition your old email addresses to this new provider, but because you neglected to follow the cushy deadline we provided you, all of your emails are gone."

Of course, they denied having ever received our calls/emails, and we'd have to provide them with our outgoing call recordings to prove that we did in fact contact them multiple times. Then they'd blame the mishap on their secretary, who would blame it on the intern, who would blame it on the IT guy, who would blame it on the janitor, and so on and so forth.

Moral of the story: always keep outgoing call recordings when you're sunsetting a product.

This is something that I hadn't done or that directly impacted me, but that had an effect in my life several years after it happened.
It's one of those stories that you think "this only happens to others", and then someday you're the "others".

So when I was born, I was, naturally, registered on the health care system. My parents chose an uncommon name for me (uncommon in my country) so I think I wasn't registered by the time of my birth, but 4 months later when all the bureaucratic crap came to an end (long story short, the guy that was there when it started died and my parents had to wait 4 months for another person to be appointed). So, when my parents finally went to register me, apparently, for some reason, the computer took my name and assumed it was a male name. As I've said, my name is uncommon in my country, there're probably 3 or 4 people with the same name here in Portugal.
Why did the computer assume it was a male name AND why didn't nobody check that? Since my parents had to ask to government entities to let them name me that name, I'm assuming it wasn't in their db. So why did it assume male? Was it purposely programmed that, by default, all "newly-registered" names were to be male? Was it random? Who the hell knows.
And how did nobody check that, every time I went to take vaccines? I don't think anyone told my mom that everytime we went there that the data was wrong, otherwise the situation wouldn't have lasted for 14 years.
We only knew about that mishap when it was time I had to take vaccines specifically for women and that I wasn't being noticed of it even though a friend 1y younger than me had already taken hers.

I find this story amusing but now that I started thinking about how it came to life (no pun intended) I'm actually a bit pissed off about how they didn't think of uncommon names and that how that could affect their registry in the system. They could have - IDK - placed "undefined" in that field so that it would caught the register's attention.
Moral of the story: don't assume stuff :v

Arg. I messed up bad today. Updated 17k records in database by mistake and had to rollback and apologize...

I won't rush on a task for rest of the day

Just got into a chown mishap, all that took was a typo space between / and rest of the path, now i can't sudo anymore 😭

What is your best sudo story?

Service Controllers book us into the power stations and mines.

Was going to check a new client's current system and develop them a new one.

Service controllers booked the PM but not me.

Oh well, now there's a dev sitting outside a power station like an arsehole coding on his android because he has literally an hour or two to waste.

They do it out of spite, not out of mishap.

Spent like all week working on a feature set in a web app, finally got to a point where i thought it was functioning well, ran tests, tests passed.

I was exhausted but happy. All along i have been pushing to my GitLab server. I save my commits and even though exhausted, i am happy as i go to bed.

I wake up, run some errands and my business partner says, eh! Can i come see that new feature set you built, sure, i will be home soon.

I was at the barbershop, trying to look like a human being again. I get home boot my computer and i scream.....

Arrrrrrrrrrrrrrgh

I check GitLab, i check my Git Log and i start to sweat, i was in the air conditioner but it felt like someone turned the heat up.

Git log shows my last commit was 2 days ago, my app is at the state it was 2 days ago and i can't frigging find all i have built.

I need to show this to the client, have no idea what to do now, so stressful. My partner say, you know what, just watch a movie. You built it before, you will do it again.

This happened to him a while ago and i gave him similar advice, it felt wicked hearing it now.

Anyways, i have to build that ish all over again, i do know i wasn't dreaming about having built it. I asked my wife and she said, i did, i was always working. So confusing.

Anyone experienced this before, i have no idea how to find my code.

Help Meeeeeeeeeeeeeeeeeeeee

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.