Just a friendly reminder to fellow developers to take care of yourself.

If your system is constantly pumping out cortisol, even when threats are minor, it gets desensitized to the stress signals. We used to react to cortisol with the fight-or-flight response when our lives were in real danger. Nowadays it's produced when you disagree with your coworker or there's a deadline coming up. So your cortisol rises but you neither fight nor run. The result is a stress response that isn't functioning properly. This is when burnout symptoms develop. Same goes for testosterone, dopamine and some other hormones and neurotransmitters. Read up and start proper work hygiene that includes workouts, fresh air activities and manual hobbies.

Your back, wrists and eyes aren't the only things you have to watch out for when coding long hours. Cheers and have a fun weekend!

!rant

Linux just made my day. Everybody knows how Windows won't let you shutdown your hardware until it updates, right? So last night I forgot I was upgrading Manjaro in a background terminal (full distro update, tons of packages) and hibernated my rig, plugged it off, took it to a different location. Today I hooked it up - different network, IP, etc. - it woke up, finished compiling whatever it ended up on then downloaded, compiled and installed everything else, said "Thank you very much!" and dropped the mic. Someone tell me this isn't pure awesomeness! 😂

It asked again for root password but other than that... shrugged off 12 hours difference like a boss!

I have ME/CFS after Covid19. My manager says its an excuse. Can't wait for them to fire me because of my performance drop. Now I only do about 100% of my work instead of 140%.

We had an obligatory training today about security of remote access to company resources.

We sat for an hour listening to some outdated advice regarding passwords and preparing a work environment at home. Finally the instructor said his goodbyes and left. The rest of us stayed in the call to pass some actual recommendations.

Then we received a join request from a waiting lobby. Everyone muted. I let the guy in. For the next 8 minutes we watched the unaware instructor eat his breakfast and sign some documents stamped with a logotype of our competition.

Then I cleared my throat very loudly. He will have to print some of those documents again.

It's 5 AM and I don't want to shit on anybody's party but trust me when I say most of you here complaining about legacy code don't know the meaning of the word.

As someone who maintained a PHP4 codebase with an average file length of 3000+ lines for almost 4 years, I feel you, I feel your pain and your helplessness. But I've seen it all and I've done it all and unless you've witnessed your IDE struggle to highlight the syntax, unless you had to make regular changes in a test-less SVN's working copy that **is** the production and unless you are the reason that working copy exists because you've had enough of `new_2_old_final_newest.php` naming scheme, you do not know legacy. If you still don't believe me bare in mind I said "is" as in: "this system is still in production".

But also bare hope. Because as much grief as it cost me and countless before me, today of all days, without a warning, it got green lit for userbase migration to a newer platform. And if this 20 years of generous custom features and per client implemented services can be shut down even though it brings more profit than all the other products combined, so can happen to any of your projects. 🙏

Unfortunately, I do mean *any*.

Last job search experience... It's fresh. I was being recruited by a girl from Aruba. During our 2nd video call she became... let's say "friendly", calling me "hun" and "sugar". Our 3rd conversation in attachment. I checked - the company is legit, she does work for them, it's not a scam. Fun fact - her full name is Jameelah but she doesn't use it at work because it's more suitable for a belly dancer than a professional IT recruiter. Her words, not mine.

Guy: - Why the hell do you keep adding new tests with "TDD" in the commit log? Is this because you're wearing this stupid TDD t-shirt!? You're only supposed to maintain this! There's nothing to develop! Nothing here will ever be test-driven!

Cprn: (turns around)

T-shirt: *Technical Debt Development*

!dev
Last week I watched a DIY video where at the end the guy dumped detergent water on the grass. I kindly commented it's a €150 fine. Their response was on the lines of "Oh yeah, Mr Proper? And what would you say if I told you I spray my whole garden with soap to get rid of weeds, huh?".

Well, you dumb fuck, I don't care what you do, I wasn't attacking you, I was being *nice* and warned you about the fucking fine that you're going to fucking pay because your channel name is your first and last name and your video shows the street and the house number but whatever.

Today I couldn't log into my YouTube account. Why was that, you might ask? Well, because the dumb fuck paid the fucking fine and assumed I was the one that ratted, so he made a video about it and his dumb fuck audience falsely reported all of my videos for child abuse and promoting terrorism.

I only upload unboxing videos that debunk scummy "deals". 🤦‍♂️

