This is the way. Exceptions are overrated.

C be like “this shit is true af” and it’s the number 6396128.

Or you can write an entire theme park simulator in assembly because you like pain or something.

Say what you will, but that was an economically viable route to take. I’m still in love with TTD and RCT2.

Invest in debugging and code review capabilities: With 45% of developers reporting increased debugging time for AI code, organizations need stronger code review processes. They need debugging tools specifically designed for AI-generated solutions.

Or, maybe, don’t use tools that generate garbage code.

I’ve been using linux as a daily driver for more than twenty years. At the same time I had to use Windows for work. Windows has always created more headaches and wasted more of my time than linux. The people who fail on linux are those who expect/demand it to work like windows and those who are not willing to invest the same amount of time they used to learn their way around windows on linux.

“Windows just works” has always been a lie. It’s a fragile heap of crap that constantly breaks or misbehaves. People spend a metric shitton of time with workarounds for failing updates, registry hacks … or externalize that cost to others. Windows “just works” if your kids, company IT, or someone else keeps it working.

If you invest the time to learn a distributions/linux ways, and make a reasonable pick for distribution, linux is much more stable and low maintenance than windows.

neat

Though, obviously I had to come up with some ridiculous solutions:

bool IsEven(int i) => ((Func<string, bool>)(s => s[^1] == 48))($"{i:B}");

This one works without conditionals :)

bool IsEven(int i)
{
    try
    {
        int _ = (i & 1) / (i & 1);
    }
    catch (Exception)
    {
        return true;
    }

    return false;
}

Not to take from all the funny answers … but

bool IsEven(int i) => (i & 1) != 1;

(C#)

At this point I assume ignorance and incompetence of everybody talking about benefits of “AI” for software development.

I’ll quote myself from some time ago:

The entire article is based on the flawed premise, that “AI” would improve the performance of developers. From my daily observation the only people increasing their throughput with “AI” are inexperienced and/or bad developers. So, create terrible code faster with “AI”. Suggestions by copilot are >95% garbage (even for trivial stuff) just slowing me down in writing proper code (obviously I disabled it precisely for that reason). And I spend more time on PRs to filter out the “AI” garbage inserted by juniors and idiots. “AI” is killing the productivity of the best developers even if they don’t use it themselves, decreases code quality leading to more bugs (more time wasted) and reducing maintainability (more time wasted). At this point I assume ignorance and incompetence of everybody talking about benefits of “AI” for software development. Oh, you have 15 years of experience in the field and “AI” has improved your workflow? You sucked at what you’ve been doing for 15 years and “AI” increases the damage you are doing which later has to be fixed by people who are more competent.

I like to style visited links blue and unvisited links purple, just to mess with people.

The unix philosophy is about making highly reusable and pluggable tools which is the exact opposite of what OP is asking for.

An example would be a REST API with a few endpoints where the database operations are handled directly in the route handlers uniquely for that specific task.

That’s a prime example for untestable code (not testable with unit tests/without IO). That might be fine for a tiny experiment, but I’d advise against it for projects of any size, even private ones. Always use a model like MVC, MVVM, three layers (data, business, user) …

I feel like we should have an in depth talk to better understand the problems you’re facing and the line of thinking that motivates your initial request. Unfortunately I currently do not have the time for that. The best I can do now, with the best of intentions, is to advise you to read literature about software development. The trouble is, that I’m not sure what to suggest, because I think there’s nothing that fits your premise. Maybe read about library development/reusable code so you better understand what not to make reusable by comparison? So maybe “Reusable Software: The Base Object-oriented Component Libraries” by Bertrand Myer or “Analysis Patterns: Reusable Object Models” by Martin Fowler. Though, both books are more on the old-fashioned side and I wouldn’t recommend them if you’re not an avid reader and (former) student of computer science.

Before I jump to “that’s a really bad idea” with my 20+ years of experience: why?

I mean, sure, don’t implement functionality you don’t need, but making code not reusable intentionally? Why?

Well, not by accident.

I just dabbled in javascript again, and that description is spot on!

console.log(‘javascript operators are b’ + ‘a’ + + ‘a’ + ‘a’);

Obligatory: how to exit vim

vim > emacs, though.