A 520MB CSV file with 29 columns and no headers.

If it's not an impertinent question, why in the name of Satan's magnificent testicles would anyone do that?

I hope their pig dies.

A few years i had wrote a little script as a proof of concept for remote injection via torrent files.

Yesterday, some doofus bruteforced into my seedbox and tried to install a miner using the same script🤦🤦🤦

Did some digging, found my way back to him and wiped the drives on his system as a gesture of thank you. Anyways, I hope he didn't have anything important on his 16TB volume, cause good luck recovering that

Fuckers didn't even give my account access to the fucking soap action I was calling after 3 weeks of email chains and other back and forth.

First the credentials I was given "we're fully set up" and now this BS??

Fucking test your live and sandbox environments work BEFORE you let your clients start their integrations.

And if they have issues, try to emulate the e-2-e test and prove you can complete the transaction yourself BEFORE emailing back 🤦

Manager: "If you need me, just @ me"
Me: "Can you look at this right now?"
Manager: "Sorry I'm at a tennis match, I'll be 30mins"
3 hours later
Manager: "Do you still need me?"

...

Me: "A device died. Playbook says we have to flash it and lose all data on it, but we could go to the vendor for a solution if their fast enough. I just need you to make the call to deviate"
Manager: "Uggghhh" (goes offline for 2 hours)

Wtf man?!

The most unrealistic deadline? Okay, here it goes. For context, this is one of my earliest jobs, and I’m actively using React.

— Kiki, I have a stunning idea! Let’s build a Figma clone!
— Okaaaay, 🧐
— You have two days.
— A what?
— I’ve just stumbled upon an amazing new technology. You maybe don’t know it yet. It’s called React.js, and you totally can build a full Figma clone in two days using it!
— …
— It’s a revolution, and you’re so ignorant for not following it. Are you even a real engineer?
— …

Two days later:
— Forget about Figma! Let’s build an online DAW for musicians!

That guy was nuts. I left when we had an executive meeting, I was explaining tech things, and he suddenly popped out a fucking tambourine and started striking it. One year later, he lost everything and went to get a junior C++ position at an outsourcing company.

Let me explain a tiny corner of some awful code I read earlier today, in layman’s terms.

It’s a method to see if the user is in a secure session — not to set up the session, just to see if it exists. The method ends with a question mark, so it’s basically a question. It should look up the info (without changing anything) and should always give a clear yes/no answer. Makes sense, right?

Let’s say the question is “am I in school right now?”

The code… well.

If there isn’t a student, the answer it gives is null, not yes or no. Null is a fancy word for no, pretty much, so that’s kinda fine, but it really should be a simple no.

It then checks to see if the school is open today. If it is open, it then checks to see if I made my lunch, if I took my backpack, and if I rode the bus — and makes these things happen if they didn’t. Forgot my backpack? Just ask “am I in school today?” And poof! There’s my backpack! … but only if the school is open.

It then, finally, checks to see if I’m actually in the school, and gives that answer.

It could just see if I’m in the school — I mean, I could be in school without a backpack, or walked there on the weekend, right? Ha! You and your silly logic have no place here.

So, by asking if the user is in a secure session, we change the answer: they weren’t before, but the act of asking makes it so. This isn’t profound or anything: I don’t work with Schrödinger. My coworkers are just idiots.

And no, the rest of the code isn’t any better…

Not laughing.

Not cursing.

Both for interviewing and being interviewed.

Some interviews could have been taken straight from a mexican telenovela.......

"Yeah, I worked for a year in the Walmart IT administration."

"Ok, what did you do?"

"Oh I had the high responsibility of taking care of swapping printer cartridges, programming the registers, stuff like that..."

"You apply for a senior database management role, you're aware of that?"

"Yeah. I took a bootcamp for 3 months in the evening after work. I'm up for the job and expect a payment of <lol, even having a stroke while writing a payment check that number will never happen>".

I made that up - but we had these cases... The story is just rewritten and mixed up for obvious reasons.

When I'm being interviewed, the same thing can happen by the way, too.

