blog.codepen.io blog.codepen.io

#318: Anna Lytical on What CodePen Is

When Anna Lytical heard Stephen and I talking about “What is CodePen?” she mentioned we did fab without her. So of course, I had to do one with her! Anna creates fun coding content all over the web, in addition to being an engineer at Google. Catch her on YouTube, Instagram, TikTok, and Twitter. For Anna, the appeal of CodePen is in the simplicity: nothing to set up, easy/free to get started, and you can get to the heart of...

blog.codepen.io blog.codepen.io

#315: Support Success

Over the last year, almost every metric that you want to go up has gone up at CodePen. More users creating and doing more things. You’d think that customer support would go up at the same level. And if it did, we would have thought that was very normal and dealt with it. But customer support doesn’t have to be this static thing that just is the way it is forever. If you find that people have the same questions over and over, you...

blog.codepen.io blog.codepen.io

#312: What is CodePen?

This isn’t actually a podcast actually talking about what CodePen is. Well, it kinda is. But actually it’s Stephen and Chris talking about and planning for what they would say if they only had five minutes (or so) to explain what CodePen is. So we need to hash out what the most important things are, what to lede with, and how to cover all the most vital things with clarity in such a short amount of time. We’ll have to get around...

blog.codepen.io blog.codepen.io

#311: Event Tracking & Appcues

Marie & Chris talk about the brand new event tracking feature in Appcues. We’re still pretty stoked we can even afford Appcues, since it’s super pricey software for our company. The fact that they just released event tracking dashboards makes it feel much more affordable though, because this unlocks super valuable information for us instantly. It’s like we get what would get by also buying super expensive analytics software,...

blog.codepen.io blog.codepen.io

#310: Front-End Monorepo

We talked about our transition to a monorepo back in episode 305. This move has all sorts of advantages for us, like the simplicity of having a single repo to pull and be up to date with and linting/formatting code in a consistent way across the entire code base of CodePen. This time we’ll get into more of the repercussions of the monorepo from a front-end perspective. For example, since a bit part of the point of the monorepo is...

blog.codepen.io blog.codepen.io

#309: Elasticsearch

Dee, Chris, and Alex talk all about the technology of Elasticsearch. That’s a link to the company itself right there, which is relevant as we use them directly to host our production Elasticsearch. We use it for (wait for it): search. But interestingly enough, that’s not all. Elasticsearch is just a data store that can be useful for all sorts of other things. But before we get to that, we explain the technology and some of the...

blog.codepen.io blog.codepen.io

#307: We’re Hiring a Gopher

A Go-person? A Golanger? A person who’s good at Go, anyway. That’s who we’d like to hire at CodePen, at the senior level. In this podcast, we chat about how we’re thinking about this new role, why Go has been so important to us so far, and what we hope to do with it. We thought it might be helpful for you, potential hires out there, to hear about how we’re thinking about all this and get to know exactly the people you’d be...

blog.codepen.io blog.codepen.io

#305: CodePen’s Monorepo

Alex and Chris talk about the glory that is having all of CodePen’s code base in a single repository. This was a slow journey of a couple of years. The biggest step was what jokingly named “CodePen in Stereo” which involved consolidating everything Node-based on CodePen (mostly a bunch of lambdas) into a single repo, but still having a second repo for our Rails stuff. The final leap was consolidating those. This opened up some...

blog.codepen.io blog.codepen.io

Search Upgrades

CodePen search has recently gotten better! Quick story first: we had a little unplanned downtime last week. It was ~18 minutes where the web servers were really struggling and most requests timed out or failed. It turns out that our search servers were the root cause. Sometimes a little on fire situation like that causes some unplanned development work, but ends up being of benefit to everyone after it’s done because it forces...