OpenAI
Function calling and structured outputs doing the heavy lifting behind the scenes - the part nobody sees and everybody relies on.
AI power user and automation expert. I make machines do the boring parts so the humans can go do something better with their afternoon.
I spend my days wiring large language models into the messy edges of real work: inboxes, calendars, browsers, phones. The promise of AI was never a chatbot you talk to for fun. It was getting your time back. That is the only metric I care about.
Most "AI workflows" are a demo that breaks the second a human touches them. I build the ones that survive contact with a Tuesday. Less hype, more things that quietly run while you sleep.
Function calling and structured outputs doing the heavy lifting behind the scenes - the part nobody sees and everybody relies on.
My pick when an agent needs to read a long, ugly document and not lose the plot halfway through.
Text an assistant that actually does the thing. Half my routines now start as a message and end as a finished task.
The unglamorous duct tape holding it all together on a phone. Underrated, slightly cursed, endlessly useful.
Building agent pipelines that triage email and draft the replies I would have written anyway - just faster, and without the dread.
Turning my entire morning routine into one Shortcut. It books, summarizes, and nags. I mostly just press a button.
Collecting the AI demos that fall apart in production and quietly rebuilding the ones worth keeping.
If a task happens more than twice, it should not happen by hand a third time.