Why do people complain so much about CSS? There’s memes and jokes about CSS… there’s all sorts of tooling for CSS… On our Frontend Feud episode when we asked, “Name something that frontend devs complain about”, CSS was the #3 answer, which was pretty high up the list.

So it seems like it is a thing that people struggle with, complain about etc. I’m just curious, why do you think that is?

In which I pick on Jamstack a bit to make a larger point that we still haven’t found that Silver Bullet and we’re not going to so let’s put our thinking caps on, make sound choices, and pick the right tools for each situation.

I wanted to surface this just in case your podcast queue is stacking up and won’t have a chance to listen to our Working in Public episode before September 1st. Hear all about it 👇

It’s easy to forget that there’s a human on the other side of that <textarea>. So we tend not to give people the benefit of the doubt on the internet. This post is a gentle reminder of that fact and how active awareness of it would go a long way toward making it a more enjoyable place for all of us.

To celebrate our friend Zeno Rocha’s first book (and our new episode with Zeno discussing all the details) we’re giving away 3 FREE bundles of Dracula PRO && 14 Habits of Highly Productive Developers 🙌

I thought it’d be cool to get mix test and mix format running on pushes to the changelog.com repo, so I gave GitHub Actions the old college try. After (not too much) futzing around on my own, I figured I’d have more success by getting an expert to help out. Good call be me! 😆

In this ~1 hour jam session, we go from zero to a successful Actions workflow. I learned a lot along the way, and you might too by joining us on the journey. Thanks, Jonathan!

We had an excellent interview with Beth Dakin and Ronak Shah from the Safari team about what’s new and interesting for developers in Safari 14. There were so many good moments that I figured a round-up post was warranted. ICYMI (or don’t have time for the full convo), here’s the highlights from my POV.

Turns out everyone’s favorite macOS package manager has an official cask for managing fonts. Who knew?!

After José’s announcement yesterday I just had to get my hands a little dirty and kick the tires.

Jam session! I sat down (metaphorically) with Phoenix’s new LiveView feature to see if I can integrate it into our admin to provide a Google Docs-esque experience for podcast co-hosts.

This is my first long-form video where I work toward a goal with no clue how to actually get there. Please let me know if you dig this style in general and/or if you have any advice on the particulars.

Dan Abramov and Dave Thomas got me thinking. Why did DRY come to mean “Don’t cut and paste”? I have a few thoughts on the subject…

Results are in for the 2019 State of JS survey. I’ve been digging through charts to see what I can see. Here are 7 insights that jumped off the page to me.

Gone are the days when we developers were too shy/humble/introverted to promote our warez with the confidence and vigor necessary to draw a crowd.

In fact, we may be experiencing an over-correction. Some of us are selling a bit too hard at times. With that in mind, here’s some help translating between how developers describe our software and what we might actually be thinking. 😉

As the saying goes… history doesn’t repeat itself, but it often rhymes.

If you want to create a successful programming language (or at least understand how you might), it’s immensely valuable to learn from others who have done just that. on Go Time episode #100, two of Go’s creators (Rob Pike and Robert Griesemer) sat down to discuss the language’s success. Here’s 5 things they attribute to its success.

The Changelog team will have a BIG presence at All Things Open in October. To celebrate, we’re giving away FREE tickets!

Here’s some hard-earned experience on how to validate an email address. If you listened to JS Party #39, then you already know this. If you think I’m about to hand the best regex you’ve ever seen…

JS Party 73 finished with an excellent segment all about recommended reading for new and aspiring JavaScript developers. Here’s the rundown!

When you hard-attach your library to a specific technology or framework, you limit its potential impact. By thinking ahead and putting in a little more effort, your library could benefit orders of magnitudes more people.

If you open source your work to (speculatively) make lots of money… you’re doing it wrong. There are much easier means to that end. But there are plenty of good reasons to do open source for free. Here’s three of them.

Until now, the best way to add a contributor to the list was via the CLI tool. That works great when you’re at your computer in “code mode”, but not when you’re mobile or just browsing the web.