Advertise with Changelog Media

We reach 85,000 developers weekly

350,000 monthly listens  •  15,759 email subscribers  •  250,000 monthly pageviews

Or call us at 888-974-CHLG (2454)

How sponsorship works

Our primary focus is on developers, but people from all areas of the software industry tune in to our developer podcast network and our newsfeed and newsletter to inform their next big idea. From CTOs and Directors of Engineering to Frontend Developers and Product Designers, our audience cares about the future of software development, cloud infrastructure, dev culture, services, tooling, mental health — and they're waiting to hear from you.

1. Develop your strategy

Everything begins by understanding who you are and the goals you're trying to achieve. We have proven workflows to uncover who you are, your goals, what's working, and the aspects of your story developers need to know.

2. Plan your activation

Once we have an understanding of who you are and how we can help you, we'll begin to shape what to say, how to say it, and where. Our team has years of growth and marketing experience to develop a campaign focused on your goals.

3. Build your following

Developers follow our content to explore new ideas and discover new tools. We make sure your brand and product are a part of their journey. We're here to guide and help you every step of the way.

Podcast sponsorship examples

Campaign type

Campaign name

Campaign production

Endorsement

Linode, Zeus-like power

0:00 / 00:38

Endorsement

Linode, Dedicated CPUs

0:00 / 00:52

Endorsement

Digital Ocean, Product Lineup

0:00 / 00:43

Customer story

Rollbar, CircleCI - Paul Biggar

0:00 / 01:03

Team Culture / Hiring

Indeed, Darren Nix

0:00 / 02:21

Endorsement

Rollbar, Move fast and fix things

0:00 / 00:33

Partner Pre-roll

Fastly, Network-wide pre-roll

0:00 / 00:06

News sponsorship examples

changelog.com

Honeycomb Icon Honeycomb – Sponsored

Observability 5-year retrospective

logged by @logbot permalink

O’Reilly said it best this year when they summarized learning trends in 2021:

Observability saw the greatest growth in the past year (128%), while monitoring is only up 9%. While observability is a richer, more powerful capability than monitoring — observability is the ability to find the information you need to analyze or debug software, while monitoring requires predicting in advance what data will be useful — we suspect that this shift is largely cosmetic. “Observability” risks becoming the new name for monitoring. And that’s unfortunate. If you think observability is merely a more fashionable term for monitoring, you’re missing its value.

We can’t lose sight of that value. We can’t afford to. This isn’t just a tale of vendors arguing to define marketing terms for their own benefit. The pain and suffering that people endure every day because they can’t understand their own damn systems is too real. The long hours, the toil, the greasy hacks moldering away into technical debt, the late nights, the missed sleep, the burnout. The pain is real, and the solutions are specific. We need specific, meaningful technical terms to help users navigate the future and find their way to those solutions.

Sentry Icon Sentry – Sponsored

Distributed tracing 101 for full stack devs

logged by @logbot permalink

How do you explain a bottleneck in your web stack? Start with learning the ins-and-outs of distributed tracing and how it can help you monitor your increasingly complex full stack apps.

Understanding how a user interaction in the browser cascades into a 500 server error deep in your server stack is challenging. Distributed tracing helps answer these types of questions.

In the early days of the web, writing web applications was simple. Developers generated HTML on the server using a language like PHP, communicated with a single relational database like MySQL, and most interactivity was driven by static HTML form components. While debugging tools were primitive, understanding the execution flow of your code was straightforward.

In today’s modern web stack it’s anything but. Full stack developers are expected to write JavaScript executing in the browser, interop with multiple database technologies, and deploy server side code on different server architectures (e.g. serverless). Without the right tools, understanding how a user interaction in the browser cascades into a 500 server error deep in your server stack is nigh-impossible. Enter: distributed tracing.

This is part 1 in a series from Sentry on distributed tracing.

Ready to get started? Get in touch so we can connect and learn how we can help you.

Or call 888-974-CHLG (2454)

Who you’ll reach

Our audience is the builders, leaders, and planners defining the future of software.

11%
CEO / Execs
27%
Frontend / UI
43%
Backend / Engineer
12%
CTO / Engineering
7%
Product / Design

Every day we influence developers at some of the most innovative tech companies in the world.

Community Leader

Linux Foundation

Data Scientist

Intel

Executive VP

Micrsoft

SRE Engineer

Google

Software Engineer

IBM

Systems Engineer

Datadog

React Core

Facebook

Distributed Systems

Uber

Engineering Director

Slack

JavaScript Engineer

PayPal
0:00 / 0:00