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's an old joke.
Let the patch be part of the code for one or two minor releases. Then revert the changes of the patch.
It may not be malice. Incompetence.
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.
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.
What's the product and what's the field?
Soda and soda accessories.
I'm a Bev tech, there's two companies that make bar guns, tapright and multiplex aka wunderbar. There's more options for fountain dispensing but most of my work is bars and restaurants.
Also AMA about soda dispensing at bars.
Windows
Have you heard of Digg?
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.
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.
they test them...
Whether they do anything with that testing is another story,.
We are supposed to be testing them? /s
you already are smh, you just don't know it!
Ah, the circle of life
Sometimes no.
Sometimes. Other times they layoff the QAs and anyone else whose job is about quality.
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.
those bits on a car are called "brakes". When a brake breaks, it's a broken brake and needs to be fixed.
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
*alright is the wrong word you meant to use there to rile someone up. "all right" is technically correct, and you'll want to avoid that.
brakes
I think "breaks" is appropriate if you own a Chrysler.
My dad has a TC Maserati (Chrysler labaron) and it's "breaks" just recently stopped working for no reason, so very accurate
Thems the brakes
braycks
Bhrakes
relevant
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.
Sheeeeit I'll do your brakes for you. Brakes is easy and satisfying.
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.
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.
Same.
Wow, what a bro. Where was this guy when I was in school?
::re-reads comment and thread::
Oh. Yeah, that one's on me. That makes a little more sense.
You read what you read
It's an excellent tactic.
He finally won the war after so many battles.
this is the first real 100x developer.
I thought that buffoon was out of my memory Everybody Loves Eric Raymond
@programming.dev
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
go to feed...
@programming.dev
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
go to feed...
Everything is open source for this guy after using this simple trick. Big techs HATE him!
save