I'm struggling with a bug. It's not my bug, it's in a lib - in an assembly function commented as "this is where the magic happens". After 27 hours of trying to determine what triggers said bug my best guess is it's a relationship between the position of Mimas and the mood of my neighbour's chonker. If it's not triggered by the Saturn's moon and a pet animal... I'm out of ideas.

Now how do I break it to my PM that we have to kill a cat?

So I just realized (while rewriting some code) Python can't import stuff from a sibling directory without voodoo tricks. Seriously. In 21st century.

There was a department. Long time ago their work was somewhat complicated: background checks of businesses, websites, ToSes, assuring agreement compliance, some risk management on top. They started as small 3 people team but over the years they were hiring new employees to catch up with the growing customer base. They were still struggling. Few years back we've integrated 3rd party services to help them and, finally, their backlog was gone!

In January they complained about how much more work they have since the merger so I inquired about which process was troublesome, what was the flow, etc., and it turned out to be very... Tinder-like - the issue was the sheer number of cases:

1. open a case,
2. check results in few windows,
3. if green + green + green, move right.
4. else move left.

It was ridiculous, I wouldn't stand for that. I sat for an hour, made some ghosting scripts that followed same business logic and saved results alongside their actual decisions. Last week I compared the two and there was zero difference so I green-lit it with my boss and pushed to prod.

Oh, the happiness on their faces when they heard the news, the disbelief, the tears of joy!

And then it happened. After 4 years of being cautious not to stir the waters I did it again. Yesterday I accidentally replaced 17 people department with 3 scripts. How was I supposed to know it was *all* they were doing??

After 4 years of being cautious not to stir the waters it happened again. There was much gratefulness. Then there was much hate. Yesterday I accidentally replaced 17 people department with 3 scripts.

So... Yesterday I ordered a meal and it had whole jalapenos in it. I didn't order jalapeños. I love the taste but I hate toilet visits after. Hence, was putting them aside. But then I got into that new code, jumping around this new project I'll be working on. We were getting intimate. I liked the architecture, I liked it a lot - it was using event sourcing and respected CQRS. Suddenly I realised I ate everything. Including jalapeños. And the only reason I noticed is because I was eating with my hands. And my eye got watery. And I wiped it.

So, yeah. Yesterday for the first time in my life I was pouring milk into my eyes. Does this count as a proper dev rant? I don't know. Fuck the protein interface that can't process simple food orders, though.

Young 22 years old me, hungry for excitement of real world issues, full of whimsical witticisms, writing bootstrap scripts that'd spit meaningful information like...

> $ run bankhack
> Shutting down the old world...
> Checking world population...
> Initializing particle accelerator...
> Exploding sun...
> Entering hell...
> Starting daemons...
> Starting lesser daemons...
> Burning logic...
> Restoring balance in the universe...
> World peace achieved.

What a naive douche he was.

Me: "Omg, I'm so not sorry you didn't get a response to your 2:00am text sent to my private phone number about that super duper not important thing that a four year old could solve... but my girlfriend gave me a wrist band thingy that puts my phone on silent whenever it thinks I'm sleeping."

Product Owner: "And you can't set it up properly!? Your title says `señor software engineer` for god's sake!"

Me: "Yeah, it does. This is a hardware issue, though."

...is what I told her and she bought it. 🤷‍♂️

Most... Awkward... Video call... Ever!

Ended about 7 minutes ago. This one guy... Seriously! I mean... 🤷‍♂️ Everyone thought he's just uncomfortably open but when he finally got out of the shower he panicked, screamed like a girl, fell down and covered his camera asking: "Guys, when you were talking just now... Was there anything... Like... *Weird* on my stream?"

We worked with that freelancer some time ago. Most talented coder I've ever known. Coding for only 3 years, and only 1 technology, but technical thinking already up to par with my own 15+ years of experience. Very rude but to the point. We loved it - "one of us". We hired that asshole for different remote projects over 20 times in 3 years. We send spec, answer questions, collaborate on chat, review work on svn, add tickets, get solutions. After about a year working like that we had minor issue with finance that revealed our prized freelancer is a chick.

Changed nothing.

A dev adds a nice range of categories that content creators can select from. Users get a neat filtering system to restrict the unwanted content.

And then...! People post everything in default category.

