Consolidating automated QA into a database
Consolidating QA data into a database makes complexity, structure and code health available to both the human and the agent.
Lynn Cole / 标签
A thread through the work.
Consolidating QA data into a database makes complexity, structure and code health available to both the human and the agent.
Training a tiny CEO model on ambition, corporate biographies and legal drama produced something unexpectedly charming.
A coding-agent hardening checklist: model support, hooks, scheduling, tooling, skills and observability, with the remaining integration work still in flight.
Building a play-training dataset takes longer than the neat plan suggested. These are the challenge counts, solution trajectories and training signals so far.
A mentor improved the training signals but weakened Qwen’s self-assessment. The next corpus starts with code reasoning and software estimation.
Product hardening means finding the seams between features, models and workflows, while reducing the task-switching cost for the human.
A planned training harness combines coding datasets, recursive refinement, compiler verification, play exercises and persona-based reviews.
Pillowfort’s planner behaves differently when asked to build a company from scratch or augment an existing one. Ambition exposes the assumptions in the design.
A long-running agent that works silently can look frozen. Progress narration became a necessary part of the product, even when the underlying work was going well.
A search engine for indie creators, with anti-SEO editorial rules, a trivia pirate, and a classifier and reviewer that argue over the intake.
An experiment proposal separating activation injection, transcript conditioning, and what a model can infer after the intervention ends.
If people stop reading generated code, what should a language for the machine look like? A deliberately obnoxious compiler proposal.
Musical failure states, control settings, impossible instruments, and why I started building my own music pipelines.
Five tickets, three worker personas, QA and visual inspection: a Rain Simulator built with Qwen3.5-9B and a 40k context window.