About

I started in radio, running digital for a handful of stations out of Pittston. Then eleven years at the University of Scranton, where I built their digital publication from nothing and learned what it actually takes to move a page through a large organization.

Scranton is also where I met Cascade. The university ran on it, so I learned it as a customer first, which I still think is the best way to learn a CMS. I spoke at Hannon Hill's user conference twice while I was there and got to know the people building it, and after a while going to work with them seemed like the obvious move. Three years in now, I sit between Support and Professional Services. Usually I'm who you get when the problem doesn't fit in a ticket, which is my favorite kind of problem. In 2026 I got to speak at that conference a third time, this time as staff, walking a room through building a Cascade site from scratch.

The through-line, if there is one: I try to hand things off. A component nobody can edit without calling me isn't finished. The documentation is as much the deliverable as the code — I've written enough of it that non-technical editors build their own pages and never file a ticket at all.

Away from work I make things about Pennsylvania. A fair amount of it is tedious, honestly. Long evenings copying rows out of one spreadsheet and into another. But I like knowing the answer at the end of it, and I like handing it to someone else for free. Scranton is a more interesting place than it gets credit for, and all three are basically arguments for that.