Technical Opinions Grounded in Real Production Software Work.
I review source code, system architecture, incident history, and engineering decisions for attorneys and parties in software disputes. My opinions are grounded in hands-on production engineering, not abstract theory.
Request a Confidential ConsultationWhen I Am a Fit
This service is for matters where the core questions involve software architecture, source code quality, operational failures, accepted engineering practices, project breakdowns, or technical causation.
Software Project Failures
Assess whether the delivered system matched the claimed scope, whether implementation choices were technically reasonable, and whether the project failed because of engineering defects, product ambiguity, or management breakdown.
Source Code and Repository Review
Review repositories, commit history, deployment artifacts, and surrounding documentation to evaluate maintainability, completeness, reliability, and adherence to accepted software engineering practices.
Outages, Data Loss, and Operational Failures
Reconstruct what failed, identify likely technical causes, separate root cause from downstream symptoms, and explain the practical impact in language attorneys and fact finders can follow.
AI-Assisted Software Disputes
Evaluate AI-generated code quality, review engineering controls around AI-assisted development, and assess whether the resulting software was suitable for production use.
Credentials Relevant to Expert Work
My background is in long-lived production software systems, source code review, incident investigation, and architecture decisions made under real operational constraints. I have worked independently since 2014 and spent 2016 through 2026 with dotstudioPRO in a technical leadership role involving backend systems, APIs, infrastructure, production operations, and engineering review authority.
Prior Testimony
Testified in 2026 in REGISTRATION EXPRESS GROUP v. TWINING, No. 25CL-00146, Shasta County Superior Court. Retained by the defendant in a software development dispute involving WordPress hosting, software transfer, and accepted software engineering practices.
Technical Scope
Relevant experience includes software architecture, backend systems, REST APIs, distributed systems, AWS infrastructure, subscription systems, source code review, software failure analysis, incident investigation, and AI-assisted software engineering evaluation.
Production Scale
Work has included high-volume API systems, subscription infrastructure supporting more than 100,000 users, AWS analytics platforms, and long-lived SaaS systems requiring reliability, incident response, and practical root-cause analysis.
Limits of Claimed Expertise
I stay within areas supported by actual work. This page does not claim expertise in cryptography, penetration testing, kernel development, embedded firmware, malware analysis, mobile security, or machine learning model training.
What an Engagement Can Include
Case Screening and Merit Assessment
Early review of pleadings, claims, repositories, communications, and technical artifacts to determine whether the matter presents a coherent software issue worth deeper analysis.
Reports, Declarations, and Rebuttal
Written opinions tied to the materials reviewed, including affirmative analysis and rebuttal of opposing technical opinions where the engineering logic does not hold.
Deposition and Trial Preparation
Support for attorney preparation, issue framing, terminology clarification, exhibit review, and testimony that explains technical decisions in direct plain English.
Methodology
My process is evidence driven. I review the actual code, infrastructure, logs, communications, timelines, and system behavior before forming opinions.
Materials Reviewed
- Source code, repository history, and deployment artifacts
- System architecture, infrastructure, and vendor dependencies
- Incident records, support history, and retrospective analysis
- Contracts, scope documents, technical communications, and handoff records
Work Performed
- Reconstruct technical timelines and decision points
- Separate root cause from downstream symptoms
- Compare implementation choices against accepted engineering practice
- Assess whether the evidence supports or limits a claimed conclusion
Output
Where the evidence supports it, I provide opinions tied to specific technical facts, explain causation and engineering alternatives in plain English, and identify the limits of the record where stronger conclusions would not be justified.
Areas I Commonly Address
- Software architecture and backend engineering
- REST APIs, distributed systems, and cloud infrastructure
- Source code quality and accepted software engineering practices
- Authentication, entitlement, and subscription systems
- Production incidents, outage analysis, and failure investigation
- Project and vendor delivery disputes
- Hosting, transfer, and operational handoff disputes
- AI-assisted software development quality and suitability
Common Questions
No. Local consulting remains a core part of the business, but expert witness matters can be handled beyond Redding when the technical issues fit my background and the engagement terms make sense.
The most useful starting materials are repository access, contracts or statements of work, technical communications, incident records, screenshots, deployment details, and a short explanation of the disputed issues and deadlines.
No. I stay within the boundaries of my actual experience. This does not include cryptography, penetration testing, kernel development, embedded firmware, malware analysis, mobile security, or machine learning model training.
Request a Confidential Consultation
Tell me the case type, venue, deadlines, and what materials are available. I can then confirm whether the matter fits my background.