The Six Stages of Code Grief

https://suppo.fi/post/9016065

Ngl that’s like baby levels of nasty code. The real nasty shit is the stuff with pointless abstractions and call chains that make you question your sanity. Stuff that looks like it’s only purpose was to burn the clock and show off a niche language feature. Or worse than that even is when the project you inherit has decade old dependencies that have all been forked and patched by the old team

If all I had to worry about was organization and naming I’d be over the moon

Git commits with message saying “pushing changes” and there are over 50 files with unrelated code in it.

In the past I had commit messages with change numbers from a system, that was no longer in use.

So the commit just said “CH-12345“. It is the kind of annoying, where you can’t even really be mad at someone.

I put my ticket numbers in my tickets, but i also try to describe the change too (e.g. “Fix bug where xyz happens due to zyx action”). Also, atomic commits: commit only related changes.

Yes, it takes longer to commit large changes, BUT you can easily merge the commits, and rollback only what needs to be rolled back.