Why work together?
Production stability, incident reduction, improved delivery pace.
Diagnosis → Action plan → Progressive implementation or team coaching.
Legacy .NET applications, technical debt, CI/CD to improve, tests to implement, team skill development.
About
Senior .NET developer and freelance Tech Lead with over 10 years of experience, I work on contexts with high technical stakes: technical debt, application modernization, team structuring and sustainable improvement of software quality. My approach is pragmatic, business-oriented, and focused on transmission and team autonomy.
Our Services
Modernize and secure your .NET application without big-bang
- •Progressive modernization of existing applications
- •Technical debt reduction and refactoring
- •Testable and scalable architecture
Reproducible production deployments with less risk
- •Implementation / improvement of CI/CD pipelines
- •Test automation and quality controls
- •Production deployment reliability
What you get
Robust CI/CD pipeline, automated deployments, measured quality
For whom / when
Risky manual deployments, lack of automated tests, unreliable release processes
Train and upskill your .NET teams with a hands-on approach
- •.NET / C# training (beginner to advanced)
- •Unit testing and software quality practices
- •Technical coaching, code reviews, Tech Lead posture
What you get
Trained and autonomous teams, solid practices in place, improved quality
For whom / when
Junior or intermediate teams, need for structure, lack of testing practices
When to contact me?
Contact me if any of these situations sounds familiar:
- your .NET application is becoming difficult to maintain or evolve
- your production deployments are risky or too manual
- you want to modernize an existing system without rewriting everything
- your teams lack solid testing and quality practices
- you need a Tech Lead perspective on a one-time or regular basis
Latest Articles
Why the Anthropic OAuth provider in Hermes failed (401 invalid x-api-key) while ChatGPT/Codex worked on the first try. Not a provider comparison: just the path that turned out simple to wire up.
Published on October 20, 2026
Three experiences with Hermes' background mode (/bg): a genuinely useful pattern for monitoring and batch work, unexpected variability between two identical runs, and a tool loop that wouldn't stop on its own.
Published on October 13, 2026
Real measurements of latency, prefill cost, and memory footprint for local LLMs (Mistral NeMo, Devstral 24B) on a CPU-only VPS, compared to a cloud model. The CPU runs them, but interactive use isn't won.
Published on October 6, 2026
Installing Docker, a private network, Ollama, and Hermes on a VPS, then the first trap I hit: the context a model advertises isn't the context you can actually use, and extending it has a cost.
Published on September 29, 2026