• 2 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: March 26th, 2025

help-circle













  • I work in this space. I agree with the gist of what you’re getting at; the catch is that it’s mostly just feeding the beast rather than breaking the dynamic.

    With LLMs, the problem is that they’re neither objective nor consistent, so the insurance companies are just going to increase their headcounts and hire more people to contest submitted claims. Deterministic output would change the picture in a big way, but I’m not seeing much appetite for that in the market for some reason.

    There’s a lot more potential for disruption in the form of advanced monitoring that can automatically flag and document complications in an objective way (which is my professional wheelhouse, for the sake of disclosure), but even then I expect payors to mostly pass the increased reimbursement rates on to their enrollees.

    A single-payor model is the biggest real cure for what ails our system, and I think I speak for a lot of us in the industry when I say that we’d happily lose our jobs to see that happen for the greater good.


  • I’m not a C guy, but afaik the closest thing to a useful manual in print is the K&R book (written by Kernighan & Ritchie, authors of the language).

    I have a copy on my shelf and it’s… alright. It’s much more focused on basic language constructs than pragmatic usage and opinionated style. Good for what it is, but you should pick up something more recent and opinionated to go alongside it IMO, based on whatever C dialect you want to focus on (C89/C23).





  • now that AI does everything 20000 times better than I ever will

    Now I’m no cognitive behavioral therapist, but, uh… this is what I think is catching you.

    I use AI plenty. I write most of my code with it. The garbage it spews out if you don’t hand-edit or get ultra-specific with design instructions is just atrocious, even if it looks sleek in the gestalt. You can give it small tasks and one-shots that it handles perfectly, sure, but it will rot a large codebase to the core if you start letting it make any real structural decisions.

    There’s simply no replacing architecture and focused thought, and writing code by hand isn’t going anywhere, even if the majority of the industry works with AI. I mentor junior engineers, I’ve seen the worst spaghetti they can make, and I can nonetheless confidently assure you that you’re better than “frontier” AI across multiple domains.


  • For the common-case risk model in the post body (SaaS user), the easy option is to set up a secondary git remote over SSH on a cheap cloud VPS. Then you can simply run git push backup-server or the like. Bonus points for setting up a cronjob to push to your backup box periodically, or to take periodic tarball snapshots of the repos on the server.

    Personally though: I self-host forgejo with registration disabled, and take automated snapshots with ZFS occasionally in case I truly bork things.