Marcos Placona

Yes!!! Another KeyStrok.es happy customer!

Video looks great, Lars!

7 Data‑Driven Checks to ensure your Documentation ROI is high …and why Dosu keeps the meter running in your favor. Author: Marcos Placona | DevRel @ Dosu It’s easy for documentation to get shoved aside when you’re racing to ship features. But it’s the quiet fo...

Most companies say docs matter, but @mplacona.com 🧮 crunched the numbers.

Good docs =
-$22k/year wasted per dev just hunting for answers
-$1.25M/year in onboarding drag for a 100-dev org
-$50k+ in support costs you could deflect with self-service

👇 Full breakdown (with data)👇
go.dosu.dev/HcW2dLS

Chat, what does this mean? Do I unlock a prize or something?

Why does authenticity matter in developer relations?

None of us likes being marketed or sold to. Developers expect transparency above all, so anything that screams marketing will be easily readable and counterproductive.

The best indie developers are leveraging AI as a tool in their coding process.

They use every tool available to build faster, ship more products in their lifetime, and run circles around normal teams.

What are your favourite? Cursor is mine right now!

Building in public builds trust.

I found that sharing my journey as an indie developer:
- Helps others learn from my wins and mistakes
- Showcases authenticity
- Builds relationships with users

Every entrepreneur faces failures.

What defines a winning entrepreneur is the one who learns and keeps moving forward! 🚀

Engaging dev communities fuels indie success.

Key strategies I use:
- Share open-source tools and libraries
- Contribute to others' projects
- Discuss topics you care about
- Seek feedback on your projects

Focus on helping others. Give more than you take. What are your strategies?

Want devs to love your SDK? Make it easy to use.

1. Ship a variety of samples.
2. Remove barriers to getting started.
3. Focus your docs on the "80% use case."

Developer love is a moat!

What people see:

- New product launches
- Multiple successful startups
- 45K users on latest product in 5 months
- Building products people love

What people don't see:

- Years working in the trenches
- Building a startup while parenting kids
- Learning and executing relentlessly

That's the path.

😮 what was the original message?

• To own your work
• To build an audience
• For the free marketing during the build phase
• To create a product with an audience in mind
• To gather feedback early on

Building in public is a superpower.

Instead of keeping ideas to yourself until you launch, you share everything, and build in public from the start. That means everything is transparent. Your progress, your learnings, and even your failures.

But why do that? 👇

Building a successful DevRel program requires three strategies at its core: enabling developers by making it easier for them to understand and integrate the solutions, having strong and accessible documentation, and engaging in public channels. Focusing on these three areas goes a long way!

Hard to believe I can do this nowadays. @lovable_dev

#buildinpublic

I'm creating something new—it's a directory!

To all the directory builders out there, what are your best tips?

2. Large companies often need more in-house resources to build and maintain SDKs in all languages.

3. SDK generation tools put independent developers at the forefront of the trend by helping them build production-ready libraries quickly.

Libraries and SDKs are becoming the new APIs:

1. Companies need libraries/SDKs to drive product adoption and reduce barriers to entry.

Looking for a recommendation for a good air quality sensor.

I’m starting to think bad air quality is getting on the way of a good night sleep.

And they do tend to be happier to part with their money for a good deal. Also, the feedback is usually awesome!

- Automate manual work away. Bots, scripts, and APIs save time on repetitive tasks and unglamorous chores.

Most importantly, launch quickly and iterate based on user feedback. Let real people—not yourself—decide whether it's worth pursuing.

- Don't overcomplicate your funnel. Credits for word-of-mouth referrals make analytics redundant.

- Create products people need (this is BIG). Solve your own problems, and others will find your product through recommendations and search.

- Productize your skills. Creating a product that leverages your strengths lets you ship more features in less time.

Here are a few lessons I've learned from my journey as an indie hacker building products without a big team or budget:

- Build tools for indie makers and devs. They're eager to try new products without requiring lengthy sales and legal reviews.

👇

In summary: empower developer success, earn their trust and loyalty. They’ll share your product as insiders.

4. Recognize Valuable Contributions
Thank developers for their time, feedback, ideas, and sample apps that benefit others. Recognizing key contributors builds goodwill and deeper connections.

3. Gather Ongoing Feedback
Follow along with developer journeys. Ask questions and implement their suggestions to demonstrate care and commitment.

2. Provide Live Support and Access
Be present where developers want live support. Make connecting with real people easy via chat, forums, and office hours. Allow direct access rather than gating all discussions.

1. Enable Developer Success
Ensure developers can integrate your product and go live smoothly, without unnecessary roadblocks or hidden fees. When they're successful, they'll naturally advocate for you.