Questions to help people decide what to learn

So much content out there disguises as 'tutorial' or 'blog post' but really is a part of the greater CV, evidence for skill and knowledge, and noticably fueled by fear of being technically wrong - the worst kind of wrong!

Mrs. Evans has this fearlessness to take on scary topics like profilers or "Ruby's Timeout", where it's hard to get a handle on all the nuances and to make a solid case. Without the need to prove anything, with no protective shield of aloofness the content turns out to be an enormous pleasure to read.

And maybe challenge the reader to produce content more honestly, too.

I was surprised how much I enjoyed clicking I learned something, even though I got the yes/no answer "correct".

Well done Julia. You have me thinking if I should prep my own content to direct new users to when fundamental questions are asked.

> people dislike questions that don’t match their mental model

> “what are the 4 parts of a HTTP request?”

I would describe this as a non-injective function. Unambiguous in one direction, but ambiguous in the other. It seems to be very common in lecturers who (1) have forgotten what it was like to learn it (2) aren't precise enough to ensure clarity as a matter of rigour.

Criticism aside, learning something is infinitely better than learning nothing. And finding a way to make it enjoyable and satisfying is a worthwhile end in itself.

An excellent way to know where you stand and learn.

(Why is this punctuation different from all other punctuation: ?)