Skip Navigation

Posts
12
Comments
355
Joined
3 yr. ago

  • Why begrudgingly?

  • Codeberg isn’t viable for proprietary software

  • 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).

  • I’m still far happier with it than literally any other programming language I’ve ever used

  • 😆 yeah I didn’t read it that hard

  • I totally agree, that Go snippet is absolutely more maintainable. Though you forgot the curly braces and the semicolons are unnecessary.

  • I’ll stick with Go TYVM

  • Yes, preferring a language that’s easy to read and therefore easy to maintain over a language like Rust is definitely coping 🙄

  • Since this is a hypothetical to make a point, obviously from scratch

  • 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.

  • There’s always room for improvement.

  • They were doing that before “AI” development was a thing

  • 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.

  • Anything that makes the codebase harder to maintain than it should be is technical 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?

  • The ecosystem is slowly migrating to Wayland. It will probably take another decade but at some point your choice is going to be Wayland, or ancient unsupported systems.

  • Programming @programming.dev

    The Curse of Knowing How, or; Fixing Everything | Blog

    notashelf.dev /posts/curse-of-knowing
  • Experienced Devs @programming.dev

    Is GitHub Copilot worth it to you?

  • .NET @programming.dev

    What am I losing by not using the C# Dev Kit?

  • Programming @programming.dev

    Why is crypto.subtle.digest async?

  • Programming @programming.dev

    What search engine do you use?

  • Programming @programming.dev

    What scientific journals do you recommend?

  • Experienced Devs @programming.dev

    Self taught = no imposter syndrome?

  • Experienced Devs @programming.dev

    Systems engineering in the software industry

  • Programming @programming.dev

    What languages are well suited for testing SDKs written in multiple other languages?

  • Programming @programming.dev

    Why should I use rust (as a Go enthusiast)?

  • Programming @programming.dev

    How often does branchless programming actually matter?

  • Experienced Devs @programming.dev

    How do you organize miscellaneous tasks?