Once again I start my day by investigating a problem that has started in the middle of the night. Turned out that the issue was with the API of the content management system. You can guess which part of the whole system was blamed in the first place…
Today is the Independence Day here in Finland. That means a couple of things:
- The majority of Finns will be watching the TV broadcast of the Independence Day ball hosted by the president and judging the dresses the guests are wearing1, and
- There will be demonstrations and marches in Helsinki assembled by various groups, including far-right nationalists (from whom the police confiscated Nazi flags [yle.fi])2 and far-left anarchists.
Of course, there are other ”traditions” that will some people just have to follow. I personally could not care less about those things.
I will roll my eyes so hard that it will make the Earth reverse its spinning direction.
Insert another eye-roll here.
Doing small changes that are not technically that difficult but that will delight1 the end users makes me happy, especially after all that shit I had to bear last week.
I know, the word has become annoying. It annoys me too, but there is no better word to be used here.
It’s not fun to start your day at the dentist. This time it was a planned dental check, so no drilling or anything like that. But I need to go again in a month to get those small issues fixed.
@matigo Yeah… I am willing to admit that I fucked up. The follow-up meeting was all about quality assurance and the workflow process. As if those could have saved this thing as the mistake was introduced by the lack of documentation from where I could have checked if the parameter I was about to remove was needed or not.
Fucked up a major feature in the app when I fixed one part of it. Now the customer is in total panic mode, even though I have fixed the issue and the new version is being rolled out to the users. Yay.
The root cause for this problem was that I removed one parameter from a message that is sent to the backend because that was no longer needed by that one part of the feature. Apparently it is indeed needed for the other part of the feature, hence, this major problem.
Support for SOAP over HTTP is deprecated, but it is still available over HTTPS.
Why should I use REST when there is SOAP available? ?