about
one engineer, working in the open.
i'm a software engineer with about four years in production systems, most recently in fintech — an industry where a process failing quietly is expensive, and where nobody is impressed by a demo.that work taught me the thing this practice is built on: the interesting part of automation is never the happy path. it's what the system does when a document is malformed, an api is down, or the model returns something confidently wrong. most of what gets sold as ai automation has no answer to any of those.so i started taking the same standard to businesses far smaller than a bank. a fifty-person firm can afford a broken process even less than a large one can — there's nobody spare to catch it.i build in public, contribute to the open-source frameworks i depend on, and publish what breaks rather than only what ships. it's the fastest way i know to stay honest about my own work.based in
india · ist
held hours
uk & ireland9:00–14:30 gmt
w. europe10:00–15:30 cet
us east9:30–13:30 edt
capacity
one build at a time
five ongoing clients, maximum
five ongoing clients, maximum
what i'm not.
- not a no-code shop. those demos work in the meeting and fail in production. i'm frequently the person who replaces them.
- not a software house looking for a big project. if the answer is a $50 monthly subscription, i'll tell you that.
- not an agency with account managers. the person who scopes the work writes every line of it.
- not a staffing arrangement. fixed scope, fixed price, fixed date.
- not an ai evangelist. plenty of processes shouldn't be automated at all. i'll say so.
tell me what's slow.
fifteen minutes, no slides. if i can't help, i'll tell you who can.