Tools people
can depend on.
C# and .NET at the core. WPF on the desktop. Blazor and Next.js in the browser. Each interface shaped around a real task.
Loading page
C# and .NET consulting for desktop and web. Modernize applications, connect data, and build software around the work people need to do.
Make legacy .NET applications easier to change. Replace manual handoffs. Build a clear path from the first request to a supported release.
C# and .NET at the core. WPF on the desktop. Blazor and Next.js in the browser. Each interface shaped around a real task.
ASP.NET services, Python data work, and repeatable console jobs. Clear contracts, useful errors, and a record of what changed.
GitHub review, deployment checks, and recovery plans. AI contributes proposals inside a workflow with accountable review.
Follow a feature through the software campus. Meet the guardians behind the interface, the service, the data, and the release.
The same family as CAD Guardian. A different world to build.
The 3D campus loads when it comes into view.
Request. One sample feature enters the campus with an acceptance check.
A fictional, deterministic demonstration. The moving packet represents one feature; technology names describe roles in the story. No live builds, cloud activity, or AI requests.
Choose a character to see what it owns and what it hands over.
The core guardian turns an accepted behavior into typed, testable logic. Desktop apps, web interfaces, and background jobs can share the same rules.
C# / .NET“The calculation is ready. Keep it off the interface thread.”
WPF“I’ll show progress and keep the draft if saving fails.”
Different tools. Shared responsibility for the result.
Sometimes the right answer is a small function. Sometimes it is a connected system. AI belongs where its contribution can be tested.
Explore the technology practiceStart with the user’s task, the existing rules, and the failure cases. Use C#, TypeScript, or Python to make the behavior explicit and testable.
Explore this approach →Use a console tool, script, or scheduled job for validation, imports, and routine transformations. Give it clear inputs, useful logs, and a safe way to retry.
Explore this approach →Use a documented contract and narrow permissions. Validate incoming data, make failures visible, and keep changes traceable to the request that caused them.
Explore this approach →Give the model approved context and a bounded task. Evaluate the proposal, handle uncertainty, and require review before consequential changes.
Explore this approach →Explore an idea, explain unfamiliar code, or compare approaches. Turn the useful result into a specification, a test, or a reviewed implementation.
Explore this approach →FryTools shows how operational software grew from workbooks into connected applications. The other stories show current, runnable approaches to modernization and data handoffs.
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.
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.
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.
Begin with one workflow and an agreed result. Test it with the people, data, and failure cases that shape the real work.
Tell us who uses the system, what fails, and what needs to keep working.
Agree on one useful improvement, how you will accept it, and what stays outside scope.
Test the change with representative data, permissions, connected systems, and failure cases.
Hand over the test results, release notes, rollback steps, known limits, and support responsibilities.
CAD Guardian works on the engineering side. TSmithCode builds the software that supports the work. CAD Guardian LLC remains the contracting and accountable entity.
Tell us who uses the current process, what fails, and what a dependable result would look like.
Show us the software problem Do not send source code, credentials, customer data, or production records in first contact.