Custom build work
I take build work on the side of the day job, in the same stack and to the same standard as the four projects on this site.
What I take
Backend systems in .NET, and the parts of an application that decide whether the rest of it can be trusted. Data models, APIs, sync between a device and a server, migrations against a database that already holds rows, and integrations with something nobody on the team wants to own.
Full-time since August 2016. As of September 2026 that has meant payment rails and their settlement, ACH and acknowledgement file parsing where a character in the wrong column is an expensive file, lending, fraud triage, and the shared packages other teams build their own work on, across thirty-two systems of which nine I started from nothing. That is where the judgement comes from, and it is written up in full on the engineering record. The four projects on this site are where you can see the same thinking applied to work whose source I can actually show you, and each is written up by the decision behind it rather than by its feature list, so you can tell whether the way I think about a problem is the way you want yours thought about.
I am one person. No cofounders, no contractors, no employees. That is a real constraint and it is better stated up front than discovered in week three: I take work that one experienced developer can carry, and I say so when something needs a team instead.
How I work
Specification first, then a plan, then the code, with the reasoning written down where the next person can find it. Not ceremony for its own sake. It is what makes a decision reviewable six months later when the person asking is you and the answer matters.
Nothing gets reported as done without the output that proves it. A test suite that was not run is not a passing test suite, and a merge request that is open is not a pipeline that is green. If I tell you something works, I ran it.
Why the company exists
SkaiiNyght Solutions LLC is the vehicle, formed in March 2026 and registered in South Dakota. It exists so that the things I build have somewhere to live that is not my personal name on an invoice, and so that a client is contracting with an entity rather than with a hobby. It is not a studio and it is not hiring. The company is how the work is structured, not what the work is.
I do not take real-money gambling work.
Getting started
Tell me what the system has to be right about. That is more useful than a feature list, and it is what I will ask about first regardless.