alright... so thats how you parse JSON in javascript in 2019? i'm vomiting right now...

i'm getting headaches right now...

When you have to work with functions clearly no one gives a fuck about... because who needs documentation... like... 2 decades later!? Oh yeah sure it might change tomorrow...

Boss: so we've got to call an app to verify data in this project. But I've got no more info and I'm on holiday next week. Please contact GuyA next week.
Me: ok I guess?
*writes email to GuyA*
GuyB: GuyA is on holiday please hold the line
*1 week later*
GuyA: we need more time it's not ready yet
*2 weeks later?
Me: so?
GuyA: yeah it's ready here's the wsdl etc your client already has the password
*1 week later*
Me: yeah so I got the data but the api says my auth isn't working
GuyB: yeah your user isn't activated on the test system. I'm gonna forward that and come back at you
*1 week later*
GuyA: so we're going live in about 2 weeks hows testing going?
Me: well I'm still waiting for the response and activation
*suddenly it works*
Me: yeah so auth is working but i can't find any data. Is there any special test data?
GuyA: oh no there is NO test data on the test system. You need to wait for GuyB but he us not here today...
Me: are you fking kidding Me?????

... no response since then and it's been days....

And you guys are complaining about javascript being weird...

Who needs a rubber duck when you can have a rubber unicorn?! 🦄❤😍

When your rubber ducks keep drowning in the code you show them after a few minutes....

Copy-pasting 90% of our entities including logic and merging some - creating thousands of duplicated lines - and then creating views for those abnomalies just to speed up the ORM fetching which could have been done with a single join...

Took me some time to delete all of that fking shitty untested code full of bugs...

So when we started this project like 4 years ago... new to the framework, kickstarting lot's of forms with file uploads. Everything seemed to work fine, uploads and downloads worked..
First version of the project got deployed to prod and for weeks or so users have been registering and submitting stuff...

Only problem was: most files were overridden by consecutive uploads as our central upload lib stored files with the same name on disk (normally the ID of the db row was injected but most files were saved before the db row was - resulting in 0 IDs...)
Yeah so... that hurt :(

Boss: "we're going to take over a project from another company. that's what we know so far - any other questions?"
Me: "do we get the history (svn/git) or just current source? unit tests?"
Other company: "no history for you. no unit tests - app was only tested manually"
Me: *sigh* :'(

The moment, when you're coding a new feature on friday, your code somehow behaves weird in firefox... dev console shows unexpected behaviour and you're starting to think YOU ARE GOING CRAZY...

And then.. you find a fricking fucking Bug from over 12 YEARS AGO which STATUS IS "NEW"!

"Yes, the problem still persist with 2.0.0.11"
"This is indeed still an issue in version 3.6.3"
"Yes, it still exists in FF 4."
"Bug still present in Firefox 8."
"This ticket is almost 10 years old. Switch to Chrome."

CONGRATS FUCKING MOZILLA! THANK YOU! <3 <3

https://bugzilla.mozilla.org/show_b...

VMWare be like: "hey lemme just benchmark your primary host disk there... wait a sec..."

*selenium tests continue with 1 keystroke per seconds*
*slow clap*
i'm gonna cry in the corner of my room now.

When you think it can't get any worse you stumble across legacy what-the-actual-fuck-was-he-thinking-templates of your hopefully slowly-dying ex-coworker...

Thinking that HTML5 Application Cache would be a good idea for an offline app :(

Code comment rant of the day... fcking excel just cost me over half an hour to fix the fking formatting...

Code snippet of the day ❤️😍😍

When I fuck up I like to punish myself by playing Modern Talking in endless loop while fixing the code...
https://youtube.com/watch/...

a workarround a day keeps the clean code away

It happened to me too 🤤😱

The story of a normal release:
- tool gets tested "intensely" by 3 ppl quite a long time - everything works
- a major 2 days reserved as maintenance window for even more testing
- release starts
- first the admin panel of the server suddenly is not accessible anymore
- after some problems the tool is deployed
- suddenly servers are down and not pingable anymore - off on off on (provider has major problems .. good job)
- ppl start testing
- testers report lots and lots of new bugs - seems like the testing wasn't that intense after all...
- people start coming with lots of new requirements (oh we need to import those excels.. excels don't match our internal stuff.. )
- confusion over confusion
- getting pissed of a lot...
- quit caring and focus on another project
- profit

Fuck my life

Dat moment when, after some hard work, you can finally delete that abomination your predecessor left you as a present...

There is always that one guy.. who doesn't give a fuck about testing and thinks he's not responsible for them...
Le Guy: lemme just push ma new code maan
Jenkins: Unit Tests failed - pls fix
Le Guy to the one who cares about testing: hey fuck uu, ur stupid tests are failing... fix them its ur problem.
*sigh*

Debugging your JavaScript Code for 2 hours and trying out every imaginable solution because it works on the demo page but not your site... and then you find out the fking library had a bug and the Readme.md contained a cdn link to an old version and the demo page was up to date... arrgghh

Not my day...and I just wanted to play darksiders :/

fuck..fuck..FUCK..FUCK YOU MANTIS!!!
fuck you and your fucking invalid security token... fucking cunt...
yeah i love extracting my notes from POST data via the browser dev console cause you fucking delete it when hitting the back button...
THANKS FOR NOTHING

*hotfixing a project without unit tests in production*

Was just browsing through some old screenshots when suddenly...