MacAMP author: why you can't just vibecode an audio player — every pipeline part matters
HankYeomans · x · 2026-09-29
MacAMP developer Hank Yeomans shared hand-drawn architecture diagrams explaining why a MacAMP-like audio player can't simply be vibecoded:
- The audio pipeline is deeply involved: the oscilloscope, visualizer, and MilkDrop visuals must accurately track the music's frequencies, and title/artist metadata must be extracted from the decode stage.
- Playlists, internet radio, docking, and skin loading each require their own architecture.
- His take: implementations that 'just bounce around' are cauliflower 'rice' — cutting corners on any part produces BS software.
Related event: Dev Shares Architecture Diagrams to Explain Why MacAMP Can't Be Vibecoded(4 posts)→
More from coding & agent
- Gamers are using Opus 5.5 to rewrite entire games in Rust and merge them together — Promptmethus · 2026-09-29
- Matt Shumer says Opus 5.5 cleared a 3D printer bed after 16 tries, taking humans out of the loop — mattshumer_ · 2026-09-29
- Claude autonomously builds a 'p(doom)' Beat Saber clone in one afternoon — burny_tech · 2026-09-29
- AlignOPSD fixes decision-timestamp mismatch in agent distillation, beating GRPO by 5.5-8.7% — Mingju Chen · 2026-09-29
- CMU's ControlScope: how much of a running agent workflow should be revised? — CarnegieMellonU · 2026-09-29
- CompoWorld scales general agent training by composing environments from reusable services — AllSpark-Research · 2026-09-29