My newest book is ready to help improve your technical content strategy. products.everydeveloper.com/

Are most API teams building endpoints or solving problems? From at least my days at duv.ly/48oUMHZ, I’ve said endpoints aren't always the same as use cases. Now the rise of AI agents has refocused us all on what they’ll need to accomplish. How do you keep your aim on solving real user problems?

Sometimes you just want coffee, but my order may have embarrassed my friend. He was beyond excited to meet me at a very fancy coffee shop in my neighborhood. This place is internationally known. There are two in the United States: one in Portland, the other in our hipster sibling city of Austin. They've been known to sell $150 cups of coffee. My friend was entirely into the experience: - He asked about the beans, their origin story, and roasting profile - Then he wanted to know grinds: coarse, fine, even knew the numbering system - And the filter, the pourover system, the temperature of the water But it wasn't over after he ordered. They brought the grounds to the table where he smelled them and he felt them with his fingers. It was a complete experience. Every choice was intentional, every detail mattered. In both coffee and technical content, the experience often matters a lot. However, it’s sometimes overshadowed by the task at hand. Which gets to my embarrassment: I asked for "coffee." I may have chosen a region at random from the menu. I'm sure I told them the size. And then, of course, the crucial piece: I wanted my coffee "for here." The key job to be done for that coffee was to buy me a seat so I could connect with my friend. It's not that my friend didn't want to see me. It's just that he also cared about the experience. Frequently, we see marketers generalize about content types. Some believe it must include a demo of the product in action. Others think it must cut away all the "fluff" and only show facts. Or we hear that it must be video, or definitely should not be video. There is no one way or one type of content that's going to be what every developer wants all the time. The job to be done for most technical content is to make sense of complex topics. To educate and inspire developers to take the next step. And that can take the shape of any number of formats. Sometimes developers want the full coffee experience—complete with bean origin stories and grinding specifications. Other times, they just want a coffee that gets them to the next step. A developer marketer’s job is to help guide them.

“What do you want to verb today?” Is this the user interface of the future? I’m seeing it more and more. What do you think

The first Demolicious I’ve attended and not organized.

Not every signal is a purchase signal. Please share this with the teams that need to hear it.

The most entertaining typo I've seen in a newspaper headline

My local hardware store gets DX

Marketing lessons from a band teacher?! 👏

"I created a rapid prototype for an API that didn’t exist 1,400 words ago with #Blackbird. My mock servers let me build the front end before the API is coded. Before starting backend, there are 679 lines I won’t have to write."- @adamd, @everydeveloper. bit.ly/3Nqub1p

Bringing my ProgrammableWeb filter, with a little help from journalist and PR friends.

To mark 100 episodes of Scaling DevTools, I wrote up what I've learned

Someone I’ve never met canceled a meeting three minutes before start time. How shall I spend that 30 minutes?

Why does this nature park have a sewer and what’s that have to do with software developers?

Some may remember my "developer D-light" behind me in my old office. I always wanted to build an example API to turn on/off virtual lights. I built a prototype of the backend for this project and, of course, wrote a blog post about it. adamd.medium.com/rapid-api-p…