Knowledge
Practical guidance for established .NET systems
Technical articles for IT leaders, engineering leads, and software architects. Each article starts with a direct answer and explains the approach, prerequisites, and limits.
System assessment and decision support
Code Forensic Assessment for established .NET systems
When a technical assessment helps before stabilization, what information it requires, and how it produces a report, review meeting, and improvement roadmap.
Read article →Modernization decision
Stabilize or rewrite a legacy system?
A decision matrix for change pressure, testability, operation, data, integrations, and the time at which value is needed.
Read article →Test strategy and change risk
Test automation in established .NET systems
How a team protects critical workflows, sets test boundaries, and gains confidence in changes without following a universal coverage target.
Read article →Build diagnosis and feedback time
Four-hour build time
How a team breaks down long feedback times, tests causes as hypotheses, and prioritizes improvements using actual measurements.
Read article →Release safety and recovery
Rollback as a minimum standard
Why an old binary alone is not a fallback and how to prepare the mechanism, data consequences, and decision separately.
Read article →Deployment knowledge and backup capability
A deployment bus factor of one
How pairing, observed runs, concise runbooks, and targeted automation turn personal knowledge into a process with dependable backup.
Read article →