It also helps that a lot of my AI use is on my own side projects, where I set the pace. That makes it fun instead of draining. Maybe the tiredness has less to do with AI itself and more to do with being pushed to maximize throughput?
271 karma · joined November 29, 2025
It also helps that a lot of my AI use is on my own side projects, where I set the pace. That makes it fun instead of draining. Maybe the tiredness has less to do with AI itself and more to do with being pushed to maximize throughput?
They vibe-coded a piano app for their daughter, and since my daughter is also learning piano I figured I'd give it a shot. The whole thing came together in minutes with Claude Code. My daughter immediately started giving feedback — she's basically the product manager now.
Full story on my blog: https://victorantos.com/posts/hold-my-beer-i-vibe-coded-a-pi...
https://codorex.com/shared/zIe6BrLCVfaPt1DuWm1DeyoMIIeTPyed
Congrats on the traction!
Built it for my 10yo. Solo dev, .NET + Claude Haiku. Free to try, no signup.
The specs are pretty wild:
Form Factor: It rests on the brain "like a piece of wet tissue paper."
Resolution: 65,536 electrodes with 1,024 simultaneous recording channels.
Bandwidth: 100 Mbps wireless link (custom ultra-wideband radio).
Power: Fully wireless via an external relay station.
The differentiator here seems to be the non-penetrating approach. Unlike Utah arrays or Neuralink threads that penetrate the cortex, this sits on top, which theoretically minimizes tissue scarring/reaction while maintaining high data throughput (100x current wireless BCIs).
Paper: Stable, chronic in-vivo recordings from a fully wireless subdural-contained 65,536-electrode brain-computer interface device
Interesting that it handles this fine (functional orbital mechanics, animation) but would probably struggle to recreate the exact pixel positions of the Space Jam layout. Confirms the pattern: good at "make something like X" but bad at "recreate X exactly."
Can confirm: Claude is weirdly good at generating functional game logic from vague prompts, but spatial precision is a constant battle. Anything involving exact pixel positions needs validation/correction layers on top.
The suggestion upthread about having it write its own measurement tools seems promising - haven't tried that approach yet.
A lot of the SD-card wear issues come from people running “normal PC workflows” on a storage medium that was never designed for that pattern.
Something I’ve seen help many newcomers is simply enabling an overlay filesystem or tmpfs-based writes. It’s basically the middle ground between a full RAM-boot distro (piCore, Alpine diskless, NetBSD) and a standard SD-based Raspberry Pi OS.
You still get the normal ecosystem and docs, but almost no writes hit the card unless you explicitly commit them.
For anyone stuck between “I want something simple” and “I don’t want my SD to die,” overlays are the easiest win.
Every design tool today (Figma, Illustrator, CAD) still uses this exact UX pattern. Sutherland nailed it 62 years ago with a light pen and an oscilloscope.
Thankfully Azure keeps deleted SQL databases recoverable, so I got it back in under an hour. But yeah - no amount of CLAUDE.md instructions would have prevented that. It no longer gets prod credentials.
Had to intervene manually. Thankfully Azure keeps deleted SQL databases recoverable for a window so I got it back in under an hour. Still way too long. Got lucky it was low traffic and most anonymous user flows hit AI APIs directly rather than the DB.
Anyway, AI coding assistants no longer get prod credentials on my projects.