I wanna fuck a certain dev with a rusty pipe that was smeared in ghost pepper chilis... hopefully they get tetanus, inflammation and an allergy shock all at once, dying a cripple painful death.

Afterwards I spike them in front of the company with the wonderful laminated piece of paper:

"The difference between being right and being dead is where that pipe took place".

Fucking numbnut discusses every meeting like they know it all - and don't you dare critique Mr High and Almighty, cause then they will discuss as long as it takes without mercy.

HR wasn't mused as Mr Almighty filed a complaint cause I kicked them out of a meeting.

Now I've got Mr Almighty and Red tape and additional meetings.

-.-

Did a backup.

Did a bulk import to a service (netbox, great tool for network documentation by the way).

Fucked it up.

Back to backup.

Fixed bug.

Fucking gerbils on ecstasy (devs) annoying the fuck out of me.

Lobotomizing meetings.

Yuck coffee. Cold, stale and over extracted.

Gerbils planning a mutiny. Killed them with a big cheese wheel (lots of stupid boring tasks as they seem to be completely missing stuff to do).

Deleted backup.

Redid import.

Small typo.

Find the mistake...

I just love it when a small task becomes a huge fuckup due to too many disturbances.

Luckily SQL UPDATE went well....

Nothing's more fun than to patch a live database.

Yeah. I didn't wanna do a new backup. :)

The "I don't give a crap mood" is sometimes a great way to accelerate tasks...

I really wanna get a keg of rum and start sailing across the globe...

Just to spank some devs / managers arses.

The last years were... very demanding regarding security and upgrades.

It hasn't gotten better.

Microsoft leaked it's security key thx to internal debugging and the tool to secure the debugging process so secure data gets filtered was buggy...

I'd guess I already have carpal tunnel after Redmond.

But the really really sad story is: This has become the gold standard.

https://lwn.net/Articles/943969/

Chrome selling the privacy mode for Ads, long topic ongoing for years... yeah they did it.

Apple... oh boy. I could write a Silmarillion about it and would still need an additional trilogy.

Amazon realizing that a Microservice architecture needs planning, cause yeah... just potting services in a data center doesn't end well.

It goes on and on and on....

Don't even get me started on the plethora of firmware / microcode updates cause there was either yet another CPU bug or another device pooped their pants cause the firmware is a mess and needed some dubious update without any background at all...

Serious question: Am I becoming a pepperidge farm uncle threatening to shoot everyone cause I'm getting old and cranky ....

Or is really everything in IT going down the drain the last few years?

It feels like every week is just another "we fucked it up" event.

Nothing's as fun as unraveling the mystery of how a certain dependency got pulled in transitively....

In a monolith.

With over 1000 dependencies.

Kinda like sorting rice by the size of each grain.

Things that make a friday entertaining.

💩💩💩💩💩💩💩💩💩💩💩💩💩💩

Things I love today.

Totally love. Like kick in the balls with testicle torsion love. Picking my eyeballs out with a spoon... I think you got the idea.

Getting updates of other managers, as I'm busy with other stuff.

More or less goes like this:

Flaky tests. Since weeks...
Ain't nobody got time for that.
🤬

I don't wanna upgrade that version to the next major version, cause then I'd have to do tests... And the tests are flaky.

🤬🤬

I wanna have shiny new thing XY, but NOONE wants to upgrade to next major version so we cannot have that

🤬🤬🤬

Oh we just crushed the live cluster cause there's this PR everyone constantly ignores cause the tests are flaky....

🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬🤬

Good thing I'm busy and just getting all the updates via the gossip mill...

I'm just prolonging my current tasks as I really don't wanna have to fix that mess.

My fix would be probably eye for eye, tooth for tooth.

...

Problem is.... I'm slowly getting into trouble because some of these fixes would be much needed for my task...

Why do I have always to be the bad cop in the company -.

I think I'm gonna ask HR what applying electro shocks would cost me, cause I think that would solve a lot of problems.

10 kV for every stupid answer.

Smells like bacon!

Opening the bag...

Stuck my nose in it. Deeeeeeep breath.

Better than sex.

Taking the scale, getting the right amount.

