Yesterday marked the end of my time working on Manuscript, as the transition of the product over to its new owner is complete. With that, I’d been looking for a new contract, and today I’m happy to announce that I’ll be joining the team at Glitch!
Glitch is the friendly community where you’ll build the app of your dreams. Born at Fog Creek Software, the company has gone all-in on making Glitch the most creative and supportive community on the web — and changed its name to reflect this focus.
While the role is still evolving, my mandate at Glitch as Customer Success Engineer will be to enhance the customer/developer experience for partners and Teams customers, scoping out projects and building apps to educate and inspire. I’m really excited about this!
Parting is sweet sorrow
For all my excitement, yesterday felt bittersweet. The Manuscript team that I’d been working with for the last year and a half is an amazing group of brilliant, thoughtful people, and I’m really going to miss them. In the Fog Creek tradition, I know they’re going to do amazing things, and I count them not only as incredible teammates, but good friends. Best of luck to you all!
Things I’ve learned
I’ve realized that as much as I need to build things, I also really enjoy working in a customer-facing role. A lot of my work with the Manuscript team was focused on the support side, which was great! I love helping people figure out how to do their best work.
And sure, part of that learning was about writing cleaner and high-performance code, but it was also about understanding how to scope out work based on a customer’s needs, managing projects, and promoting effective and empathetic communication between all stakeholders.
This new position is going to take what I’ve learned to the next level, which is awesome!
What I want for Glitch
Glitch is growing (over 1 million projects have been created, a number that still blows my mind), and I’m really excited to see what happens next. I have a lot of big dreams for the platform (which may or may not be shared by the team as a whole, and in no way reflect their current plans); here are a few things I’d personally love to see:
- “Remix me on Glitch” becomes the new “Fork me on GitHub”
- Glitch embeds become a de facto standard for live, running code in API documentation
- Glitch becomes the go-to in classrooms and hackathons alike
There’s a lot of work to do, and I’m looking forward to rolling up my shirtsleeves and helping make Glitch the fun and safe place to create and learn on the web.
(But first, a few days off to recharge and reset!)