Sarp

To rule hardware in or out, two quick tests.

Wiggle the plug while something is playing. A crackle, or sound appearing briefly, means a mechanical problem — a worn jack, or debris. Jacks fill with pocket lint remarkably fast, and a wooden toothpick and compressed air fixes a surprising share of "dead" headphone sockets.

Boot something else. A live USB system, or another operating system if the machine dual boots. Working there means the hardware is fine and the problem is entirely software on the original system. That single test saves a lot of guessing and takes ten minutes.

If it is silent everywhere, including in firmware beeps and in another operating system, then it is the jack or the board.

Work from power outward, because everything above it is meaningless if power is wrong.

1. Measure the supply at the module's own pins. Not at the board's output — at the module, with the meter. Cheap jumper wires and breadboards fail constantly and a wire that looks connected often is not.

2. Check the voltage the module wants. This is the single biggest cause with marketplace modules. Many want 3.3 V and will be damaged or simply not respond at 5 V, and plenty of tutorials were written for a different board. Check the module's markings and your board's pin voltage.

3. Check the logic levels match. A 3.3 V module and a 5 V board need level shifting on the signal lines. Sometimes it works anyway, sometimes it does not, and sometimes it works until it does not.

4. Confirm the bus finds it. For anything on a shared bus there is a scanner sketch that lists the addresses it can see. If your module does not appear, stop debugging the library — you have a wiring or power problem.

That scanner step is the one that saves the most time. It splits the problem cleanly in two.

Once the module answers on the bus, the remaining causes are software and counterfeits.

The library expects different pins. Example code hard-codes the pins the author used. On a different board those pins may not exist, may not do that function, or may be used for something else. Check your board's pin mapping rather than the tutorial's.

The chip is not what the listing said. Marketplace modules are frequently built around a clone or a relabelled part with different behaviour. Symptoms are initialising fine and returning nonsense, or working intermittently. If a module behaves oddly and everything else checks out, buying one from a different seller is a legitimate diagnostic step rather than giving up.

A missing pull-up or an unconnected enable pin. Some modules need a pin held high or low that the tutorial's board did on its own.

The module is dead. These are cheap and a proportion arrive faulty. This is why buying two of anything cheap is sensible — a second unit turns a week of doubt into a five-minute test.

On when a separate terminal is worth it, the honest answer is that the built-in monitor is fine for most work and there are three cases where it is not.

You need the port while the editor has it. Only one program can hold a serial port. A standalone terminal you can close independently is easier than fighting the editor for it, and this is the most common reason people switch.

You need to see the board boot. The interesting output often appears in the first moments after reset, and by the time the editor's monitor opens it has been missed. A terminal already connected when you press reset catches it.

You need logging, or non-text data. Capturing to a file over hours, or looking at raw bytes in hexadecimal, is what the standalone tools are for.

For anything else, the built-in one is fewer moving parts.

A practical caution against the enthusiastic version of this: do not build the structure first.

The failure mode is spending weeks on an elaborate scheme of index notes and naming conventions, with almost no actual content, and then abandoning it. The systems that survive grow from writing.

The minimum that works: write notes, link when you naturally refer to something, and let the structure emerge. If a concept gets referred to often, it earns its own note at that point rather than in advance.

Also worth knowing that linking and folders are not exclusive. I use folders for coarse separation — work, personal, reference — and links for everything within. The argument between them is mostly people defending whichever they adopted.