I had the perfect opportunity to finally do some hobby project coding: a 6 hour fight.

I take my fucking expensive laptop out of my bag, it's hot as fuck. FACKING WINDOWS 10 didn't shut down properly, took up ALL battery (which usually lasts ~12 hours). FACKING waste of 6 hours of private time. FUCK WINDOWS 10. FACK. I am now about to embark on 6 hours of boredom. FUCKING PIECE OF SHIT OS

When I see two fields, one for username and one for password, I expect I can fill them out immediately subsequently with only a tab in between. While typing my password I DON'T want to get sent to a page where I can enter my password only: I was entering it already! Sometimes I even make it until I pressed the enter key that was supposed to log me in, but then I'm kindly requested to reenter my password. At that moment I not-so-kindly think: FUCK YOU Microsoft, you should know better. Even when logging into Visual Studio for fack sake

FUCK Windows 10 and it's HATEFUL tendency to open everything with FACKING Edge even though it overrides that the default browser is chrome. Especially fucking Skype for business.

Fack Skype too

Me: Okay so here's the progress of your page so far.
Client: This doesn't mean sh1t to me show me the end result and I'll make adjustments then.
Me: oh my bad I didn't know you had a degree in web development the fack of me then. Like you know how to make adjustments...

I am fed uuuuuup with the whole Corona bullshit at work, every, single, damn, daaaaay.

Fack.

Fack I hate this CMS we have. Using Fetch and sending data as encoded JSON doesn't get parsed nor recognized by the CMS. I was pulling my hair out, understanding the differences, switched back to XHR... and then noticed the buggar:

XHR sends data as "FormData()".

I switched everything to FormData and TADAAA IT WORKS MOTHERFUCKA

Lost a whole fucking day on this trying to understand whether it was my code or the CMS the problem.

Ah yes, of course, I had to reproduce the CMS on my machine, instead of having the developers lend us a "development" platform on it, so obviously I don't know what's happening under the hood :))))))))

I may have been drinking too much coffee. I really like (need?) it.

Do you know the feeling after say eating the same meal a free evenings in a row makes you dislike that for a while?

I think that's happening to me now for coffee :(

What the FACK am I gonna do now? Drink tea? 😦

!rant

Struggled for 2 hours now. How the heck can a create a directory on android. My code:
File dir = new File(Environment.getExternalStorageDirectory(), "Directory");
dir.mkdirs();

Fetch API gives CORS error..

Then I use JQuery AJAX request and it works fine...? 😑

Can you even handle CORS requests with Fetch?
🤔

This is an actual transcript...
Since it's way too long for the normal 5000 characters, hence splitting it up...

Infra Guy: mr Dev, could you please give some rational for update of jjb?
Dev: sparse checkout support is missing
Infra Guy: is this support mandatory to achive whatever you trying to do?
Dev: yes
Infra Guy: u trying to get set of specific folder for set of specific components?
Dev: yes
Infra Guy: bash script with cp or mv will not work for you?
Dev: no
Infra Guy: ?
Dev: when you have already present functionality why reinvent the wheel
Dev: jenkins has support for it
Dev: the jjb is the bottle neck
Infra Guy: getting this functionality onto our infra would have some implications
Dev: why should I write bash script if jenkins allows me to do that
Dev: what implications ??
Infra Guy: will you commit to solve all the issues caused by new jjb?
Dev: you show me the implications first
Infra Guy: like a year ago i have tried to get new jjb <commit_url>
Infra Guy: no, the implications is a grey area
Infra Guy: i cant show all of them and they may hit like in week or eve month
Dev: then why was it not tackled
Dev: and why was it kept like that
Infra Guy: few jobs got broken on something
Dev: it will crop up some time later
Dev: if jobs get broken because of syntax
Dev: then jobs can be fixed
Dev: is it not ???
Infra Guy: ofc
Infra Guy: its just a question who will fix them
Dev: follow the syntax and follow the guidelines
Dev: put up a test server and try and lets see
Dev: you have a dev server
Dev: why not try on that one and see what all jobs fails
Dev: and why they fail
Dev: rather than saying it will fail and who will fix
Dev: let them fail and then lets find why
Dev: I manually define a job
Dev: I get it done
Infra Guy: i dont think we have test server which have the same workload and same attention as our prod
Dev: unless you test how would you know ??
Dev: and just saying that it broke one with a version hence I wont do it
Infra Guy: and im not sure if thats fair for us to deal with implication of upgrading of the major components just cause bash script is not good enough for u
Dev: its pretty bad
Infra Guy: i do agree
Infra TL Guy: Dev, what Infra Guy is saying is that its not possible to upgrade without downtime
Infra Guy: no
Dev: how long a downtime are we looking at ??
Infra Guy: im saying that after this upgrade we will have deal with consequences for long time
Infra Guy-2: No this is not testing the upgrade is the huge effort as we dont have dev resources to handle each job to run
Dev: if your jjb compiles all the yaml without error
Dev: I am not sure what consequences are we talking of
Infra Guy: so you think there will be no consequences, right?
Dev: unless you take the plunge will you know ??
Dev: you have a dev server running at port 9000
Infra Guy: this servers runs nothing
Dev: that is good
Dev: there you can take the risk
Infra Guy: and the fack we have managed to put something onto api doesnt mean it works
Dev: what API ?
Infra Guy: jenkins api
Infra Guy: hmmm
Dev: what have you put on Jenkins API ??
Infra Guy: (
Dev: jjb is a CLI
Infra Guy: ((
Dev: is what I understand
Dev: not a Jenkins API
Infra Guy: (((
Dev: (((((
Infra Guy: jjb build xmls and push them onto api
Infra Guy: and its doent matter
Dev: so you mean to say upgrading a CLI is goig to upgrade your core jenkisn API
Dev: give me a break
Infra Guy: the matter is that even if have managed to build something and put it onto api
Infra Guy: doesnt mean it will work
Dev: the API consumes the xml file and creates a job
Infra Guy: right
Dev: if it confirms to the options which it understands
Dev: then everything will work
Dev: I am actually not getting your point Infra Guy
Infra Guy: i do agree mr Dev
Dev: we are beating around the bush
Infra Guy: just want to be sure that if this upgrade will break something
Infra Guy: we will have a person who will fix it
Dev: that is what CICD is supposed to let me know with valid reasons
Dev: why can't that upgrade be done
Infra Guy: it can be done
Infra Guy: i even have commit in place

Fack..! ಠ_ಠノ
This year feels like 2020 divided by 5