How did you vet the quality of the documentation? I have no doubt that an LLM could produce a great deal of plausible-sounding documentation in short order. Even assuming you’re already completely familiar with the code base, reading through that documentation and fact checking it would take a great deal of effort.

What’s the quality like? I’d expect it to be riddled with subtly wrong explanations. Is Claude really that much better than older models (eg. GPT-4)?

Edit: Oops, just saw your other comment saying you’d verified it manually.

Addendum: if not a dog person, may I suggest ‘motorcycle’ as an alternative?

This chap certainly recommends it for his worries: https://www.youtube.com/watch?v=S83zwxkNio8

Edit: A motorcycle that is, unless someone has created 200mph dogs...

This is always what leaps out at me with this kind of “live better be happier” article. Yeah, if you’re sleeping well, eating well, working out regularly, spending quality time with friends, and have a healthy work life balance, you probably aren’t depressed. Might there be some possibility, perchance, that this is because any single one of those factors is almost impossible when in the pit of despair, let alone all of them at once? It’s like saying glasses cause short sightedness because hey, you almost never see someone with good eyesight wearing glasses.

Spam. :P

so 90% of the AI market?

Binary formats (that you can just fopen(), fseek(), fread() etc.) are generally super platform dependent. You can read in an array of bytes and then manually deserialise it (and I’ve done this, for sure!) but that’s basically one step away from parsing anyway.

Turns out if you design a forum where a high effort, high quality post can be devalued by a low effort response, you discourage high effort, high quality posters.

This is where we need SO's "The Answer" feature, whatever they called it. Never seen it distilled so well.

Ah yes, like those EV chargers that are rated at X kWh/hour.

You would hope that an EV reporting x kWh/hour considers the charge curve when charging for an hour. Then it makes sense to report that instead of the peak kW rating. But reality is that they just report the peak kW rating as the "kWh/hour" :-(

Tidy desk, tidy mind. Empty desk, empty mind.

Oh HELL no. :P Gcode is (at least if you’re talking about machining) the very definition of something you want to generate analytically using tried and tested algorithms with full consideration taken for the specifics of the machine and material involved.

I guess if you just want to use it to wiggle something around using a stepper motor and a spare 3D printer control board, it might be OK though. :)