Feeding the grinder, thinking about whom to kill... Watching get them torn to pieces, shredded bit by bit.

Preheating the iron, getting the water up to temperature.

Filling up the espresso can, turning it on.

Boiling fresh espresso.

Nothing's sexier than the sound of the steam and the smell of fresh grinded and brewed espresso.

Good Sunday.

https://bugs.launchpad.net/ubuntu/...

Please universe, stop fucking my ass.

I'm far beyond prolapse and I really don't want your filthy surprises.

LTS my ass.

Compromise.

I think that sums up development pretty much.

Take for example coding patterns: Most of them *could* be applied on a global scale (all products)… But that doesn't mean you *should* apply them. :-)

Find a matching **compromise** that makes specific sense for the product you develop.

Small example: SOLID / DRY are good practices. But breaking these principles by for example introducing redundant code could be a very wise design decision - an example would be if you know full ahead that the redundancy is needed for further changes ahead. Going full DRY only to add the redundancy later is time spent better elsewhere.

The principle of compromise applies to other things, too.

Take for example architecture design.

Instead of trying to enforce your whole vision of a product, focus on key areas that you really think must be done.

Don't waste your breath on small stuff - cause then you probably lack the strength for focusing on the important things.

Compromise - choose what is *truly* important and make sure that gets integrated vs trying to "get your will done".

Small example: It doesn't really matter if a function is called myDingDong or myDingDongWithBells - one is longer, other shorter. Refactoring tools make renaming a function an easy task. What matters is what this function does and that it does this efficiently and precise. Instead of discussing the *name* of the function, focus on what the function *does*.

If you've read so far and think this example is dumb: Nope... I've seen PR reports where people struggled for hours with lil shit while the elephant in the room like an N+1 problem / database query or other fundamental things completely drowned in the small shit discussion noise.

We had code design, we had architecture... Same goes for people, debugging, and everything else.

Just because you don't like what weird person A does, doesn't mean it's shit.

Compromise. You don't have to like them. Just tolerate them. Listen. Then try to process their feedback unbiased. Simple as that. Don't make discussions personal - and don't isolate yourself by just working with specific persons. Cause living in such a bubble means you miss out a lot of knowledge and insight… or in short: You suck because of your own choices. :-)

Debugging... Again compromise: instead of wasting hours on debugging a problem, ASK for help. A simple: Has anyone done debugging this before or has some input for how to debug this problem efficiently?... Can sometimes work wonders. Don't start debugging without looking into alternative solutions like telemetry, metrics, known problems etc.
It could be a viable, better long term solution to add metrics to a product than to debug for hours ... Compromise. Find a fitting approach to analyze a problem instead of just starting a brute force approach.

....

Et cetera et cetera.

Stitching old frameworks / libraries together...

What a lovely joy.

An override here... Testing if it runs.

Oh lovely, shitty shaded jars.

Creating other project for shitty shaded jar.

An override here, an override there...

Oh we need some system property to unfuck JVM upgrade...

Since it's shaded, need to add overrides for the non shaded and shaded variant...

Done...

Back to framework / library....

Another override, another system property...

Its seemingly endless.

Stitching together old shit with new shit to get JDK 20 plus running.

I hate everything.

I ended today a meeting.

Was annoyed.

Did it bastard administrator of hell style.

I shut down the necessary staging machine for presentation after disabling the network service.

Of course the machine died unexpectedly and sadly we had to postpone this important meeting.

In reality this meeting was as important as hay rolling down a street.

I hate everything at the moment.

I wanna have 8 arms.

Two to rip heads off.

Two to tear people apart.

Two to wank.

Two to code.

All at the same time, best.

https://micronaut-projects.github.io/...

Micronaut never ceases to amaze me.

Compared to commons cli, the annotation based approach makes it simple.

Fat jar, easily distributable.

Modularity of micronaut, easy to pick only what you need.

I am.... Happy?

Ugh. That was a disturbing word.

The joy when tools do not have machine parseable output.

I'm looking at you SBT. My favorite pile of poo.

Remove the logging level from each line, then trim the line, then stab around inside the line with regexes, fishing for a possible match which hopefully is right...

