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
-
A contractor at my old job was doing a development role and was constantly annoyed and the idiotic design decisions going into the website backend we were developing 🙄😒
When he decided enough was enough he could have easily written a really snarky email but instead he wrote the most sincere and professional email to his boss and the director thanking them profusely for the opportunity and hopes he would be welcome for future work with the business....👍
He was a really good Dev and the email made the bosses super happy thanking him so much and how much of a shame it was he was going....😍
He bcc'd me on the mail and when he handed his computer in he told me to open the email and highlight in full....👌
At the end of every line in white text was 'Go Fuck yourself' or 'Zero fucks given'
The bosses never realised... And I know he's been back there about 4 months now..... But shhh 😭3 -
I have always thought that I am to dumb to become a dev, but after a few years doing sysadmin shit I have realized that even the most stupid, dumb and idiotic people can be a wordpress developer!
There is still hope for me9 -
I was bored so I scanned through Dev.to and Medium. I lost the remnants of the little hope I had left for mankind...
JS this, Python that, JS that... and so much other mindless articles of exactly zero substance and headlines to make any self-respecting dev cringe for days.
I meant to write something else, too, but I'm too saddened now. I no longer wonder why so many of the fresher self-made "devs" are so idiotic of a breed...35 -
Harsh truth:
My side SaaS project made more money in its first month (built late winter last year, MVP released after ~3 weeks of development) than the sTaRtUp I work for over its total lifetime so far (built over 3+ months, MVP released in May last year)
...is it time to rage quit?
Often I have dreams of going full-time solo dev, leaving every idiotic, clueless, fumbling clown behind, but I feel like I just don't have the financial runway to do it. However, even from just a few months in 2021 while I was on the job hunt, I created some side revenue streams which I'm still receiving decent revenues from (selling courses, saas products, minor freelancing). I'm just not 100% sure if I was "lucky" during this time period, or if a few more months going at it I'd be able to scrape my way towards a meager (though livable!) income.
Give me biased views, devRant!6 -
This was some time ago. A Legendary bug appeared. It worked in the dev environment, but not in the test and production environment.
It had been a week since I was working on the issue. I couldn't pinpoint the problem. We CANNOT change the code that was already there, so we needed to override the code that was written. As I was going at it, something happened.
---
Manager: "Hey, it's working now. What did you do?"
Me: *Very confused because I know I was nowhere close to finding the real source of the problem* Oh, it is? Let me check.
Also me: *Goes and check on the test and prod environment and indeed, it's already working*
Also me to the power of three: *Contemplates on life, the meaning of it, of why I am here, who's going to throw out the trash later, asking myself whether my buddies and I will be drinking tonight, only to realize that I am still on the phone with my manager*
Me again: "Oh wow, it's working."
Manager: "Great job. What were the changes in the code?"
Me: "All I did was put console logs and pushed the changes to test and prod if they were producing the same log results."
Manager: "So there were no changes whatsoever, is that what you mean?"
Me: "Yep. I've no idea why it just suddenly worked."
Manager: "Well, as long as it's working! Just remove those logs and deploy them again to the test and prod environment and add 'Test and prod fix' to the commit comment."
Me: "But what if the problem comes up again? I mean technically we haven't resolved the issue. The only change I made were like 20 lines of console logs! "
Manager: "It's working, isn't it? If it becomes a problem, we'll work it out later."
---
I did as I was told, and Lo and Behold, the problem never occurred again.
Was the system playing a joke on me? The system probably felt sorry for me and thought, "Look at this poor fucker, having such a hard time on a problem he can't even comprehend. That idiotic programmer had so many sleepless nights and yet still couldn't find the solution. Guess I gotta do my job and fix it for him. I'm the only one doing the work around here. Pathetic Homo sapiens!"
Don't get me wrong, I'm glad that it's over but..
What the fuck happened?5 -
Dear my school app developer,
.
I'd like to say FUCK YOU! update your app before asking money from me.
1 -
Not specifically a Dev job, but I did do a bit of development at this wifi startup. It was a wifi shop where we set up wifi for hotel clients all over the US. Anyways, they said I would make great money doing "on call" support, and me being an intern and naive I said absolutely I'd do it. Well 3 months later I was put on call essentially every day and one weekend I was with my mother and it was her birthday. At her party at this nice restaurant, with all of our close friends/family, I got a call. It took me 45 minutes to solve because of how idiotic the clients were, and after that I got 4 more calls equally as frustrating and long throughout that night. I asked for help from employees, the owner, ANYONE. Nobody helped. Needless to say I emailed the owner and said farewell that following Monday.
-
Pretty much when i stopped listening to the same old "my printer is jammed" requests in helpdesk and saw a friend dev earn twice as much as i dis at that time without dealing with (that many) idiotic situations.
A few years later - i'm a happy little coder. And i have my own minions to deal with support. Seniority rules :D3 -
!dev
Decided to spend more time on LinkedIn to familiarise myself and start looking for potential employment opportunities.
For past month or so, I've seen few decent opportunities, which is a nice start. However, for every decent post, I've come across:
- About a hundred of posts by self-proclaimed crypto experts who spout absolute gibberish and somehow get thousands of likes. 5 min google search and absolute minimum knowledge of economic theory discards 99% of their claims and statements
- Handful of idiotic "career advice" blog posts
- Numerous posts, both bashing and helplessly supporting shitty recruiter practices
- more crypto nonsense
- People jerking themselves off for running a profitable business (company launched a 1-5months ago)
Really starting to hate the platform, seems like all the integrity it had before becoming fully mainstream, has gone down the drain and it's become a straight up corporate circle jerk1 -
!rant
The new end to the idiotic code snippet head scratchers interviews (awkward for both parties but nobody is willing to admit it)?
Hometasks.
Infinite internet access, use whatever tools you want, do as much as you can in 2-3 hours.
The best non-toxic way to see how someone works as a dev.
This is the way I expect you to work, so this is the way I will interview you.
Sorry silicon valley, we don't need people who can write up a binary search algo from rote memory.3 -
So this is the most idiotic thing I have ever done!
Was resolving an issue in a module in our application on "Test" Instance, instead of uploading file to "Test" I was uploading to "Dev" and I was wondering for the last 2 hours why the hell changes are not working!!!
I need a break, Thank god its half day today... its a rest day now 🙈2 -
!dev
So as usual I received some call from telemarketer and I started from other perspective this time.
I asked how I can be sure that the person on the other side is telling the truth.
That pissed the telemarketer that started challenging me by reading my company data but I calmly responded that it doesn’t proof anything cause I don’t know anything about you - the person who are calling me.
I know who I am but how I can trust who you are ? You just provided me your name that I don’t know it’s true cause I have no methods to verify that.
That pissed telemarketer so much.
Some time ago before you put money in bank you know the banker. If someone was stealing this money you probably know from your police who is it and where he’s probably hiding.
The future we’re trying to go right now with this machine stuff that makes job for us is completely different.
We’re more and more separated from reality that is our planet dying. More and more animals and plants are dying, nobody cares about it.
Despite me working a lot with new tech I am more and more sceptic of how technology is shaping us. We sooner or later wont be able to shit without computer ( lots of us is probably already there bringing cellphones as companions for good nice shit rolling ).
Is it the future we want ?
The future where you need to beat computer to have contact with nice people. Cause I see it everywhere now. The technology is stupid and not perfect so lots of us is forced to align to this crap right now. Use the technology and beat the algorithms to connect with human. That’s the future we want ? Really ?
Some idiotic algorithms that are trying to tell us that this is what you need to watch ? This is what you need to eat ?
This is where you need to be ?
Take our time and turn it to view count slash likes and subscribes shit hole ?
The technology power show that everyone wants to buy but you won’t even use 10% of it’s capabilities cause it’s blocked by company that sells it ?
I’m more and more disappointed by this world.
Anyway Telemarketer didn’t want to admit that is alien robot who is trying to kill humans by selling me this machine so I hanged up cause I had nothing more interesting to say.
I think they will finally stop calling me.2 -
Lazy / idiotic PMs or BAs. No mather how hard the dev team tries, if the analisys or the management is bad, you're screwed.1
-
In reply to this:
https://devrant.com/rants/260590/...
As a senior dev for over 13 years, I will break you point by point in the most realistic way, so you don't get in troubles for following internet boring paternal advices.
1) False. Being go-ahead, pro active and prone to learn is a good thing in most places.
This doesn't mean being an entitled asshole, but standing for yourself (don't get put down and used to do shit for others, or it will become the routine) and show good learning and exploration skills will definitely put you under a good light.
2)False. 2 things to check:
a) if the guy over you is an entitled asshole who thinkg you're going to steal his job and will try to sabotage you or not answer acting annoyed, or if it's a cool guy.
Choose wisely your questions and put them all togheter. Don't be that guy that fires questions in crumbles, one every 2 minutes.
Put them togheter and try to work out the obvious and what can be done through google or chatgpt by yourself. Then collect the hard ones for the experienced guy and ask them all at once. He's been put over you to help you.
3) Idiotic. NO.
Working code = good code. It's always been like this.
If you follow this idiotic advice you will annoy everyone.
The thing about renaming variables and crap it's called a standard. Most company will have a document with one if there is a need to follow it.
What remains are common programming conventions that everyone mostly follows.
Else you'll end up getting crazy at all the rules and small conventions and will start to do messy hot spaghetti code filled with syntactic sugar that no one likes, included yourself.
4)LMAO.
This mostly never happens (seniors send to juniors) in real life.
But it happens on the other side (junior code gets reviewed).
He must either be a crap programmer or stopped learning years ago(?)
5) This is absolutely true.
Programming is not a forgiving job if you're not honest.
Covering up mess in programming is mostly impossible, expecially when git and all that stuff with your name on it came out.
Be honest, admit your faults, ask if not sure.
Code is code, if it's wrong it won't work magically and sooner or later it will fire back.
6)Somewhat true, but it all depends on the deadline you're given and the complexity of the logic to be implemented.
If very complex you have to divide an conquer (usually)
7)LMAO, this one might be true for multi billionaire companies with thousand of employees.
Normal companies rarely do that because it's a waste of time. They pass knowledge by word or with concise documentation that later gets explained by seniors or TL's to the devs.
Try following this and as a junior:
1) you will have written shit docs and wasted time
2) you will come up to the devs at the deadline with half of the code done and them saying wtf who told you to do that
8) See? What an oxymoron ahahah
Look at point 3 of this guy than re-read this.
This alone should prove you that I'm right for everything else.
9) Half true.
Watch your ass. You need to understand what you're going to put yourself into.
If it's some unknown deep sea shit, with no documentations whatsoever you will end up with a sore ass and pulling your hair finding crumbles of code that make that unknown thing work.
Believe me and not him.
I have been there. To say one, I've been doing some high level project for using powerful RFID reading antennas for doing large warehouse inventory with high speed (instead of counting manually or scanning pieces, the put rfid tags inside the boxes and pass a scanner between shelves, reading all the inventory).
I had to deal with all the RFID protocol, the math behind radio waves (yes, knowing it will let you configure them more efficently and avoid conflicts), know a whole new SDK from them I've never used again (useless knowledge = time wasted and no resume worthy material for your next job) and so on.
It was a grueling, hair pulling, horrible experience that brought me nothing in return execpt the skill of accepting and embracing the pain of such experiences.
And I can go on with other stories. Horror Stories.
If it's something that is doable but it's complex, hard or just interesting, go for it. Expecially if the tech involved is something marketable.
10) Yes, and you can't stop learning, expecially now that AI will start to cover more and more of our work.4
Top Tags
Weekly Rant
View