I got in trouble for refactoring code to be modular. They said “thats too complicated the maintenance team”.

Said coworker produced a kludge of copy pasted code so the dumb ass maintenance team could understand it.

tldr; interfaces and abstract classes are too advanced for our employees so make the codebase shitty on purpose.

Open source is poison, hoax and source of much troubles.

Even as I love OSS, and I use it a lot, when things go south, they go south terribly.

There was "security" updates in one OSS program I have been using, that accidentally prevented use cases which specifically affected me. I raised bug report, made issue and gave small repro for it.
One of the core developers acknowledges that yes, this is problem, and could be handled with few added options, which users of similar use case could use to keep things working. He then tags issue "needs help" and disappears.
After I have waited some time, I ask help how I could fix it myself, like how to setup proper dev environment for that tool. Asked it in their forums few days later, as issue didn't get any response. Then asked help in their slack, as forums didn't get any help.

Figured out how to get dev environment up, fix done (~4 lines changed, adding simple check for option enabled or not) and figured out how to test that this works.
I create pull request to project, checking their CONTRIBUTING and following instructions there. Then I wait. I wait two weeks, and then one of the core develors goes to add label "needs response from maintainer". That is now almost two weeks ago...

So, bug that appeared in October, and issue that was created October 8th, is still not fixed, even as there is fix in PR for 28 days this far.

And what really ticks me off? People who make statements like: "it is OSS, have you thought of contributing and fixing things yourself?" when we run into problems with open source software.

Making fix yourself ain't biggest problem... but getting it actually applied seems to be biggest roadblock. This kind of experiences doesn't really encourage me to spend time fixing bugs in OSS, time is often better spend changing to different tool, or making changes in my own workflow or going around problem some kludge way.

I try to get business starting, and based on OSS tools. But my decision is staggering, as I had also made decision to contribute back to OSS... but first experiences ain't that encouraging.

Currently, OSS feels like cancer.

Every once in a while the volume for my default audio output decides to max out on login. How this can happen is apparently a mystery. Other than its a shitty OS called Windows 11. Windows 10 never did this shit, or if it did it was fixed quickly and never did it again. So there is always a non-zero chance of logging into windows and getting ear raped if you have headphones when playing any audio.

Enter SetVol.exe. Apparently open source and can be run in a batch script. So now I have this kludge of every time I login a task is run to call my bat file to fix this garbage. This is the worst case of quality control I have seen in any supported product. Not a single MS helper in any channel online has had a good fix for this. This is a fundamental design issue in how they handle volume settings. Absolute garbage.

Everyone from ma and pa to audio engineers are screaming about this. How? How does it get this bad?

tfw you have matured enough as a developer to look at old legacy code (some of which you contributed to) from a hacked together UI Frankenstein kludge and immediately you notice all the security flaws.

How fortunate there is strong query param validation going on...otherwise this would be a veritable shit storm.

new Confession(new Rant()).admit("My kludge bit me in the ass. But If I make a series of classes that encapsulate (hide) the awful hacks, one day I can replace the hacks with nice code. This is why I say I love refactoring. But right now, procrastination looks ugly.").asRant()