I just looked at code so bad that I decided to resign today instead of December.

I feel like Satan just reached through my eyeballs and punched me in my frontal cortex.

@ludicity wow that is impressive. Leave a commit with a single added line:

//TODO: Resign

@ludicity
Well, if you're that miserable maybe it's the push you needed and you can send Satan a fruit basket or something.

@ludicity Godspeed.

@ludicity cackling, that's hella ballsy

@ludicity "I guess maybe today after all, Satan"

@ludicity CONGRATS GRAD

@ludicity ha creating code so bad that it makes someone ragequit is now on my bucket list.

In all seriousness, congratulations mate.

@ludicity and/or a git blame “-you- made me do this”

@MaryAustinBooks So true, thank you Satan!

@Cacotopos

"As a data engineer

I want to die

So that you can't hurt me with this architecture anymore"

@ludicity git commit -m “i quit”

@ludicity oh you saw my recent series?

@banana Someone here once saw me write a commit without -m, and it turns out 60% of the team didn't know you could do that, which is why 50% of our commits, and this is serious, say "linting fix".

There are also 27 instances of the word "stupid".

@ludicity @banana What's wrong with writing "linting fix" if the commit is just a linting fix?
That said, I'd say usually it's best to amend the previous commit with the linting fixes if they haven't been pushed yet.

@ludicity They don’t know how to use git on the command line* _and_ they don’t use a GUI tool such as GitHub Desktop?

*I don’t blame them for that.

@ludicity @banana I have a wrapper function around git which forbids me from using -m for exactly that reason

@DrHyde @ludicity @banana I have "git commit -save" in my typing muscle memory, where 'e' opens the editor, and 'v' also shows the diff which is quite convenient.

@ludicity

I've pretty much worked on my own code for 35 years now, so my problems are self inflicted. They aren't that bad, though, at least not *to me*.

In what I read from your blog post (so far) you seem to be dealing with Google Analytics and AWS logs. I'm semi-convinced that they break those on purpose because their income depends on projects being untrackable.

I've pretty much worked on my own code for 35 years now, so my problems are self inflicted.

This is what I do here too, sadly it does not pay the bills.

CC: @ludicity@mastodon.sprawl.club

@vv221

I've done it in a decidedly bill paying sense (single person highly specialized business).

@ludicity

That might be the trick: here I keep doing it as a non-profit activity, so I need to regularly take a job working on someone else’s awful code.

CC: @ludicity@mastodon.sprawl.club