About Trac Lam

Software Engineer · Backend Specialist · Product Builder

I’m a software engineer and product builder with over 10 years of experience building, maintaining, and improving web applications for international clients.

My work focuses on backend engineering, SaaS product development, system design, and AI-augmented software delivery. I believe the value of an experienced engineer goes beyond writing code. It comes from understanding business problems, making sound architectural decisions, building reliable systems, and taking ownership of the final outcome.

I’m particularly interested in how software engineering, infrastructure security, and AI can come together to help teams build better software faster—without compromising correctness, security, or long-term maintainability.

My Journey: From Urban Engineering to Software

My path into software engineering wasn’t conventional.

I graduated from the Ho Chi Minh City University of Architecture with a degree in Urban Infrastructure Engineering. During my studies, I learned to think about complex, interconnected systems: how individual components interact, how infrastructure supports human activity, and how design decisions affect long-term reliability and scalability.

Along the way, I discovered programming and began teaching myself web development, database design, and Linux system administration.

Over time, that curiosity became a career. I’ve worked across different layers of the web stack, helping international clients maintain and evolve production applications while developing a deeper understanding of backend systems, infrastructure, and software architecture.

My background in urban engineering continues to influence how I approach software. I tend to look beyond individual features and consider the larger system: its dependencies, failure points, operational constraints, and ability to evolve as requirements change.

What I Focus On

Backend Engineering & System Design

I specialize in backend-oriented web development, with experience designing APIs, data models, integrations, and maintainable application architectures.

My background includes PHP, Laravel, WordPress, JavaScript, and modern web application architectures. I’m also expanding my expertise in Go, Python, and Node.js to build backend services and SaaS products with different performance, scalability, and operational requirements.

I care about more than whether a system works today. I care about whether it can be understood, tested, maintained, and extended tomorrow.

Infrastructure Security & AI-Era Threat Response

As AI makes software development and cyberattacks increasingly accessible and scalable, infrastructure security has become an important part of my engineering focus.

I’ve designed a defense-in-depth security architecture for a fleet of hundreds of WordPress websites, with an emphasis on:

  • Zero Trust access: Reducing unnecessary trust and limiting access to critical infrastructure.
  • Infrastructure isolation: Containing potential compromises and reducing the impact of individual failures.
  • Centralized vulnerability response: Improving visibility into known vulnerabilities and coordinating CVE remediation across multiple websites.
  • Controlled security remediation: Applying security changes in a way that balances risk reduction with production stability.

This work reflects a broader principle: security should be built into the architecture and operational workflow, not treated as an afterthought.

AI-Augmented Software Engineering

I’m exploring how AI coding agents can improve the entire software development lifecycle, rather than simply generate code.

My interests include integrating AI into requirements analysis, technical specifications, implementation, automated testing, code review, and validation. I’m particularly interested in workflows where agents can work independently within clear boundaries, produce verifiable evidence, and escalate consequential decisions to humans.

Tools and technologies I explore include Claude Code, LLM integrations, and the Model Context Protocol (MCP).

My goal is not to maximize code generation at any cost. It’s to improve engineering throughput while preserving correctness, security, accountability, and maintainability.

SaaS Product Engineering

Alongside client work, I build and explore SaaS products and AI-enabled engineering tools to apply these ideas to real-world problems.

Working on products requires a different perspective from implementing isolated features. It means connecting technical decisions to user needs, business constraints, operational costs, and the product’s long-term direction.

I enjoy working across the full product lifecycle: understanding a problem, designing a solution, implementing the system, validating its behavior, and improving it based on real-world use.

End-to-End Engineering Ownership

I value engineers who can take responsibility for outcomes, not just assigned tasks.

For me, that means being able to move between business requirements, technical design, implementation, debugging, testing, deployment, and production troubleshooting. It also means identifying ambiguity early, challenging assumptions when necessary, and making trade-offs explicit.

Good engineering is not about choosing the most fashionable technology. It’s about choosing an appropriate solution, understanding its consequences, and ensuring that it delivers lasting value.

My Current Technical Focus

Technology evolves quickly, and I’m particularly interested in the intersection of backend engineering, infrastructure, and AI-driven development.

My current areas of focus include:

  • Backend development: Go, PHP, Python, Node.js, and API design.
  • Data infrastructure: PostgreSQL, data modeling, and application-level data architecture.
  • Cloud & DevOps: Docker, deployment workflows, infrastructure reliability, and security.
  • AI engineering: LLM integrations, AI coding agents, MCP, and agentic workflows.
  • SaaS architecture: Building practical, maintainable products that can evolve with real business needs.

Rather than pursuing every new framework or trend, I prefer to understand the underlying problems, evaluate the trade-offs, and adopt technologies where they create meaningful improvements.

My Engineering Philosophy

Three principles guide the way I approach software.

1. Understand the Problem Before Building the Solution

A technically elegant solution is not necessarily the right solution. I start by understanding the underlying problem, the people affected by it, and the constraints that shape a successful outcome.

2. Build Systems, Not Just Features

Individual features matter, but sustainable software depends on the systems around them: architecture, testing, security, observability, deployment, and maintenance. I aim to build solutions that remain understandable and dependable as they grow.

3. Take Ownership of the Outcome

Engineering decisions have consequences beyond the codebase. They affect users, business operations, security, delivery timelines, and long-term costs. I believe engineers should understand these consequences and take responsibility for the quality of what they deliver.

These principles become even more important as AI changes how software is built. When code generation becomes easier, sound judgment, critical thinking, verification, and accountability become increasingly valuable.

Beyond Client Work

I’m interested in building things that solve practical problems and exploring ideas that can become useful products.

My personal projects serve as a space to experiment with SaaS architecture, AI-enabled workflows, developer tools, and new approaches to software delivery. They also provide an opportunity to turn engineering ideas into working systems and learn from the constraints that only appear in real implementations.

I see continuous learning as part of the job—not because every new technology deserves attention, but because understanding how the field changes helps me make better decisions about what to build and how to build it.

Let’s Connect

This blog is my engineering notebook and digital workshop. I use it to document technical explorations, share lessons from real-world development, examine architectural decisions, and write about practical applications of AI in software engineering.

I hope these articles are useful to other engineers, technical leaders, and product builders who care about building software that works well today and remains valuable over time.

If you’re interested in backend engineering, system architecture, infrastructure security, AI-assisted development, or SaaS product building, feel free to connect with me on: