TSmithCode is the software engineering practice of CAD Guardian LLC, building and modernizing applications around the work teams already depend on—from workbooks and desktop tools to connected platforms, data, reporting, and controlled automation.
This buyer-safe model shows trusted behavior, data, failure paths, release decisions, and the ownership a working system needs.
A production-shaped vertical slice exposes authoritative records, decisions, exceptions, and ownership from input to outcome.
FryTools shows how operational software grew from workbooks into connected applications. The modernization and data stories show current, runnable approaches to difficult software decisions.
FryTools grew from quote/RFQ workbooks into 14 documented desktop applications and then an integrated Blazor platform, while preserved solution snapshots expose up to 46 projects across apps, services, libraries, data, tests, deployment, and support—not 46 apps.
A runnable public kit turns a legacy .NET request into a framework, package, authentication, data, UI, deployment, parity, rollback, and first-slice decision without pretending a fixture scan proves a production migration.
Public data-integration and reporting fixtures make source ownership, field mapping, nulls, duplicates, validation, lineage, reconciliation, exceptions, retries, and decision-safe reporting inspectable before live credentials or customer exports are introduced.
We trace the users, trusted behavior, source data, integrations, failure modes, and release path around the request before deciding what to change.
Trusted behavior is distributed across legacy code, databases, integrations, deployment steps, and operator knowledge.
Spreadsheets, inboxes, shared files, and manual reconciliation are carrying application-level responsibility.
System handoffs and probabilistic automation need explicit ownership, validation, retries, review, fallback, and support.
Map the current behavior, move it into maintainable software, connect the right data, and give the team a release path it can support.
Users, behavior, data, integrations, release, and ownership shape the solution. The stack follows those operating needs.
Build internal applications and workflow systems around explicit users, records, decisions, exceptions, and ownership.
Review solutionStabilize and modernize business-critical C#, VB.NET, desktop, web, API, service, SQL, and reporting systems in reversible slices.
Review solutionClarify system boundaries, dependencies, trusted behavior, delivery controls, release quality, observability, and support ownership.
Review solutionDefine authoritative data, versioned contracts, validation, reconciliation, retries, audit evidence, and operational support.
Review solutionPlace AI inside bounded workflows with approved context, evaluation, reviewer decisions, correction, fallback, privacy, and cost controls.
Review solutionThese models make modernization, integration, and controlled automation concrete before a team commits to implementation.
Modernization advances through behavior-backed slices with explicit compatibility, release, rollback, and ownership controls.
Integration becomes supportable when ownership, contract state, reconciliation, retries, and exceptions share one operating view.
Probabilistic output stays inside a bounded review loop with evaluation, correction, fallback, privacy, and cost controls.
Each step keeps current behavior, data effects, security, validation, release, rollback, and support clear from discovery through handoff.
Name users, trusted behavior, data, integrations, environments, failure modes, release constraints, and accountable owners.
Define the smallest end-to-end change, acceptance criteria, privacy and security needs, fallback, and stop conditions.
Build one focused slice and test representative behavior, data effects, integrations, permissions, failures, deployment, and recovery.
Leave test results, observability, rollback guidance, known limitations, documentation, and clear support responsibility.
The practice focuses on internal and technical systems where users, data, integrations, release, privacy, and support all affect whether the software can be trusted.
TSmithCode handles software-led systems. CAD Guardian handles CAD-led delivery. Both stay close to the work, data, and people responsible for the result.
Both practices operate through CAD Guardian LLC, but their public buyer journeys, services, implementation stories, discovery, and contact routes remain distinct.
Name the users, current behavior, stack, source data, integrations, failure mode, constraints, and timeline.
Do not send source code, credentials, customer data, or production records in first contact.
