.NET / ASP.NET Core
C#, ASP.NET/Core, Web API, Razor Pages, service seams, and maintainable modernization architecture.
Open .NET / SQL pathMichael Kappel — Senior Software Engineer / Software Architect
I help teams modernize legacy .NET and SQL Server systems without breaking business-critical behavior, then support that work with TypeScript/Angular front ends and human-reviewed AI-assisted engineering.
Best fit for
Short path for recruiters and hiring managers; deep proof remains one click away.
Choose a review path
The deep evidence remains available, but first-time visitors get resume, project, case-study, and contact choices before research utilities.
Front-door map
Resume and selected proof come before research, utilities, and machine-readable review paths.
About & skills
Michael Kappel is a senior software engineer and software architect focused on translating legacy business logic into maintainable systems. The portfolio now presents the recruiter path first, then keeps technical and structured-review depth behind clear secondary links.
C#, ASP.NET/Core, Web API, Razor Pages, service seams, and maintainable modernization architecture.
Open .NET / SQL pathSQL-heavy systems, stored procedures, business rules, reporting, and parity checks.
Open SQL modernization pathTyped UI patterns, Angular/RxJS experience, API contracts, and accessibility-aware delivery.
Open TypeScript / Angular pathPrompt contracts, handoff memory, semantic search, and review checkpoints as supporting engineering practice.
Open AI workflow pathA separate image-forward portfolio showing composition, public media archives, visual systems, and creative range.
Open photography portfolio
What I solve
The homepage gives a short human path first, then opens deeper evidence for architects and technical reviewers.
Stabilize brittle Web Forms, Classic ASP, stored-procedure, and undocumented business-rule systems before rewriting them.
View .NET / SQL pathMake TypeScript, Angular/RxJS, browser-local tooling, and service contracts readable as implementation evidence.
View TypeScript pathUse prompts, semantic search, handoff memory, and review checkpoints as supporting engineering artifacts, not as a replacement for human review.
View AI architectureModernization flow
A lightweight source-level diagram replaces stock imagery and keeps private client details out of public copy.
Text alternative: legacy screens and stored procedures are inventoried first, parity evidence is captured before changes, modern API and SQL seams are extracted behind tests, and reviewer proof is published through case studies, Architecture Notes, the Evidence Map, and machine-readable handoff files.
Selected projects & case studies
The default set is intentionally short; the full evidence surfaces stay available when a deeper technical review is needed.
Resume Backed Professional Pattern
A resume-backed case study for modernizing legacy Web Forms, Classic ASP, and SQL-heavy systems while preserving business behavior through comparison screens, generated scenarios, and test coverage.
/dotnet-sql-modernization/ /evidence-map/ Public Platform
A public-platform case study for AI memory, file handoff, project handoff, and compact AI handoff state mapped to long-term Architecture Notes research.
/ /case-studies/ Public Platform
A public-platform case study for durable AI-ready knowledge systems, trust labels, source boundaries, governance, and retrieval-friendly content design.
/case-studies/ /evidence-map/ Experience & career path
Use the career and experience routes for the full sequence; this homepage summarizes the proof path without becoming another dense resume.
.NET, SQL Server, reporting, line-of-business workflows, and long-lived modernization work.
Experience routeBusiness-rule translation, testing seams, API boundaries, reviewer-readable documentation, and mentoring.
Career overviewResume, case studies, evidence map, Architecture Notes, and machine-readable discovery files.
Evidence mapTechnical appendix
These cards remain secondary to the resume and selected proof path, but keep source-backed evidence available for reviewers who need it.
Evidence lane
UAIX-style package wizard support, Project Handoff, Agent File Handoff, compact AI handoff memory, Architecture Notes, manifest exports, and receiver startup packets.
Evidence lane
Modern Angular target architecture, TypeScript, RxJS, component orchestration, SSR/SSG-first routing, reactive state, browser-local tooling, and asynchronous API-facing UI patterns.
Evidence lane
Python AI pipelines, MySQL-backed cognitive packet exchange, metadata validation, passive endpoint validation, and quarantine-first memory review.
Evidence lane
ASP.NET Core, C#, MVC, Razor Pages, Web API, EF Core, dependency injection, layered design, legacy modernization, and public API surfaces.
Technical appendix
Architecture Notes remain curated public documentation. Reports, search, dashboard routes, and machine-readable files remain secondary utility surfaces with explicit boundaries.
Structured review files
Structured review files provide manifests, route indexes, JSON-LD, boundaries, and recommended reading order. They do not permit private probing or tool execution.
/llms.txt /llms-full.txt /route-qa-contract.json /api/public-route-index.json
Resume and contact
Email, phone, LinkedIn, and location are shown from approved resume/contact artifacts. Use the direct links below for the fastest contact path.
Paste a job description, recruiter note, or technical requirement only when tool-based matching is useful. The analysis remains browser-local and the manual evidence paths stay available.
Browser-local. No pasted text is sent anywhere. Use the manual evidence map if a tool-based review is not needed.
Claim boundary
Research and handoff records are review material. This site does not claim consciousness, biological equivalence, formal standards approval, SOC 2/ISO compliance, accessibility certification, or production access to private systems.