IMHO a interview is made not only for the company, but for me as an employee, too. I don't sugar coat it. I want to know what type of shit I'm getting into and how much I'm drowning in it.

Some "types" of interviewers react kinda funny when I start roasting them with questions...

For example, the authoritarian type usually reacts with disrespect. How dare u piss on my front lawn.... Kind of reaction. Which makes it hard not too laugh, because who wants to work for someone who throws a tamper tantrum during a interview? Even harder when the same guy promised you heaveb before (the flowery kind of bullshit, like everything's peaceful and fine and teams great and they have such a great leadership...)

Even worse is the patsy.

When you're sitting in an interview and the only answers you get are:

- Sorry, I don't know.
- I'm not allowed to ....
- Not in my area of expertise....

All just nice ways of saying: I will say nothing cause then I'd need to take some responsibility.

:)

The most Mexican telenovela stuff though in being interviewed is when I managed to divide a team of interviewers and it starts to become a "Judge Judy" or similar freaked out justice show...

A: "No, our team doesn't work that way".
B: "But you will in the short future, WE committed to it".
C: "Not that I'm aware of".

And me, an obvious sinner and person who enjoys entertainment and schadenfreude, just keeps adding kerosene to the fire.

"So, it seems like the team of A has its own rules which do not apply to B and C, do they also have greater funding?".

Oh it makes just fun to spur a good blood bath.

Just saw a youtube video about what the author of the core-js library is going through.

I feel for the man, honestly, I could never work fully on open sourced software since I know how hard it makes it to pay the bills, and but a handful of developers can actively receive financial backup.

What seems crazy to me, is that no company has come forward as sponsors for his creation.

His github account is a wild ride:

https://github.com/zloirock/core-js

I looked around the internet, there is a lot of hate aimed at this man, which I think it is unfair.

Devs can be really mean spirited

I post an answer to StackOverflow for the first time in a few months. INSTANT DOWNVOTE + "CORRECT BUT NOT `LOGICAL ENOUGH`"

FUCK YOU

thx for coming to my TedTalk

I hate people who think they are always right.

A coworker who seemed to be a friend turns out to be an emotionally needy narcissist who seems to think that he is a perfect human being and is the best example of how to live.

Long story short is that we did some bonding via alcohol and smoking cigarettes. Especially when I was in a bad period in my life where I had little self confidence, was in a bad financial situation and overshared many details abound my personal life.

And yeah we also work as software devs in the same team but I started avoiding working with him directly, because due to his seniority he overcomplicates things a lot to the point where stuff gets postponed for months. Meanwhile I am a simple guy, I do my tasks and if they are not up to the standard I just work on the feedback until Im up to the standard, thats it. Its just a job for me, for him its a way of life and he considers himself to be basically an artist.

Hes always trying to prove me something, showing that the "long way" is the best way and so on. In reality I dont give a fuck about him. I live my own life and I have my own priorities. I work fulltime in one job, also I work part time as a freelancer and in total I make about 20 percent more than he does. Previously before this job I owned my own company where for 2 years I ran my own projects which generated a decent revenue. I know what is hard work and how to sacrifice myself in order to achieve results. I am more pragmatic and I have some limitations of what I can be good at (since I have a shitty working memory due to my ADHD). So I have systems in place and bottom line is that I earn a decent living and my skillset is different. Yeah I agree that in some ways he is better than me, but dude has such a massive inflated ego that now he thinks that he unlocked some sort of universal wisdom and now hes suddenly experienced in every field of life and his opinion is the right one.

This guy takes a massive pride in how good software engineer he is and in every topic or interaction he tries to one up me. Which most of the time is just his preference or in order to gain a 0.0001 percent performance increase. Dude is basically a big walking ego and since "we are close now" his ego started bleeding into personal relationship.

In my personal life, Im in a stable relationship, thinking of proposing soon and getting married. I already co-own an apartment with my current girlfriend. Everything is serious and planned, Im soon to be 30 years old. He is the same age but he still thinks hes young hot shit and all he cares about is getting shitfaced a couple times a week after work and he doesnt really have any other hobbies. He has a girlfriend but I dont see any future in there TBH.

