Tuff Shed

Tuff Shed’s data platform sits at the center of a distributed system spanning legacy ERP, cloud infrastructure, and a modern digital storefront. The core work involves designing and maintaining the pipelines, models, and services that keep operational and fiscal data clean, accessible, and in sync across the stack.

Frontend Monorepo

The monorepo is built on Next.js with TypeScript and orchestrated by Turborepo and pnpm workspaces. The team built and maintains a shared UI component library of 75+ components consumed across all applications, along with a shared helpers package that abstracts integrations with Salesforce, Storyblok CMS, Google Maps and Places, and analytics. The system uses Jotai for lightweight state management, Formik and Yup for form validation, and DAPR for inter-service communication.

The architecture keeps six distinct applications aligned through shared packages, consistent TypeScript configuration, and a unified design system built on Tailwind CSS. It’s the kind of codebase where a new teammate can spin up any app and immediately recognize the patterns.

Backend Services

The backend is a .NET 9.0 microservices architecture with 13 services — including a DataMigrationService, NextworldService, SalesforceService, JdeService (for JD Edwards legacy integration), and HomeDepotService — all communicating via DAPR sidecars. Infrastructure runs on Azure with Redis caching, SQL Server and MongoDB databases, and Docker Compose for local development.

The team built RESTful APIs in C# using ASP.NET Core with proper MVC patterns — 28 controllers, DTOs, repository abstraction, and polymorphic domain models with inheritance hierarchies. The Bogus library is used for realistic test data generation, and defensive programming patterns maximize backward compatibility in production hot patches.

Promotions Engine

Beyond the core monorepo, the team designed and maintains a configuration-driven promotion rules engine that powers the company’s discount and offer system. The engine supports six distinct promotion types — percentage-off, free upgrades, buy-X-get-Y, tiered spend thresholds, and location-specific product discounts — all defined declaratively in CSV-based rule files versioned in Git and deployed via CI/CD. The rules span multiple dimensions including building type, product series, and store location, making the system flexible enough to support diverse marketing strategies without code changes.