Business problem
The useful logic had to survive while ownership, state, integration, and support became visible.
Loading page
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.
Engineering systems implementationFry RegletCAD Technical Manager; Operations Technology SpecialistAug 2017–Sep 2021
The useful logic had to survive while ownership, state, integration, and support became visible.
CAD Technical Manager; Operations Technology Specialist
The project taxonomy makes both end-user capability and supporting engineering visible.
14 delivered desktop apps · 44–46 classified solution projects · integrated Blazor platform
Contemporaneous résumé count, not a solution-project count.
Includes applications, services, libraries, data layers, tests, installer/support, and obsolete components.
Customer, pricing, product, source, and private workflow records remain protected.
The useful logic had to survive while ownership, state, integration, and support became visible.
14 delivered desktop apps 44–46 classified solution projects integrated Blazor platform
The project taxonomy makes both end-user capability and supporting engineering visible.
Customer Manager, RFQ Intake, Project Tracking, Quote Tool, Project Services, Lifecycle, Order Management, and related modules represented the work as records, states, decisions, and handoffs.
Open technical detailThe up-to-46-project census makes the architecture inspectable without calling every project an application: user-facing modules were supported by domain rules, data access, integration, tests, deployment, update, and audit components.
Open technical detailThe Blazor transition preserved useful desktop and workbook behavior while connecting role controls, NAV services, Power BI, files, configuration, documents, and project-service handoffs.
Open technical detail14 delivered desktop apps
A production-shaped vertical slice exposes authoritative records, decisions, exceptions, and ownership from input to outcome.
Start with the users, trusted behavior, data, integrations, release risk, and the first result worth implementing.
Review authorship, inputs, constraints, rules, outputs, integrations, validation, metrics, and source context in directly linkable technical sections.
Customer Manager, RFQ Intake, Project Tracking, Quote Tool, Project Services, Lifecycle, Order Management, and related modules represented the work as records, states, decisions, and handoffs.
Demonstrates operational software built from the real workflow rather than placed over undefined ownership.
A production-shaped vertical slice exposes authoritative records, decisions, exceptions, and ownership from input to outcome.
Workbook-to-platform operating-software lineage — Prior employment at Fry Reglet · documented software evolution. Public-safe reconstruction from dated presentations and private solution census.
The up-to-46-project census makes the architecture inspectable without calling every project an application: user-facing modules were supported by domain rules, data access, integration, tests, deployment, update, and audit components.
Shows the engineering needed to turn a collection of useful tools into a supported software platform.
A production-shaped vertical slice exposes authoritative records, decisions, exceptions, and ownership from input to outcome.
Workbook-to-platform operating-software lineage — Prior employment at Fry Reglet · documented software evolution. Public-safe reconstruction from dated presentations and private solution census.
The Blazor transition preserved useful desktop and workbook behavior while connecting role controls, NAV services, Power BI, files, configuration, documents, and project-service handoffs.
Provides a concrete, non-generic example of evolving software around operating continuity.
A production-shaped vertical slice exposes authoritative records, decisions, exceptions, and ownership from input to outcome.
Workbook-to-platform operating-software lineage — Prior employment at Fry Reglet · documented software evolution. Public-safe reconstruction from dated presentations and private solution census.
14 delivered desktop applications — Contemporaneous résumé count, not a solution-project count.
44–46 projects in three solution snapshots — Includes applications, services, libraries, data layers, tests, installer/support, and obsolete components.
Prior employment at Fry Reglet · documented software evolution. Contemporaneous résumé plus project-by-project private solution census and dated architecture decks.
Prior employment at Fry Reglet · documented software evolution. contemporaneous application and architecture presentations
Publication limit: No employer source, quote or customer record, pricing, product rule, credential, internal path, screenshot, or production artifact is published.
Prior employment at Fry Reglet · documented software evolution. 2021 résumé
Publication limit: No employer source, quote or customer record, pricing, product rule, credential, internal path, screenshot, or production artifact is published.
Prior employment at Fry Reglet · documented software evolution. private 44–46-project solution census
Publication limit: No employer source, quote or customer record, pricing, product rule, credential, internal path, screenshot, or production artifact is published.
Start with the users, current workflow, accepted output, failure mode, connected systems, and the first implementation decision.