Product engineering from first architecture to production operations.

01 · Independent software practice

DontSweat.Tech

A software engineering practice for businesses that need to design, build, stabilize, and ship clear working systems.

I use DontSweat.Tech as the home for hands-on client work across product development, architecture, cloud infrastructure, integrations, performance, and technical leadership.

• Turn ambiguous business needs into practical delivery plans
• Build across frontend, backend, data, and deployment boundaries
• Leave clients with clearer systems, ownership, and operating paths

02 · Client ecommerce launch

Vye Coconut Water

A modern ecommerce presence for Vye Brands Inc., delivered with the launch infrastructure around it.

The project connected a polished customer experience with Stripe checkout, transactional email, store-location maps, domain migration, DNS cleanup, and email deliverability. I treated those pieces as one coordinated release instead of separate handoffs.

• Customer-ready storefront and Stripe-backed checkout
• Resend-powered email and Leaflet store-location experiences
• A coordinated domain, DNS, and mail migration

03 · Workforce coordination SaaS

Farero

A multi-organization workforce platform for schedules, timekeeping, reporting, and day-to-day team coordination.

Farero brings calendar workflows, client and team management, role-aware timesheets, PDF reporting, notifications, and structured quick intake into one operational product. The backend emphasizes tenant boundaries, explicit review flows, and production-minded rollout controls.

• Multi-team identity and role-aware access boundaries
• Timesheet, scheduling, reporting, and client-site workflows
• Encrypted intake drafts with review-before-commit behavior

04 · Wholesale ordering platform

Jumun

A wholesale commerce system with separate retailer, operations, and API applications inside one coordinated product architecture.

I structured Jumun as independently deployable storefront and admin frontends backed by a Spring Boot modular monolith. Shared design primitives and an OpenAPI-generated client keep the product coherent without coupling every release.

• Separate retailer and administrative experiences
• Domain-oriented Spring Boot API with PostgreSQL and Flyway
• Independent AWS delivery paths for frontend and backend workloads

05 · Migrations, AEM, and reliability

Enterprise platform delivery

Large-scale platform work shaped around content operations, governance, accessibility, security, and release constraints.

My enterprise work includes moving on-premise platforms toward cloud-native delivery, refactoring more than 40 backend services, building AEM components, and designing cache behavior across Apache, Dispatcher, and CDN layers while keeping releases available and supportable.

• AEM migrations and reusable component implementation
• Cloud delivery and zero-downtime release planning
• WCAG-aware frontend work, security hardening, and production support