So what I did now is I started putting some distance between us. No more drinking every week with him, maybe maximum once in 2 or 3 weeks. I started working from home more. Also I stopped sharing my personal life with him. Each time when he thinks he is right I just go along with it and dont even pay attention to his emotional manipulations. I just hope one day he fucks off completely and I wont give in to his gaslighting. Maybe in a few months I will be leaving this job, so I will never have to deal with him again.

Lesson learned: dont be vulnerable to coworkers who you bond together only via alcohol.

Trash, trash, trash.
Who the fuck writes this shit?

Who the fuck lets these trash should-be-junior devs roll their own crypto? and then approves it?

The garbage heap of a feature (signing for all apis) doesn't follow Ruby standards, doesn't follow codebase conventions, has `// this is bridge` style comments (and no documentation), and it requires consumer devs to do unnecessary work to integrate it, and on top of all this: it leaks end-user data. on all apis. in plaintext.

Fucking hell.

Ok so we have 2 useless remote contractors in our team who got hired as seniors but actually are juniors. They take weeks to deliver most basic things and never ask for help or offer help for others. They take days to fix most basic comments after review.

Today our teamlead in a call said that it's a cultural difference, these guys dont ask for help because they are very independent.

MOTHERFUCKER, I WOULD BET MY SALARY THAT THESE IDIOTS DONT WORK EVEN 10 HOURS A WEEK.

I was doing more than them when I was a mere junior.

Fuck whoever invented caramel and chocolate and particularly whoever mixed them. How am I supposed to stop eating this? It so fucking delicious.

I got assigned approximately 20 tasks, all are high priority.

Coworker got assigned 2 tasks, (“like fix button sizes and padding”, “localisation “)

He completed.

I got questioned: “are you sure you are a senior developer? Are you doing your work at all? If your coworker can finish low priority tasks in a day , why you as a senior can’t? “

Me :”if you have the ability to see , please tell me how many tasks I have that are in high priority.”

“Exactly, I need you to complete it now , I expect more from you as a senior. “

Me: “why not you tell me which tasks are higher priority? Because can’t be all are urgent. If everything is urgent , nothing is urgent.”

“Stop giving excuses, be a team player.”

Me :” how is it making excuses for asking urgencies of the tasks?”

“Hahaha you called yourself a senior. What a joke”

Me:”likewise, you called yourself a Project manager yet can’t manage. What a joke indeed.”

Windows 10 had one groundbreaking UI innovation, but no one adopted it and even Windows 11 discareded this revolutionary idea:

BUTTONS NEXT TO EACH OTHER AND AT THE EDGE OF A BOX DON"T NEED AN ADDITIONAL MARGIN

Windows 10 was the first and last OS where I never accidentally clicked right next to the X on a window, in a passive area that had no other purpose so it might as well have belonged to that motherfucking button.

I passionately hate this trend, adopted nowadays by every OS, that everything needs to be rounded, separated from the things around it, and "allowed to breathe". They don't breathe. They're not alive. They're fucking UI elements and the space between them is unused, lost space.

The only interaction a button has with its surroundings is that it pushes other content away to make room for itself and responds to the cursor. It doesn't wiggle, it doesn't grow and shrink, and it ESPECIALLY doesn't fucking breathe. Please, just let me click the motherfucking button.

Relatedly, do you know of a good, preferably bluish dark GTK theme that provides window decorations that stretch the full height of the titlebar and are laid out next to each other at the very end of the bar without gaps?

now a funny thing that happened to me a few weeks ago:

a recruiter contacted me on linkedin... wait, don't laugh yet, that's not the whole joke (this time)...

...asking whether I'm interested in something, I was like yeah, but I'm looking for part-time because i'd like to not have a mental breakdown after 6 months this time...

her response: "well... I don't have any part-times, but I have an almost part-time..."

" 'almost part-time'? first time I've heard that phrase, what exactly does that mean?"

"it means about 160 hours"

