Listen to Kamran read this

A developer files a GitHub issue and "solutions it" in the issue. In the end they boldly claim:

"Here's what you should do. That should work."

Ah... a maintainer nightmare scenario. Close the browser tab.

It may solve their problem. It's even possible they are so well-informed that it's viable and feasible but... usually, that's not the end of the story.

Does it align with the strategy? Does it have other side effects? Is it backward compatible? Will we need a migration? Is it already planned? Have we tried solving it before and it didn't work?

There's often so much more to a proposed solution.

Think of it the same way for your content.

You design developer personas and the research you've put in (and continue to put in since they're evergreen) will help you determine what needs you'll need to cater to in your content. You are making a strategic decision as to the audience you serve and who you don't. It's a mindful choice.

You can't please everyone. It doesn't work in software. It doesn't work in marketing. And it sure as heck doesn't work in learning.

It's just not feasible – unless you have a virtually unlimited budget.

If you truly thought you had to cater to everyone, you'd write every sample and snippet in every language used in the software industry. (That's right, we support Brainf*ck.)

There is a line that must be drawn – but the good part is that you can be very intentional through your personas on where that is and you can always adjust the line when necessary.

It's not carved in stone.

Have a lovely day,

Works as designed

Want devs to love your product?

Hi 👋 I'm Kamran. I'm a consulting developer educator who can help your DevRel team increase adoption with better docs, samples, and courseware.
Sign up