That isn't a razor...
nods to Crocodile Dundee . . .
Feynman’s Razor
11–20 of 138 posts
Re: Feynman’s Razor
#12Re: Feynman’s Razor
#13I agree this is true if your goal is to inform. If, however, your goal is to increase clicks, decrease support tickets, and get engagement, I'd be surprised if being technically descriptive and accurate is better than dumbing it down to the point of inaccuracy. None of that is to say that I agree with the goal of engagement over conveying information.
Re: Feynman’s Razor
#14What’s the point of conveying root causes to the user? In this case the error tells you what you need to know: copy the message. Send it again if you want.
The point of communication isn’t always education. This isn’t a razor. It doesn’t do anything to help you consider audience. It will lead you to bad conclusions.
Re: Feynman’s Razor
#15Feynman confused pedagogical skill with expertise in a given field. He insisted that experts could explain things. No, that's what a teacher does. Feynman was good at both and apparently had no one to challenge him on his claim that they were the same. It's possible to be a great teacher without being an expert on given subject matter. And it's possible to have the most expertise but be inscrutable. In the case of th…
Feynman was not a great teacher. Lots of people love his lectures now. But they're not getting graded on it. Actual students were considerably more mixed. Obviously individuals vary so if I post how most of his students were totally lost in class, they'll post how one student went on to win a Nobel prize and say gotcha.
Feynman was a world class second type teacher. If you already know how to work with physics equations and solve problems, then Feynman's lectures will improve your understanding considerably. The simplification process he does, gives you a grand understanding of the theory.
Due to this, much of Feynman's pedagogy is not suitable for the first type of teaching. And should not be used as such.
Re: Feynman’s Razor
#16Funny thing is I think this about Feynman’s own writing for “the layperson”. I think things like Feynman’s “little arrows” descriptions in QED only muddied and added to the mystique and mysticism of the physics he loved. Which is interesting because his written lectures[1], though, in their breadth and complexity require effort, seem as if they are intended for experts while being approachable to ”the layperson“. My…
Re: Feynman’s Razor
#17Re: Feynman’s Razor
#18Funny thing is I think this about Feynman’s own writing for “the layperson”. I think things like Feynman’s “little arrows” descriptions in QED only muddied and added to the mystique and mysticism of the physics he loved. Which is interesting because his written lectures[1], though, in their breadth and complexity require effort, seem as if they are intended for experts while being approachable to ”the layperson“. My…
Re: Feynman’s Razor
#19The original message is enough information to deduce what’s probably going on as an expert and not feel alien to the customer base. What’s the point of conveying root causes to the user? In this case the error tells you what you need to know: copy the message. Send it again if you want. The point of communication isn’t always education. This isn’t a razor. It doesn’t do anything to help you consider audience. It will…
I dunno, I had no idea what the original message was trying to convey; it wasn't until I read lisper's comment that I got what was going on.
Re: Feynman’s Razor
#20Every other storage-related system I’ve ever used either had inscrutable gibberish like:
“Mode 5/7?” [Y]
Or overly dumbed down questions like: Are you sure? [N]
What am I sure about!? What is mode 5? Or is it 7? Both? What!? [1]Norton meanwhile had several paragraphs of text explaining what every decision meant. It explained concepts inline. It provided an explanation of the benefits and risks. It let you make an informed choice instead of just hitting Y over and over and hoping for the best.
This kind of respect for the reader / user applies to all forms of technical writing such as manuals, user interfaces, blog articles, and API docs.
Instead of trying to dumb down the text for a “lay” audience, try to educate all audiences to become more technical after having read and understood what you wrote.
[1] That is verbatim from a Hitachi SAN array that was holding all of the data for a government department. The manual helpfully explained that this option toggles between mode 5/7 being either on or off. If you choose wrong the array will erase itself and kill your cat. Or neither of those things. Who knows?