About
I build software that can be operated with confidence
I’m Joey Wang, a software engineer and consultant. I work across three areas that keep software dependable as it grows: DevOps and reliability, AI-native engineering, and full stack development.
My background is rooted in long-lived web systems. I’ve designed and maintained learning platforms, worked on product teams, modernized application and deployment infrastructure, and supported systems where reliability matters to the people using them every day.
The interesting work is rarely just choosing a framework. It is understanding the existing system, finding the constraint that is actually limiting it, making a change that can be explained, and leaving the next person with a safer path forward.
What I work on
- DevOps and Reliability: Kubernetes, PostgreSQL, cloud infrastructure, CI, and the operational feedback loops that make deployments boring. See DevOps and Reliability.
- AI-Native Engineering: coding agents, LLM features, and local model workflows with explicit boundaries around verification, privacy, and human approval. See AI-Native Engineering.
- Full Stack Development: Rails and learning platforms improved incrementally, from slow queries to frontend behavior, without pretending a rewrite is free. See Full Stack Development.
How I work
I start with evidence: the code, the data, the deployment path, the logs, and the experience of the people using the system. I prefer a small, reversible improvement over a broad redesign justified by fashion.
A typical engagement may involve:
- understanding the current architecture and the problem behind the request;
- identifying risks, dependencies, and a practical first slice;
- implementing and testing the smallest coherent change;
- documenting what was learned and how to operate or roll it back.
That approach is useful when a team has a Rails application that has grown over time, an LMS that is difficult to change safely, or a delivery process that no longer gives enough confidence.
Selected work
- Consulting: a practical starting point for Rails, LMS, reliability, and modernization conversations.
- When a Rails or LMS Platform Becomes Hard to Change: an evidence-led way to diagnose platform friction.
- AI’s Impact on the Software Development Lifecycle: thinking about useful AI without confusing assistance with judgment.
- Durable Codebase Context: notes on making engineering context easier to inspect and reuse.
A note on this site
This site is a working record rather than a catalogue of buzzwords. Some posts describe completed engineering work; others are experiments or developing ideas. I try to make that distinction clear, show the reasoning behind decisions, and avoid presenting an interesting possibility as a shipped result.
If you are dealing with a difficult-to-change Rails or learning platform, get in touch through the Consulting page.