I started as a STEM teacher, ended up running academic programs for a tech-education company β nine years of watching what actually helps someone learn, and what's just noise. In June 2026 I left that job to find out if I could build the same thing in software: Orchable, a platform that generates real, personalized learning paths instead of another static course catalog.
I'm not a career engineer. I'm someone who spent years automating classrooms and admin work with n8n before "agentic workflows" was a term anyone used β and eventually realized the tool I kept reaching for should be the product.
- π© I default to building the system that solves a problem for everyone, not the one-off fix that solves it for one person today
- π― I'd rather ship something that quietly works than demo something that impressively doesn't β which means I spend a lot of time in the unglamorous last mile before something goes public
- π§ͺ Most of what I know about AI orchestration, I learned by breaking my own n8n workflows first
- π£οΈ I think in writing before I think out loud β most of what I share (this profile included) is written, not spoken
- π± Currently deep in multi-agent pipelines: how to make several AI steps hand off work to each other reliably, not just chain prompts
|
π³ knowledge-tree An attempt to map how tools and skills actually connect β so a learning path isn't a random list, it's a graph that makes sense from day one. The seed of the thinking behind Orchable. 
|
