Prepared for Presentation at The Collaborative, Trinity University
W. Caleb McDaniel
Rice University
- Introductions: Homepage and Twitter
- Acknowledgments to Center for Teaching Excellence and DU Writing Center
#!/bin/bash | |
# change to directory that holds my Gitit wiki | |
cd /path/to/dir/with/git/repo | |
if git log -1 --pretty=%s | grep -iq tweak; then | |
exit 0 | |
else | |
MESSAGE="Updated some notes in my open research notebook:" | |
SHA=`git rev-parse HEAD` |
Prepared for Presentation at The Collaborative, Trinity University
W. Caleb McDaniel
Rice University
Practiced writers and presenters analyze their audiences and address them accordingly. But in the beginning, novice writers are often so focused on what they know or want to say that they forget to think about whom they are addressing.
For example, in their eagerness to share in detail what they know, novice writers may spend too much time on facts the audience already knows, or they may develop their points for longer and in a different tone than the audience expects. On the other hand, a novice writer may assume too much about what the audience knows or expects and therefore neglect to explain unfamiliar topics, to choose understandable words, to cite sources correctly, or to persuade the audience that the author's subject is important. Such examples of mismatch between an author's work and the audience's expectations typically arise when the author has th
Whether communicating in writing or orally, effective communication requires ongoing attention to multiple levels of your presentation, from the level of the sentence all the way up to the level of the presentation as a whole. Communication is ineffective when it violates rules of correct communication and/or veers from widely accepted principles about how to present ideas.
Emerging Practice: When you are just beginning to learn how to take positions in your writing, you may find yourself producing work that merely shares information or reports on positions that other writers have already taken. Novice writers make lots of points in their work without connecting them together to stake out a coherent, complex position to which all the points contribute. A piece of writing with lots of "points" but no "position" also tends to rely on assertion and generalization: instead of showing why something is the case, novice writers simply say that it is the case, relying on imprecise appeals to common sense or overly simplistic theories of explanation, instead of on specific available evidence and logical reasoning. They pay little if any attention to alternative interpretations or explanations of the same evidence, either because the
#!/usr/local/bin/python | |
# -*- coding: utf-8 -*- | |
# Usage: pandoc --filter=wayback.py input | |
# Install pandocfilters and requests with pip before using | |
# Warning: may take a while to process input with lots of links | |
# Note: Links that can't be saved to WBM or already point to WBM are left as is | |
from pandocfilters import toJSONFilter, Link | |
import requests |
#! /usr/bin/env python | |
import sys, requests | |
# Usage: Pass URL to script, get back URL to Wayback Machine snapshot | |
base_url = 'http://web.archive.org' | |
r = requests.get(base_url + '/save/' + sys.argv[1]) | |
if r.status_code == requests.codes.ok: |
The inaugural Baker-Duncan Hack-a-Thon begins Sunday at 1 p.m. and runs through Monday at 8 p.m. Let's see what we can build together that will improve our lives in the colleges! Read on for more details, and contact Caleb McDaniel (Duncan) or Stephen Bradshaw (Baker) with any questions.
Everyone from Duncan and Baker is welcome (even if you haven't signed up) and there are lots of ways to participate! You are NOT required to have technical experience or any experience with hack-a-thons to participate in BaDunc Hack.
In a typical hack, small teams of two to five people work to create something new over the course of the hack-a-thon. Our challenge to BaDunc teams is to use code, data, or just some focused collaboration to build something that will improve the quality of life for students at Baker and Duncan, whether that be a new web app,
" Vim filetype plugin file | |
" Language: Mail | |
" Maintainer: Bram Moolenaar <[email protected]> | |
" Last Change: 2009 Jun 03 | |
" Only do this when not done yet for this buffer | |
if exists("b:did_ftplugin") | |
finish | |
endif | |
let b:did_ftplugin = 1 |
#!/usr/bin/python | |
# I run a wiki on Gitit at http://wiki.wcaleb.rice.edu. It's usually | |
# updated by pushing to the wiki's remote git repo from my local machine. | |
# I have a `post-receive` hook in that repo that runs this script, like so: | |
# | |
# unset GIT_DIR | |
# python /path/to/wikitweet.py | |
# | |
# Now, whenever I push to the repo, the script looks to see which files have |