MichaelFBryan

Google defines it pretty well: A worked example is a step-by-step demonstration showing how to solve a problem or complete a task.

A worked example of how an ordinary Go service can quietly grow into an application runtime, and how a well-designed abstraction can make that hidden architecture explicit.

An entity is a person, place, or organization that you want to track in your Second Brain. By creating separate notes in your Obsidian vault for each entity and using the power of backlinks, you can create a rich, interconnected knowledge base.

> The interesting thing with this example in particular is that the audio output from the radio is already very well-gated thanks to an RF squelch

Author here. Luckily for my purposes I can rely on the radio already having a squelch, so I could get away with using the naive solution.

If it was the raw audio I'd probably need to implement something more sophisticated such as splitting the audio by frequency and giving each band a noise threshold (as atoav mentioned).

I like the idea of breaking things up by frequency! Luckily my application (radio transmissions) is quite amenable to this naive noise gate, but I can imagine for more complex audio (e.g. if the radio doesn't have a built-in squelch) having tighter control over what triggers the gate would greatly improve quality.

i'm more thinking about libraries like tensorflow, ssh, or libgit2.

Yes you could rewrite them in Rust, but considering these are tools which are used all over the ecosystem and have massive momentum behind them, your time would be better spent building cool things on top of existing work than reinventing the wheel and trying to convert the ecosystem to something which will (initially, at least) be an inferior product.

The original statement was deliberately opinionated and extreme, but I still feel like the pragmatic approach of reusing existing libraries instead of rewriting them is the best one for the short/medium term (jury's still out on the long term costs/effects).