Can you post a speci
[2022-04-24 11:51:05 AM] : Can you post a specific example of a thread and your best attempt at safari notes on that thread, Duy Hoang?
1 Reply
[2022-04-24 12:17:59 PM] : Surely :slightly_smiling_face:
Thread: https://www.reddit.com/r/learnjavascript/comments/uanb39/really_need_some_advice_on_higher_order_functions/
Painstorming:
- "I've been learning or attempting to learn JS"
* "Felt like making decent progress till I reached callbacks / higher order functions"
* "No matter how many videos / lectures I watch / read"
* "Feels like the wall I can't get over"
* "If you guys had any advice on some more resources I could use"
* "Maybe even just another way of looking at it."
* "I admit its not easy to explain."
* "Contact me for better explaination, visual stuff"
Questions:
* "What specifically are you struggling with?"
* "What don't you get though, more specifically?"
Suggestions:
* "That's all callbacks are - ways of specialising another function."
* "You just make things worse. He doesn't understand callbacks and you suggest koa-compose?"
* "You can look at some techniques that explore this idea: Currying, Middleware"
* "Plain callbacks is just nodejs standard stuff"
* "Reading up and watching videos on those concepts specifically"
[2022-04-24 01:15:51 PM] : got it!
[2022-04-24 01:15:59 PM] : so the notes you've taken so far look great, nice work! here are a couple of suggestions to answer your question about long threaded responses:
[2022-04-24 01:25:25 PM] : "general suggestions" can be useful to note, but I see some examples of pain between the code that is a little more subtle. for example...
from the long message with code: "This [example] isn't the most common way of using callbacks though - they can get messy, so you really only want to use them in very specific situations." lots of good subtle pain in there!
[2022-04-24 01:25:28 PM] : also try thinking about why that long threaded reply exists. what does that long threaded reply assume about the situation? what is it trying to accomplish? in this case, it looks to me like the writer of that longer technical comment is trying to show a simple example before explaining a complicated one, plus the line "there is no magic" suggests some things about what they might think the reader isn't seeing.
[2022-04-24 01:29:32 PM] : this isn't as applicable in this thread, but you can also "zoom out" and try to synthesize things like:
• why are people reacting to this question in this way?
• what knowledge is assumed? what knowledge might be missing from the conversation?
• what's missing from this conversation? what isn't being said?
[2022-04-24 01:32:59 PM] : besides those suggestions, you did a very good job of capturing most of the surface level pain on the page. the next level is reading a bit closer, and using your understanding of the problem area to figure out what pain isn't as obvious.
watching or re-watching the 30x500 lessons that introduce "safari gold" (a.k.a. the more subtle kinds of pain, jargon, and worldview) would be a good idea for making sure you are getting stuff between the lines of the code examples.
[2022-04-24 01:41:54 PM] : I'll ask myself those questions and be more concise the next time I practice pain storming. I haven't gotten around to watching those advanced pain storming techniques videos yet, but I will. Thank you for your comments and suggestions. Thank you very much!
[2022-04-24 01:42:44 PM] : you're very welcome. you did an excellent job if you haven't moved on to the more advanced safari lessons yet!
[2022-04-24 01:42:51 PM] : keep up the practice :thumbsup: