How would that change the way you thought about it? Would you... * Create a product team around it? * Create a roadmap for it? * Work on it in sprints? * Have daily scrums? * Instrument and measure the experience? * Perform usability studies? * Market it? * Create native apps? * Add a SaaS on top of
In the inaugural episode of the DevEducate podcast, I invited Todd Gardner (co-founder of TrackJS) to come on the show and talk about how he approached marketing and educating developers to grow his two developer tooling SaaS products.
This week's Fundo Friday event is about creating reusable "audiogram" templates in Descript, something I worked on this week as I get ready to launch the podcast.
Recently I wrote about the challenge of communication tools like Slack and Discord locking in knowledge within their walls and not making it easy to find previous discussions. This makes learning less accessible and searchable. Despite this drawback, many companies use Slack and Discord as developer communities and support forums.
Normally we tend to see docs as ancillary to a software product – but what if it was another product? I'm not sure that could be the case all the time but for reference material sometimes there's innate value in it depending on how it's
When a developer leaves a comment on your work, you know you've cooked a tasty piece of content – they've engaged! But that's where the trail ends. If they copy/paste any code somewhere else, you won't really know. On the other hand,
