So;dfjkhijasdfkjq;sdfhjkl;asdf

I copy a line from one spec (to create a user) and paste it in another spec. It works just dandy in the first, and throws MySQL missing column errors in the other.

Fucking what.

This codebase is full of shit like this. Things work in one place but not another, and it’s never obvious why. Tens of thousands of gotchas and quirks. The only way I can get an answer to things like these is to either beg my boss for an explanation, which I’m sure he’s long since tired of, or spend a full day (or more) wading through several rabbit holes filled with raw sewage.

I wasted two hours today trying to get a simple fucking factory to work. And you know what? I just gave up and used the existing admin user. Yeah it’s a bad idea, but it’s fucking good enough.

They can yell if they want.
I have no cares left.

Get assigned ticket.
Finish the most of the feature. Finish most of the specs.
Push.

Second dev wants to own accounting half of the ticket.
Rip out half my changes, rewrite specs.
Push.

Code review asks for minor changes.
Finish them.
Push.

Product creep creeps the scope.
Finish the feature again.
Push.

Product creep creep-creeps the scope.
Finish the feature again.
Push.

New release happens.
Merge in master; fix conflicts. Run specs; random unrelated specs fail, some fail intermittently. Rabbit holes of complicated, unexplored, obviously-flawed code.
Fuck that. Push.

Had a 1:1 with my boss last night and together we figured out a tricky bug related to my PR. However, either my PR or that bug patch broke a tangentially-related test. Queue my usual exhaustion, and I gave up trying to fix it.

This morning, I'm looking at it and nothing makes sense. My change should not have broken the test. So I reran the controller's tests, and... they all pass?

What is logic.

Good thing, though; that test leads to a few rabbit holes I haven't even begun exploring yet.

Oh, never mind. It broke again.
Ergh, here we go. 😔

Oh God, guys.
It was the stuff of nightmares! It's going to keep me up forever tonight

Through a strange series of events, my job has led me to looking at an uncompressed image of atv riders taken in 2004. This career field might be the most full of rabbit holes to go down.

After a wildly productive day yesterday, I've spent most of today staring at my screen, going down mental rabbit holes. Sod's law!

It's not helped by an accidental all-nighter last night - I'm too old for that shit these days

God I hate rabbit holes.

FUCK rabbit holes real hard. When you spend a week creating a super optimized recursive handler for mapping redundant database row results and you wake up from your coma realizing everything could be handled by a much simpler SQL query done in five minutes. Fuck me, fuck the rabbits creating holes to fall into and fuck Alice for creating the fucking illusion of wonderland.

Has modern day development become all rabbit holes all the time?

Seems that way to me. Tired of it.

yo yall posting shit "rabbit holes" now? b64 isn't a rabbit hole, it's a wrapper.

It is currently 5:30 AM, I've been trying to upgrade a server by one single major OS release for the last 3.5 hours. All major apps were no issue, except one.

Redmine.

That thing runs on Ruby.

Ruby, as it turns out, doesn't really like the way Debian handles package management.

And now, I have Redmine that, even if I completely uninstall / reinstall, won't start

I went down several rabbit holes, trying to operatively find what the issue is. But I never got to the key issue.

Fuck ruby. Fuck Redmine. Fuck nothing-saying error messages. Fuck bundle. Fuck gem. Fuck it all.

I'm redirecting the Redmine domain onto the server backup I've made. Upgrading that thing is a nightmare.

Maybe now I can finally go to bed...