The outcome matters. The decision that changed the system matters more.
See how Chris reasons across product, engineering, QA, release, infrastructure, and AI delivery, and how those decisions changed the product system.
What these stories are
These are permanently anonymized accounts from Chris Martinez’s prior professional experience. They are not presented as CAM Software client engagements. When approximate figures appear, the individual story identifies them as owner-observed testing; unsupported or identifying claims remain omitted.
Product recovery
Recovering a critical mobile workflow and changing how the company built and supported apps
A rebuilt production application took roughly 10 seconds to open an important record on a current iPad and 30 seconds or longer on older Fire-class tablets in the observed test contexts.
Decision
Repair the request, state, and rendering path; validate it across controlled accounts; then convert the evidence into architecture and device-support standards.
Replatforming
Rebuilding an e-prescribing application when the old product was the only documentation
The original application had working behavior but little reliable documentation for why screens, workflows, and API calls worked the way they did.
Decision
Treat the migration as product and behavior recovery, and bring product ownership and QA into the work before release pressure peaks.
Product delivery
Turning an established EHR web workflow into a mobile-first product for internal beta
An established healthcare company needed a new React Native product that translated, rather than merely copied, its web application for therapists and practice staff.
Decision
Use existing business logic and APIs where they fit, while redesigning the experience around mobile authentication, lighter payloads, multi-account calendars, messaging, and mobile-first use.
AI delivery
Making AI part of a controlled engineering system instead of an unreviewed shortcut
Teams wanted faster delivery from large language models, but token usage and code generation alone could not provide architectural consistency, acceptance-criteria coverage, or accountable decisions.
Decision
Give each agent a narrow responsibility and place human review and approval between meaningful transitions.
Release infrastructure
Replacing a temporary mobile build bottleneck with an automated release path
A team regularly exhausted its free hosted-build allowance, then moved artifacts manually between the build service, shared storage, QA, BrowserStack, and the app stores.
Decision
Pay for short-term capacity while the launch was at risk, then build the owned Azure pipeline only after the team had room to do it safely.
Bring the same rigor to the decision holding your product back.
One less thing to worry about.