I have to let it out. It's been brewing for years now.

Why does MySQL still exist?

Really, WHY?!
It was lousy as hell 8 years ago, and since then it hasn't changed one bit. Why do people use it?

First off, it doesn't conform to standards, allowing you to aggregate without explicitly grouping, in which case you get god knows what type of shit in there, and then everybody asks why the numbers are so weird.

Second... it's $(CURRENT_YEAR) for fucks sake! This is the time of large data sets and complex requirements from those data sets. Just an hour through SO will show you dozens of poor people trying to do with MySQL what MySQL just can't do because it's stupid.

Recursion? 4 lines in any other large RDBMS, and tough luck in MySQL. So what next? Are you supposed to use Lemograph alongside MySQL just because you don't know that PostgreSQL is free and super fast?

Window functions to mix rows and do neat stuff? Naaah, who the hell needs that, right? Who needs to find the products ordered by the customer with the biggest order anyway? Oh you need that actually? Well you should write 3-4 queries, nest them in an incredibly fucked up way, summon a demon and feed it the first menstrual blood of your virgin daughter.

There used to be some excuses in the past "but but but, shared hosting only has MySQL". Which was wrong by the way. This was true only for big hosting names, and for people who didn't bother searching for alternatives. And now it's even better, since VPS and PaaS solutions are now available at prices lower than shared hosting, which give you better speed, performance and stability than shared hosting ever did.

"But but but Wordpress uses MySQL" - well then kill it! There are other platforms out there, that aren't just outrageously horrible on the inside and outside. Wordpress is crap, and work on it pays crap. Learn Laravel, Symfony, Zend, or even Drupal. You'll be able to create much more value than those shitty Wordpress sites that nobody ever visits or pay money on.

"But but but my client wants some static pages presented beside their online shop" - so why use Wordpress then? Static pages are static pages. Whip up a basic MVC set-up in literally any framework out there, avoid MySQL, include a basic ACL package for that framework, create a controller where you add a CKEditor to edit page content, and stick a nice template from themeforest for that page and be done with that shit! Save the mock-up for later use if you do that stuff often. Or if you're lazy to even do that, then take up Drupal.

But sure, this is going a bit over the scope. I actually don't care where you insert content for your few pages. It can be a JSON file for all I care. But if I catch you doing an e-commerce solution, or anything else than just text storage, on MySQL, I'll literally start re-assessing your ability to think rationally.

FUCK GOOGLE.

FUCK THE GOOGLE PLAY REVIEW TEAM.

FUCK THEIR BOT GENERATED EMAILS.

FUCK THEIR DEVELOPER SUPPORT.

I am trying to launch a fucking action game. There will be fucking guns and muzzle flashes shown in the screenshots. Stop fucking rejecting the app. There is no blood in the icon or screenshots. Stop sending me bot generated emails and tell me what content is being flagged.

A little information on the whole scenario: My game was rejected so immediately I contacted the support as to what was the issue. The guy told me 2 screenshots were flagged because they had the muzzle flashes and damage indicator (call of duty type which tells the direction from where the bullets are coming from). So I removed the screenshots and still the game was rejected. FUCK THESE ASSHOLES. SAME GOES FOR APPLE.

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.

Inspiration to code kicks in!

Kids asleep, everybody’s asleep, house is quiet. The kind of peace ive always wanted and wished! (Parents here will understand.)

Get to my laptop, opened up code editor, start fresh and clean! Created new file, about to type my first code and.........blood dripping from my nose. It doesn’t stop there, its like flowing for a while!

I noticed it keeps flowing while im projecting the inner excitement to code. When my mind drifted a bit, the nose bleeding stops. Wth? Its like my body is ejaculating when im excited to code, yeah.. it ls blood shot out of my nose, wtf!

...and i have to stop what im doing. Then the ideas just spoofly gone. Suddenly i dont know why im staring at an empty code editor.. (what was im about to code again?) i totally cant recall, it simply gone. Damn it. That could be a million dollar apps! Wish i can go back to an hour ago and record myself when i received that historic inspirational moment. 😔

People caught using emojis in code should be driven into the sea.

Otherwise one day its gonna just be straight magic, without reason or understanding.

You're gonna type a bunch of moon runes into a glowing floaty interface, pour the blood of a chicken into a collector tray (totally not a pentagram) and "shit just happens" (tm).

And "scholars" (neckbeards) will spend all their time shape-in-wrong-hole idiocracy-style button mashing their mystical ouija board IDEs in the grim dark future, looking for combinations that do something useful.

Every time it glows red? Compile error.

Every time it glows green? Christmas is near, congrats it compiled.

Every time it sets off a mystical air siren (henceforth known as "fusrohdah"), runtime error. And probably explosions.

In the grim dark future of Apple 40k. A.D, there is only war, warp demons, and pending VSCode updates.

2 hour meeting to brainstorm ideas to improve our system health monitoring (logging, alerting, monitoring, and metrics)

