Details
-
AboutStandard web eng
-
Skillsjs, node, webdev, dev patterns
Joined devRant on 4/10/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
-
"Are you familiar with uploading your code to Google Drive?"
I left the building at that exact moment.7 -
Today I was 25 years old, asking for a raise or a opportunity to reach the next level of my career.
My department manager simply said:
"I'm sorry, but in terms of salary you have already reached the end of your career."
Bye then :)34 -
Why is it that mediocre people are so loud mouthed.
some stupid wannabe fuck buys a sports car ranging around 100k, he will 3 stories of a week of that car.
Meanwhile the guy who has his own yatch and 12 properties doesn't say a word about it and appears lowkey
i find this fascinating af8 -
SonarQube reduces our code quality through arbitrary nonsense rules, and it's inability to understand perfectly decent Kotlin code. Unfortunately we have a CTO who is completely enamoured with it. I hope someone from Sonar is reading this: You made my pleasurable Dev job a misery, and it may very well be the thing that makes me quit. Fuck your arrogant product. I honestly wouldn't mind it so much if your UX offered a way to discuss each warning and provide affected code snippets so you could argue your case and collaborate on the rule set. But no, you know my code base best right? Fuck you and and your ivory tower.8
-
Manager: How come I go on vacation for 2 weeks and you are able to start, complete, and ship an entire sprint in that time where as when I'm around, the same amount of work takes months? I even got COMPLIMENTS from *the client* about how smoothly things went while I was gone...THIS IS COMPLETELY EMBARRASSING AND UNACCEPTABLE!
Dev: Well. I cancelled all of the status meetings, created tickets with clear expectations, didn't change those expectations, didn't add every idea that popped into the client's head during those two weeks to the current sprint, didn't pull anyone off their tickets to teach me to code, cut the budget for making degrading comments to zero, and incentivised everyone to work by allowing a half days on fridays to work on personal projects if we stayed on schedule.
Manager: THAT'S NOT YOUR JOB! I'M THE MANAGER AND ALL. OF. THOSE. THINGS. ARE. MY JOB! NOT YOURS!
Dev: ...I know.16 -
Just had a (freshly outta college) kid ask me "but who still uses Linux, anyway?"
When I could not hold my laughter, he doubled down with "I mean, no serious company would risk everything on open source packages that they can't know who made!"
I just sent him to talk to our sysadmin and I'm still thinking "man, I should have a sick 1337 burn ready for this situation".
Can someone suggest some snarky rebuttals? Thanks!16 -
PSA.
Bad Managers will, sometimes, abuse imposter syndrome to have you work longer hours. Don't let them.9 -
Simple 1 day task. This idiot takes two weeks and after 7 days of hounding finally opens a pull request.
I go in to review the code. Should be a simple 10-15 line patch.
13,000 lines of code changed.
THIRTEEN THOUSAND!
"I fixed a bunch of formatting mistakes and replaced all instances of single quotes to double. Consistency is important you know."20 -
Tried to impress the boss with my work ethic by staying late to install a new VoIP system. Wasn’t even part of my job description. A few days later I had a flat tire on the way to work. It took me a couple hours to get that taken care of. When I got to work, the boss told me I had to work 2 extra hours that week to make it up. I reminded him that I had worked overtime recently to install his new phone system. He said, “Doesn’t matter. You still need to make up the hours.”
From that moment on I never worked one second more for him than I had to. I quit less than a year into the job.13 -
My biggest pet peeve at the moment is people without any development experience using version numbers.
Me: "Communicating a release date for the feature towards clients is dangerous, we have a developer shortage, and currently don't really have enough capacity to..."
Manager: "What we release next month doesn't have to be perfect, it is just a v1"
Me: "You mean it's a beta? If that's the case, could you maybe differentiate the requirements of the beta, let's call it a 0.1.0, versus the 1.0.0-rc, the release candidate?"
*Feature is eventually merged into production, barely in a beta state*
Manager: "So I have some ideas for the v2"
Me: "You mean 1.0.0"
Manager: "Let's compromise and call it v1.5"
Me: "Let's compromise, you stop communicating release dates, AND you stop using version numbers..."
Manager: "That's not a compromise..."
Me: "...I wasn't finished... And I won't respond to the recruiter who just offered me a better paying job"5 -
Be me, new dev on a team. Taking a look through source code to get up to speed.
Dev: **thinking to self** why is there no package lock.. let me bring this up to boss man
Dev: hey boss man, you’ve got no package lock, did we forget to commit it?
Manager: no I don’t like package locks.
Dev: ...why?
Manager: they fuck up computer. The project never ran with a package lock.
Dev: ..how will you make sure that every dev has the same packages while developing?
Manager: don’t worry, I’ve done this before, we haven’t had any issues.
**couple weeks goes by**
Dev: pushes code
Manager: hey your feature is not working on my machine
Dev: it’s working on mine, and the dev servers. Let’s take a look and see
**finds out he deletes his package lock every time he does npm install, so therefore he literally has the latest of like a 50 packages with no testing**
Dev: well you see you have some packages here that updates, and have broken some of the features.
Manager: >=|, fix it.
Dev: commit a working package lock so we’re all on the same.
Manager: just set the package version to whatever works.
Dev: okay
**more weeks go by**
Manager: why are we having so many issues between devs, why are things working on some computers and not others??? We can’t be having this it’s wasting time.
Dev: **takes a look at everyone’s packages** we all have different packages.
Manager: that’s it, no one can use Mac computers. You must use these windows computers, and you must install npm v6.0 and node v15.11. Everyone must have the same system and software install to guarantee we’re all on the same page
Dev: so can we also commit package lock so we’re all having the same packages as well?
Manager: No, package locks don’t work.
**few days go by**
Manager: GUYS WHY IS THE CODE DEPLOYING TO PRODUCTION NOT WORKING. IT WAS WORKING IN DEV
DEV: **looks at packages**, when the project was built on dev on 9/1 package x was on version 1.1, when it was approved and moved to prod on 9/3 package x was now on version 1.2 which was a change that broke our code.
Manager: CHANGE THE DEPLOYMENT SCRIPTS THEN. MAKE PROD RSYNC NODE_MODULES WITH DEV
Dev: okay
Manager: just trust me, I’ve been doing this for years
Who the fuck put this man in charge.11 -
Get idea, buy domain, make git repo, let the domain expire, post memes about how side projects are always abandoned!3
-
Manager: Why aren’t you working?
Dev: I am, I’m just not typing because I’m thinking an issue out.
Manager: Well what is taking so long? You haven’t written any code for like 15 minutes, you’ve just been doodling on your notepad.
Dev: I’m not “doodling”. I’m taking notes and trying to visualize the issue. It’s a complicated issue with application stat—
Manager: Well just simplify it then
Dev: ?
Manager: Instead of making it a complicated issue just simplify it and then it won’t take you so long. You’re likely overthinking it, I never spend more than 30 seconds thinking about any issue before coming up with a solution. That’s what makes me so effective at my job is my ability to be lean like that.
Dev: …this issue is a bit harder than deciding what to have for lunch26 -
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 -
Look, if I send you an email, don't just immediately ping me via IM to answer. I sent you an email because (a) I was too busy to chat in the first place, and (b) it wasn't a super-critical question requiring an immediate interaction. I was, in fact, trying to do YOU a favor by using a medium that almost by design doesn't dictate an instant reply. You basically defeated the entire purpose of me CHOOSING to send an email in the first place.
Yeah, I know, I should just be happy that you are a helpful person who respects me and so wanted to get to me ASAP rather than one of the dinguses that never answer anything... but I'm a dick too, so I'm not.
Honor the "Importance Code of the Communication Mechanisms", damn it!7 -
I answered an robocall and all the robot said was "good bye". This must be the unit test of robocalls.3
-
Programmer’s life cycle:
- Nothing can stop me today
- A bug huh? let's squash
- I can’t fix this
- Confidence crisis
- Questions career
- Questions life
- Oh it was a typo
- Nothing can stop me today1 -
I login this morning
Everyone going crazy as prod is broken in a million ways. 2.5 million exceptions In 24 hours.
We talk for 1 hour and solve nothing.
I diagnose the 2 biggest sources of exceptions and explain every step I took with screen snippets to reach my conclusions
The one other competent person on my team agrees. Otherwise complete silence.
I'm told not to fix the issue because I am leaving in 6 weeks and other people have to start taking responsibility.
No one fixes the issues. Instead they leave early. Now it's the weekend and the product is fucked.
Fucking useless people. Can't wait to leave.12 -
Both kids and my wife are home today.
Up until COVID working at home was great.
Today I work in the Palace of Pandemonium.7 -
For fucks sake, corporate IT has locked a database application for new entries because it will be phased out by the end of the year. However, the new application is not yet working.
The interim solution? An excel sheet on a shared network drive. In fucking 2020! Unbe-fucking-lievable!12 -
You know what?
Young cocky React devs can suck my old fuckin LAMP and Objective-C balls.
Got a new freelance job and got brought in to triage a React Native iOS/Android app. Lead dev's first comment to me is: "Bro, have you ever used React Native".
To which I had to reply to save my honor publicly, "No, but I have like 8 years with Objective-C and 3 years with Swift, and 3 years with Node, so I maybe I'll still be able help. Sometimes it just helps to have a fresh set of eyes."
"Well, nobody but me can work on this code."
And that, as it turned out was almost true.
After going back and forth with our PM and this dev I finally get his code base.
"Just run "npm install" he says".
Like no fuckin shit junior... lets see if that will actually work.
Node 14... nope whole project dies.
Node 12 LTS... nope whole project dies.
Install all of react native globally because fuck it, try again... still dies.
Node 10 LTS... project installs but still won't run or build complaining about some conflict with React Native libraries and Cocoa pods.
Go back to my PM... "Um, this project won't work on any version of Node newer than about 5 years old... and even if it did it still won't build, and even if it would build it still runs like shit. And even if we fix all of that Apple might still tell us to fuck off because it's React Native.
Spend like a week in npm and node hell just trying to fucking hand install enough dependencies to unfuck this turds project.
All the while the original dev is still trying TO FIX HIS OWN FUCKING CODE while also being a cocky ass the entire time. Now, I can appreciate a cocky dev... I was horrendously cocky in my younger days and have only gotten marginally better with age. But if you're gonna be cocky, you also have to be good at it. And this guy was not.
Lo, we're not done. OG Dev comes down with "Corona Virus"... I put this in quotes because the dude ends up drawing out his "virus" for over 4 months before finally putting us in touch with "another dev team he sometimes uses".
Next, me and my PM get on a MS Teams call with this Indian house. No problems there, I've worked with the Indians before... but... these are guys are not good. They're talking about how they've already built the iOS build... but then I ask them what they did to sort out the ReactNative/Cocoa Pods conflict and they have no idea what I'm talking about.
Why?
Well, one of these suckers sends a link to some repo and I find out why. When he sends the link it exposes his email...
This Indian dude's emails was our-devs-name@gmail.com...
We'd been played.
Company sued the shit out of the OG dev and the Indian company he was selling off his work to.
I rewrote the app in Swift.
So, lets review... the React dev fucked up his own project so bad even he couldn't fix it... had to get a team of Indians to help who also couldn't fix it... was still a dickhead to me when I couldn't fix it... and in the end it was all so broken we had to just do a rewrite.
None of you get npm. None of you get React. None of you get that doing the web the way Mark Zucherberg does it just makes you a choad locked into that ecosystem. None of you can fix your own damn projects when one of the 6,000 dependency developers pushes breaking changes. None of you ever even bother with "npm audit fix" because if security was a concern you'd be using a server side language for fucking server side programming like a grown up.
So, next time a senior dev with 20 years exp. gets brought in to help triage a project that you yourself fucked up... Remember that the new thing you know and think makes you cool? It's not new and it's not cool. It's just JavaScript on the server so you script kiddies never have to learn anything but JavaScript... which makes you inarguably worse programmers.
And, MF, I was literally writing javascript while you were sucking your mommas titties so just chill... this shit ain't new and I've got a dozen of my own Node daemons running right now... difference is?
Mine are still working.34 -
Trump: I pay taxes as little as possible!
Me: I write code as little as possible!
I have written less than 2000 lines of code in production in 5 years(about 2 line per working day)but with my luck, I earn more than average wherever I live. God, I live this profession AND my luck.
Note: I write fewer sloc not because I am lazy but because of my industry.7 -
I really, really need an office. Today I've been in a meeting for 2 hours with my mum hoovering in the background and my sister playing the entire fucking soundtrack to Chicago. FUCKING KILL ME!!!
Every time I fucking talk all you can hear is "'n' all that jazz" in the fucking background.
I CAN'T TAKE IT ANYMOREEEEE D'X14