I'm excited to share that after 3.5 years at Amplitude I'm joining Honeycomb in a little over a week. I'm joining Honeycomb for a slew of reasons. I'll share just a few:

• I'm excited about the product and the way it can improve our ability as developers to reason about complicated systems
• I've been following the talks and blog posts of the founders for years, and I'd love to learn from them as an employee
• It feels like a great culture fit for me. I often feel like I need to change myself to match the culture of tech companies that I join. This is the first company where I don't feel like I'll need to do that.
• I joined Amplitude when it was a Series D company, and experienced an exciting time in its growth trajectory. I'd like the chance to go through that growth trajectory again, better equipped.

While I joined Amplitude to specifically work on the design systems team, my role shifted to include frontend infrastructure as well. I learned from a number of fantastic collaborators, especially Jack McCloy, Ryan Kahn, Meredith Fay, and Jimmy Wilson. I also worked hard to grow my skills in various frontend infrastructure areas, including web performance, CI/CD, deployments, test infrastructure, and monorepo management.

The upside to being in an intense learning period at work is that I can look back on my time at Amplitude and be proud of what I accomplished.

The downside is that I was left with no time to write posts for this blog! I'm looking forward to retroactively sharing learnings from my time at Amplitude, as well as topics I learn about while at Honeycomb.

To hold myself accountable, I wanted to share the topics that I'm considering writing about, and to hear from you about which ones sound most interesting.

• CSS cascade layers as a solution to css overrides in a microfrontend architecture
• How to use turborepo to improve CI/CD caching
• Facade components: A technique for migrating components to a new version when you don't have semantic versioning
• The headless component library I’d choose if I was building a new design system
• My thoughts on shadcn as a way of building components
• How to use codemods to help with design systems migrations
• How I ran the dark mode project at Amplitude
• The dangers of distributed monoliths
• Why you need an escape hatch for style overrides, even if your main goal is design consistency

Please let me know if any of these topics resonate with you. While I love writing this newsletter as a way to get my thoughts in order, I'm really writing it for you, my reader.

I'm so looking forward to joining the team at Honeycomb. I can't wait to dive in and start learning new things from everyone that I collaborate with.

For now, I hope everyone has a restful weekend. Take care of yourselves.