Details
-
AboutTeacher, data scientist, software engineer, musician. In no particular order.
-
SkillsAnything really as long as you give me a couple of weeks to learn it
-
LocationNetherlands
-
Github
Joined devRant on 3/14/2019
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
-
"Why did you bring Wagyu beef to the meeting?"
"Because the calendar description said: Engineers should proactively add value for our steak holders"
(True story -- They told me to do what management instructs, without correcting anyone and without asking questions. And I love playing that game!)6 -
Conversation with the bank today
Bank: For security purposes what was your childhood nickname?
Me: H%!TxxNhd8dclWGbe:/d,TU.w>"$B?O2>a>'jmFpmJ^5wyz@>uFvT'DYg>NdZ&ER=t/\{.[7U[>iW/,LJPGW<L:5.etj_N\X@n|ZMpndTh(O0[}N:aDo'kh$4+TkfpJW3d(T{s?FRppN$nM!q+!FS^Z]X2cri1,R%1*w61\t=]6ESyK@V6[@lZMwikH"=+(:+PC57v{,JK7>*%D1T=c%e3L]4^=Q0xAh0\]V7[TULzU}b^|,P/;I(.w9"h]{B#"|
Bank: What, I mean, Can you repeat that?
Me: I had a rough childhood!5 -
Manager: You devs are constantly complaining about context switching, if you were on my level you would be able to multitask and switch from task to task without an— hold on I’m getting a text *tap* *tap* *tap tap* *tap* *send noise*
Manager: Right, what were we talking about again?
Dev: …15 -
Shoutout to my recent client who not only referred a friend of theirs to me for an additional project but is first making them define their project with process models before the customer interview to ensure no one’s time is wasted.
I always recommend to my customers that they define their project before taking it to me because otherwise it becomes billable consultation hours if I sit down with them and talk about the project and create the process models on my end.
This is a good customer experience and what I like to see when working 😁5 -
I had an interview yesterday with the CEO of a startup going into Series A for the position of Principal Developer, remote. I've only ever heard of 'tech-bros', but I was unfortunate to meet one in-person. It went something like this:
CEO-bro: Good morning.
Me: Morning.
CEO-bro: It says here on your resume you live in X. That place is a shithole, and I have to look down on you because of that, bro. LoL.
Me: ......
(40 minutes of self-promotion pass)
CEO-bro: Anyway, we don't pay high salaries but offer bonuses for high performing staff instead. I'll ask HR to send you an offer.
Me: Let me think about it.
CEO-bro: One question bro. You have siblings?
Me: One.
CEO-bro: Parents still alive?
Me: No...what?!
CEO-bro: Yeah, me too. People like us don't let anything get in the way.
I wrote them an email this morning withdrawing my application 🤦🏽♂️11 -
[Certified CMS Of Doom™ moment]
Ah yes, the good old "generate a huge CSV just to know how many rows there are"15 -
Today is sprint demo day. As usual I'm only half paying attention since being a Platform Engineer, my work is always technically being "demoed" (shit's running ain't it? There you go, enjoy the EC2 instances.)
One team presents a new thing they built. I'm still half paying attention, half playing Rocket League on another monitor.
Then someone says
"We're storing in prod-db-3"
They have my curiosity.
"Storing x amount of data at y rate"
They now have my attention. I speak up "Do you have a plan to drop data after a certain period of time?"
They don't. I reply "Okay, then your new feature only has about 2 months to live before you exhaust the disk on prod-db-3 and we need to add more storage"
I am asked if we can add more storage preemptively.
"Sure, I say." I then direct my attention to the VP "{VP} I'll make the change request to approve the spend for additional volume on prod-db-3"
VP immediately balks and asks why this wasn't considered before. I calmly reply "I'm not sure. This is the first time I'm learning of this new feature even coming to life. Had anyone consulted with the Platform team we'd have made sure the storage availability was there."
VP asks product guy what happened.
"We didn't think we'd need platform resources for this so we never reached out for anything".
I calmly mute myself, turn my camera back off and go back to Rocket League as the VP goes off about planning and collaboration.
"CT we'll reach out to you next week about getting this all done"
*unmute, camera stays off* "Sounds good" *clears ball*4 -
Manager: We do not identify as a tech company so don’t expect tech company salary increases this year
Dev: Well don’t expect me to bring a tech work ethic then
Manager: !!5 -
Finally resigned.
I didn't hate my work but I need to grow. I was 4 years experienced and I was working on entry level positions. That's because for getting promoted I need to work like I'm on the next level for a year consistently, I don't know if I was working on next level but I felt confident that I can, so I switched companies finally. I don't know if work will be a lot what will I do but I have enough hard skills, my soft skills might not be that good but I'm finally doing something to achieve growth in that area. I'll be scared, anxious, helpless and all but let it be. I'll sprint, rest and repeat.8 -
Fuck the memes.
Fuck the framework battles.
Fuck the language battles.
Fuck the titles.
Anybody who has been in this field long enough knows that it doesn't matter if your linus fucking torvalds, there is no human who has lived or ever will live that simultaneously understands, knows, and remembers how to implement, in multiple languages, the following:
- jest mocks for complex React components (partial mocks, full mocks, no mocks at all!)
- token cancellation for asynchronous Tasks in C#
- fullstack CRUD, REST, and websocket communication (throw in gRPC for bonus points)
- database query optimization, seeding, and design
- nginx routing, https redirection
- build automation with full test coverage and environment consideration
- docker container versioning, restoration, and cleanup
- internationalization on both the front AND backends
- secret storage, security audits
- package management, maintenence, and deprecation reviews
- integrating with dozens of APIs
- fucking how to center a div
and that's a _comically_ incomplete list; barely scratches the surface of the full range of what a dev can encounter in a given day of writing software
have many of us probably done one or even all of these at different times? surely.
but does that mean we are supposed to draw that up at a moment's notice some cookie-cutter solution like a fucking robot and spit out an answer on a fax sheet?
recruiters, if you read this site (perhaps only the good ones do anyway so its wasted oxygen), just know that whoever you hire its literally the luck of the draw of how well they perform during the interview. sure, perhaps some perform better, but you can never know how good someone is until they literally start working at your org, so... have fun with that.
Oh and I almost forgot, again for you recruiters, on top of that list which you probably won't ever understand for the entirety of your lives, you can also add writing documentation, backup scripts, and orchestrating / administrating fucking JIRA or actually any somewhat technical dashboard like a CMS or website, because once again, the devs are the only truly competent ones - and i don't even mean in a technical sense, i mean in a HUMAN sense of GETTING SHIT DONE IN GENERAL.
There's literally 2 types of people in the world: those who sit around drawing flow charts and talking on the phone all day, and those WHO LITERALLY FUCKING BUILD THE WORLD
why don't i just run the whole fucking company at this point? you guys are "celebrating" that you made literally $5 dollars from a single customer and i'm just sitting here coding 12 hours a day like all is fine and well
i'm so ANGRY its always the same no matter where i go, non-technical people have just no clue, even when you implore them how long things take, they just nod and smile and say "we'll do it the MVP way". sure, fine, you can do that like 2 or 3 times, but not for 6 fucking months until you have a stack of "MVPs" that come toppling down like the garbage they are.
How do expect to keep the "momentum" of your customers and sales (I hope you can hear the hatred of each of these market words as I type them) if the entire system is glued together with ducktape because YOU wanted to expedite the feature by doing it the EASY way instead of the RIGHT way. god, just forget it, nobody is going to listen anyway, its like the 5th time a row in my life
we NEED tests!
we NEED to know our code coverage!
we NEED to design our system to handle large amounts of traffic!
we NEED detailed logging!
we NEED to start building an exception database!
BILBO BAGGINS! I'm not trying to hurt you! I'm trying to help you!
Don't really know what this rant was, I'm just raging and all over the place at the universe. I'm going to bed.20 -
The Manager kept masturbating over "low hanging fruit".
The apples on the bottom of The Product have all been picked.
The apples at the top are starting to rot.
The Manager masturbated a bit more over the low hanging fruit.
The bottom of The Product is now so slippery with Manager Cum that the brave engineers can't reach the top anymore.
Time to bring my axe to work.13 -
Googe Analytics illegal in EU.
Fucking love you Europeans.
And for that matter any analytics software that sends or stores data in US serves, because it's against GDPR.
https://techcrunch.com/2022/01/...30 -
Apple macbook engineering department hard at work:
1) Some app freezes
2) Then the Touch-bar freezes
3) I hit cmd+alt+esc to force close it
4) Touch bar is frozen so esc won’t work
5) *confused noises*11 -
It happened again.
This time my colleague, is abbreviating "cumulative" as "cum" in a variable name, and now I have to control my 6th grade humor...24 -
start teaching people how and why to delete code instead of teaching them only how to write code
compare functional and object oriented languages as well as high level and low level languages and explain what are advantages of using certain language without going into the syntax
let people do mistakes and don’t punish people for making them but let them explain what happened, if they know what was the cause of mistake it is worth ten times than doing things correctly
mix teams per period of time instead of per project
make showcases how to modify ugly code to pretty one and what are the steps and what patterns people should look after
teach by not showing old stuff but showing where old stuff exists in modern things and why it’s important there and what’s the purpose of doing things certain way instead of flat theory based on ancient examples1 -
Manager: We need to setup the security in the Mexico server
Dev: You mean that 3rd party firewall add on?
Manager: Yes
Dev: And set up the billing on the Mexico account?
Manager: Yes
Dev: lol, sure thing I’ll create the ticket
Manager: What’s so funny?
Dev: Nothing
Ticket: Build wall and get Mexico to pay for it.12 -
Finally got some free time cook for myself a lunch...
Don't have worry about the company project anymore.
😋17 -
Python async is a total, unapologetic shitshow. It’s as if the design goal was explicitly to invalidate the maximum number of thoughtful stackoverflow QAs possible. Pro tip: make you sure to memorize the release dates of every minor version of python from 3.5-3.10, so that you know which stackoverflow answers are not relevant in any way to your codebase.2
-
Manager: We should do X with the database
Dev: That will cause issue Y
Manager: But I read an article that said that issue Y wasn’t a problem
Dev: It did?
Manager: Well it didn’t mention issue Y
Dev: …2 -
So today this Mother F**ker get HR to back him up to accuse me of not communicating well in the team because I consistently asked him (the code owner) why he kept coding not following the coding guideline.
How is it not communicating? He literally ghosted me and blocked me every time I ask him questions. Which I somewhat don't understand what he is trying to do. HR lady told me that a senior software engineer should have the knowledge to understand everything and all the code.
But the code looks like this :43 -
My friend, Gavin, an air steward (a job that he had done for decades), told me about an incident at work. He said that (shockingly to me) passengers occasionally die on a flight (particularly long-haul), just as a matter of course. This can be because people sometimes travel to visit loved ones BECAUSE they are dying, people sometimes find travelling itself stressful (so it can exacerbate an existing medical condition), or simply that, if you took a large number of people and shut them up in a space together for some considerable time, some of them would pop off through sheer statistical probability. Cabin crew are, apparently, fully trained to deal within this eventually in a calm, almost routine manner.
This particular flight, Gavin was working with another gay man: Peter, who was actually a VERY funny personality. Camp, extravagant and loud, Peter really lit up the place. But naturally, when the very elderly male passenger in seat 38b died peacefully in his sleep halfway across the Atlantic, Peter acted (like the entire crew), with decorum and dignity. As per the protocol, all the lights in the cabin were dimmed. A hush fell over the passengers (Gavin told me that, although no announcement is ever made, the other passengers nearly always instinctively know what's happened, with the news spreading via the media of hushed whispers and nudges). Then, as per standing instructions, two of the crew carefully lifted the deceased out of his seat and gently carried him to the crew station where he was laid down on a bed for the remainder of the flight.
After the late gentleman disappeared behind the discreetly drawn curtain, you could have heard a pin drop. There was a demure pause during which, slowly, the lights went back up.
Suddenly Peter's cheery face appeared, poking through the gap in the drapes. He looked around, blinking brightly with curiosity at the seated passengers, and said, in a voice that echoed around the whole cabin:
"SO! Anyone else have the fish?"
He narrowly avoided getting sacked.10 -
Dev: Sam’s a little nervous about taking his paid leave. I guess it’s not common in Nigeria. He needs to hear from the company that taking time off like that is acceptable.
HR: THAT’S SO INAPPROPRIATE! YOU CAN’T ASSUME HE’S FRON NIGERIA JUST BECAUSE HE’S BLACK. BLACK PEOPLE HAVE A VERY RICH AND DIVERSE CULTURE, THEY ARE NOT ALL FROM NIGERIA!!!
Dev: Sam is from Nigeria. He told me so. He tells me a lot of stories from there.
HR: …
Dev: Can you tell me something about Sam besides his skin colour?
HR: …
Dev: …14 -
Guy: - Why the hell do you keep adding new tests with "TDD" in the commit log? Is this because you're wearing this stupid TDD t-shirt!? You're only supposed to maintain this! There's nothing to develop! Nothing here will ever be test-driven!
Cprn: (turns around)
T-shirt: *Technical Debt Development*6