Recovering a black box without guessing.
Behavioral reconstruction, runtime evidence, protocol inspection, binaries, data, logs, and the difference between reverse engineering and random poking.
Engineering Notes / Technical Radar
What I’m watching,
testing, and thinking about.
A place for architecture notes, production lessons, reverse-engineering writeups, modernization patterns, and a curated radar of changes that matter to working engineers.
From the field
Notes I plan to write.
Modernizing a monolith without rewriting the business.
How to identify seams, preserve revenue-producing behavior, and migrate risk in pieces instead of betting the company on a clean rewrite.
Human engineered. AI accelerated.
Where AI belongs in testing, secondary review, coverage analysis, documentation, and research, and where human engineering judgment still owns the decision.
When an engineer should be able to talk money.
Connecting feature cost, technical risk, delivery sequence, and potential revenue so product decisions are grounded in both engineering and business reality.
Engineering radar · curated Oct 2026
Current signals worth reading.
Performance Improvements in .NET 11
Microsoft’s detailed tour of runtime and framework performance work in .NET 11.
Open .NET Blog →Azure Architecture Center updates
Recent guidance includes microservices with Container Apps and Dapr, idempotent consumers, monitoring, hybrid networking, and new reference architectures.
Open Azure Architecture Center →Resilience, isolation, and streaming
The AWS Architecture Blog continues to publish real-world patterns around EKS tenant isolation, streaming workers, DynamoDB, and cost-conscious architectures.
Open AWS Architecture Blog →MSVC, CMake, and code intelligence
The Microsoft C++ team is shipping work across CMake tooling, MSVC C++23 support, and whole-codebase indexing for large native repositories.
Open C++ Team Blog →C++26 and the road toward C++29
Reflection, contracts, safety work, string_view improvements, structured-binding packs, and ongoing standards evolution.
Open Standard C++ →Input Domain Modeling & graph coverage
Model inputs into characteristics and blocks, derive coverage requirements, then use control-flow graphs to reason systematically about test paths.
Testing reference →