The Tale of Mouse and Watch

Once upon a time, a mouse wanted to know what time it was. So it asked the first guy who came along, but it didn't understand Suaheli. Anyway, he just had mumbled, gotta kick the cat in its lazy ass.

So the mouse moved on and nearly got it when it met another mouse who bad been sewn to a dead elephant's ear exactly 27 years ago - but unfortunately, it had forgotten the time of day when that had happened.

The seeking mouse came up with the idea of doing something with the sun, but since it was only dumb mouse, it looked right into the sun and was blinded.

Now pretty desperate, it tumbled through the gutters that were full of trash. Accidentally, it fell over a dumped watch, and the mouse broke its nose.

The lesson: sometimes, even a blind mouse may find a broken watch!

Here we are, three years later. Our system breaks down at the slightest load. An architecture is hardly recognizable anymore. The code consists of methods that have been refactored beyond recognition. The so-called architects came and went, leaving behind an ever-growing fiasco. Wrong decisions are concealed, criticism of them dismissed as ignorance. Our clients are on the verge of having us all killed. Daily crisis meetings are the norm. The remaining developers skulk around the unmaintainable code like emaciated ghosts. Everyone who has even the slightest chance to escape takes a parachute. Our dailies are made up of lies to cover up yesterday's lies. Our Mondays have become days of dread, because that's when the weekend disaster news has to be analyzed. Yet there are still developers who turn a blind eye. Who recommend this and that workaround in a good-humored tone. The code consists only of workarounds. Sarcasm has replaced any normal discussion. Reasonable suggestions on how to basically refactor the whole thing are rejected for cost reasons. In the process, our entire budget is eaten up by maintenance costs. Middle management should be put up against the wall. Why am I still here? This deceptive feeling that one could still turn the tide. This is eating me up.

I love how stupid idiotic shit companies think their bullshit email spam abuse works. Hell no fuck off blind monkey fuckers. You sick fucks makes me sick. The only thing i hate more than normal company spam is when your shitty company (in this case Sound cloud) begs for money. Just because a meme of a platform like that that was only used by people to find leaked songs got bought by some shitty investment company. You will have to be the biggest idiot that has never existed to buy "premium" on a clear ineferrior platform that is clearly a joke compeared to serious music platforms.

But hey thank you for remining me to remove my accounts you begging rats. Hope nobody is dumb enough to support your shitty platform.

How many years experience as a dev do you need to feel like the cool hacker guy in the movies instead of a blind monkey trying to play the violin for the first time?

How do I deal with this;

Edge case hiccup on production, no errors in the available logs(very shallow logging), no access to the production server, issue unreproducable on staging and a manager that want me to fix it AFTER I already said that im kind of sailing blind and can't do much without logs or access, and already looked at it with another dev who also has no idea what is going on