Never got past the alerting part. Piss poor excuses for human being managers kept 'blaming' our logging infrastructure for allowing them to log exceptions as 'Warnings', purposely by-passing the alerting system.

Then the d-head tried to 'educate' everyone the difference between error and exception …frack-wad…the difference isn't philosophical…shut up.

The B manager kept referring to our old logging system (like we stopped using it 5 years ago) and if it were written correctly, the legacy code would be easier to migrate. Fracking lying B….shut the frack up.

The fracking idiots then wanted to add direct-bypass of the alerting system (I purposely made the code to bypass alerting painful to write)

Mgr1: "The only way this will work is if you, by default, allow errors to bypass the alerting system. When all of our code is migrated, we'll change a config or something to enable alerting. That shouldn't be too hard."
Me: "Not going to happen. I made by-passing the alert system painful on purpose. If I make it easy, you'll never go back and change code."
Mgr2: "Oh, yes we will. Just mark that method as obsolete. That way, it will force us to fix the code."
Me: "The by-pass method is already obsolete and the teams are already ignoring the build warnings."
Mgr1: "No, that is not correct. We have a process to fix all build warnings related to obsolete methods."
Mgr2: "Yes. It won't be like the old system. We just never had time to go back and fix that code."
Me: "The method has been obsolete for almost a year. If your teams haven't fixed their code by now, it's not going to be fixed."
Mgr1: "You're expecting everything to be changed in one day. Our code base is way too big and there are too many changes to make. All we are asking for is a simple change that will give us the time we need to make the system better. We all want to make the system better…right?"
Me: "We made the changes to the core system over two years ago, and we had this same conversation, remember? If your team hasn't made any changes by now, they aren't going to. The only way they will change code to the new standard is if we make the old way painful. Sorry, that's the truth."
Mgr2: "Why did we make changes to the logging system? Why weren't any of us involved? If there were going to be all these changes, our team should have been part of the process."
Me: "You were and declined every meeting and every attempt to include your area. Considering the massive amount of infrastructure changes there was zero code changes required by your team. The new system simply worked. You can't take advantage of the new features which is why we're here today. I'm here to offer my help in any way I can with the transition."
Mgr1: "The new logging doesn't support logging of the different web page areas. Until you can make that change, we can't begin changing our code."
Me: "Logging properties is just a name+value pair dictionary. All you need to do is standardize on a name and how you add it to the collection."
Mgr2: "So, it's not a standard field? How difficult would it be to change the core assembly? This has to be standard across all our areas and shouldn't be up to the developers to type in anything they want."
- Frack wads smile and nod to each other like fracking chickens in a feeding frenzy
Me: "It can, but what will you call this property? What controls its value?"
- The look I got from both the d-bags I could tell a blood vessel popped.
Mgr1: "Oh…um….I don't know…Area? Yea … Area."
Mgr2: "Um…that's not specific enough. How about Page?"
Mgr1: "Well, pages can cross different areas, and areas cross different pages…what do you think?"
Me: "Don't know, don't care. It's up to you. I just need a name."
Mgr2: "Modules! Our MVC framework is broken up in Modules."
DevMgr: "We already have a field for Module. It's how we're segmenting the different business processes"
Mgr1: "Doesn't matter, we'll come up with a name later. Until then, we won't make any changes until there is a name."
DevMgr: "So what did we accomplish?"
Me: "That we need to review the web's logging and alerting process and make sure we're capturing errors being hidden as warnings."
Mgr1: "Nooo….we didn't accomplish anything. This meeting had no agenda and no purpose. We should have been included in the logging process changes from day one."
Mgr2: "I agree, I'm not sure why we're here"
Me: "This was a brainstorming meeting as listed in the agenda. We've accomplished 2 of the 4 items. I think we've established your commitment to making the system better. Thank you all for coming."

- Mgr1 and 2 left without looking at me or saying a word.

HAHA FUCK YOU HR RECRUITER!!
This fucking lady tries to steal my devs while i spent a lot of blood sweat and tears raising them.
Thankfully my devs are happy with their work type, salary, and conditions. So they showed me a screenshot of her phishing attempts.

There is so much damage I can do to her, and her company as i got all the information, its very tempting.

Since its a "common" dirty and distasteful move, the most sensible course of action I can think of is public shaming. That too is common, dirty and distasteful. But im not that kind of guy.

What do you guys think, should i suck it in and let it slide or public shame her for her actions?

I was brought into my new position as part of an transformation of waterfall to agile methodology.

We are now running 4 while projects and need to restart the remaining 29 projects using agile principles. The business management type people love agile, but somehow the people inside the current waterfall practices doesn't.

They are afraid their silo work will either expand or not exist thus making it hard to transform the company. Also the company have been subjected to the dead sea effect.

Therfore, the project that is currently in the space of transformation is making my blood boil because people just ain't passionate enough about software.

Either you craft software, or, well you sit and suckle other's money. People suckling should please grow up and start venturing beyond there cozy 9 to 5 and transform to be a professional software doer rather than a BA, DEV, IT GUY.