Then stripping scala information like the object type, cause yeah...
A line can be for example "[info] Vector(File(...),File(...))" where info is the log level, Vector the wrapping sequence type, File(...) the wrapping element type and the string inside File(...) what yours truly needs.

As this is lot of shitty shabby string stabby stabby, we need to add a fuckton of boiler plate validation cause who knows what we just murdered.

To make it even more fucked up, a multi project project can produce different output for the same key.

:-)

Yeah. So we need to fix that too.

By the way, one can set log output to unbuffered in SBT.

Then the output is in random order :-)

Isn't that fun? Come on, you wanna poke that pile of shit, too.

The SBT plugin way is by the way no alternative, as I need a full Java environment for execution.

Which brings me to the last point:

For fucks sake, writing CLI applications in Java is so much bloody boilerplate code.

There's ugly and then there's the "please kill me" kind of level.

50 lines just to write a basic validation of argc / argv with commons cli.

That's 6 lines in python. Not kidding. :(

I currently hate everything.

Moments where the job sucks: When you have to hotwire two electric cables with high currency by giving both cables the blowjob of your life.

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.

Had a longer talk with a friend today.

Acquaintances of theirs were at a restaurant (!) a few days ago, complaining about how much they paid for breakfast buffet. Their rant went on how the restaurant didn't even include coffee in the breakfast buffet.

I know this restaurant. I really like it there. They roast their own coffee in the back. They have a transparent bakery with spelt flour, from certified organic farming. They support the regional farmers, even the meat for the cold cuts etc comes from a local butcher, livestock is from regional free range farming.

If you wanna know what's wrong with customers, that's the prime example.

Not only didn't they bother at all to look at the menu... They ignored at all what they paid for. Just stuffed themselves without any thought at all.

Then they wondered why the price was so high.

Of course, high price = bad, so they rant everywhere what a bad restaurant they visited.

It just made me so fucking angry, cause that's the same shit I have to deal every day with. Not giving a damn, not reading any information at all - but spouting nonsense and foul mouthing everything is okay.

Fuck those kinds of humans.

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

Python muses me sometimes.

Gunicorn has a preload mode. It enables forking...

So Gunicorn starts, when Gunicorn loaded it forks the workers (Uvicorn / FastAPI in my case).

https://github.com/tiangolo/...

So if we add a function that creates the app... this function will be executed before forking, thus the memory at the state of creating the app will be duplicated.

You can thus spawn 40 workers, they would all have the same ML models.

Or in my case a client who does some things that should only be run by a single thread (with locking).

So the client has a cache, as long as I load the cache during the create_app phase, the cache will be shared between all instances and not created per instance.

It's ... Such a small detail. So simple.

Yet completely fucks my brain.

It's logical, yes. I understand what it does, yes.

But it still makes my brain fart.

Maybe in special dedication to @kiki.

I cut the unit tests down in LOC size by roughly 50 - 60 % in most projects.

It's really easy once one sees unit tests not as a dunking pile of copy pasta wild west, but rather as a code base that needs architecture and design.

Some extensions, some annotations, some good old helper classes.

Pooooof.

Why I did this? ...

Because it's fucking annoying when you read a PR with tests and need a fucking diff tool to spot the difference between two tests cause they're 80 % the same.

Yeah. Thx for giving me brain cramps, motherducker.

I'm not an expert in unit tests, but if all test codebases look like the "usual stuff" in our projects...

It's no wonder bugs exist...

mfucking piece of garbage.

filth could be cleaned, but that mess can onle be purged by a supernova along with the galaxy.

when you explain a whole fucking week to someone that the goal is to have an adaptive algorithm that detects a version and handles different versions in an best effort principle....

YEAH.

YOU GET A LIBRARY WITH HARDCODED VERSION ENUMERATION AND NO ADAPTIVE ALGORITHM AT ALL.

For fucks sake, the stupidity of devs drive me insane.

So lets start from the beginning, best send them back to kindergarten, so they learn that a square is not a circle.

https://stefan-marr.de/2023/06/...

Fascinating.

Company has a severe lack of fresh blood.

