Details
-
AboutJunior Backend Developer
-
LocationGermany
Joined devRant on 1/27/2018
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Just a friendly reminder that when you hear one or more of the following:
- underrepresented
- identity politics
- *phobia
- toxic *ity
- cis* (though "cisco" is fine)
- diversity
- culture appropriation
- passive-aggressive
- patriarchy
...and other bullshit, feel free to not talk to that person ever again. You'll miss nothing. Always remember that their goal is not equality but power to oppress whoever have a different worldview.
If you fear twitter backlash, fear not. Political shit comes and goes, but the inherent value of what you do is here to stay and means something at all times.
To anyone who wants to judge me because of this — remember, what you have read above comes from a bipolar transgender bisexual rape victim.38 -
Dont get me wrong I like C, but I've never seen so many different ways to do things where I cant even tell whats fucking happening in the snippet of code.11
-
Debugged a complex bug at 10 PM, drunk and eating potato wedges, while on the phone with another drunk co worker.
Woke up next morning and had no memory of the fix.7 -
I hate having to deal with our IT service desk. Every time it takes enormous energy to get to the right people and make them understand that no, you are not an idiot, but you actually have a technical issue.
Sure thing they do have a few competent nice folks there too I've gotten to know over time and they indeed have to deal with a ton of dumb non-tech savvy idiots on a daily basis. However, if my job title mentions "software" and "engineer" they should at least assume I'm an idiot in tech. Or something. Every single time I need to open a ticket, even for the simplest "add x to env y", I need to quadruple check that the subject line is moron-friendly because otherwise they would take every chance to respond "nah we can't do that", "that's not us", or "sry that's not allowed". And then I would need to respond, "yes you do:) your slightly more competent colleague just did this for us 2 weeks ago".
Now you might imagine this is on even another level when the problem is complex.
One of our internal apps has been failing because one of the internal APIs managed by a service desk team responds a 500 status code randomly but only when called with a specific internal account managed by another service desk team.
(when I say "managed by", that doesn't mean they maintain it, it just mean they are the only ones who would have access to change something)
Yesterday I spent over a fucking hour writing a super precise essay detailing the issue, proving a million times it's not on our end and that they need to fix it. Now here is an insight to what beautiful "IT service" our service desk provides:
1) ticket gets assigned to a "Connectivity Engineer" lady
2) few hours later she responds and asks me to give her the app and environment IDs and grant her access to those
(naturally everything in my email was ignored including these two IDs)
3) since the app needs to be in prod for the issue, I make a copy isolating the failing part and grant her access to the original "for reference" and the copy to play with
4) few hours later I get an email from the env that some guy called P made changes to the actual app, no changes to the copy
(maybe they immediately fixed the app even though I asked them to only touch the copy)
I also check the env and the live app had been shared with another 2 people giving them editing rights:)
5) another few hours pass and the lady responds that she had been chatting with P (no mention of who tf that guy is) and that P has a suggestion that might work and I should test it, "please see screen shot" for details:
These motherfuckers sent me a fucking screenshot of the env config file where "P has edited a few parameters" that might help. The screenshot had a 16 line part of the config json with a bunch of IDs and Base64 params which HE EDITED LOCALLY.
Again, because I needed a few iterations to realise what I've just witnessed:
These idiots modified some things in the main app (not the copy) for hours. Then came to the conclusion that the config needs some IDs and params updated. They downloaded the config json. Edited it locally. Did not fucking upload it back to the main or test app. Did not test it live. Did not CC in or direct the guy with changes to me. Did not send me the modified config file. Did not even paste the new IDs into the email. But TOOK A FUCKING SCREENSHOT OF THE MODIFIED FILE AND SENT THAT SHIT TO ME. And then had the audacity to ask me to test it when they had access to it and that's literally their fucking job.
I had to compare the fucking screenshot to the live config file and manually type in the changes.
And no, it still doesn't work. And Now I have to get back to them showing it still fails the same way but I just can't deal with these people. Fuck. Was hoping by the time I write it all down it'd be better, and it does feel a bit better, but I still need to get this app fixed. And I can only do it through these... monkeys. I just can't. Talking to these people drains my life energy... I'm just sad. -
soy eating developer: * change the name of his master branch to "main" *
Me: That's it, you ended racism!25 -
Indian Product Management community is the shittiest community for any professional domain.
Everyone is just focused on being a guru preaching shit to others when they themselves no nothing about the function or possess any significant skill(s) to perform at their job.
A bunch of bozos, themselves struggling to stay afloat, are saving others. Fucking hilarious.
What makes this worse is that the entire community is so inclined towards "cracking the interview" and landing a job.
Instead what they should be focusing on is teaching them younglings what the role is and how to develop the right skill set. More importantly why the role exist in the first place.
That way, they will automatically land a good gig and solve critical user problems.
No wonder, most products these days are bloated with garbage and PMs are only focused on engagement, retention, and more fancy buzzwords which make absolutely no sense.8 -
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
Java Wicket UI is the worst
I typed every line instead of copying & pasting4 -
text-align: center
Designer: “it’s not cantered, it’s 2px too much to the left”
Me: *does nothing* “what about now?”
Designer: “perfect”
Yup. This IS the Truman show.17 -
German bureaucracy, German tax offices, German pension insurance: of course we should feel very lucky and grateful for those institutions but currently, all they do is keep frustrating me with their kafkaesque bureaucracy. Don't they have anything more useful and productive to do than bother me with their bean counting?!20
-
Microsoft 2015:
Windows 10 is our last version.
.
.
Microsoft 2021:
Have you heard of the new Windows 11?8 -
Him/Her/It/She/They bullshit!!!
We all know what you are, we are not blind. Get over the public self jerking.22