Why you can't just vibecode MacAMP: everything done well has architecture
HankYeomans · x · 2026-09-29
Responding to "why not just vibecode it," HankYeomans shares architecture sketches of his MacAMP music player to show the audio pipeline is deeply involved: the oscilloscope must track the track's actual frequencies, the visualizer and Milkdrop visuals likewise, title/artist metadata must be extracted from the decode, and a functional playlist demands even more architecture. A "just bounces around" playlist, he quips, is cauliflower rice — the reason most things built without architecture fall short: everything done well has an architecture.
Related event: Dev Shares Architecture Diagrams to Explain Why MacAMP Can't Be Vibecoded(4 posts)→
More from coding & agent
- Community-maintained list tracks 51 active AI angel investors with sources and verification dates — TheMoonMidas · 2026-09-29
- px0 release fixes LSP memory leaks, ReDoS vulnerability, adds CSV table rendering — arpit_bhayani · 2026-09-29
- Local gamedev AI stack: Meta's Muse Glimmer nails tool use in one try where Gemma 4 12b fails — draginol · 2026-09-29
- Founder: AI Can Now Do the Work of 10 Employees Before You Hire — FinanceYF5 · 2026-09-29
- Univer open-sources an Office SDK for AI agents: spreadsheets, docs and slides in one runtime — abhishek__AI · 2026-09-29
- Gamers are using Opus 5.5 to rewrite entire games in Rust and merge them together — Promptmethus · 2026-09-29