Skip to main content
The Rework Podcast

Blogging Isn't Dead

14 min episode · 2 min read
·
Kimberly Rhodes,Jorge Manrubia

Episode

14 min

Read time

2 min

Topics

Productivity, Marketing, Software Development

AI-Generated Summary

Key Takeaways

  • No Editorial Process: Anyone at 37signals can publish without approval or assigned topics. Authors write only when they have something meaningful to share, with no required cadence or SEO-driven content strategy.
  • Share Production Code: 37signals publishes actual code snippets from their commercial products in technical articles. This transparency differentiates them and builds audience trust without revealing competitive advantages through limited code samples.
  • Writing Clarifies Thinking: Technical writing helps authors structure complex problems and learn while documenting. The process transforms unclear thoughts into clear understanding, making writing valuable for the author before considering audience benefits.

What It Covers

Principal programmer Jorge Manrubia explains how 37signals runs their developer blog with no editorial process, focusing on authentic technical content that shares real production code publicly.

Key Questions Answered

  • No Editorial Process: Anyone at 37signals can publish without approval or assigned topics. Authors write only when they have something meaningful to share, with no required cadence or SEO-driven content strategy.
  • Share Production Code: 37signals publishes actual code snippets from their commercial products in technical articles. This transparency differentiates them and builds audience trust without revealing competitive advantages through limited code samples.
  • Writing Clarifies Thinking: Technical writing helps authors structure complex problems and learn while documenting. The process transforms unclear thoughts into clear understanding, making writing valuable for the author before considering audience benefits.

Notable Moment

Jorge describes how sharing details of a Friday email server crisis in HEY resonated strongly with readers, demonstrating that audiences value authentic problem documentation over polished success stories.

Know someone who'd find this useful?

Episode Transcript

Welcome to Rework, a podcast by thirty seven signals about the better way to work and run your business. I'm your host, Kimberly Rhodes. If you've listened to the Rework podcast at all, you've heard our cofounders, Jason Fried and David Heinemeier Hanssen talking about hiring great writers. We also say we should out teach the competition, and these two things come together in many ways, and one of them is our developer's blog. To talk about it, I brought our principal programmer, Jorge Manrubia, to talk all about it, how it got started, what we're doing on it now, and how it has helped us as a company. Jorge, welcome to the podcast. Hey, Kimberly. Thank you. Thank you so much for having me. Hey. Before we jump in, tell us a little bit about you, what you do here at thirty seven signals, how long you've been here, and then we'll dive into the developer's blog. Sure. So I'm a principal programmer in the product team. So I work on thirty seven signals product. And I've been working, for Thirty seven Signals for over five years now. Very nice. Okay. So we've linked a couple times over the years in the podcast to the developer's blog, to particular blog articles that have been written. Kind of tell me the history of it. How did it get started? How did it come to be? Sure. You know, after I joined the company, I think there was already this desire in the team for technical folks to have a place to write about technical content. So there are three technical teams in the company. We can say we have parameters, we have designers, and we have ops, which are system administrators. And I think that it was a a shared feeling that we all wanted to have a place to to share our opinions because because thirty seven signals is a company of builders. We like building things, and we, like, tell the world about what we build. So back in the day, thirty seven signals had this very popular blog for the company called signals versus noise. Right. And I used to be a huge fan of it because it shared, like, technical posts, but also business posts, how to work posts, so all sorts of of content. And, well, I was among the the many fans of that blog. So eventually, the company stopped, or or closed the signal versus noise, so we didn't have a place to to write what our thoughts. And, well, a group of folks got together and decided to launch a new place. Of course, with David and Jason being very keen about having that in place. Right. On this blog, tell me who contributes to it. I know you mentioned there's several different teams. Is everyone writing on it? I know I looked and you have several articles on it, but who kind of can contribute to that dev blog? Sure. Actually, …

Get the full transcript (2,751 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Rework Podcast transcripts →

You just read a 3-minute summary of a 11-minute episode.

Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from The Rework Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The Rework Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime