Who I am
I'm Mila Chen. I build systems from zero to one: test automation, CI/CD, local RAG, content publishing — each starting from the first line of the framework. Self-taught all the way up, so I know the pain points and the professional side both; the quality bar is simple — nothing ships without passing verification. This site records what I actually built and which holes I stepped in, posted when there is something worth posting, not on a schedule.
Whether something got done properly matters to me, a lot.
Whether it's my own work or something I've shipped, I don't settle for good enough. It isn't about chasing perfection. It's that quality lives in the details nobody asked for, and nobody may ever notice.
Quality is the one thing I won't compromise on.
What I do
- Automation pipelines: chaining repetitive manual work into one line, from trigger to verification to output
- RAG / local AI: offline knowledge bases, retrieval pipelines, multi-agent workflows
- Web engineering: static sites and template systems, with all styling generated from a single brand config
- Document engineering: templated notes / reports / logs / guides — one source file, many outputs
How I work
"One person, a team's output" is not about working around the clock. It runs on a self-built cognitive operating system: three layers of infrastructure, carrying this site and every pipeline on the tools page.
- Memory: decisions and lessons persist across working sessions, so no hole gets stepped in twice
- Learning: uncertainty is never guessed away; it goes into a queue, gets researched, and the knowledge base sharpens with use
- Process: one person under full team discipline, claim, branch, review, verify, and the main line stays clean
Services (B2B)
Anything software can verify can be fully automated.
I build test automation for server products, and every step of the road is one I have walked myself: manual testing → designing test suites, test cases and test steps → designing and building the automation framework → scaling the automated tests → setting up CI/CD → finally chaining it all into one pipeline nobody has to watch. This house was not handed over floor by floor — one person built it from the foundation up. A real case: one person, one year, matching the output a large team elsewhere took years to produce.
Confidentiality concerns? NDA is fine — or I design the architecture only, and implementation stays with your own team.
Contact & channels
For work inquiries, or to follow what I am building: