this is why open source?
Bro that reminds me when I was in university and I used to tutor fellow students with the goal of getting laid. As soon as I got laid I stopped tutoring. Now unfortunately I’m married and have kids because of that.
It’s an excellent tactic.
wat
He tutored girls with the hopes of getting laid, but then when he did, it turns out he liked her and settled down with her and is now married to her.
Ohhhh for some reason my mind went to him trying to tutor other dudes to help them with women. Was very confused.
You guys ooze heteronormativism
You ooze self-righteousness.
The original commenter @cumskin_genocide@lemm.ee did neither specify their own sex nor the gender of the people they tutored.
Multiple people under that comment simply assumed that OP is male and was tutoring girls. That is heteronormative. Yes, I formulated that with a bit of snark. But come on.
But come on.
Unironically, no u.
You read what you read
pooping cough was confused by cumskin genocide.
the guy who contributed to proprietary software
Maybe the guy is content where he was, asks just wanted to fix that bug
That screams: Open you source code and accepted correction !
It screams made-up internet story.
It screams both!
Let the patch be part of the code for one or two minor releases. Then revert the changes of the patch.
Calm down, Satan
Why would they do that? Talk about generating mistrust.
Rehire obv.
Good luck with that lol. Who would fall for that.
It may not be malice. Incompetence.
They are going to “accidentally” remove a fix?
By not understanding how version control works. I’ve worked at places that had a surprising number of developers who would just merge things in ways that drop code from other developers.
Can you give an example how that would happen?
It’s pretty straightforward. Merge conflicts? No such thing! Just make my version the next version.
Also that’s likely a team that doesn’t use a branching workflow, has poor review on merges, and/or using Git like it’s SVN.
I dunno, but it’d be funny
Everything is open source for this guy after using this simple trick. Big techs HATE him!
More like source available, since you can’t use the code in your stuff without the permission of the company 🤓
Imagine getting a big enough resume to get jobs at any company just so you can do this one neat little trick.
Honestly, anybody with a gender studies degree can get into software developer nowadays no sweat, nowadays the fortune 500 standards are so low that they’ll just hire anyone on the spot without even questioning it. Honestly only started to take note of this the second Biden got into office, the quality of software overall has gone down. Overall, back to open source, I never truly got the open source movement in general, never been my thing. Proprietary software is inheitly more secure which is why most enterprise systems still use windows xp.
G8 B8 M8
I kept reading waiting for the punch line, didn’t see one. I think I’ve fallen victim to Poe’s law. I legitimately can’t tell if this is satire.
NGL I apply to places where I use the software. But it’s not one thing, it’s a dozen things I would fix.
I actually never successfully got the job. Probably because during the interview, I come off like a rambling psychopath pointing out extremely specific things.
Part of my previous company’s hiring process included having the candidate use our software, then asking what they thought of the experience and what improvements they thought would have the most impact. It wasn’t entirely useful because devs weren’t in control of prioritizing changes, but it was always interesting to see which pain points stuck out to the candidate.
This strikes me as a really good idea… If they come up with batshit insane things, or obviously can’t click straight, it’s a good indicator.
It does give some insight into how people think. Some people are bothered with UI events and placement, others wanted to reduce the bandwidth it required, we had one girl who approached it focused on the accessibility of the software, and unfortunately for us support was abysmal. You also need thick skin to invite random joe off the street to tell you how your software sucks.
ESR: “Every good work of software starts by scratching a developer’s personal itch.”
inb4 they wait until his last day then roll back the changes because functional code/unauthorized changes are against company policy and actually they need that bug to slow down the user so they don’t click so fast the database crashes.
Oh, you cynical (and probably right) monster. Cheers!
Repost #357
That happened.
He finally won the war after so many battles.
It seems like I’m constantly finding bugs in businesses’ apps. Do they not have people test them?
They do, and they have a backlog of hundreds of issues to fix and they must prioritise then. If fixing a bug doesn’t make money, it’s not priority.
I am steadfast that I will occasionally take some time and kill off some low hanging fruit. For me, its kind of like a break and lets me clear my head on the bigger issues.
Even then, there are bugs that need multiple people (design, engineering, content, QA, etc) and are not something that can be fixed on a whim.
Those would not be considered low hanging fruit.
The problem is that what users consider low hanging fruit is often not, and what is low hanging fruit for devs, is invisible stuff that users don’t notice. The intersection is the tastiest low hanging fruit, but as such it’s also rare and easily picked by anyone.
I deal with this every day. It hurts me to my core.
I hate how they’ll spend 4 years squashing all the bugs…and then they cancel the software, and release a new buggy version.
i will never forgive the emby team for creating the single most idiotic (although rather funny) transcoding system.
It has a resolution selection, along with a bitrate selection, so you would think it forces transcoding.
It turns out the resolution is actually just a suggestion, and the bitrate is what it targets, if it doesn’t meet the bitrate, it will transcode, and if you get lucky, it might transcode to the specified resolution.
cough Sonos
I would fix that bug but the complete rewrite that management has had me working on for the past two years will make it obsolete anyway.
They usually do yes however it’s all about prioritization.
You may have hundreds or thousands or open requests and issues.
With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.
There’s usually a feature roadmap which is where most of the development money and time is spent. If it’s an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn’t severe it’s usually deprioritized next to higher priority work.
Sometimes. Other times they layoff the QAs and anyone else whose job is about quality.
Sometimes no.
sure they do, you’re one of them
As someone in the dev team for a “business app”, we probably know about most or all of them, but they’re just not important enough for anyone in management to prioritize them as part of a sprint. It’s also possible no one has given us reproducible steps to make them happen, so we just straight up don’t know what to fix. Usually the former though.
Yes, they’re called “customers”.
they test them…
Whether they do anything with that testing is another story,.
We are supposed to be testing them? /s
Reminds me of when my breaks started failing on my 1990 Chrysler LeBaron so I got a job at a break repair place long enough to fix them then I quit.
What needed repaired?
Pads, calibers and new discs. That seemed like a lot of money for 17 year old kid. I worked there for a couple of months. I learned a few things, like working on brakes is not for me.
I hate working on brakes. Even just replacing pads can be a pain in the ass nevermind when you have to do real work to 'em.
I try to do all the basic work/maintenance myself, but fuck brakes.
those bits on a car are called “brakes”. When a brake breaks, it’s a broken brake and needs to be fixed.
“if it ain’t brakes, we don’t fix it”
Thank you. That’s one of my little pet peeves I see online; that and when people are trying to say lose but type loose.
They’re they’re, it’ll be all right.
Don’t forget to breath
But then all the sudden everything went wrong on accident.
brakes
Lol, ya it was the breaks that I was too broke to afford brakes.
Thems the brakes
relevant
braycks
Bhrakes
And its pronounced “Brad”
I think “breaks” is appropriate if you own a Chrysler.
