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 …
-
-
So, to be easier overall, it "just" needs to be made easy to check the code fragments embedded within some text (in whatever form), without forcing the author to jump through too many hoops to set everything up. I have a background process running in my brain working on this.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thinking of your presentation at
@ScaleByTheBay and reading this: something tells me you have a proposed solution to this
pic.twitter.com/EnyqrHfgDR -
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
End of conversation
New conversation -
-
-
It is amazing how many code examples from the internet or even from books don't compile, because of real errors.
-
Haha! That's probably true too! I just don't know because I can't get past the missing imports...
End of conversation
New conversation -
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.