When I say "course" you say...? "Video!" But a course is just format and structure (with learning objectives) – the implementation could be through email, podcast, Slack messages, video, or... docs. For a dev tools docs site which is chock full of written content, one idea for
This talk of neurodiversity, tutorials, and shareable open source components brings up a thought I've had in the past but haven't written much about yet, which is the idea of developing a "developer learning experience (DLX) design system" (or maybe, "developer experience design
Imagine getting invited to a friend-of-a-friend's house and then when you get there, there's no indication of where to go. Do you knock? Go through the house? Around back? Do you need to 'beware of dog'? Oh CRUD, did you forget to bring dessert?
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
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
