Have you not had friends or family come to you to solve their computer problems? Their problems are almost always some tedious, boring, “How do I make program X do thing Y?” It’s just a technical literacy skill check (how well can you navigate modern apps) not an actual “do you know how computers work” problem. Tedious as fuck. God save me from that shit.
If my girlfriend was a programmer bringing me some interesting technical problem, maybe. But even then, I spend 8 hours dealing with that shit, the chances that I want to deal with more of it after work are slim.
IMO that’s less idiomatic Go, more just plain old clearly written code. Whenever possible, the nominal (non-error) path should stay at the same level of indentation. Indentation should be reserved (as much as is possible) for loops and atypical conditions (including errors).
Maybe if you didn’t make unqualified blanket statements people would take you more seriously. If I trained my own LLM and kept it for my own personal use, in what way is that fascism? Because according to you it is, since all AI is fascism.
Ok…? That doesn’t change the fact that Microsoft was enshitifying the software they bought before “AI” was a thing. They didn’t suddenly start doing it when LLMs happened.
If we’re talking about the Linux kernel or Netflix’s video delivery infrastructure, maybe. But the majority of developers are not working on those. And I’m still going to call it “unavoidable technical debt” because for all intents and purposes that’s what it is.
If your project is easy to maintain (aka low tech debt) that means it should be easy to understand the overall structure and it should be easy to understand any given component. So a new dev should be able to quickly figure out what part they need to change and how to change that part.
Some large, complex systems (like an OS) are unavoidably complex. Maybe it’s not fair to call that tech debt, but it’s still functionally the same thing - stuff that slows down development velocity due to difficulty of understanding. It’s just (probably) unavoidable given the domain.
But the majority of software projects aren’t that complex. The majority of software is apps and libraries that aren’t terribly complex. Monsters like operating systems and million to billion user scale products are outliers.
“How easy is it to onboard?” is functionally equivalent to “How easy is it to understand?”. The biggest factor in maintainability almost always boils down to how easy it is to understand. So, difficult to onboard almost certainly means difficult to maintain, and thus is tech debt.
So… are you using nothing but FOSS from activist projects? That doesn’t seem like a big pool, from what I’ve seen. Or do you mean support as in with your time and/or money?
Have you not had friends or family come to you to solve their computer problems? Their problems are almost always some tedious, boring, “How do I make program X do thing Y?” It’s just a technical literacy skill check (how well can you navigate modern apps) not an actual “do you know how computers work” problem. Tedious as fuck. God save me from that shit.
If my girlfriend was a programmer bringing me some interesting technical problem, maybe. But even then, I spend 8 hours dealing with that shit, the chances that I want to deal with more of it after work are slim.