Systems studio
EngContinuum Judgment across the full path — board to agent.
Device bring-up and agent-assisted delivery, written as evidence. Registers, flash paths, and contracts — not a tour of CRUD demos.
Practice
Device → protocol → service → agent
Mode
One-person studio + AI leverage
Offer
Authority IP · selective reviews
Start here
- Contract-first Vibe Coding Generate the API contract before the frontend or the backend. Shared types and a fixed response envelope are what stop field names from drifting when an agent writes both sides.
- AI-assisted debug of an Ingenic T23 SFC Treat a flash-program failure as one hypothesis per measurement. On a T23, PERM ERR and stage2_write error(-1) were closed by readback regions, not by another cloner retry. A rail drop mid-write is a different bug with a similar log line.
Latest notes
All notes →- Rescuing a T23 NOR with a CH341A and an SOP-8 clip When the USB cloner can still read but can no longer write through the SoC SFC, stop retrying the broken master — clip the flash, dump first, then erase, program, and verify off-board.
- Debugging an SFC failure with Vibe Coding How a contract-first agent loop turned a T23 flash-program failure into a hardware conclusion — and which lookalike bugs had to be ruled out first.
- A Vibe Coding workflow that ships A personal practice for turning a PRD into a running frontend, API, and database — contract first, then code.