209 lines
7.8 KiB
HTML
209 lines
7.8 KiB
HTML
<!doctype html>
|
|
<html>
|
|
<head>
|
|
<title>Zk | RAWR day 1</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 | RAWR day 1</h1>
|
|
</header>
|
|
<article class="content">
|
|
<h1 id="administrator-lecture">Administrator lecture</h1>
|
|
<ul>
|
|
<li>History</li>
|
|
<li>Goal:<ul>
|
|
<li>Bring everyone together</li>
|
|
<li>Lean on instructors and others</li>
|
|
</ul>
|
|
</li>
|
|
<li>Structure:<ul>
|
|
<li>Morning: Lecture:<ul>
|
|
<li>In the drive, lectures are explained in EVENTS</li>
|
|
<li>Living schedule</li>
|
|
</ul>
|
|
</li>
|
|
<li>Reading:<ul>
|
|
<li>Monday/Wednesday</li>
|
|
<li>Reading/critique of stories:<ul>
|
|
<li>Discussions just talking about stories</li>
|
|
<li>Critiques have specific structure.</li>
|
|
<li>Critiques need to be in before session.</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Coaching:<ul>
|
|
<li>Entitled to single session with each instructor</li>
|
|
<li>Aim for doing after critique</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Code of conduct:<ul>
|
|
<li>Don’t be a jerk</li>
|
|
<li>Conversation, not a shouting match</li>
|
|
<li>If something makes you uncomfortable, say something</li>
|
|
<li>Put TW/CWs on work (updated documents for such)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Harassment policy:<ul>
|
|
<li>If you feel someone’s conduct is inappropriate</li>
|
|
<li>Let either the other person or an instructor know</li>
|
|
</ul>
|
|
</li>
|
|
<li>Feedback and complaints:<ul>
|
|
<li>Lean on email - Alkani</li>
|
|
<li>Survey after</li>
|
|
</ul>
|
|
</li>
|
|
<li>Post event:<ul>
|
|
<li>Survive the Crucible - very compressed event</li>
|
|
<li>Emails will be transferred to alumni list</li>
|
|
<li>Slack after</li>
|
|
<li>ReRAWR</li>
|
|
<li>50% discount for <a href="https://www.archivos.digital/">Archivos</a> tool - mindmapping, cloud-based, etc.</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h1 id="instructors-lecture">Instructors’ lecture</h1>
|
|
<ul>
|
|
<li>Staff and Instructors:<ul>
|
|
<li>Kyell Gold:<ul>
|
|
<li>Been doing it for about 6 years, Alkani runs logistics</li>
|
|
<li>Weird doing it in person, hang out online!</li>
|
|
<li>BG:<ul>
|
|
<li>Attended Clarion 10 years ago</li>
|
|
<li>Writing for a long time, hope to share</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Dayna Smith:<ul>
|
|
<li>Met Kyell at novel workshop</li>
|
|
<li>Lecture given elsewhere (Wiscon, etc).</li>
|
|
<li>Read “Hangdog”</li>
|
|
<li>BG:<ul>
|
|
<li>Clarion 6 years ago</li>
|
|
<li>Mostly novels, but also writing for Lovestruck (app)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Suggestions:<ul>
|
|
<li>Hang out in common room often to learn from each other, etc</li>
|
|
<li>Learn from each other, take chances</li>
|
|
<li>Stay in touch, use alumni network</li>
|
|
<li>The story that we produce will be a first draft, nothing needs to stay secret, don’t worry about making it polished</li>
|
|
<li>All of us help each other become better storytellers - no one wins the workshop, or rather, all of us win it</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>The Story:<ul>
|
|
<li>One thing we will be doing here is creating something wholly new</li>
|
|
<li>That will be Th critiques</li>
|
|
<li>From Julia Rios (started at Strange Horizons, moved to Uncanny)</li>
|
|
<li>“Come up with something new, doesn’t have to be long (follow RAWR guidelines), but it has to be complete”</li>
|
|
<li>Don’t freak out - you get out of it what you put into it</li>
|
|
<li>Know what you can do on the fly, so this shows what you can do, have fun</li>
|
|
<li>Useful if you have a deadline if you’re prone to overthinking</li>
|
|
</ul>
|
|
</li>
|
|
<li>Critique:<ul>
|
|
<li>The better you learn how to critique, the more you learn about your own writing, let you critique your own as you work</li>
|
|
<li>The point is to help the author improve the story, how to make it more effective</li>
|
|
<li>Author is always free to reject a critique, but every critique is valid</li>
|
|
<li>How:<ul>
|
|
<li>Read it through once to get a sense of the story, let it work its magic</li>
|
|
<li>Go back with ‘red pen’, what worked, what didn’t work, where did we fall away, what was exciting, characters, what to see more of, what to see less of, etc</li>
|
|
<li>First readthrough shows where the author is going so you can see early setups pay off</li>
|
|
<li>First time, author just listens</li>
|
|
</ul>
|
|
</li>
|
|
<li>Mechanics:<ul>
|
|
<li>Make notes with whatever program</li>
|
|
<li>Written critique - basically an essay about feelings of story:<ul>
|
|
<li>Was the story engaging? Was there a point where it lost you/you got bored? (MEGO - my eyes glazed over; red line through story where it stopped being engaging)</li>
|
|
<li>Story components:<ul>
|
|
<li>Setting (add to the story)</li>
|
|
<li>Characters (interesting)</li>
|
|
<li>Description (clear and enjoyable picture)</li>
|
|
<li>Language (nice to read)</li>
|
|
<li>Dialog (flow, not <em>too</em> realistic, more like movie dialog)</li>
|
|
<li>Story and plot (satisfying, useful structure)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Highlight both good and improvement</li>
|
|
<li>A few minutes to read through essay during critique (or bullet points)</li>
|
|
<li>Instructors will have longer critiques</li>
|
|
<li>Critique story, not author (don’t hearken back to other stories, etc)</li>
|
|
<li>What was intended, how effective was that</li>
|
|
</ul>
|
|
</li>
|
|
<li>Positive, yet constructive:<ul>
|
|
<li>even if it doesn’t work for you, find positivity</li>
|
|
<li>Helps for saying nice things about your own story</li>
|
|
<li>Aim for ‘improvement’ rather than just ‘didn’t like it’</li>
|
|
</ul>
|
|
</li>
|
|
<li>Don’t try and rewrite:<ul>
|
|
<li>“If this were my story, I might do…”</li>
|
|
<li>not “You should do this”</li>
|
|
<li>If multiple people say that something didn’t work, they’re probably right, but if they tell you how, they’re probably wrong</li>
|
|
<li>Author can ask for that during dialog after silent listening</li>
|
|
</ul>
|
|
</li>
|
|
<li>tally mark of confirmation is fine, don’t need to hammer in a point someone already said (“ditto x” or “I disagree with x”)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Receiving critique:<ul>
|
|
<li>Be prepared for folks to tell you what’s wrong with the story (compliments make it easier)</li>
|
|
<li>Take a lot of notes (make sure to write down praise, very easy to forget praise, important to have sense of what you do well)</li>
|
|
<li>Every critique is valid, but you’ll never get 100% agreement, up to you to decide if you’ll tweak</li>
|
|
<li>When brought into the discussion, that’s when you can ask questions</li>
|
|
<li>From both sides, trying to make the story better, so accept critique in that spirit</li>
|
|
<li>If you’re writing about something personal, let folks know if we’re prancing around on sore spots</li>
|
|
<li>Feel free to write personal stuff, experiment, etc</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>Introductions:<ul>
|
|
<li>Alkani (they/he)</li>
|
|
<li>Dayna (she/they)</li>
|
|
<li>Kyell (he/him)</li>
|
|
<li>Makyo/Maddy (she/her)</li>
|
|
<li>Kiri (she/her)</li>
|
|
<li>Al (he/they)</li>
|
|
<li>We’ll have a common room that’s mostly w/o instructors in order to get some space to chat or work together (can ask for that)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h1 id="assignment">Assignment</h1>
|
|
<ul>
|
|
<li>ASSIGNMENT: Read stories in drive (links/PDFs provided) for discussion tomorrow.<ul>
|
|
<li>“Guide to Working Breeds” by Vina Jie-Min Prasad</li>
|
|
<li>“A Soft White Damn” by Ryan Campbell</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>
|