Clarity over cleverness
Code should be easy to reason about six months later, not just impressive for six minutes.
I am a software engineer and team lead focused on modern web development. My work sits between frontend engineering, custom WordPress development and the practical realities of shipping for clients.
I started by building websites hands-on and gradually moved deeper into custom engineering, integrations, performance and team leadership. That mix matters: I still like being close to the code, but I also think about scope, maintainability, communication and what happens after launch.
I have worked across custom WordPress themes, ACF-heavy content systems, React/Next.js applications, Shopify customizations, landing-page platforms and the odd “why is this only broken on iPhone?” emergency.
Code should be easy to reason about six months later, not just impressive for six minutes.
Spacing, hierarchy, feedback and motion are not polish at the end—they shape how the product feels.
The first version should be strong, but it should also leave room to evolve without a rewrite.
If something is unclear, fragile or likely to fail later, surface it early and solve the actual problem.
HTML, CSS, JavaScript, TypeScript, React, Next.js, jQuery, GSAP, Swiper
PHP, ACF, WooCommerce, CPTs, WP_Query, AJAX, Elementor, WPBakery
Shopify, Webflow, Unbounce, GoHighLevel, Vercel, Hostinger
Git, GitHub, Figma, REST APIs, QA, technical planning, code review
Make it clear. Make it fast. Make it resilient. Then make it feel like someone cared.