"let's recruit everyone who has an IQ over room temperature and barely passes the mark".

Me protesting bloody murder cause I know that the idea is not just profoundly dumb, but frustration from high staff turnover takes a toll on *everyone*.

"nah can't be that bad".

Then the discussion started who could do monitoring and mentoring, so we can sort out the bad apples *quickly*.

Me reminding again that this is exactly what leads to a high staff turnover, as this is nothing else than "hire, hire - quickly fire".

Guess who won the award of being the mentor / monitor ....

*drum roll*

Come on, I know you would NEVER expect this.

Let me surprise you: M E.

Yeah. They chose the person that was absolutely against this idea...

Because that person is "most qualified for the task at hand and has the necessary qualifications".

Today was the first 4 h workshop with a new recruit.

The Lord has had zero mercy on me.

I started to mute myself after 30 minutes in regular intervals to just scream and curse the world.

How profound dumb a person can be amazes me.

Person has had a "very expensive 6 month boot camp course".

I was close asking if the boot camp course was in watching porn and wanking their brain cells out....

Git... Yeah he knew what he was doing...

Except that he messed up every commit by either not sticking to the companies format or - what I found funny the first 2 times, then not so much anymore - just writing a git commit message like a 15 year old teenage girl would write to their diary.

Programming. Oh yeah. He should be a programmer.

He had much Bootcamp.

Bootcamp expensive. Bootcamp good.

If someone is unable to iterate over an iterator... And instead starts creating an integer based array of a map's key name to then fetch the map value in an for loop based on the created key array.

Yeah. Bootcamp much good.

Creating DTOs...

It took an hour to write a DTO with him... Cause constructors are hard and it's even harder when you have to explain primitive datatypes in Java, null safety, constructors, NPEs, final, ...

Like really no experience at all.

The next week's will be amazing.

Either I get a valium drop or I'm gonna blow my head off, cause mentoring will drain the last bit of hope I had left in me.

Note that I do not blame the recruit (yeah he's dumb. But he has ZERO work experience, so it's not unexpected), I'm just too fed up with getting the poo crown despite being against the whole process.

I think the recruit could make it..........

But that I got the shittiest job ever is really haunting me.

I dunno how I survive the next weeks.

And this is just the first recruit... There will be more.

Mother fucking cunts should be shot into the sun...

It's worse enough when you have to deal with many things at once...

But how the fuck can 3 people from 3 different teams have the same bullshit idea to disturb a meeting and just start talking like it's the most normal thing.

YEAH. INTERRUPTING MEETING AND JUST BLABBERING ON AND ON...

Then fucking laughing how funny it is.

Upper management found it absolutely not funny.

Working from home prevented a mass murder today.

This week is the week of planning ahead for the whole left year upto beginning of next year.

My tongue has muscle soreness, my brains gyri are straightened out, my throat is hoarse... And talking really feels like licking a cactus.

I. Hate. Talking.

Just one more day with 8 hours of meetings.

*drools*

Level of fuckity fuck mood.

After changing dozens of build plans in Bamboo, the build system of poo...

How to verify that nothing has gone wrong?

Poking the database, you'll be surprised that Bamboo stores the buildplan definition as XML.

Another surprise: Some of the keys / values have typos.

Yeah. You read that right. There are typos inside the XML...

Now together with Postgres, we can use XPATH and have some fun.

UNNEST(COALESCE(XPATH('/configuration/buildTasks/taskDefinition[userDescription[contains(text(),"Bleep")]]', build_definition.xml_definition_data::xml)::varchar[], ARRAY['']))

Lovely wrapping via coalesce for some null safety.

Now we get da task definitions for fields having user description text containing bleep.

Wrapping it in two REGEXP_REPLACE to strip out stupid identifiers....

REGEXP_REPLACE(REGEXP_REPLACE(...., '<id>\d+</id>', ''), '<oid>\d+</oid>', ''))

Then wrap that in MD5.

Boom. Lots of MD5 sums to help you identify if the configs are identical for a task or not.

Now wrapping that in another select to group by the MD5 and filter out the non identical ones.

