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.

Dgraph founder Manish R Jain gave us an excellent explanation of graph databases on episode 322 of The Changelog. I extracted that section from our trusty episode transcript for your reading pleasure…

Little bits of appreciation can make big differences in maintainers’ lives. Here’s one way you can show appreciation that will take less than five minutes out of your day and just might make someone else’s. 🙌

Hacktoberfest is here once again, and we devs will do just about anything for a free shirt.

However, there’s a war inside us. The Acquire Free Swag inclination is at odds with the Be Super Lazy inclination, leaving many wondering… “What’s the absolute easiest route to that sweet, sweet swag?!”

Very cool! I tried to get to a Command Prompt, but it seems key input has been disabled.

There’s lots of fun comments in this Twitter thread.

Overcast reports podcast subscriber counts in is crawler user agent. How cool is that? All podcast apps that have their own crawler should do this! 🙏

Those of you who’ve been following along on Twitch know we’ve been working towards open sourcing our podcast show notes so the community can help improve them. I’m happy to announce that THIS is now a thing!

I was perusing this popular VS Code feature request yesterday when I spotted a disturbing trend: more than a dozen comments containing nothing more than a +1

Reading Amjith’s git hack reminded me that I wrote up a few techniques I use to retain my dev flow between coding sessions. I wrote this post back in 2011, but I’m happy to report I still use #2 and #3 all the time. ✊