A development lead who connects technology and designs direction

I began my career in web design with a visual design background, and now work across design and engineering. I have practical experience in frontend, backend, infrastructure, and cloud, and I previously led projects as a team lead. I think in terms of service outcomes, not isolated features.

I prioritize context before depth

I am less focused on mastering only one tool deeply from day one, and more focused on understanding how multiple technologies connect in a real service.

When I face a new technology, I build quickly first, make a structural hypothesis, and then validate it against docs and implementation details.

I treat technology as a tool

React, Next.js, Spring Boot, NestJS, Redis, AWS, and Kubernetes are not goals by themselves. I choose combinations based on product constraints and operating conditions.

I adjust depth intentionally

I design for system balance first, then dive deep where bottlenecks or failures actually require it. As a lead, choosing what to optimize, how far to implement, and when to refactor matters most.

In short, I am an engineer who can connect technologies into a working structure and still go deep when needed to deliver outcomes.