I hate it how sometimes one has to seemingly do a full 2 hour dance for something as stupid as validation.

I'm pretty glad though for XML and XPATH.

Cause otherwise that would have been a whole can of worms I don't wanna think about....

A bit longer rant, somehow triggered by the end of this rant:

https://devrant.com/rants/7145365/...

The discussion revolved around strpos returning false or a positive integer.

Instead of an Option or a Exception.

I said I'm a sucker for exception, but I'm also a sucker for typing.

Which is something most languages lack - except the lower level ones like C / C++.

I always loved languages which have unsigned and signed types.

There, I said it... :) I know that signed / unsigned is controversial, Google immediately leads to blog entries screaming bloody murder because unsigned can overflow – or underflow, if someone tries to use a -1on an unsigned integer.

Note that my love is only meant for numeric types, unsigned / signed char is ... a whole can of insanity on its own.

https://phoronix.com/news/...

If you wanna know more.

Back to the strpos problem, now with my secret love exposed:

strpos works on a single string, where a string is a sequence of chars starting with 0.

0 is a positive integer.

In case the needle (char that should be looked up in the string) cannot be found in the haystack (the string), PHP returns "false".

This leads to the necessity of explicitly checking the type as "0" (beginning of string, a string position)... So strpos !== false.

PHP interprets 0 as false, any other integer value is true.

In the discussion, the suggestion came up to return -1 if a value could not be found – which some languages do, for example Scala.

Now I said I have a love for unsigned & signed integers vs. just signed integers...

Can you guess why the -1 bothers me very much?

Because it's a value that's illogical.

A search in a sequence that is indexed by 0 can only have 0 or more elements, not less than zero elements.

-1 refers to a position in the sequence that *cannot* exist.

Which is - of course - the reason -1 was chosen as a return value for false, but it still annoys me.

An unsigned integer with an exception would be my love as a return value, mostly because an unsigned integer represents the return value *best*. After all, the sequence can only return a value of 0 ... X.

*sigh*

Yes, I know I'm weird.

I'm also missing unsigned in Postgres, which was more or less not implemented because it's not in the SQL standard...

*sob*

A colleague of mine had to debug performance problems in a foreign, proprietary application that is ancient.

To be crystal clear: Only reason that thing exists is because some old geezers fear change.

Asked me for help cause it's an _ancient_ MS SQL server that is luckily running on hardware owned by us.

Finding the credentials was already a funny task.

We had to access the vault (not joking here, we have a physical vault for storing sensitive data and critical backups), grab a folder and find the necessary data cause no one ever dares to touch that thing.

The application is btw for a sort of ERP / inventory system that is used in some ancient shops not yet migrated...

Yeah. Story speaks for itself.

Anyway, after dusting off ourselves, we were able to connect.

Was a bit ... Interesting. Everything's in german. The worst kind of german.

After looking at the first tables, I started giggling.

My colleague knew immediately that this was a sign of danger (insert Simpson meme here), raised his eyebrows and asked "How bad is it....".

Me, still giggling, "lemme take a further look, this is gold".

*long sigh from the colleague*

Well... It ended with me putting my hands in front of my eyes, turning around and saying: "I cannot look at it anymore, it hurts too much...."

To summarize:
- German table names
- When a table exceeded 300 plus columns, they added another table with the same plus suffix "_ddd"… where ddd is an zero filled integer sequence like 001
- To join this mess, they created views... Named "generator" - Sequence Number ... Some had the beginning of table names appended, which doesn't make it less confusing.
- the process list was listing queries running longer than 5 mins.

Which isn't at all surprising when generating carrtesian products of N tables with left join.

I've seen shit.... I've seen a lot of shit.

But that shit scared me.

Other build tools:

Here is a plugin, use it . Be done.

Scala Build Tool aka SBT:

Build your own plugin.

Everything is scala...
You can create by the way funny endless loops when using the wrong syntax - yet it might compile successfully. And then when you load the plugin, it works. Till it is evaluated - lazy evaluation for the fun.

Error messages are at best cryptic.

*If* you manage to get a working plugin and *if* it runs...

Surprise. Surprise.

You might need to parse the log output of SBT.