YOU BASTARDS GET A SHITLOAD OF MONEY AND DON'T DESERVE IT FOR THE EFFORT YOU BRING.

It is your software, own it, be proud of it. Read up to make it better. And as always, the people debugging your code can be a violent psychopath

All programmers have the same blood type, c++.

This *is* a question you silly wrong tagging mother fucker, how dare you doubt me?

Alright, no more disclaimer: I like dungeons and dragons, but it's too fucking much in terms of rules and systems and shit, as in just *making* a character can take a long ass while.

And if that's the highest level of all your ANAL preferences then OK, but I'm not you and things only come OUT of my ass, not inwards, I swear.

Anyhoo, I got fed up with it and wrote my own ruleset and setting as a last fuck you to everyone. It's very simple: if you want to be some kinky magical alien hermaphrodite royal prostitute half sewer dragon princess and three quarters bearded female incest child of demons and fairies then FINE, but you get no bonuses for that shit.

Get it? No complex racial level scaling bullshit, FUCK YOU, race and background is just for vibes, end of story.

You get no attribute or skills or shit to distribute on level one. All you get is a prompt: pick three actions, that's it. You wanna be sexy? Pick "seduce". You wanna set turds on fire? Pick "ignite". Are you an edge lord? Pick "summon". Would you be my wife? Pick "heal", "buff" and "smite".

The game is turn based, and each action you can take is effectively a spell. Everyone can cast a basic spell like walk, attack, talk, crouch, etcetera -- that costs no mana. Special crap like flying and firing fucking electricity costs mana, and you can only do those if you either picked the spell on level one or learnt it later from a book/tutor/demonic bargain/whatever.

Which spells are valid for taking at level one is up to the game master; I just tell people to pick three verbs or short sentences, and if they choose something that's too broken like "split the Red Sea" I'm like nah you're not Moses, try again.

Still with me? Good. You get eight points of health, four points of mana, and one point of stamina. They're all energy, and you can use it to power your magery, but spending all your health means you fucking die.

Stamina recharges fully every turn, and is used for the aforementioned basic actions. All of these cost one point of stamina each. If you run out of stamina, you can use mana. Or your BLOOD.

Level one spells cost one mana, level two cost two and so on. You get back one point of mana each turn, and you can fire all the spells you want during it, long as you have mana. Or BLOOD.

That's good and all, but if you spend anywhere over eleven combined points of energy in one go, you spontaneously combust and die, erasing all signs of life in a twenty-meter radius. This is called incineration, and it *will* leave behind a blackened crater from which the dark servants of the Horror Immemorial may or may not crawl out of.

In case you didn't guess by now, your blood doesn't fucking come back unless you eat, sleep or see a healer.

But anyway, the more points you spend into casting a spell -- and remember, basic attack counts as a spell -- the more powerful it is, so the bigger your diceroll can get. My rule is I add one dice for every fourth point of energy spent, so (1d4), (1d4 + 1d6), (1d4 + 1d6 + 1d8), incineration.

Additionally, for every three points of energy spent, your spell can hit one more target. That's right, you like AoE? Then spend more mana, bitch. Oh, and if you're using shit like poison it lasts one more turn for every two points of energy spent.

How do we calculate damage? Diceroll over two and fuck your mother. Armor class? Resistances? Out of my face with that shit. Damage reduction is called "tyranny" and is for dungeon bosses only.

If you live long enough to get to level two, you *do* get attributes. Pick:
- Grit: +2 health, +1 to fighter shit type rolls.
- Cunning: +2 mana, +1 to rogue shit type rolls.
- Allure: +1 stamina, +2 to wizard shit type rolls.
- Spirit: +1 to elemental shit type spells.
- Faith: +1 to benefactor paragon asshole shit type spells.
- Hatred: +1 to demonic murder hobo destructive shit type spells.

On second level, you can pick one of the spells you know to get +1 to it, specifically. Eh, "+1" just means you get a bonus to some diceroll, no time to explain I'm running out of characters what the fuck.

On level three, the cycle repeats. Pick attr, pick spell. DONE.

Oh right, and weapons. Mostly just vibes, pick your fancy and fuck off. Normally, you can hit things one tile away; if you have a BIG melee weapon you can hit from *two* tiles away, and if you have a ranged weapon you can shoot anyone in sight, but you need to spend one point of energy to reload.

And there, all bases covered in less that 5000 characters with some flair to spare, now suck my fucking cock Hasbro.

What was the question? Oh yeah right, I'm gonna GPL this shit and put it in browsers. I think I'm going to write it in Kotlin but I'm open to suggestions. Would you guys like to play it/contribute to it's development for shits and giggles?

I went to the doctor today and he told me I had type A blood but it was a type O.

So i was writing sql query and every time i was getting "data type mismatch error."

In frustrations i slammed the table and went outside for some fresh air.

After 15 minutes i came back and runs the query again. Voila, it is working now.

My god these queries burned half of my blood today. LOL. 😁

My ex had an accident. I told the paramedics the wrong blood type for her. She'll finally experience what rejection is really like.