An invitation: a little about me and this site
A warm hello if you are new here, plus a short tour of the work I do, based on the same path you would see on my full resume.
If you have landed on this page from a link, a search, or a friend, welcome. I built this site as a home for the things I care about professionally: how software gets designed, how teams ship, and how people learn. Below is a compact version of my path. If you want the full version later, the details still live in the usual places, but for now, here is the human version.
Why this site exists
You should not have to dig through a PDF to get a feel for who someone is. Here you will find a Portfolio take on how I think about work, a Books page if you are curious about my writing, and a Contact page if you want to get in touch. The goal is easy scanning: a few well structured pages instead of a wall of keywords.
Big teams, big surfaces
A lot of my energy has gone into work where mistakes are expensive and scale is real. At Bloomberg, I helped build responsive web products used by millions of people every day, alongside work on data heavy legal analytics, ML for text and recommendations, and the day to day of shipping in a large engineering culture.
At Meta (Facebook), the problems shifted toward messaging, infrastructure, and very large user surfaces. I led or contributed to iOS, Android, and web initiatives, from messaging and queues to ML driven features that had to be safe, measured, and reliable for people all over the world. More recently I have also worked in the broader Meta ecosystem, including product direction around AI in Reality Labs, where constraints and tooling are still evolving fast.
Mobile, product, and startups
Not everything has been a giant org chart. I have been a senior engineer on React Native and payment adjacent flows at a dating product startup, owned releases and push notification pipelines, and sat closer to the product and store submission cycle than a pure platform team sometimes does. That range matters to me. Shipping on a phone in someone’s hand teaches different lessons than shipping a dashboard in a browser.
Teaching, writing, and paying it forward
I care about clarity for learners. I was Lead Developer and Academic Director at the New York Code and Design Academy, where I worked with a team, shaped Rails and Node curriculum, and taught in person. I have been an author with Manning on Node.js, with curriculum tied to university use, and I have written and spoken for a wider audience in other channels too.
I still think of "engineer" and "educator" as two parts of the same job: you only really know a topic when you can help someone else get unstuck.
The independent thread
For years I have also run my own small shop, Hacky Apps, where I design and build for clients, coordinate contractors, and stay close to UI and product decisions. It keeps me honest about tradeoffs, timelines, and what "done" really means for a business, not just for a ticket.
If you want to go deeper
That is the short version. The longer story includes earlier teaching assistant work at Brandeis, volunteer instruction for CodeNation and Re:Coded, a couple of degrees I am still proud of, and a lot of small team wins that do not fit a headline. When you are ready, wander over to the rest of the site, or just say hello through Contact. I am glad you are here.