Full-stack development, for me, means being willing to follow the problem across boundaries. A polished React interface is useful only if the backend state is coherent. A clean API is useful only if it matches the workflow. Infrastructure choices matter because they determine whether the software can be maintained when priorities shift.
The work on this site spans TypeScript, React, Next.js, Electron, PHP, Python, C#, WordPress, WooCommerce, Docker, Linux, and databases. I do not treat that list as a brand identity. It is the set of tools I reach for when the job needs a public website, an internal workflow, a desktop experiment, a small hardware bridge, or a service that has to run quietly in the background.
I care about software that holds up in the real world: code that can be changed, systems that can be observed, interfaces that fit the people using them, and deployment choices that do not make every future change expensive. The technical decisions I write about tend to focus on those tradeoffs rather than framework novelty alone.
This topic is the broad index for my web development, infrastructure, project architecture, and tool-building work.