We have to stop insisting that software updates, etc. need to be distributed over HTTPS. Let me tell you why this is not an ideal way of going about it.

Did you hear that Go Time panelist Mark Bates won a FREE Raspberry Pi 400 by besting his fellow gophers in our Go Panic game show at GopherCon?

Turns out he declined the prize, so we’re giving it away to a member of our lovely Go Time audience!!

SMTP should be blocked on public networks.

Email technology offers no effective means to stop phishing, so it’s been a runaway success for the attackers, and a disaster for millions of victims.

Sunsetting SMTP is clearly necessary and feasible. So, I’ve drafted a protocol called TMTP and I’d like to tell you about it.

There’s a new stack in town. PETAL. It destructures to Phoenix, Elixir, Tailwind, Alpine and LiveView. So what is it? Well, it helps you build web applications. Let me tell you about it…

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?

As the editor of the Elixir Radar newsletter, I read lots of articles related to Elixir every single week. Along the year I read probably more than 700 articles, so I could curate the best ones and send them to Elixir Radar’s subscribers.

In this article, I share the 11 most popular articles on Elixir Radar in 2020. Those are the ones that had the biggest engagement from Elixir Radar subscribers in each month of 2020, in terms of CTOR (click-to-open rate).

Envoy’s open source community is amazing. I looked the other day, and at least on GitHub, just from a code contribution perspective, we’re almost at 600 contributors. Which for a fairly low-level C++ project… that is freakin’ incredible. It just blows my mind. And then you look at all of the vertical products and all these other things that are built on top…

There are many factors that contributed to this success, but one thing I did early on stands out as the most important thing I could’ve done. In this post I share my secret with you.

Git is actually sooo hard. Not just to learn, but also to use consistently. And I say that as a person who used it for probably over ten years. Here’s my thoughts on the matter.

In this post I share the latest 2020 and beyond details for changelog.com’s infrastructure.

Why Kubernetes? How is Kubernetes simpler than what we had before? What was our journey to running production on Kubernetes? What worked well? What could have been better? What comes next for changelog.com? Read this post and listen to episode #419 to learn all the details.

Typically, people say that testing is like a pyramid. A wide base of unit tests and very few end-to-end tests. I believe we’ve come to a point where a crab strategy is a better approach.

I am a huge proponent of a couple of specific ideas. One is that you should always try to understand what problems a specific tool is trying to solve… And another is that you need to understand exactly what problems you are trying to solve in your own application right now, and pick the tools that solve your problem best.

With constant change being our new normal these days, I cannot attest enough to the importance of implementing the habit of self-care. The biggest reason, aside from the sheer benefit of taking care of yourself, is the crucial by-product of margin that we gain. However, the challenge is that we often know what’s important for our health, yet we fail to incorporate these “knowns” into our daily lives.

In this post I cover what self-care is and the ways to establish habits that can help you create more margin in your life.

It has become even more clear to me during the era of COVID-19 that poor communication is the reason systems and relationships fail. Every time I’ve failed to get what myself, my team, or a community wanted out of an engineering team was because I neglected to communicate why and how it would be impactful to them in a digestible way.

In this post, I share a few lessons learned as a non-technical launching hardware and software products over the last decade. We’ll explore tactics and skills teams can use to communicate more effectively.

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.

To celebrate our 100th episode of Practical AI, we’re giving away 3 FREE AI hardware bundles! Enter for your chance to win an NVIDIA Jetson Nano, Intel’s Neural Compute Stick, and Google’s Coral Dev Board (plus swag).