Stupid pipeline bullshit.

Yeah i get it, it speeds up development/deployment time, but debugging this shit with secret variables/generated config and only viewable inside kubernetes after everything has been entered into the helm charts through Key Vaults in the pipeline just to see the docker image fail with "no such file found" or similar errors...

This means, a new commit, a new commit message, waiting for the docker build and push to finish, waiting for the release pipeline to trigger, a new helm chart release, waiting for kubernetes deployment and taking a look at the logs...

And another error which shouldn't happen.

Docker, fixes "it runs on my machine"
Kubernetes, fixes "it runs on my docker image"
Helm, fixes "it runs in my kubernetes cluster"

Why is this stuff always so unnecessarily hard to debug?!

I sure hope the devs appreciate my struggle with this... well guess what, they won't.

Anyways, weekend is near and my last day in this company is only four months away.

1. Music, something fast paced with minimal to zero lyrics (usually a GOA radio station in my case)
2. No distractions around (use a "do-not-disturb" flag or something to hang on your monitor or show on your desk)
3. No chats or other communication/social media visible, best case those apps / tabs are completely closed or muted
4. Having a clear goal to achieve, might even be only a sub-goal for the current coding session.
5. Structure your code before your actually write it, I usually create step-by-step comments in each file, documenting my thought process and what steps the current file/class/whatever should do.
6. Try to code your stuff in the same order as the aforementioned comment step-by-step list dictates (unless there is a reason to change the coding order)
7. Only windows open: IDE/Editor, Browser
8. Also keep only the browser tabs needed for your work open (testing clients, documentation, music if using a browser client, etc.)

At least that's what works for me

Why does on-call schedule always ramp up shortly before the final hour?

Due to christmas and vacations I had on-call schedule, five days off, on-call schedule and both times, riiiight before my schedule ended, the monitoring/alerting system EXPLODED!!11!1

Seriously, I get the need for on-call schedule, but how are you supposed to get regular day-to-day work done when you're always on the edge because you're just waiting for the next alert to pop-up.

I'm so glad when I finally move from this company, no on-call schedule and other stuffs (which are unrelated for now, maybe in another rant) anymore.

I really respect people who are doing on-call schedule and such but I am definitely not meant for it.

When friends ask me to do some coding...

Them: I want/need this and that and... [trillions of features and "cool" stuffs]

Me: ...okay

Them: Oh and this and that and [more "cool" stuff]

Me: Alright.. when do you need it?

Them: something around a week?

Is it just me or does everyone -not- accustomed to coding think that projects are usually done in a few days...?

Maybe the common opinion about coders is something like: They aren't humans, they are machines which convert caffeine during night time to source code

Nine hours... friggin nine hours..

Reinstalled my machine and forgot to save my workflow scripts so I first had to recover from a backup, copy my scripts to a USB drive and do the reinstall again..

GAH! FUCKING VOLUME!!

Logic Pro X is killing either me or my ears!
The track is completely fine when I edit it there but when I export it and listen to the file that single instrument... is WAY TOO LOUD! WHY?
Is the converter script broken or something? Or am I just too blind to see the fucking volume switch?

Why?!
I want to support! I really do!

Gah f......appstore... stupid piece o.....

They want what?! Call me away from vacation even though I'm not employed there anymore because they are to STUPID to read a FUCKING EMAIL?!

I sent the mail to THREE PEOPLE with the path to the docs and friggin TRIPLE CHECKED THE PATH AND FILES...

"Yeah could you please be there tomorrow morning?"

So..
The company I was working at until two weeks ago just called me because they don't understand the project I've been working on (even though I provided in-depth documentation, which felt like I documented closely every bit twice -.- ) and they don't have any developer left who knows even a bit of python.

WHY PYTHON IN THE FIRST PLACE IF YOU DON'T EXTEND THE CONTRACT FOR THE MAIN DEVELOPER?!?!

Hypocrites...

The moment when your code is like,
Yeah I'm working, not throwing errors, but not doing anything closely related to the things I should do.

Fuck this construct, I'll recode the whole thing and stop using any two-year old legacy code, for this project

Half rant, half shameless self-advertisement (I guess)

I created a (currently rather basic) devRant sidebar for atom.io:

https://github.com/sambadevi/...

But this STUPID thing took me WAY too long to code it, the plugin structure was sooo frustrating that I decided to recode the whole thing after I had probably 80% done!

Reminder to self:
Next time just use another DOM element...

Internationalization be like:
Yo dawg, look, you can use mutliple languages now!

Suddenly gettext won't find any language files and every string is empty ;_;

WHY HAVE YOU FORSAKEN ME GNU?!

While I was waiting for the JDK to install for the FOURTH TIME!?!?....
Ahem...
So I was listening to some music from Papa Roach when suddenly my mind did some weird stuff, which led me to the following conclusion:

Sometimes I just hate my own mind...

Threaded API Calls, or rather:

How I killed five server instances in one shot..

Creating 50000 Threads sounds like a good idea in general, the bad part starts when you use start() in a for loop to run them all at once.

No further comments your honor...