Tell me what you lived through
Don't just regurgitate the docs
Don't just regurgitate the docs
Continuing in this series of examples of tension in technical storytelling (part 1, part 2), I said previously that it's important to close the loop and release tension after you create it. Because if you don't, it will eat at the learner, at best distracting them,
I just wrote about creating tension by showing The Wrong Way First, but there are other ways to do this, too. I said the Wrong Way First method isn't as effective when introducing new concepts. So, how can tension be created effectively in that case? This example comes
I have written before about the strategy of creating tension in storytelling – and I get that it might seem abstract so I wanted to share a concrete example (a tactic!) of one way to create tension in teaching technical content. I am reviewing an upcoming Pluralsight course that deals with
Hint: Tell a story
Recently for Excalibur we've been seeing some success driving traffic through blog posts cross-posted to Dev.to (with canonical source set to our blog). These are not written by me or Erik, they're written by some of our amazing community members and contributors. Excalibur — DEV Community