I don't quite understand why the author is doing special handling for PSG versus PCM audio.

My GameBoy emulator generates one "audio sample" per clock tick (which is ~1 mhz, so massive 'oversampling'), decimates that signal down to like 100 ksample/sec, then uses a low-pass biquad filter or two to go down to 16 bit / 48 khz and remove beyond-Nyquist frequencies. Doesn't have any of the "muffling" properties this guy is seeing, aside from those literally caused by the low-pass.

This article is taking some liberties with the word "prodigy" that I disagree with.

If the way you nurture a talented student is via "intense drilling", I would argue that the student is not a prodigy in the traditional sense, but a talented and determined student who may or may not be dealing with parental pressure.

The actual prodigies I've known absorb information and gain skills without significant effort - I knew someone who enrolled in a calculus class, skimmed through the book in a week or so, and then would only show up to class for tests (which they would ace).

So the article conclusion doesn't surprise me - inflict relentless training on a young talented person and yeah maybe they won't want to do that as an adult.

But as far as actual "prodigies"? There is no burn-out because there is no (or minimal) effort. The choice of whether to stick with an area of interest through adulthood is more of a personal preference than anything ingrained.

What if the tool required an "un-safeword" to do destructive things?

"Do you really want to 'rm -rf /'? Type 'fiberglass' to proceed."

There is a package called molly-guard that makes you type the computer's hostname when you are trying to do a shutdown or restart. I love it.

Like tarsnap's --nuke command:

  --nuke  Delete all of the archives stored.  To protect against accidental
          data loss, tarsnap will ask you to type the text "No Tomorrow"
          when using the --nuke command.

Probably inspired by Vinum's "NO FUTURE" for destructive operations. (Vinum was a raid system used on older versions of FreeBSD.)

Sure, in those cases - but if a command has a chance of nuking prod, you want some extra step in there. Preferably something that can't be muscle-memoried through.

probably best that you didn't say what kind of machine :D

This... what is this even doing? The camera controls are all fucked up. Why is mousewheel bound to rotate on the X axis? I can't actually select and move things. The container example is... is this supposed to be an object? Why is a cylinder floating above it? Why is shading all fucked up on the "twisted ribbon"? Etcetera etcetera.

Oh, it's vibe coded? And the author seems to have a bad case of Dunning-Kruger?

Yeah, I'll pass.

Damn, even his blog posts sound AI-written: https://campedersen.com/brep-kernel

"I'm not building a weekend project. I'm building a Fusion 360 replacement."

So here's what's worked for me over the years -

I collect interesting links/pages/stuff by emailing myself notes about them. I never actually _do_ anything with these notes, but from time to time I open the "Notes To Self" folder and skim through them. Anything that seems worthless I delete, anything that seems obvious I delete, the rest just sit there.

And that's more useful than you'd think - by reviewing them semi-regularly, you're indirectly memorizing their contents and refreshing their presence in your short term memory. And that to me is the benefit - not "copy this cool thing", but "feed my mind cool ideas until it has digested them and incorporated them into the gestalt.

I do something similar but also cooy the most interesting of these into Obsidian. Doesn't take long and the activity of sorting helps me remember. It's amazing how often when I skim these that I find something interesting/profound/useful that I've forgotten.

Cool! This just goes to show that old savings can sometimes come in handy.

Thank you for sharing the email‑to‑self workflow and regular review habit. How often you prune the folder and whether you’d appreciate intelligent reminders.

I don't give a shit if this thing works or not, the lols are worth it. :D :D :D

They can't do the work because they copied the firmware from some other company's product and don't actually know how it works.

That other company probably also copied it from somewhere else, etc.

Yeah. They, too, likely hired someone to reverse engineer it to make their own modifications. Let's add another to the chain. Surely the firmware could only become more "safe" with Lego block hacks. That's the point, right, OP?

All things considered, it sounds like the "gyro board" module is probably something that is OTS and already certified for use in a healthcare product. Wonder what the legality is of modifying such a thing in such a way?

As others have suggested, make your own or use a more ubiquitous module from the open source community. Integration wise, Claude can probably get you 80% of the way there.