Why Ask a Developer?
We love learning about individual developers! But it can be misleading to rely too much on anecdotal evidence. That’s why we also use data like that collected by Evans Data Corporation, SlashData, and our own surveys. However, running an idea, question or assumption by a member of the audience (MOA) can still add value. In this case, our MOAs are your audience, too — developers and other IT professionals.
While there may be as many answers as there are developers, often interesting trends as well as hard-to-find nuances emerge. Unsurprisingly, stories told at a human scale often appear as overarching themes or trends at a population scale. That’s why we asked celebrity developer and Twitch Live Coder Jeffrey Fritz to ask fellow developers some of the questions technical content marketers most want answered.
Meet Andy Schwam
Fritz caught up with Andy Schwam, AVP of Enterprise Architecture for the Global Indemnity Group and an organizer of TechBash at TechBash 2019. Fritz asked Schwam about his favorite types of technical content and what makes them useful.
What Type of Tech Content Do You Like?
Take a Stand
Schwam likes blog posts, particularly those that state a specific opinion. They help him better understand the author’s perspective, and ultimately, the technology being written about. Another way to draw him into technical content (and the technology itself) is to offer a dialogue within the content by comparing and contrasting a technology or approach.
“The ‘because’ is critical,” according to Schwam. “If I don’t get the ‘why,’ I might apply it in the wrong cases.”
Text-Based Short Form Content Is Good
Schwam prefers shorter form content — but for longer form explorations he prefers text-based content if he’s going to snag a code snippet.
Tell Him How
Schwam’s favorite type of content is quick and to-the-point how-to’s.
What Makes Tutorials and How-To’s Developer-Friendly?
Schwam craves currency, as in content that is updated and current. For a blog post, it’s okay to treat it like it has a longer shelf life, but documentation needs to be updated frequently (ideally with prominent versioning). Of course, technical accuracy is paramount, but don’t skimp on presentation. Spelling errors and grammatical mistakes make Schwam wonder how accurate everything really is — including the technical portions.