About · the developer
End to end,
one developer.
Building since 2019, delivering for clients since 2022. This is the long version: how I got here, how I work, and everything I can build for you.
I started building in 2019, teaching myself the fundamentals and putting them to work on real projects until the pieces started to make sense.
Client work in 2022 was where it really clicked. The learning curve went vertical. My logic sharpened, systems I'd only half-understood started fitting together, and I learned what actually matters to a business, not just what works in a tutorial.
I work front to back because owning the whole thing myself means fewer handoffs and fewer gaps. Lately that includes wiring AI into the products I build, where it genuinely helps. A full-stack engineer with a modern edge.
- 2019building since
- 0+projects delivered
- 0+international projects
- 0+niches served
The trajectory
2019 to now. Every year a deliberate step deeper into the craft.
- 2019First lines of code.
Started building websites to understand how the web actually works: HTML, CSS, and JavaScript, one broken layout at a time.
- 2021Full-stack foundations.
Backends, databases, auth, APIs. The discipline of building something that works for more than one person and doesn't fall over.
- 2022First client work.
Started shipping for real clients: websites, CMS builds, and small web apps that businesses actually ran on.
- 2024Complete products.
Next.js applications end to end: dashboards, e-commerce, booking systems, owning the front end, back end, and deploy.
- 2026Adding the AI edge.
Integrating LLM APIs and AI features into web apps where they make the product genuinely better. The modern extension of solid engineering.
Operating principles
Four rules, learned the practical way: on real projects, for real people.
- 01Reliability over flash.A site that loads, works on every phone, and does the job beats an architecture nobody asked for. I optimize for the thing that's actually shipped and used, not the thing that's clever on a whiteboard.
- 02Own the whole stack.Front end, back end, database, deploy. When one person owns the full stack, the bugs that usually hide in the handoffs between specialists simply don't get a place to live.
- 03Build for whoever's next.Clean code, a headless CMS your team can actually use, and real documentation, so you're never locked to me. The best handover is one where you don't need me anymore.
- 04AI where it earns its place.I add AI when it makes a product genuinely better: a smarter search, a faster draft, a helpful assistant, not because it's the trend. Solid engineering comes first; AI is the edge that sharpens it.
Capabilities, in detail
The full map. What each line on the homepage actually means in practice.
/frontend
- React & Next.js applicationsSingle-page apps and server-rendered sites with the App Router, built component-first
- Pixel-perfect design-to-codeFaithful, pixel-perfect builds from a Figma file or a rough sketch
- Performance & Core Web VitalsFast first paint, healthy Core Web Vitals, images and bundles kept lean
- TypeScript, front to backTyped front to back, so refactors don't break things silently
- Responsive, accessible interfacesLayouts that work on every screen and for every user, keyboard and screen-reader included
- Reusable component systemsReusable, documented UI a team can keep building on
- Site builders: WordPress & WixWordPress and Wix when a client wants to manage it themselves
/backend
- REST & typed APIs (Node.js, Express)REST and typed endpoints in Node.js and Express, designed to be easy to consume
- Databases: PostgreSQL, MongoDBPostgreSQL and MongoDB: schema design, queries, and migrations done by hand
- AI integration & automationLLM APIs (OpenAI, Claude) wired into real features, with a human in control
- Auth, roles & permissionsSessions, roles, and access control that hold up to real use
- Payments & integrationsStripe checkout, webhooks, and third-party APIs wired in cleanly
- WordPress plugin developmentCustom plugin development for sites that live on WordPress
- Wix Velo & backend APIsBackend code and APIs on Wix when that's where a client already is
/launch
- Deployment: Vercel, Netlify, DockerVercel, Netlify, or Docker, set up so deploys are boring and reversible
- CI/CD & Git workflowsGit-based pipelines that test and ship on every push
- Domain, DNS & email setupThe unglamorous setup that makes a site actually go live and reachable
- Analytics, SEO & monitoringMeasurement, metadata, and sitemaps so the work gets found and understood
- Debugging & troubleshootingTracking down the bug in someone else's codebase, not just my own
- Security & data protectionInput validation, rate limiting, and sensible handling of user data
- Docs, handover & no lock-inClear docs and a clean repo, so the project is yours, not mine