Do you need a backend your team can keep running after I leave?
Go services, the APIs in front of them, and command-line tools, built to a fixed price.
From $30,000 · fixed price
The question
Go services and the APIs in front of them. Command-line tools your team will use instead of the shell scripts they replace. The unglamorous backend a platform rests on, written by someone who has kept that kind of code running against a fleet in the thousands.
What you get
What lands in your repo, every time:
- The code and its tests. Tests you can read and run yourself, not a coverage number.
- CI that builds and releases it. It ships the same way after I leave as it did while I was here.
- Documentation you can follow. Verified by running it, not by reading it.
- Whatever the artifact needs. Helm chart, signed release, container image, Homebrew formula.
- A written handoff. Plus written answers afterward when your team hits something surprising.
Price
The price is fixed and starts at $30,000. That means the estimate is my problem, not yours. If the work runs longer than I judged, that is my cost to absorb and your number does not move.
That is what you are buying above a daily rate, and it is why these are not priced as days.
Who does the work
Douglas Adolph. I designed and built the deployment system behind a fleet of thousands of production Kubernetes clusters at a Fortune 50 company, and took deployments to that fleet from weeks down to seconds, and I still maintain it today. Around it I have written the controllers that keep a fleet honest, the authentication path teams use to reach clusters at all, the secrets tooling, and the post-deploy verification that catches a release which reconciled cleanly and is quietly unhealthy.
The engineer who scopes your work is the engineer who does it.
Longer background, and the public code I own, at douglasadolph.com. Read the source before you talk to me.
Send me the problem
Tell me what you are trying to find out and I will tell you whether I can help, including when the answer is that you do not need me.
- What is stuck, or what you are trying to measure.
- What you have already tried, and what happened.
- Any date you are working against.
A short note beats a long form. What comes back is a reply from me rather than a scheduling link, which engagement fits or that none of them does, and for a build, a scope and a number before you owe anything.