💡 Open to ideas
🚫 Closed to nonsense
Tech leader and software architect. I own the thread from what users see to what runs in prod: APIs, data flows, Salesforce-shaped integrations, and the boring stuff that keeps services alive—metrics, deployments, failure modes. Architecture isn’t a diagram; it’s what you debug when something subtle breaks in serialization or CRM sync.
Main lane: TypeScript, React, and Node. Also deep in enterprise Java and Salesforce—mortgage flows, risk calls, regulated data, and systems that stay observable and safe to change.
- Product & delivery — Shipped beats clever. Clear scope, reviewable iterations, outcomes you can point at. Figma tokens and code stay aligned when the IDE shares the toolchain (MCP).
- Architecture & reliability — HTTP boundaries, versioning, performance when it matters, and production reality: CI, metrics, failure modes.
- Lending, CRM & risk — Loan lifecycles, CRM picklists, strict null handling, and risk engines with testable domain logic and honest HTTP contracts.
- Delivery automation — GitHub Actions, Jenkins, Argo CD, Helm / Kubernetes: repeatable CI, declarative CD, gates before merge, promotion across dev/stage/prod.
- AI-assisted engineering — Cursor, ChatGPT, Claude, Codex as a fast pair—not an oracle. Models suggest; humans and CI own the merge.
Focus: Systems you can change without heroics—and “works on my machine” doesn’t count.
Primary: TypeScript / React / Node · also Java, Salesforce, AWS / Kubernetes.
Product
Enterprise & APIs
-007396?style=flat&logo=openjdk&logoColor=white){kind=icon}
Data & CRM
Platform & cloud
Delivery & AI
- Automation — Pipelines teams can read and fix: CI gates, GitOps rollouts, traceable releases.
- AI — Same bar as any other change: read the diff, run tests/linters, no silent production deploys.
| Repository | What it is |
|---|---|
limited_wecheck |
Gradle monorepo: mortgage domain, Salesforce connectors, loan models, and an HTTP risk engine with tests for ugly inputs. |
serverless |
Lambdas, SQS, schedulers, thin HTTP—event-driven work that shouldn’t live in the monolith (CRM sync, notifications). |
devops_infra |
Helm / Kubernetes: ingress, TLS, env parity for risk / CRM, secrets, and CI artifacts landing where the cluster expects them. |
frontend |
React / TypeScript for lending and ops—REST-backed flows with the same vocabulary as the Java and serverless pieces. |
docs |
OpenAPI, Postman, Markdown, Confluence—one place for integration semantics so eng, architecture, and QA aren’t arguing from three PDFs. |
|
|
|
