Engineering field notes

The bugs, trade-offs, and production lessons behind the diagrams.

This page is the publishing pipeline for practical technical writing. Draft topics are visible, but unconfirmed fixes and outcomes are not presented as completed case studies.

Draft details pending

.NET deployment

Static-file behavior after a .NET 9 to .NET 10 deployment

A recent deployment exposed a non-obvious static-files issue whose resolution required finding the relevant framework discussion.

Pending: reproducible symptoms, root cause, exact fix, version context, and sanitized code.

Verified technical lesson

Performance

Why XML work inside inner loops becomes expensive

A third-party integration repeatedly processed XML nodes and fetched broad datasets. The safe lesson: move invariant parsing out of hot paths and narrow retrieval to the data the operation needs.

Pending: benchmark method and approved before/after numbers.

Verified technology

Observability

Centralizing service signals with Azure Monitor and Log Analytics

The implementation used Azure Monitor and Azure Log Analytics across services.

Pending: an anonymized signal flow, dashboard examples, alerting strategy, and an incident story.

Outline pending

Modernization

Lessons from moving systems through .NET 7, 9, and 10

Confirmed experience exists; the useful story still needs project-specific compatibility issues, rollout choices, and outcomes.

Story pending

Architecture decisions

Ready-made capability or custom build?

The decision depends on requirements, delivery speed, debt, data needs, and operational complexity.

Pending: one sanitized example with options, decision, trade-off, and result.

Future notes

Repository-derived backlog

Production bugs worth teaching from

Generic, confidentiality-safe bug summaries will be added after Ayaz compiles them from project histories.