The Output Looked Good
I built a test to compare local models with the cloud. The first thing it caught was the cloud making something up.
Read the storyI notice the frustrating parts. Then I build something to fix them.
I'm Kevin, a technical operations engineer. This is where I share what I'm making, what I'm figuring out, and the thoughts that follow me home.
01 / Writing
I built a test to compare local models with the cloud. The first thing it caught was the cloud making something up.
Read the storyAlso in the notebook
Things I've tried, things I've changed my mind about, and things I'm still working through.
02 / Selected builds
Support / Knowledge systems
The answer is probably in an old ticket. Finding it shouldn't be another investigation.
A knowledge graph built from support tickets, connecting recurring issues with the answers that resolved them.
Agents / Durable memory
The session ends. The work shouldn't disappear with it.
A local archive that makes agent conversations searchable, carries context between tools, and turns past investigations into reusable playbooks.
The next case improves the next answer.
Commercial / Internal tools
A shared spreadsheet grew into a pricing tool used by sales teams worldwide.
Database-backed rates and tested formulas give sales teams clear discount ranges, with every calculation recorded for the pricing team.
Same formulas. Clearer guidance.
03 / The person behind it
I've spent 15+ years in support and technical operations. The part I keep coming back to is understanding why something is frustrating, then doing something about it.
These days I'm a Senior Technical Operations Engineer at Enode. Outside of that, I build tools, tinker with my own systems, and write here to work through what I'm learning.
Find me on GitHubAlways interested in what other people are making