Details
-
AboutDeveloper / devops engineer from the Netherlands
-
SkillsJava, Kotlin, Typescript, PHP, Kubernetes
-
LocationNetherlands
Joined devRant on 6/9/2016
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
-
"I am not happy with the quality of the product"
*Ignores
"I dislike how I am forced to work here"
*Ignores
"The team does not understand software design and is writing 2000 line single functions"
*Ignores
"I am starting to think the product cannot be saved unless we start focusing on quality"
*Ignores
"I am not happy in my job anymore because I want to work as a professional..."
*Ignores
"All I ever do now is put out fires"
*Ignores
"I quit"12 -
How do you deal with a manager like this?
My manager is close with 2 colleagues who constantly suck up to them and who they're pretty much friends with.
I don't particularly like to do stuff like that and don't really like the manager either (in my opinion they're incompetent) but now, often when I write code, the manager will have those colleagues "check" it. Not peer review, as I never get feedback. Just occasionally I'll find out they "checked" my code to see if I work/do my job right.
This is despite me being more senior than the both of them, having contributed far more actual code to the project than both combined and one of them can not even write proper code!!!
I'm honestly tired of sitting here and working on boring long tasks, and then being treated (behind my back) as if I am not working.
It's building up this paranoia in my head that this problem is also making other colleages/my boss think that I am slacking.
I used to be so close with everyone at the company, but now I feel completely alone and alienated...28 -
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 -
How much does a syntax of a language impact ur opinion of it and wether you'll want to use/learn it?
Some languages I look at and it just looks like an unreadable mess, i dont even bother with. Avoided nodejs up until i didnt have to deal with 100 nested callbacks...10 -
Newcomer: I can do fizzbuzz in 6 lines of code
Experienced: I can do fizzbuzz in 3 lines of code
Professional: I can do fizzbuzz in 1 line of code
Enterprise: you did not create the user epic for this problem, I can't accept these solutions until you have done this. Please speak with Mike on getting this properly setup. I expect a full report of this by Monday.
Them: but it's Friday...
Enterprise: Get it done. I am not paying your overtime either
https://github.com/EnterpriseQualit...8 -
Root gets ignored.
I've been working on this monster ticket for a week and a half now (five days plus other tickets). It involves removing all foreign keys from mass assignment (create, update, save, ...), which breaks 1780 specs.
For those of you who don't know, this is part of how rails works. If you create a Page object, you specify the book_id of its parent Book so they're linked. (If you don't, they're orphans.) Example: `Page.create(text: params[:text], book_id: params[:book_id], ...)` or more simply: `Page.create(params)`
Obviously removing the ability to do this is problematic. The "solution" is to create the object without the book_id, save it, then set the book_id and save it again. Two roundtrips. bad.
I came up with a solution early last week that, while it doesn't resolve the security warnings, it does fix the actual security issue: whitelisting what params users are allowed to send, and validating them. (StrongParams + validation). I had a 1:1 with my boss today about this ticket, and I told him about that solution. He sort of hand-waved it away and said it wouldn't work because <lots of unrelated things>. huh.
He worked through a failed spec to see what the ticket was about, and eventually (20 minutes later) ran into the same issues Idid, and said "there's no way around this" (meaning what security wants won't actually help).
I remembered that Ruby has a `taint` state tracking, and realized I could use that to write a super elegant drop-in solution: some Rack middleware or a StrongParams monkeypatch to mark all foreign keys from user-input as tainted (so devs can validate and un-taint them), and also monkeypatch ACtiveRecord's create/save/update/etc. to raise an exception when seeing tainted data. I brought this up, and he searched for it. we discovered someone had already build this (not surprising), but also that Ruby2.7 deprecates the `taint` mechanism literally "because nobody uses it." joy. Boss also somehow thought I came up with it because I saw the other person's implementation, despite us searching for it because I brought it up? 🤨
Foregoing that, we looked up more possibilities, and he saw the whitelist+validation pattern quite a few more times, which he quickly dimissed as bad, and eventually decided that we "need to noodle on it for awhile" and come up with something else.
Shortly (seriously 3-5 minutes) after the call, he said that the StrongParams (whitelist) plus validation makes the most sense and is the approach we should use.
ffs.
I came up with that last week and he said no.
I brought it up multiple times during our call and he said it was bad or simply talked over me. He saw lots of examples in the wild and said it was bad. I came up with a better, more elegant solution, and he credited someone else. then he decided after the call that the StrongParams idea he came up with (?!) was better.
jfc i'm getting pissy again.9 -
After one year of procrastination I finally made the game with unity
Ladies and gentleman, spherical voronoi minesweeper
Yes, I made the game before with in c++ which looks quite shitty, but finally, unity33 -
Code review titles by year:
1990 - your code is using to much memory
1995 - your code is not running on window 95
2000 - your code is slow
2003 - your code don't have tests
2005 - your code is not 64 bit
2009 - your code is not using mvc patters
2010 - your code is not horizontal scalable
2011 - your code should be written in js
2015 - your code is not mobile ready
2020 - your code is racist24 -
If a teamviewer sessions counts as "screenshare", I've got a good one.
The company I'm working for also got an internal video player in the webfrontend of it's product. A customer called in, because the player "stays black", instead of playing his videos. It's a player for a media library of the customer, so it can be any content. A collegue did some trouble shooting, but since the customer was not very experienced in IT they arranged a teamviewer session. At the appointed time, my collegue called the customer and asked him to reproduce the issue, while watching via teamviewer.
When opening the media player, it stayed black indeed, so my collegue asked the customer to try another video. From my desk I heard my collegue say "Oh god, no" (phone muted) pretty loudy and he asked us to come to his place quickly. The customer decided, it would be a good idea to try the video player with gay porn. So we stood there around my collegues desk, watching a hairy man, getting his asshole licked by another an even hairier man for a few secs.
The customer stopped the playback, said "ok, maybe the other file was just broken.", thanked my collegue and the call was over.
We had a few similar cases.5 -
Probably Dennis Ritchie. Inventor of a timeless language and member of the Unix project at Bell. I think his work is significant and he lived his life, then died a good man.