The tools behind what I build.
From the editor to the edge, this is the technology stack I work with and where each part fits.
Frontend
Interface layer focused on clarity, interaction quality, and presentation. I use these tools to ship responsive interfaces that feel polished.
My primary editor, shaped around a tuned setup of extensions, keybindings, and routines.
Semantic, accessible markup. Every project starts here.
I use custom properties, grid, flexbox, and animation when I want more control over the interface.
Component-driven UIs. Used for interactive interfaces and single-page applications.
Full-stack React framework. Server rendering, API routes, and file-based routing.
Utility-first CSS framework. Fast prototyping and consistent design systems.
Backend + Data
Application logic, data, and the machinery behind products. I mostly build this layer in PHP and Node.js, backed by both SQL and NoSQL databases.
My primary backend language, used with Laravel for products like Qixla Cloud and this site.
Event-driven runtime. Used for bots, APIs, and real-time applications.
Document database. Flexible schemas for rapidly evolving products.
Relational database. The go-to for structured data and complex queries.
In-memory data store. Caching, sessions, queues, and pub/sub.
Infra + Delivery
Systems side focused on keeping products running in production, from containerization through deployment, edge caching, and day-to-day operations.
Containerization for consistent environments and reproducible deployments.
The foundation for my production systems, including Ubuntu and Debian server management.
Reverse proxy, load balancing, TLS termination, and static file serving.
Code hosting, CI/CD with Actions, and collaboration on all projects.
Version control. Branching strategies, rebasing, and clean commit history.
DNS, CDN, DDoS protection, and edge caching across the domains and products I run.