Project writeups
These writeups frame the kinds of systems I have worked on and the engineering judgment behind them. They are intentionally practical: what the project needed, what the stack was good at, and where the tradeoffs lived.
Ionic and Capacitor workflow for shipping one operational app across web and mobile while keeping native device behavior within reach.
Built for fast iteration, offline-tolerant screens, and practical deployment across mixed devices.
Server-rendered and API-backed PHP applications with database-backed workflows, clear admin surfaces, and maintainable deployment paths.
Focused on boring reliability: readable code, stable data flows, and interfaces people can use repeatedly.
Hands-on mobile work in Swift, Java, and Kotlin to understand platform conventions beyond hybrid wrappers.
Better decisions around when to stay hybrid and when a platform-specific path is worth the cost.
C projects, Lua scripting, and current Rust study for deeper control over memory, performance, and runtime behavior.
A steady habit of learning beneath the framework layer so higher-level work stays grounded.
Small experiments with Convex for realtime state, quick product ideas, and backend-light prototypes.
A playground for trying ideas quickly without turning every prototype into infrastructure work.