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 …
I think there's an easier way. I'm thinking of something lightweight enough to be worth embedding in a chat comment, for example. (If only chat clients were capable of processing it...)
-
-
The build tool is necessary, but I see a big opportunity to reuse "contexts".
-
I'm sure when you actually unveil what you have in mind it'll make sense, but it's a bit nebulous right now. The build tool is necessary but it'll work within an external chat client, the build tool is necessary but you have something simpler in mind...
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.