... i sit in confused silence for a bit, then write back as I calculate: "i'm assuming you mean 160 hours a month, which is 40 hours a week, which is 8 hours a day, which is full-time. please point out where am I mistaken."

recruiter: * crickets *

An old company contacted me, seemed remorseful and said I probably didn't want to work there again but kept pushing. Eventually he said a high salary and I figured ok they had easy projects and the overpaying would beat the underpaying they did while I was there, right?

The new lead dev at the place took a month to give me work, tried to pressure me by saying she was going to tell management they are behind because of me, and then progressively stopped assigning tickets to me and assign-then-reassign them from me according to my schedule/predictions I revealed during the daily stand-ups. Why hire me at all. Then they said they changed their business direction at 3 months and let me go. What a waste of everyone's time.

My company’s code base is so messy that the dev branch and master branch is so buggy. But they put the blame on me as usual.

I use git blame, I wasn’t the author .

Ticket: Add <feature> to <thing>. It works in <other things> so just copy it over. Easy.

Thing: tangled, over-complicated mess.
Feature: tangled and broken, and winds much too deep to refactor. Gets an almost-right answer by doing lots of things that shouldn't work but somehow manage to.

I write a quick patch that avoids the decent into madness and duplicates the broken behavior in a simple way for consistency and ease of fixing later. I inform my boss of my findings and push the code.

He gets angry and mildly chews me out for it. During the code review, he calls my patch naive, and says the original feature is obviously not broken or convoluted. During the course of proving me wrong, he has trouble following it, and eventually finds out that it really is broken -- and refuses to admit i was right about any of it. I'm still in trouble for taking too long, doing it naively, and not doing it correctly.

He schedules a meeting with product to see if we should do it correctly. He tells product to say no. Product says no. He then tells me to duplicate the broken behavior. ... which I already did.

At this point I'm in trouble for:
1) Taking too long copying a simple feature over.
2) Showing said feature is not simple, but convoluted and broken.
3) Reimplementing the broken feature in a simpler way.
4) Not making my new implementation correct despite it not working anywhere else, and despite how that would be inconsistent.

Did everything right, still in the wrong.

Also, they decided I'm not allowed to fix the original, that it should stay broken, and that I should make sure it's broken here, too.

You just have to admire the sound reasoning and mutual respect on display. Best in class.

Is it done yet?

Stop micromanaging! We are providing updates every morning, what difference does it make to ask for the update in the evening?!? Don't think no one can see that all you are asking is "is it done yet?"

Like a small child who does not understand the concepts of travel yet, you won't understand why "such a small change" takes so long. It's because we are scooping all the crap, patched by assholes who cared only to please you and did not had the courage to say no to your pressure and do things smart way.

If you think it is necessary to keep reminding everyone to do their job - then you you do not belong in IT.

Our parents keep reminding us about the time change that happens every half a year. To remember that the clocks need to be adjusted. And we, the children, keep reminding them, that most devices are already connected to the internet and use the time servers for reference. Which surprises our parents every time. 🙃

I used to think that I had matured. That I should stop letting my emotions get the better of me. Turns out there's only so much one can bottle up before it snaps.

