I take on outside Go engineering work in the evenings and on weekends. It comes in small pieces with a spending cap, so neither of us has to guess how long something will take before we start.
Engineering block
$400, up to four hours.
You bring one named problem in an existing Go repository: a bug you can reproduce or can’t, an API integration that stalled, or a controller or CLI that does the wrong thing. Before I start, we write down what you see, what should happen instead, and what access I have.
After two hours I send you an update. At four hours I stop, and you get a reproduction, what I found, and a tested patch if I got that far. An unfamiliar bug is not always fixed in four hours, and if it looks that way I will tell you at the two-hour mark.
More hours happen only when you ask for them, at $100 an hour, agreed in writing each time.
Second opinion
$950, in writing, within three business days.
One decision you are about to make: a design doc, an architecture choice, a vendor pick, or a pull request you are unsure about. You send me one thing I can read in an afternoon. I send back what I would do, what I would watch, and where I think it breaks. No call required.
Larger work
If a block turns into something bigger, we scope it together from what the block found. I do not quote builds sight unseen.
How it works
- Evenings, Central time, and weekends. If the work needs me during business hours, I am the wrong fit, and I would rather say so up front.
- I check every engagement for conflicts with my day job before I accept it.
- Each block is paid before it starts. Invoices come from my LLC.
- Your code stays yours. You get the patch and the findings, and I keep nothing from your repository once the work is done.
The projects page shows what I build on my own time. Nearly all of it is public, so you can read the code before you write to me.
Get in touch
Email d.adolph.atx@gmail.com with a line about the repository and the problem.