I think the solution, at least from a social perspective, is to make authoring a blog or tutorial which includes all the appropriate package names easier than authoring a blog or tutorial which omits them.https://twitter.com/propensive/status/1201177788247683072 …
-
Show this thread
-
How could that possibly be? Well, nobody writes examples without doing some form of checking on them. Having a compiler check the examples is already easier than compiling them (reliably) in your head, and it forces you to provide all necessary context.
3 replies 0 retweets 1 likeShow this thread -
Replying to @propensive
Thinking of your presentation at
@ScaleByTheBay and reading this: something tells me you have a proposed solution to this
pic.twitter.com/EnyqrHfgDR1 reply 0 retweets 2 likes
I have vague ideas, but I'm not fully satisfied with them yet. I don't want people to have to commit to my whole Amok solution just to benefit from compiler-checked examples. But I want to take advantage of Fury's ability to define builds which could provide the necessary context
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.