Another funny surprise: Log output isn't configurable. You can configure the log level. That's it.

So after a lot of pain stakingly putting together a fucking shitty plugin, you can now grind the rest of your brain with ...
sed.

Cause yeah. You can now use regex to parse an sbt build log and extract the necessary information.

:)

...

So....

Are we there?

Mwahahahhaa.

Only if you haven't forgotten to either disable colored output for SBT... Or take an extra mile with e.g. less -R.

Otherwise you have ASCII control characters in your file. :-)

After getting that shit to work, you now have finally a parseable build log.

Just took days instead of hours.

But that's SBT. :-)

You all need it.

Today is not a day for pancakes.

Today we need waffles.

Fresh warm waffles. With strawberries.

How resource calculations for software services like code analysis, monitoring, etc are done:

Opening fridge, putting all the beer one can find in it.

Opening the necessary tools, e.g Excel, Accounting software, ....

Drinking the first beer.

Starting to aggregate the monthly costs - cause you can never trust the reports written by someone else...

First beer poof.

Looking at the monthly cost, adding columns "Intended use", "Actual usage pattern", "Usage factor"...

Opening next beer...

Usage factor is btw a factor of 0.1 ... 1.0 - to give an estimate how much the products feature are actually used, for further analysis if the invest is justified or not...

Oh. Another half bottle gone...

Filling in the columns...

Oh. Bottle empty and the next one toooooooooooooooo...

*burping*
*cracking finger joints*

Now let's get to the sad part...

Next worksheet, adding infrastructure costs...

Cost and description as columns.

Hehe. Column sounds like gollum.

Another beer...

Ugh. Need the paper reports, manually typing off things for stuff that was e.g. tax deductible.

Many beers die during this task. Poor little beers, dying for such an boring and mundane task...

SUM is a real useful function. I don't think I can add numbers anymore.

Now we can add another sheet.

Hehe. Sheet sounds like shit. And yes, everything in this file is shit.

Summing up costs from both sheets and including the cost factor from 1
... Beeeeeeeer Beeeeer beer we need more beer here... Beer beer beer...

Where was I. Oh yeah. Cost factorization total vs effective.

Why do I want to get even more drunk.

Oh yeah. Most software is completely underused and the costs aren't justified.

Let's add some colored highlighting ...

Uuuuh. ,Too much red. Better change the highlights.

Too much red.

More beer.

Don't give a fuck.

Hm.

Time for some whiskey.

What else is there to do....

Oh yeah.

Diagrams.

The bloody wankers from accounting need diagrams as numbers are too boring.

Not that everything in accounting is boring, no matter how much you paint colors on it... *sigh*

Hm. More whiskey...

Hehe. Whiskey rhymes with frisky.

Uff. Now just need to write mail. Mail mail mail....

"Copy paste the last mail from last month"

Hm.

Ah.

*sipping whiskey*

Spell check extension - to the rescue.

Thesaurus *burps*.

Let's change a few words here and there... Maybe another paragraph there.

Uh....

Trying to attach file...

*fucking mouse is pretty constantly crashing into empty beer bottles*

Done.

Damn.

Need to press send button.

*Creating mess on the desk by just randomly crashing the beer bottles*

Done.

*Pressing computers power button*

Mwahahahaha. No mouse needed.

*regretting to stand up too quickly, nearly barfing on the floor*

Couch ... Where Couch...

After hitting several doors, frames and other stuff, the glorious mission ended successfully with a most graciously executed gut buster on the couch.

(Regretting next morning to have emptied two 6 packs and a few glasses of whiskey)

I love to work on very small, but completely retarded shitty projects.

It's just satisfying cause the projects are dead as fuck, only kept alive because the migrations still take too long...

Most of them only work entirely correct when all stars align, Nostradamus raises from it's grave and fulfills the prophecy of world end.

Joke aside, they really only work under very specific constraints....

.......

😈

So no one gives a damn when you just reformat the whole project, making it less of a diarrhea infested mess....

Plus add some much needed sanity by throwing refactoring fission bomb in it.

Still not works entirely correct...

... But it looks way sexier. :)

Small things that count... XD