I help small engineering teams ship code that's cheap to debug and easy to change six months later
I'm a lead software engineer, 12 years in — five of them leading a 10-developer team at Mindtech, now contracting on an Azure + .NET + React stack for Synthera. I help 2–10 person teams turn "it works on my machine" into code the next person can debug, change and trust.
I've led 5 concurrent projects across 3 departments, owned the code reviews and technical-debt work on a shipped C# product, written the coding standards and run the TDD and pair-programming training, cut a live product's bug count 75% by rebuilding how the team debugged, and architected its move from boxed product to SaaS.
My own product, AhChord: .NET 10 + ASP.NET Core, EF Core, PostgreSQL, SignalR, React 18 + TypeScript, one Docker container. 627 API tests, 134 web tests, a zero-warnings build gate, 102 filed tickets with evidence and the smallest fix.
Bring the code: a repo that's expensive to change, a bug nobody can reproduce, a Unity build that won't hold frame rate, a launch that needs a second pair of eyes.
On the thing that is stuck: the bug nobody can reproduce, the change nobody wants to make, the decision that keeps getting postponed. Screen shared, I drive, your repo. You leave with the next two moves, what I would test first, and a short written summary in the thread after we hang up. Small-team C#/.NET, React + TypeScript, Postgres, Azure, Unity 3D.
No pitch, no obligation. You describe the repo, the bug, or the launch; I say out loud the 2-3 things I would look at first, and what a paid session on it would cover. If it is not a fit I say that too, and point you at the cheapest way to fix it yourself. Bring the repo, a branch, or the error.
Eight weeks with a senior pair of eyes on the codebase: 4 x 30-minute sessions and 2 async repo reviews, used as you hit the wall. Sessions for triage, a design decision, an unblock; reviews send a repo back as a recorded review plus a written findings list. Book sessions as you need them, spread the reviews across the eight weeks, and anything unused converts to a review. 2-10 person teams.
On the thing that is stuck: the bug nobody can reproduce, the change nobody wants to make, the decision that keeps getting postponed. Screen shared, I drive, your repo. You leave with the next two moves, what I would test first, and a short written summary in the thread after we hang up. Small-team C#/.NET, React + TypeScript, Postgres, Azure, Unity 3D.
No pitch, no obligation. You describe the repo, the bug, or the launch; I say out loud the 2-3 things I would look at first, and what a paid session on it would cover. If it is not a fit I say that too, and point you at the cheapest way to fix it yourself. Bring the repo, a branch, or the error.
Eight weeks with a senior pair of eyes on the codebase: 4 x 30-minute sessions and 2 async repo reviews, used as you hit the wall. Sessions for triage, a design decision, an unblock; reviews send a repo back as a recorded review plus a written findings list. Book sessions as you need them, spread the reviews across the eight weeks, and anything unused converts to a review. 2-10 person teams.