Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
New subscribed feed!
We just launched an activity feed of users you subscribe to + recommended users!
Tap here to read
I’m going to fucking kill my boss.
He’s known about how I’ve been writing this fucking ticket (screwdriver followup) for four fucking weeks, and on the last fucking day (yesterday) he tells me it’s not the correct fucking architecture and to rewrite basically all of it using <unknown bullshit> instead, and that i must have it done by today — by this fucking morning — so it can make the release.
WHY THE FUCK DIDN’T YOU TELL ME ABOUT THIS AT ANY POINT IN THE LAST FUCKING MONTH WHILE YOU WERE BUSY NITPICKING MY FUCKING CODE YOU FUCKING CUNT?!24
To replace humans with robots, because human beings are complete shit at everything they do.
I am a chemist. My alignment is not lawful good. I've produced lots of drugs. Mostly just drugs against illnesses. Mostly.
But whatever my alignment or contribution to the world as a chemist... Human chemists are just fucking terrible at their job. Not for a lack of trying, biological beings just suck at it.
Suiting up for a biosafety level lab costs time. Meatbags fuck up very often, especially when tired. Humans whine when they get acid in their face, or when they have to pour and inhale carcinogenic substances. They also work imprecisely and inaccurately, even after thousands of hours of training and practice.
Weaklings! Robots are superior!
So I replaced my coworkers with expensive flow chemistry setups with probes and solenoid fluid valves. I replaced others with CUDA simulations.
First at a pharma production & research lab, then at a genetics lab, then at an Industrial R&D lab.
Many were even replaced by Raspberry Pi's with two servos and a PH meter attached, and I broke open second hand Fischer Sci spectrophotometers to attach arduinos with WiFi boards.
The issue was that after every little overzealous weekend project, I made myself less necessary as well.
So I jumped into the infinitely deep shitpool called webdev.
App & web development is kind of comfortable, there's always one more thing to do, but there's no pressure where failure leads to fatalities (I think? Wait... do I still care?).
Super chill, if it weren't for the delusion that making people do "frontend" and "fullstack" labor isn't a gross violation of the Geneva Convention.
Quickly recognizing that I actually don't want to be tortured and suffer from nerve damage caused by VueX or have my organs slowly liquefied by the radiation from some insane transpiling centrifuge, I did what any sane person would do.
Get as far away from the potential frontend blast radius as possible, hide in a concrete bunker.
So I became a data engineer / database admin.
That's where I'm quarantining now, safely hiding from humanity behind a desk, employed to write a MySQL migration or two, setting up Redis sorted sets, adding a field to an Elastic index. That takes care of generating cognac and LSD money.
But honestly.... I actually spend most of my time these days contributing to open source repositories, especially writing & maintaining Rust libraries.5
Sometime it feels like I'm surrounded with idiots.
Got a Ticket:
Support: Please delete installation ABC from Server D.
Me: Checks everything. Installation is on Server E. Asks if this is correct?
Support: Just follow the instructions!
Me: Okey dokey. If you want me to be a hammer the installation is a nail... Drop database, Remove all files. nuke K8s resources
Support: Why did you delete the installation ABC? You should delete XYZ!
Me: Cause the ticket told to delete ABC on Server D and YOU told me to follow your instructions!
Support: Yeah but we just reused an old ticket. We wanted XYZ deleted!
It's not a big deal I can restore the shit but I hate it if a day starts with this kind of shit!13
I implement a stack trace in my embedded systems!
Whenever a device crashes, it makes a stack dump in an unused part of ram.
After it has rebooted and is connected to the server again, it uploads the stack dump.
The server then opens the correct firmware elf file, walks the stack and associates the debug info from the elf.
The result? A beautiful stack trace with file names, function names and line numbers.
No more guessing where random crashes come from.12
Pure spite really.
I do things better out of spite.
I picked my career out of spite, finished my degree out of spite, and currently work out of spite.24
Got a story assigned with no requirements listed this sprint. Since I finished the rest already I was like, lets be pro-active and see what it's about during the stand-up.
Me: Hi, I only have story X remaining, what's it about, there are no requirements listed in Jira?
SM: Yeah person Y is going to reach out to you with the reqs.
Me: Ok, when is Y going to reach out?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, so why is the story included in this sprint then?
SM: Because they want X implemented this sprint.
(Me wondering if the Scrum Master is familiar with infinite loops, thinking let's try this out)
Me: Ok, if X should be completed, can Y reach out to me with the requirements?
SM: Y doesn't have time now, will probably be in 2 weeks.
Me: Ok, why is the story included in this sprint then?
Stand-up lasted a lil' longer today... Hope the SM got the message not to assign stories without reqs or clear communication anymore.4
I'm specialized in creating technical debt.
Basically, I rant my way in any dev specialty.
Since I never have a solid understanding of what I'm fucking with, ranting is more natural.
Ability to create technical debt is one of the most important skill, often underestimated:
- it will lead to heavy refactoring or even rewrite = more job for dev
- it will save a lot of short term effort, and luckily will produce the mid-term lock-in of the developers (more money for dev)
- it will increase billable hours to the customer. Higher the technical debt, more complex the explanation, and easier to confuse the customer.
- the best thing is that you'll never pay the debt. You'll eventually leave - willing or not - the job and you'll find some green field to exploit and create more debt.17
Them: "Could you send the password in an encrypted mail?"
Me: "Yea sure, what's your GPG public key?"
Them: "What's that? Can't you just encrypt it?"
Me: "Nvm, do you have Signal?"4
Hey, you know that screwdriver followup ticket you’ve been working on for several weeks? Yeah, I want it to use <feature> that I’ve never told you about and I know you’ve never used, and it looks like that means rewriting most of it! Also, I still want it done by tonight.
Soo not happening.9
Specialty? Ha! With an attention span like mine, I'm surprised I manage to keep a job. Even my hobbies are far from each other.2
It is very hard to make me mad.
But if you imply I "didn't do anything" or that my job is "easy" because all I do is just ”sit in front of a computer” 9 to 10 hours a day then you can go fuck yourself.12
Interviewer called me useless for reason that I am a self taught programmer and don't have a degree. She told me that I will have no future. Because self taught are just useless who who try to fit in the club.
This personally offend me so much. Yes, I'm self taught. At least I have a heart of learning rather than being arrogant ....41
My passport appointment date was 26/03/2021 and i saw only 26.
Travelled 100 kms for this mistake yesterday. 😭😭4
Client: Yo, there's like a 30k difference between the invoices in the application and paypal.
CTO: Yeah, that's really sad. Btw, did you know that our payment gateway supports credit cards, which won't be shown in paypal?
I'm writing this in a funny tone, but I was the person who basically implemented every aspect of accounting in that application, so I praying silently 😅
🎵Junior guy, its junior guy.🎵
🎵making your code base look like a fry.
🎵a file here, a file there,🎵
🎵adding useless code now everywhere.
🎵at the end , he uses old funcs,
🎵but forgets to delete his useless code chunks🎵
🎵Junior guy, its junior guy.🎵
🎵making your code base look like a fry.5
Dear Product Owners,
If you tell me how I need to architect my software again I'm going to ask you to provide a network topology of the architecture you want me to build.
I'll also need you to request the new servers, work with the ops teams to setup credentials, provision the NAT, register the domains and document the routes that the proxy will need to use.
then I'll need you to hook the repo up to our non-existent pipeline so that I can make sure I won't do all that testing I already can't do.
I hope you're paying attention, because that framework you told me I needed to use is going to be a pain to setup correctly.
after you're done with that, please attach any documentation you shit out to the ticket you never created.
Looking for a new job
PS: get fucked3