Why Gmail. Why the fuck do your search parameters, especially your date filters, not work anywhere near as expected.

You make me have to query and test, query and test, just, randomly fucking guessing because, fuck it, right?

With a good 10 second refresh time. I love twiddling my thumbs and pulling my hair out.

after:2018/11/1 should produce emails from Nov 1st onward.

Not, TODAY ONLY, if no other parameters are
specified.

If there's a from: parameter, now we want to do after Nov 1st, right?

And also, don't show me how to sort in reverse order, either. Not without a complete rewrite of my class there, which clearly I'm too lazy to do right now.

Fuck the Gmail Api, responsible for weeks of wasted dev time... or more aptly put, "fuck devs using our gmail api" says the maniacal, sociopath devils that created it

fuckers.

Holy fucking shit are email clients bullshit.
I don't know what happened there but if you thought the chrome-firefox-ie-egde gaps back in the days were sick - let me tell you.. email clients are made by the devil himself. All of them. All of them? Yup. Because he made some of them being owned by apple, working beatuiful and no weird stuff.
But on the same end he made some of them owned by microsoft and their office Studios. They use the word engine to render html emails. Read this again. Read it without starting to cry in agony.
But thats not enough. Let's make some of them use an ie-engine and the mac os variants going to use some webkit based renderer. This way there will be no valid ruleset to make it look good on all of them, isn't this great??
Now this might be hell already. But lets pour more salt into these wide opened wounds.
Let there be Germany and United Internet, owning trash like Web.de and GMX, whose android clients going to work completely different across Android and app-versions!
Once you've mastered these, let me introduce you to gmail. Lets take only the body node of your email and do some fuck up with it, so you have to display a non-responsive variant on mobile.
Now you might be thinking "but there are web-based clients, they'll do good ain't they?" Long story short: fuck you.
Not enough.
Let's go back to ms.
Hey dude lets make it possible to scale up your whole system. So old people can read shit better. And now the funny part: let's make it so that the word rendering engine, rendering emails goes completely mayhem on your mail, so it looks like a completely different thing! (:

If you ever receive a newsletter in your inbox and that shit looks like it's planned to look like.. appreciate that shit. Sacrifice a virgin as thanksgiving for it.

TL;DR:
E-Mail needs to die. I'm doing this for over 2 years now and this shit needs to stop asap.

Global variables destroyed my day

Of course you can call me a bad programmer and all. When you have the idea, sometimes globals make it seem easy, accessible and "saving resources". They are devils.

The app was connected to a suite of applications. So I ended up silently destroying it neighbors. I committed and pushed the shit. Just when the testers made their weed high smoke tests, a server stopped working.

I got an email that boss wanted the latest version, I reverted the wrong branch, which had code unrelated to its name, pushed shit again and voila.

I went to the bathroom and laughed. I had to take a smoke. I'm still laughing while typing this. The damage is too much and I can't help it. I'll go home, leave this pc on and work remotely through the night. It might be the hysterics speaking now, but I messed up, and I need magic by friday morning.

Saw my dad doing some frontend work alongside the devils spawn work (PHP), when I was 8 years old. Ever since I've fallen in love with programming, especially in backend work.

[CONCEITED RANT]
I'm frustrated than I'm better tha 99% programmers I ever worked with.

Yes, it might sound so conceited.
I Work mainly with C#/.NET Ecosystem as fullstack dev (so also sql, backend, frontend etc), but I'm also forced to use that abhorrent horror that is js and angular.
I write readable code, I write easy code that works and rarely, RARELY causes any problem, The only fancy stuff I do is using new language features that come up with new C# versions, that in latest version were mostly syntactic sugar to make code shorter/more readable/easier.

People I have ever worked with (lot of) mostly try to overdo, overengineer, overcomplicate code, subdivide into methods when not needed fragmenting code and putting tons of variables.

People only needed me to explain my code when the codebase was huge (200K+ lines mostly written by me) of big so they don't have to spend hours to understand what's going on, or, if the customer requested a new technology to explain such new technology so they don't have to study it (which is perfectly understandable). (for example it happened that I was forced to use Devexpress package because they wanted to port a huge application from .NET 4.5 to .NET 8 and rewriting the whole devexpress logic had a HUGE impact on costs so I explained thoroughly and supported during developement because they didn't knew devexpress).

I don't write genius code or clevel tricks and patterns. My code works, doesn't create memory leaks or slowness and mostly works when doing unit tests at first run. Of course I also put bugs and everything, but that's part of the process.

THe point is that other people makes unreadable code, and when they pass code around you hear rising chaos, people cursing "WTF this even means, why he put that here, what the heck this is even supposed to do", you got the drill. And this happens when I read everyone code too.

But it doesn't happens the opposite. My code is often readable because I do code triple backflips only on personal projects because I don't have to explain anyone and I can learn new things and new coding styles.

Instead, people want to impress at work, and this results in unintelligible, chaotic code, full of bugs and that people can't read. They want to mix in the coolest technologies because they feel their virtual penis growing to showoff that they are latest bleeding edge technology experts and all.

They want to experiment on business code at the expense of all the other poor devils who will have to manage it.

Heck, I even worked with a few Microsoft MVPs.
Those are deadly. They're superfast code throughput people that combine lot of stuff.
THen they leave at you the problems once they leave.

This MVP guy on a big project for paperworks digital acquisiton for a big company did this huge project I got called to work in, which consited in a backend and a frontend web portal, and pushed at all costs to put in the middle another CDN web project and another Identity Server project to both do Caching with the cdn "to make it faster" and identity server for SSO (Single sign on).

We had to deal with gruesome work to deal with browser poor caching management and when he left, the SSO server started to loop after authentication at random intervals and I had to solve that stuff he put in with days of debugging that nasty stuff he did.

People definitely can't code, except me.
They have this "first of the class syndrome" which goes to the extent that their skill allows them to and try to do code backflips when they can't even do code pushups, to put them in a physical exercise parallelism.

And most people is like this. They will deny and won't admit, they believe they're good at it, but in reality they aren't.

There is some genius out there that does revoluitionary code and maybe needs to do horrible code to do amazing stuff, and that's ok. And there is also few people like me, with which you can work and produce great stuff.

I found one colleague like this and we had a $800.000 (yes, 800k) project in .NET Technology, which consisted in the renewal of 56 webservices and 3 web portals and 2 Winforms applications for our country main railway transport system. We worked in 2 on it, with a PM from the railway company.

It was estimated 14 months of work and we took 11 and all was working wonders. We had ton of fun doing it because also their PM was a cool guy and we did an awesome project and codebase was a jewel. The difficult thing you couldn't grasp if you read the code is if you don't know how railway systems work and that's the only difficult thing.

Sight, there people is macking me sick of this job