Allow me to introduce you folks to this wonderful piece of software: PaddleOCR (https://github.com/PaddlePaddle/...). At this time I'll gladly take any free OCR library that isn't Tesseract. I saw the thing, thought: "Heh. 3 lines quick start. Cool.", and the accuracy is decent. I thought it was a treasure trove that I could shill to other people. That was before I found out how shit of a package it is.

First test, I found out that logging is enabled by default. Sure, logging is good. But I was already rocking my own logger, and I wanted it to shut the fuck up about its log because it was noise to the stuffs I actually wanted to log. Could not intercept its logging events, and somehow just importing it set the global logging level from INFO to DEBUG. Maybe it's Python's quirk, who knows. Check the source code, ah, the constructors gaves `show_log` arg to control logging. The fuck? Why? Why not let the user opt into your logs? Why is the logging on by default?

But sure, it's just logging. Surely, no big deal. SURELY, it's got decent documentation that is easily searchable. Oh, oh sweet summer child, there ain't. Docs are just some loosely bundled together Markdowns chucked into /doc. Hey, docs at least. Surely, surely there's something somewhere about all the args to the OCRer constructor somewhere. NOPE! Turns out, all the args, you gotta reference its `--help` switch on the command line. And like all "good" software from academia, unless you're part of academia, it's obtuse as fuck. Fine, fuck it, back to /doc, and it took me 10 minutes of rummaging to find the correct Markdown file that describes the params. And good-fucking-luck to you trying to translate all them command line args into Python constructor params.

"But PTH, you're overreacting!". No, fuck you, I'm not. Guess whose code broke today because of a 4th number version bump. Yes, you are reading correctly: My code broke, because of a 4th number version bump, from 2.6.0.1, to 2.6.0.2, introducing a breaking change. Why? Because apparently, upstream decided to nest the OCR result in another layer. Fuck knows why. They did change the doc. Guess what they didn't do. PROVIDING, A DAMN, RELEASE NOTE. Checked their repo, checked their tags, nothing marking any releases from the 3rd number. All releases goes straight to PyPI, quietly, silently, like a moron. And bless you if you tell me "Well you should have reviewed the docs". If you do that for your project, for all of your dependencies, my condolences.

Could I just fix it? Yes. Without ranting? Yes. But for fuck sake if you're writing software for a wide audience you're kinda expected to be even more sane in your software's structure and release conventions. Not this. And note: The people writing this, aren't random people without coding expertise. But man they feel like they are.

A personal memo to all developers on devRant:

* Assume every external line of code, (including every service you consume) is an unreliable crock of flaming shit. These services can and will fail in the most glorious ways. Write your code to be resilient, and ASSUME FAILURE of dependencies. Even if it's your own team writing the other service.

Heard in a meeting today: "Your team's service outage is going to cause my service to corrupt the database!"

Response I wanted to give: "No, you asshat, my service outage is a normal part of living with microservices. Your app should have been smart enough to recognize the failure."

Seriously guys, how do you deal when remotely collaborating with lets say not the most motivated and competent devs?

Our scrum team got formed about 6 months ago from leftover devs of other teams, choosing a couple competent devs at the core and other devs who were kinda gotten rid of by their old teams, and after 6 months of working together I can see why.

Situation is that we are 7 devs in our team and 4 of devs are not pulling their weight. They are seniors on paper, but in reality not really.

They rarely take something complex to work on and even if they do, they make sure they take as much time as possible. Two of them are contractors who I imagine decided to treat the job as a paycheck and nothing more. There is no initiative, no push to make things better and in general attitude is to do bare minimum: only what is being asked and then delaying the hell out of tasks.

Im not exaggareting: Im talking about every possible way of dragging out the tasks: delaying communication, sitting around for a few days while not asking for new tasks to work on if they are blocked, also avoiding standups. Working for days on very basic comments in their MR's. Getting "sick" for a couple days on deadline when things get tough, so that someone else would come in, refactor and save the day. Once or twice it could be a coincidence, but nowadays I can already guess ahead of time what kind of trick they will pull now.

Our project is an android app where we have to support few different tablets, so the most recent new trick that I witnessed is devs avoiding hardware delivers, sometimes for months. Idea seems to be if you dont ping your team that you dont have hardware, then you can avoid working on related tasks with that hardware.

Worst part is that they get away with it. Our teamlead is a senior dev who is first time teamlead, doesnt code anymore and doesnt want to rock the boat. He is the type of teamlead who sets arbitrary deadlines, makes it sound that they are urgent and takes a few days off in the middle of chaos just before deadline. Restrospectives don't help at all and if I try to bring up stuff directly to him he tells me to bring it up during retrospectives. We discuss issues, rant a bit ant then continue carying on like nothing happened and nothing changes.

So little by little in the past 6 months we came to this point where 2-3 devs are carrying the weight of the team and are in a constant crunch mode, while others are allowed to slack. Its becoming ridiculous.

Problem is that this is starting to affect our morale. Only way that is left to keep my sanity right now is to pull away sometimes and also slack. Then I come back at full capacity, give my best for a couple weeks until I have to go and fix some basic leftover task that has been purposefully dragged out for 2 months and left unfinished, then I just want to scream and I know that its time to disconnect again.

Junior engineer asking managers on Slack about prioritisation..

Junior eng: Hey managers, I have these tasks A & B lined up and some other type of work... Is it ok if I finish A by Weds and B by the end of week or should it be done sooner? Also, is the order fine or should I prio B first?

*silence for hours*

Random dev feeling bad for junior getting no response chips in: Hey, you are doing great, that order makes sense to me and let me know if you need any guidance or have questions!

Junior dev: Thaanks and will do!

*another hour goes by*

Manager: Hi team. I have asked other engineer X to do task B tomorrow.

what the fuck. at least answer the fucking question and say it needs to be done sooner. felt bad for poor junior here. :/

In flutter , there’s something called TextButton.icon. Which render a button look like this :

(👍🏼 Like Button)

But there’s this tiny twat decided to use countless of nested column in a nested row and containers just to create a fucking button! This particular class contains 1438 lines of code! Most of the code are redundant and nested fucking shit.

I want to punch this guy so hard but I do not intend to start a ww3 with china.

That means I have no choice but refactor it as I implement a feature requested by the product team, every components break. It is like a land mine field here. One changes , the entire application crash.

So there are useless mother fucking Sherlock fucking holmes kept telling me that “don’t worry about refactoring now , just complete the task.” , like seriously “how in the name of mother fucking god of all arseholes can I complete my task when I can’t change even one component?”

These people are fucking genius. Their intelligence resurrected Einstein and made him die the second time.

first off, they've defined (just yesterday) FOUR (not ONE) features to be done by the end of the month (yes really no joke, i mean _this_ month, as in october, i.e. they mean by monday)

four of them still have "to be defined" labels

so, what, you guys gonna define those today so we have uh.... all of friday to do them?

🤡🤡🤡🤡🤡🤡

Having just endured 30 excruciating minutes of utter braindead idiocy that is trying to setup and configure WPA2-Enterprise on a Windows 10 machine, I wanna go and fucking kill myself.

How can it be so bad after so many years this protocol has been out?! Not only can the authentication options be changed only in the who knows how many years old control panel settings and not the modern settings app, but once you finish setting up the network, you can no longer modify some of the key attributes like which CA certificates to validate the radius server against!

What. The. Fuck. Microsoft.

I swear, I don't usually get my jimmies rustled at work, but this... This just bloody infuriated me!

I hate people who think that building software is all about one click away and generating things. I got told to complete the task faster than the speed of light.

Fancy me some rant time? Let's name that cunt, "Bob".

"
Hey Bob, I got questions for you. Are you sure you were in your mum's womb for 8-9 months? Are you the kind of twat who honk at people as soon as the traffic light's turning green?

Building software takes time, the CI/CD takes time, TestFlight takes time, approvals from the Google Play store take time, approvals from Apple App Store connect take time, Unit testing takes time and every fucking thing you can name takes time!

It's just like sex, nobody wants to be with someone who can only last in bed for 0.000000000001 nanoseconds, the longer, the better, (but not too long).

It is also like building houses, which takes months to build not hours. As from my experience so far, something tells me that you are not the kind of person who would understand how to build a house but a sand castle which takes only hours to build.

Relentlessly, you bombarded me with a pile of bollocks and a pile of nonsense is not going to fasten up the compilation of the software.

"

managers: We're all aligned! Let's work as a team and get this started!

devs: ok...

managers and devs meeting to discuss next features: * canceled by managers *

managers: (word for word, can't make this shit up) we cancelled the meeting, we will define the roadmap for everyone

> WE will define the roadmap for EVERYONE

devs: uh wtf???

one hour later, managers: guys we are defining the roadmap can we have a call to discuss?

fucking asshat, insolent, disrespectful pieces of shit