ABOUT IAN

I build systems that expandwhat one person can do.

I’m Ian Yu, a Senior Full-Stack Engineer and the founder of Amender Studio.

After more than a decade of building production software for established businesses, I now apply the same engineering discipline to independent products, AI agent systems, knowledge infrastructure, and self-funded market research.

01 / ENGINEERING

Engineering has always been the foundation.

My experience spans backend systems, frontend architecture, platform infrastructure, and production operations. I have designed and delivered enterprise-grade systems across online gaming, back-office operations, and intellectual-property management—from .NET and C# distributed services using Clean Architecture to Vue 3, Nuxt 3, and TypeScript applications. Software quality, to me, includes reliability, maintainability, and whether a system continues to serve its purpose over time.

02 / AI COLLABORATION

AI changed the scale of my work—not my responsibility for it.

I use Cursor, Claude, Codex, Hermes, Agent Skills, and MCP integrations to accelerate implementation, refactoring, research, documentation, and collaborative analysis. Architecture, quality standards, validation, and final accountability remain human responsibilities. My focus has grown from individual assistants to coordinated agent workflows for research, implementation, review, and knowledge capture.

03 / THE STUDIO

Amender Studio is an independent lab.

It is not an agency or a conventional startup. It is where I turn ideas, research, and personal systems into visible outcomes. Some experiments become open-source projects or independent apps; others become reports, workflows, or lessons that shape the next project. Not every experiment needs to become a business, but every meaningful experiment should leave something useful behind.

PRINCIPLES

Working principles

Build real artifacts

Turn ideas into things that can be run, tested, read, or used.

Keep human accountability

AI expands the process; architecture, quality, and decisions remain mine.

Design for compounding

Leave reusable code, knowledge, infrastructure, or judgment behind.

Document the evolution

Changes in tools, methods, and judgment are part of the work.

Back to home↗