Personally, I’ve been compiling a cache of datacentric interpolations of real-world metrics used to synergistically integrate human intelligence with the intersection of science, technology, mathematics, arts, and philosophy since the moment I was born, and let me tell you, this is what I was born for.

This is a dream job!

I mean, nightmares are dreams, too.

Bruh yer not doing it right. Are you stupid, bruh? You gotta work on yer promps, bruh. You gotta watch some tiktoks on it, bruh. Bruh, go watch @demisets4, bruh. Learn to prompt, bruh. Your not good at it, bruh. Bruh, you should try something else if you can’t figure it out that’s a you problem, bruh.

Which sounds like great, practical advice in a theoretical perfect world!

But, the reality of the situation is that professionals are usually balancing a myriad of concerns and considerations using objective and subjective evaluations of what’s required of us and quite often inefficiency, whether in the form of programmatic complexity or in the form of disk storage or otherwise, has a relatively low precedent compared to everything else we need to achieve if we want happy clients and a pay check.

I’m a purist. The stable and persistent main branch, regardless of what you want to call it, should always and only ever be exactly the same as the code that’s currently deployed to the production server. Generally the only exception is for the short duration between a push and deployment under normal circumstances.

But every job I’ve ever had, there’s at least one maverick who knows git way better than anybody else and is super advanced, so they do their own thing which is totally better in a million different ways but essentially fucks everybody else over. And I’m not even here to say they aren’t smarter than the rest of us and I’m sure that somehow their process is better than what we currently do. But with version control, my anecdotal experience has been that the most important things for running smoothly are: consistency and having everybody on the same page. Process doesn’t need to be perfect, maximally efficient, bleeding edge, etc to achieve that.