.NET 10 development & modernization
New services on .NET 10, and existing ones brought up to it without a rewrite.
Three fields, one method: measure the process, name what it costs, then change one thing at a time.
Architecture, .NET modernisation, data migrations and engineering management — for systems that are already carrying load.
New services on .NET 10, and existing ones brought up to it without a rewrite.
Off Framework, off Windows Server, onto Linux containers — while the system keeps serving traffic.
Moving to a document store when the access pattern justifies it — and saying so when it does not.
Pipelines that finish, restart cleanly, and tell you when they lied.
A review that ends in a ranked list of what will break first, and what it costs to fix each one.
For a team that is busy every week and shipping less than it used to.
LLMs and agents placed inside a stack that already exists, as a step in a process that runs without anyone watching it.
Using models inside your engineering process — migration rigs, code conversion, review — with the output verified rather than trusted.
Specific hours of routine work every week, identified and then automated — starting with the ones that pay back fastest.
FDM as a production process — part design, material selection and tuning, up to a print that repeats.
For a workshop deciding whether to buy a printer, and what to buy — before it becomes a shelf ornament.
Parts designed for the process that makes them — so they print without a fight and hold up in use.
Choosing the filament for the job and tuning the process around it, until the tenth part matches the first.