We Want MoR – Chapters 25 and 26

WWMoR-Square

Harry sets off a plot to squash Rita Skeeter.


We are happy to be a part of the Doof! Media podcast network! Check their stuff and support them/us on Patreon! Chat with us and everyone else in the Doof! network on Discord by becoming a supporter!


Original chapters, written by Eliezer Yudkowsky, can be read here and the audiobook chapters, recorded by Eneasz Brodski, can be found earlier in this podcast feed and on the website.


In next week’s episode, we will be covering chapters 27 and 28.


Album art courtesy of Lorec from The Bayesian Conspiracy podcast’s Discord. Thank you!

Coy on the same Discord manages an RSS feed that compiles the relevant audiobook chapters with the WW MoR counterparts. Just copy and paste that link into your favorite podcast app in the “add by url” option. Thanks, Coy!

Bookmark the permalink.

3 Comments

  1. The tossing of the Portkey Knut was actually a reference to one of the most common nitpick complaints about the fourth Harry Potter book. The villain goes through this whole overly elaborate plan with hundreds of moving parts that not only could but should have gone wrong, just to get Harry to touch a Portkey. Instead he should have just thrown him an enchanted Knut, which Harry would have instinctively caught.

    And so Quirrel does it here, in a completely different context.

  2. I didn’t have any expectations concerning that name, but the more I was
    amazed. The author did a great job, he reminded me about the author that wrote this https://nightclubchicago.org/. I spent a
    couple of minutes reading and checking the facts.
    Everything is very clear and understandable.
    I enjoy posts that fill in your knowledge gaps.
    This one is of that sort. Moreover, I like how the writer organized his thoughts as well as the visual part.

  3. Sebastian Weinberg

    I think that Brian, having seen the benefits of Agile over Waterfall, has developed a bit of an aversion to ANY form of planning.  In this case, I believe that you’re conflating a good method for achieving goals (Agile development) with a good method for identifying what the goals ought to be — i.e. thinking about it for at least five minutes.

    Agile development doesn’t protect you from achieving the wrong goals.  How often have you seen a perfectly developed piece of software delivered to the customer, only to get the reply, “We asked you for X, and that’s what you delivered, but it turns out that we actually needed Y all along.”  Well, okay, probably never, because it’s usually phrased as, “We needed Y! Why the hell did you deliver X?!” and it’s bad for business to reply truthfully, “Because you explicitly and specifically ASKED for X, along every step of the way.  That’s why.”

    It’s all well and good to say, “Get in there and start fucking up quickly,” but you need to know what you intend to achieve, before you can agilely set out to achieve it — otherwise how do you tell the difference between fucking up and succeeding?

    The method brought up in the fic, “Examine the problem/situation from all angles and in all aspects, before you even think about solving it, let alone proposing any SPECIFIC solution,” doesn’t say anything about planning, nor how rigid or flexible plans ought to be (Waterfall vs. Agile).  On the contrary, it tells you NOT to plan, not even set goals to plan for, until you’ve fully pondered the situation.
     

    Regarding Quirrel’s office hours and draconian rules for using them, the impression I got from it was that this was an extension of his “doesn’t suffer fools gladly” persona.  You brought up the example of a sixth or seventh year student asking for advanced information, and whether Quirrel would just tell them to fuck off; my impression was that that would be the ONLY kind of interaction he’d allow, and he wants everyone else to piss off and, if possible, die in a fire.

    You need to have earned at least one point in his class, just to knock on the door, and if you bother him with something trivial or stupid (like brown-nosers who want a pat on the head, or lazy students who don’t want to look something up in the library, etc.) then you get hit with a 50-point deduction.
     

    Steven, you are not going to Podcast Hell for pointing out something that was right there on the page, if you notice that Brian seems to have missed it.  Especially if it is the ONE important line that suddenly recontextualises half the events leading up to it.  That cannot possibly be a spoiler, because, when you actually think about it, MISSING it would actually spoil the enjoyment of the chapter far more.

    People can sometimes go a bit insane where spoilers are concerned — or in what they somehow consider “spoilers”.  For example, I follow a lovely YouTuber who does Let’s Plays of video games.  He’s very funny, but he has a tendency to get distracted and not pay a lot of attention to the game he’s playing, concentrating on being entertaining to us, the viewers, instead.

    One time, he missed a vital piece of information about game mechanics that the game was tutorialising, because he was busy delivering some hilarious monologue.  When I posted in the comments on his site, something along the lines of, “Hey, just FYI, you missed a tutorial message at 05:23.  You’ll need to know that, if you ever want to use that specific game mechanic.”

    Immediately some other commenters started screaming at me, “Waah waah, spoilers, waaaaahh!!!”

    My reaction was, “How the fuck can that be a spoiler?!  That was explicit information, stated in bright, neon green letters in the middle of the screen!  The fact that he wasn’t paying attention at the time and missed it DOESN’T TURN IT INTO A SPOILER!  That’s not how spoilers work.  That’s not how ANYTHING works.  Go away and for god’s sake take your meds.”

Leave a Reply to Patti Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.