In my last job they required us to turn on a task timer for every little thing. Remembering to do that, and to turn it off, was a royal pain. First I had to look up which task it is, start the timer, stop the timer, find the next task and repeat, then flip back to the first task. Lots of open browser tabs within tab groups to keep track of it all. And if I came up short or went over on budget, there was a “conversation” with management to account for discrepancies. Then I had to go by memory and try to reconstruct the “missing time” accurately enough to be convincing.

Now that I’m freelancing, I try to keep up the habit because it does have merit for tracking estimates and actuals, but now it’s just me to answer to for discrepancies and I can fudge the numbers as I see fit. The time records did, however, save my bacon in a recent dispute.

MFA authentication setups that don't support standard authenticator apps, like 1Password or Google Authenticator can burn.

Yes, Microsoft, I am looking at you.

Most tedious part of my day...

While meetings are boring and awful and all, it's probably spinup times for me. Each and every change requires a minimum of 35 seconds of spinup to test. If i'm testing something with mailers or other daemons, that increases to easily 90+ seconds (plus the worker thread pickup times).

It's not enough time to do anything useful, and more than enough time to lose my focus. It turns every task into boring, tedious struggle. It's awful.

Apart from my coworkers, this is the single worst part about my job. (Okay, the awful code quality totally pushes this to third place.)

Useless meetings

HTML. I'm a C++ dev. That shit ain't for me.

Working along in a codebase for a few weeks. Then finding out there is a better more performant way to do something. Having to go back and tweak everything to use that feature you should have been using in the first place.

Thankfully, this has taught me to be more modular in the code.

The most tedious part of my day is when WSL crashes. I then have to close my editor, shutdown WSL in cmd, start the editor again, open a terminal and start over. This happens 2-3 times a day.

I got terminal white-space autism because of the CMS Of Doom.
Forgetting one or adding one too many leads to major problems on prod.

The meetings where you have to attend the whole thing, but only the few minutes are actually applicable to you.

Let me quietly leave and get back to work.

import some random files to the database, daily

dealing with a crippling realization that my depressed brain is a pale shadow of former myself before bipolar, but getting lost in a contradiction posed by the fact that I have more experience and clearer vision now, not being able to decide what's better and who I'd rather be

Time sheets. I'm not a fan of our task management system, you don't check out jobs or tasks like moving cards on a kanban board, it's more of a loose, calendar-based setup. We're also in a small, open office so it can be difficult to remember to log things in the software when you could tell the person opposite you that their task is finished. On top of that a lot of the time it takes me longer than the scheduled time to get a job finished as I'm learning a lot of new stuff, so digitally documenting things like that worry me a little. I don't want to look like I can't hack it just because a job takes me longer than my much-more-experienced colleagues.
I should note that I understand it's all incredibly useful data to the company, but I hate doing it and it's very easy to forget or ignore.

Documentation...

Typing

Having to rewrite features because someone changes their mind

People deviating from what is optimal in general