277,248 NAND Gates, Printable Robots, and the Art of Building to Understand
How this was made Verified AI
Every Intellegix briefing is generated from that day's broadcast and run through automated checks before it publishes — with a human paged on any flag. Here is the trail for this edition.
Someone built a working computer from 277,248 discrete NAND gates — not a simulation, not an FPGA abstraction, but physical gates wired together to implement an ALU, memory controller, and everything else a functional processor requires. The NAND-16, as the project is called, drew 148 points and an 87-comment thread on Hacker News. Its pedagogical value lies in inverting the usual trajectory of computer science education: rather than starting several abstraction layers above the hardware, the NAND-16 forces the builder to watch complexity compound with each layer added, demonstrating in physical form why those abstractions exist.
At the other end of the accessibility spectrum, the JBR-001 is an open-source desktop robot powered by an Arduino Uno and designed to be fully 3D printable. It received a modest 13 points — typical for Show HN hardware posts — but its project documentation is thorough enough that a motivated stranger with a printer and basic electronics skills could replicate it. That replicability is the benchmark for a successful open-source hardware release.
The phyllotaxis LED display from Jagi Studio drew 302 points and sat at the aesthetic intersection of mathematics, biology, and physical computing. Phyllotaxis is the pattern governing how seeds arrange in a sunflower and leaves spiral around a stem, derived from the golden ratio; the project maps that pattern onto an audio-reactive LED array that pulses and flows in response to music. A real-time solar system visualization rendering 526,000 tracked asteroids and all catalogued satellites — with accurate orbital mechanics drawn from JPL's Near Earth Object catalog — offered a different kind of visual depth, its comment section filling with readers identifying specific asteroids in interesting resonance orbits.
The Floppy Emu hardware failure analysis contributed something less glamorous but arguably more durable: a public teardown of which components fail, how they fail, and what the failure modes reveal about the design. Rigorous failure documentation shared openly is, as commenters noted, what keeps vintage computing communities functional. Knowledge about how to fix things does not survive if knowledge about how they break is not recorded.
On the software side, Matt Keeter's post on WebGPU data layouts and the Facet property-testing framework addressed a specific, underspecified problem in GPU compute pipelines. WebGPU is young enough that established best practices do not yet exist for many of these problems; each piece of well-documented technical writing contributes to an emerging canon. Similarly, a post on applying 2D Discrete Fourier Transforms and advanced dithering to maximize image quality on eInk displays — devices with constrained color palettes and specific refresh characteristics — exemplified what commenters called over-engineering in the best possible sense: accepting nothing from the default and instead modeling the physics of the hardware to optimize accordingly.