91 lines
3.8 KiB
HTML
91 lines
3.8 KiB
HTML
<!doctype html>
|
|
<html>
|
|
<head>
|
|
<title>Zk | Friday — Critical Reading</title>
|
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Gentium+Plus&family=Lato&family=Ubuntu+Monodisplay=swap" />
|
|
<link rel="stylesheet" type="text/css" href="/style.css?2024-05-04" />
|
|
<meta name="viewport" content="width=device-width" />
|
|
<meta charset="utf-8" />
|
|
</head>
|
|
<body>
|
|
<main>
|
|
<header>
|
|
<h1>Zk | Friday — Critical Reading</h1>
|
|
</header>
|
|
<article class="content">
|
|
<ul>
|
|
<li>Intro<ul>
|
|
<li>Intro self (incl “this is for MFA” spiel)</li>
|
|
<li>Allow others to intro</li>
|
|
</ul>
|
|
</li>
|
|
<li>Ice breaker: What is your least favorite part of your favorite movie?</li>
|
|
<li>Lead into what is a text:<ul>
|
|
<li>Books/writing, yes, but also anything that tells a story — film, games, etc</li>
|
|
<li>Thus, what is critical reading?</li>
|
|
</ul>
|
|
</li>
|
|
<li>Intentional engagement with a text, especially WRT the self:<ul>
|
|
<li>Back to ice breaker: how do you intentionally engage with your favorite film?</li>
|
|
<li>How do we intentionally engage with a text in furry?<ul>
|
|
<li>What do we like in a furry text?</li>
|
|
<li>What <em>don’t</em> we like?</li>
|
|
<li>Notably, not asking what makes a text furry — that we are furries is what enables us to read in that context</li>
|
|
<li>Thus, how do we engage with a text that <em>we</em> feel is furry <em>as</em> furries?</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>What goes into critical reading?<ul>
|
|
<li>Layers:<ul>
|
|
<li>Mechanical: presentation, word choice, language usage, writing style, etc</li>
|
|
<li>Subjective: emotional impact, plot effectiveness, description, evocativeness</li>
|
|
</ul>
|
|
</li>
|
|
<li>“7 Trips Through the Score” — may n ot need that many, but multiple (or at least slow) reading can let us focus on one layer at a time</li>
|
|
</ul>
|
|
</li>
|
|
<li>Reading exercise:<ul>
|
|
<li>Pick 1 of these 2 categories to pay attention to first and read, then read for the second</li>
|
|
<li>Critique tomorrow, but preview: we’re not tearing a text apart, we’re asking it questions:<ul>
|
|
<li>How did we feel the plot worked? Was there a structure? Could we follow it?</li>
|
|
<li>What was told? What was left out? How did (not) knowing make us feel?</li>
|
|
<li>What type of language usage was there? Word choice? Style usage?</li>
|
|
<li>How about emotional impact? Was the story impactful? Did the mechanics help or hiinder?</li>
|
|
<li>Was it evocative? How did the furry elements play into it? Did you want to learn more? Was it engaging?</li>
|
|
</ul>
|
|
</li>
|
|
<li>Be ready to summarize</li>
|
|
<li>(~10 minutes to read)</li>
|
|
<li>Someone summarize</li>
|
|
<li>Talk through each</li>
|
|
<li>Talk through how the exercise felt:<ul>
|
|
<li>Was it useful? Tiring? Enjoyable?</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Tomorrow, we’ll go through critiquing writing and actually workshop a piece — one of mine that has already been workshopped and published, so it’s just an example of critiquing for a present author without putting anyone on the spot</li>
|
|
<li>Do you want optional homework for Sunday?<ul>
|
|
<li>Write a short ~500 word snippet (or offer one already written) to go through a gentle workshopping</li>
|
|
<li>While writing, think about what we talked through today</li>
|
|
<li>Email to me, I’ll put it online for all to read in the workshop</li>
|
|
<li>Will be asking how it felt/etc</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</article>
|
|
<footer>
|
|
<p>Page generated on 2024-05-04</p>
|
|
</footer>
|
|
</main>
|
|
<script type="text/javascript">
|
|
document.querySelectorAll('.tag').forEach(tag => {
|
|
let text = tag.innerText;
|
|
tag.innerText = '';
|
|
tag.innerHTML = `<a href="/tags.html#${text}">${text}</a>`;
|
|
});
|
|
</script>
|
|
</body>
|
|
</html>
|