# Developer marketing Published articles for Developer marketing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## +14% activated users for AppSignal: designing a new homepage in code DevFeed: [+14% activated users for AppSignal: designing a new homepage in code]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [Application Performance Management (APM)](), [error tracking](), [Tooling](), [Code](), [Figma](), [Artificial Intelligence]() Tags: [agentic-development](), [ai](), [apm](), [case-study](), [code](), [design](), [design-for-devtools](), [developer-marketing](), [developer-products](), [engineering](), [error-tracking](), [figma](), [product-development](), [tooling]() ### AI overview Evil Martians designed and shipped a new AppSignal homepage primarily in code, combining code, Figma, and AI during exploration and prototyping. The selected direction was validated through an A/B test that showed a 14% increase in activated users over the previous site. ### Source excerpt We designed and shipped a fresh AppSignal homepage in code, then validated it in an A/B test with a 14% lift in activated users. ## 2 Martians, greenfield to MVP in 4 weeks: agentic coding on Rails DevFeed: [2 Martians, greenfield to MVP in 4 weeks: agentic coding on Rails]() Original publisher: [Read original article]() Author: Travis Turner (richardturner@evilmartians.com) Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Evil Martians]() Topics: [agentic-coding](), [Rails](), [coding](), [React](), [Storybook](), [Open Source](), [stripe]() Tags: [agentic](), [agentic-coding](), [ai](), [app](), [authentication](), [building](), [case-study](), [coding](), [designer](), [developer-marketing](), [developer-products](), [google-analytics](), [onboarding](), [open-source](), [payments](), [platform](), [product](), [product-development](), [production](), [prototype](), [rails](), [react](), [skills](), [storybook]() ### AI overview A designer and an engineer describe how they shipped Thicket, a production MVP, in four weeks using agentic coding with Rails, Inertia, React, and Storybook. They discuss their workflow, project-specific skills, user validation, and the resulting open-source practices. ### Source excerpt A designer and an engineer shipped a production MVP in four weeks on Rails + Inertia. In this post, we share our agentic coding stack, the skills we built, and why it clicked. ## Sourcing developer marketing content DevFeed: [Sourcing developer marketing content]() Original publisher: [Read original article]() Author: Map Published: 2017-12-28T20:55:56Z Content type: article Language: en Sources: [Craig Kerstiens]() Topics: [Development](), [Tool](), [Users]() Tags: [blog-post](), [content](), [developer](), [developer-marketing](), [email](), [marketing](), [technical]() ### AI overview The article shares ways for developer-focused companies to source high-quality marketing content from within their organizations. It recommends turning well-written engineering emails into blog posts and capturing interactions with newer product users to maintain a beginner mindset. ### Source excerpt I spend a lot of time with dev tool and data companies. I think I've more or less banished myself to a life of working in the space, no consumer products for me. In that world a common topic that comes up amongst marketing teams is how do I get my team to contribute to content? Sometimes the person already has an idea of how they want the team to jump onto the bandwagon of their plan, sometimes they're entirely open minded. I won't get into pros and cons of various approaches here, rather after sharing some of my approaches in one on one settings I thought it could be useful to share more broadly here. Turn emails into blogs I'm a big fan of high quality content when it comes to developer focused products. Yes, you can publish x vs. y with FUD and get some traction with it. You can publish high level customer stories that don't get down into the details. But publishing high quality deep technical content that other engineers appreciate gives you a huge head start in getting buy in from your customers. The best thing about much of this type of content is you likely already have it sitting within your organization. Engineers spend a lot of time being thorough and articulate in their emails to their peers. If you see a well written email from one engineer to the engineers@ list and then others chime in either with questions, follow-up, or praise then it's likely a great candidate for a blog post. We recently had one of these at Citus where another engineer replied with "Nice blog post :)", a few weeks later we had a post for the rest of the world to read. The thing about emails though is the engineers won't usually take and turn them into a blog post. Get a technically minded person that likes to write and put some framing around it, pull out relevant details, and collaborate with the engineer. I've often found going from one of these emails to a fully published blog post can be anywhere from 2-8 hrs (including reviews and edits). Beginner mindset with tickets As your ## Scaling Evangelism - Creating Advocates DevFeed: [Scaling Evangelism - Creating Advocates]() Original publisher: [Read original article]() Author: Map Published: 2013-04-16T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [communications](), [scaling]() Tags: [developer-marketing](), [marketing](), [scaling]() ### AI overview The article describes a developer-marketing approach for creating advocates by mentoring a small group of people, helping them succeed, and empowering them to communicate their experiences. It recommends collaboration, private communication channels, and support with sharing success stories. ### Source excerpt The first area I tend to think about when it comes to developer marketing is around advocates. A simple definition of an advocate is someone that speaks/writes in favor of some thing. Creating advocates is a means of creating more of myself to go out and talk loudly and ideally effectively. However, they do take time to cultivate and it is a hard item to track. But by cultivating advocates I'm able to scale what would otherwise be a bottleneck of my own personal time. Mentorship The people in your group of 3 you'll have nearly daily communications with, even if quick. These are the first people you think to work and collaborate with. It's the case with all, but especially so here that there may be some strong mutual benefit. With both the groups of 3 and 12 you'll be looking to: Co-author content with Collaborate on projects Help amplify their content Helping them Succeed For a few years I've followed a similar process to this. Essentially creating advocates is done through first making them successful, then empowering to talk about their success. I've often done this by giving people a private channel to me - through IM, SMS, Phone, Skype, or even in person. Sure its easy enough to get my work email address, its a pretty easy one to guess, and even at that address I do aim to respond to every request. These channels in reality don't make me more available; but they do allow a different type of communication to happen. My personal approach has found it more out of place to ask how someones weekend was over email - IM or Skype make this easy. Broader questions of how someones actually doing in life generally are much easier to do over a coffee or a beer. This allows for a deeper relationship; at the same time I can ensure everyone I interact with is successful. It's easier to ensure someones successful if they're willing to talk to you, actually connecting with people enables this. Communicate Once someones been successful theres usually some value in their story. Th