ArduinoLibraries

Arduino libraries for the chips that turned up again and again across the projects — the garden’s early bench, written down. Driver code for the LED drivers, the port expanders, the sensors and relays that every 2011–2013 build seemed to need: written once, kept where every later build could reach them.

Each library is C++ in the Arduino tradition — a class, a begin() method, a handful of calls that make a strange chip feel like an old friend. They were forged the hard way, chip by chip, the way libraries always are: in the middle of a project that needed the chip yesterday.

They exist because the young maker in Athlone learned what every maker learns — that you build the tool first, and the thing second.

Ogma, the honey-mouthed god of the Irish, looked at ink on a skin and was not impressed. Ink fades, skins burn, floods carry pages to the sea — so Ogma cut his letters into stone instead, and named the cutting ogham, and ogham’s whole grammar is edges: a stroke for the ridge of a stone, a notch for its corner. A thing carved once is read by everything after. The Athlone workshop learned the same sermon around 2012, when the bench was a desk, the solder iron was new, and every project kept reaching for the same half-dozen chips — the LED driver, the expander, the relay — and kept writing the same forty lines to wake each one up. The young maker did what Ogma did: stopped, cut it into a library, and let the stone do the remembering. After that the chips answered by name. One of those cuts is on film — an LED rig failing beautifully on the bench while the library held — and the scar it left grew moss. Write once, in stone, said the bench. Everything after will read you.

The camera came to the bench itself, and the reels it carried back are planted here:

ledion fail — an LED scar, filmed where the libraries were forged.