The operator
Kyle Green
I run Starhold Software. It is one person, and that person is me.
I build automation and the platforms it runs on. Most of what I do starts the same way: somebody has a process that works right up until the person who knows it is on holiday, and they want it to stop depending on that.
I take the whole thing — the code, the host it runs on, the alert that fires when it stops — because handing back a script and wishing you luck is how the problem comes back in six months.
Certifications
- AWS Certified Solutions Architect
- Certified in Python
- Certified in log aggregation at the administration tier
Day job
By day I keep automation running for an organisation that operates worldwide. I do not name the employer here, and this work is entirely separate from it.
How an engagement works
- You describe the problem. Email is fine; a screen recording of the manual process is better.
- I come back with a scope, a price, and the parts I think are a bad idea.
- I build it, you watch it run, and I hand over the code and the runbook.
- If I am hosting it, it goes on the status page like everything else I operate.