Cron Labs
Jul 2024 – PresentFull-stack delivery across two enterprise products for external clients: a finance platform for a large manufacturer, and a seed-to-sale cultivation ERP. Both are closed-source client work, so the write-up below describes the engineering without naming the clients or the products.
Accounts-finance platform
Django REST · React 19 + TypeScript · Redis · MySQL · Azure · SAP PI/PO · Docker
- Own the SAP ERP integration and the multi-step approval workflow, from the Django data model up to the React 19 UI.
- Built the integration client around the failure modes that actually cost money — retries deliberately exclude POST, because a retried post double-books an accounting document, and SAP's HTTP-200 business errors are detected rather than read as success.
- Audit and hardening: an append-only audit log with a Redis write-behind buffer that can never block the operation it audits, a per-day dashboard cache, a sliding-window rate limiter, and the Azure AD SSO flow on the frontend.
Seed-to-sale cultivation ERP
Django 4 · DRF · React 18 · MUI · MySQL · Redis · Highcharts · AWS S3 · Metrc API
- Rebuilt the Metrc compliance layer — the state-mandated seed-to-sale system operators report to — as a declarative registry of 57 endpoint configurations, with failure handling for the HTTP 200 and empty body Metrc returns on some successful writes, which a naive parse reports as a failed sync.
- Two-way sync across plants, harvests, packages, lab-test lots and personnel, plus a crop-plan and routine engine rewrite, a read-authorization gap closed in DRF's default permission map, and IoT device integration modelled as data so onboarding a new device is a row insert rather than a deploy.