During a health and safety course today I was asked to talk about the workspace ergonomics. Part of that course is to make sure everyone knows how to customise their seat, screen, keyboard, etc., so I told everyone to unfold those little feet on the bottom of their keyboards and everyone did... Everyone but a cheeky little customer service girl who was more interested in taking selfies of her skirt coincidentally matching the carpet. I cleared my throat and said again:

- "Please, unfold your keyboard's feet."

Nothing. Coughed. Nothing. Finally, quite annoyed, I repeated myself for the 3rd time:

- "Unfold the feet, please!"

She jumped. Eyes wide. Noticed everyone staring. And very very slowly, with a look of complete puzzlement, she spread her legs.

This girl from financial department pissed me off so badly I took 15 minutes of my private time to slightly modify CSS and JS for her user in our intranet panel, made everything pink and blue, animate all the buttons to randomly barrel roll and made the mouse cursor explode colourful star particles with each click.

She *liked* it, said it was *sweet* and *apologized* for being an ass. Robbed me of all the satisfaction. :(

How can I find all my comments (not posts) on devRant?

WTF is going on in web development nowadays that makes people ask me to compile C# projects to Electron?

Let that sink. I'm being asked to compile a C# project that can run as a beautifully integrated seamless *native* and lightning fast application... to JS so it would run as a *website* in the Electron *browser*. Am I the only one seeing how much cancer that is?

To all the masochists who spent hours debugging misspellings:

1. Learn your tools
2. Learn good practice

Every IDE should point out when you're not using a variable you've initiated or using an uninitiated variable as well as at least highlight, if not simply list, every occurrence of the variable under your cursor and let you find all references or even display the number of references next to a variable at all times, and finally, every IDE should autocomplete for you so when it doesn't you know you've messed up. Good IDE makes all the easy mistakes hard and all of the hard tasks easy. Including running tests. If you don't know how to configure your IDE to do all these things take time and learn it. If you still can't figure it out, replace your IDE maybe...?

Also use the debugger. Preferably one that nicely integrates with your IDE. If you don't, check point 1.

Also write tests and *run them*.

Also if your misspellings tend to consist of a missing `s` at the end of a plural noun just call it `entityCollection` instead of `entities`. And read up on more good programming practices and naming conventions.

My No.1 interview question for UX developers:

What are the CSS default text and background colours?

The correct answer is: "undefined-on-undefined".

If your 1st thought was "black-on-white", you're the reason we can't have nice things.

Today, during deployment on server without remote access:

Me (on the phone calling our data centre Admin): "There's a permissions mismatch. The following paths need write access from the following users..."

Admin: "Okay, okay, slow down... I'm still in the elevator." - 10 minutes later - "Okay, ready."

And I gave him the paths and he said: "Try now."

And I tried and it still didn't work. And then we tried all that again. And again. And finally he said:

Admin: "Okay, I give up, I'm going back down to get the screen."

Guy: - "Your restart script doesn't work."
Me: - "What do you mean?"
Guy: - "It does nothing."
Me: - "It should kill every processes that's running within the project and start them again. Wait... Why do you terminate it?"
Guy: - "I don't. It just stops."
Me: - "It says `Terminated` here. You killed it. Just let it do it's job, don't kill it."
Guy: - "I'm not killing it! It just stops!"

(...two hours later...)

Me: - "Wait... Where do you run it from?"
Guy: - "What do you mean? I just run the script you gave me."
Me: - "Yeah, but where do you run it from? Where did you put it?"
Guy: - "It's part of the project so I put it in the project, d'oh!"

September 13th, 2013 at 06:20 AM
===========================

~$ cd /mnt/backupdisk
backupdisk$ make_backup --output=./~
Cannot access storage: /mnt/backupdisk/~
backupdisk$ ls
~
backupdisk$ rm -rf ~
^C ^C ^C ^C ^C

...never name your backup same as your home directory.

Seven months ago:
===============
Project Manager: - "Guys, we need to make this brand new ProjectX, here are the specs. What do you think?"

Bored Old Lead: - "I was going to resign this week but you've convinced me, this is a challenge, I never worked with this stack, I'm staying! I'll gladly play with this framework I never used before, it seems to work with this libA I can use here and this libB that I can use here! Such fun!"

Project Manager: - "Awesome! I'm counting on you!"

Six months ago:
====================
Cprn: - "So this part you asked me to implement is tons of work due to the way you're using libA. I really don't think we need it here. We could use a more common approach."

Bored Old Lead: - "No, I already rewrote parts of libB to work with libA, we're keeping it. Just do what's needed."

Cprn: - "Really? Oh, I see. It solves this one issue I'm having at least. Did you push the changes upstream?"

Bored Old Lead: - "No, nobody uses it like that, people don't need it."

Cprn: - "Wait... What? Then why did you even *think* about using those two libs together? It makes no sense."

Bored Old Lead: - "Come on, it's a challenge! Read it! Understand it! It'll make you a better coder!"

Four months ago:
==============
Cprn: - "That version of the framework you used is loosing support next month. We really should update."

Bored Old Lead: - "Yeah, we can't. I changed some core framework mechanics and the patches won't work with the new version. I'd have to rewrite these."

Cprn: - "Please do?"

Bored Old Lead: - "Nah, it's a waste of time! We're not updating!"

Three months ago:
===============
Bored Old Lead: - "The code you committed doesn't pass the tests."

Cprn: - "I just run it on my working copy and everything passes."

Bored Old Lead: - "Doesn't work on mine."

Cprn: - "Let me take a look... Ah! Here you go! You've misused these two options in the framework config for your dev environment."

Bored Old Lead: - "No, I had to hack them like that to work with libB."

Cprn: - "But the new framework version already brings everything we need from libB. We could just update and drop it."

Bored Old Lead: - "No! Can't update, remember?"

Last Friday:
=========
Bored Old Lead: - "You need to rewrite these tests. They work really slow. Two hours to pass all."

Cprn: - "What..? How come? I just run them on revision from this morning and all passed in a minute."

Bored Old Lead: - "Pull the changes and try again. I changed few input dataset objects and then copied results from error messages to assertions to make the tests pass and now it takes two hours. I've narrowed it to those weird tests here."

Cprn: - "Yeah, all of those use ORM. Maybe it's something with the model?"

Bored Old Lead: - "No, all is fine with the model. I was just there rewriting the way framework maps data types to accommodate for my new type that's really just an enum but I made it into a special custom object that needs special custom handling in the ORM. I haven't noticed any issues."

Cprn: - "What!? This makes *zero* sense! You're rewriting vendor code and expect everything to just work!? You're using libs that aren't designed to work together in production code because you wanted a challenge!?? And when everything blows up you're blaming my test code that you're feeding with incorrect dataset!??? See you on Monday, I'm going home! *door slam*"

Today:
=====
Project Manager: - "Cprn, Bored Old Lead left on Friday. He said he can't work with you. You're responsible for Project X now."

Few years ago a girl from our HR was hitting on my co-worker. She was asking all kinds of personal and professional favours just so he would come by her place, etc. One time she asked him to send her few C/C++ questions that she could use to thin the crowd of potential candidates before inviting them for the formal interview that he'd conduct later on. Obviously she wouldn't know if the answer is good or not but hell with it, he was ready to storm that pink fortress! So he came up with some mind twisters. She left two days later before he even reached the drawbridge. Sad.

So about six months ago he got fed up with some bullshit and left the company. Yesterday we had dinner. He was interviewing for quite some time being picky about which offer to accept and, surprisingly, during his last interview he got asked very familiar set of questions. He answered each. Then he couldn't resist and asked if the girl works there. The guy confirmed and, without a warning, called her. As if it wasn't awkward enough this is how I was told the conversation went:

- "Joan! You won't guess who I've got here! Your very good friend, Peter! Nope. Yeah, that one - how did you kn... Uh-huh. Oh? Yeah. Are you sure? I mean, I wouldn't. Deal!"

Then he turned out to Peter and said:

- "You know what? I wasn't going to hire you for shit because in my opinion your knowledge on the subject matter, how to put that gently, sucks ass... But apparently Joan here says you're professional and can handle everything we'll be able to throw at you. So when can you start?"

Needless to say he took the job. The fortress fell soon after and he wanted to meet to ask if I'm coming for the bachelor party. I'm ordering t-shirts with "batch mode off" in monospace.

"Yeah, I got your e-mail, I see the subject. Oh no, dude, it says urgent so it went straight to the URGENT queue. Yeah? Ah. Sure, I'll get to it as soon as I get through the ASAP, NOW and YESTERDAY queues. Well, if you wanted me to read it right away you should've say there's NO HURRY - I read only one no-hurry e-mail a day but there's currently 0 tasks on that queue."