It’s just a branch guard + properly implementing git user and team permission structures - you’re not “configuring a server”

git never --gonna-let-you-down

🎶 every branch is sacred 🎶

Ideally:

how much of this can I automate so it just purrs like a kitten for as long as possible

Realistically:

how quickly can I satisfy these stupid fucking product requirements without incurring so much tech debt that it makes my job soul-destroying?

Hell yeah non-Euclidean downloads are the best

Look at what they need to mimic a fraction inaccurately.

The fundamental mathematical nature of how binary floating point values are stored means that extremely straightforward and rational (in the mathematical sense of the term) base-10 arithmetic can surprisingly often yield results that are irrational (again, mathematically) in binary - hence why you’ll sometimes see a result of 3.000000000101325 or something like that in places where you’d expect the result to be simply 3.0

But also, perhaps a proctologist

I mean… I just don’t plug in or use any of the LLM shit, and it works quite nicely. You’re not forced to use that part of it, no matter how much they try to market it.

And if it gets to the point where it’s truly unavoidable, there’s always the “fork it and strip it” option, since the code is open source.

Lmfao

Exposed deprecated cred-inclusion URI format, wheeeee

And the db name is short for “analysis”, of course

🤓🫠

Try Zed. It’s a lot like VSCodium (de-MS’d VSCode), but written in Rust, so it’s stupid fast.

I suppose they prefer buttons to snaps, zippers, Velcro, or toggle loops

Oh, it gets better: three different retired programmers who made attempts to implement objects three different ways into C, in the style of three entirely separate languages that are idiomatically alien to C.

Your boss doesn’t get to leave the room, it seems.

Any time I have a “superior” that insists tech debt isn’t a problem, I feel an incredibly strong compulsion to lock them in a room with a laptop and tell them to implement something extensibly and maintainably in our codebase, and that they won’t be let out or fed until they do.

And by “implement” I mean write the code and the tests and test automation.

And then they have to pass a code review, and write appropriate doc for any externally facing interfaces/apis/ui/etc.

We’d stop having stupid fucking opinions like that right goddamn quick if this policy were implemented.

Login with your mom 👩‍🦳

Ngl I kinda want to get into metalworking. It looks super fun, tbh.

Gotta get my nut

You left off a zero

If I’m gonna have to un-fuck your AI slop codebase, you better fucking believe I’m going to charge you through the nose for it.

Corollary:

The job market will be flooded with a shitload of junior devs who never actually earned their degree in the coming years, and anyone older than a mid-gen zoomer is gonna be able to pretty much write their own check.