» Read more
Jelly came to see simultaneously that all of life with others is games and that the rules of all the games are mostly lies. Someone told her once that a rule cannot be followed privately. It had the ring of truth, seemed a new dispensation, appeared a better rule (about rules). Yet it was certainly a lie, or fairly certainly. Or probably. Plausibly. But she also felt a sort of conviction that the rules she ascertained in her own thinking were really bounds marked by her own language. The instants in which she felt real joy were mostly moments in which she broke those, so to speak. And these could never be properly shared. If absolute truth lived in the perfect correspondence of words to the world, then freedom must dwell in lies, in transcendent fictions. So she came to make the contours of her experience conform not to the truth but to its dissolution. She imagined piling untruth upon untruth sky high, so, like the Tower of Babel, she might climb up and up and up upon them so as to mount, finally, an assault on heaven and on god. Ghost Songs in the Rafters, Book II
Articles by R.
Here are some guidelines I've come to believe useful in providing feedback on others' writing, through both my teaching and my own experience as a writer.
- Make a point of identifying things that you think work well or you found resonant. It's hard to take feedback as constructive if the comments give the impression that there's nothing good about the piece.
- Direct all judgements at the writing and not the writer. Couching critiques in terms that can be read as generalizations about the person rather than the piece is a good way to make said critiques personal, even hurtful. It also misses the point, distracts from the central task at hand, which is working on the text and not the personality or positionality of the author.
- Direct judgements at the piece as it is and not as if it ought to be something else entirely. There are times, of course, when a text strays topically from a prompt or given aim or breaks with a given genre. But most critiques of a piece of writing that come off as essentially saying, "You should have written something altogether different," are difficult to read as constructive and should be avoided if at all possible.
- Broad critiques of a writing effort such as, "You're trying to do too much," ought to be accompanied with a concrete suggestion as to how the perceived problem might be addressed. If you think a writer is trying to do too much, for example, make the effort to propose an alternative bracketing or scope. Otherwise, such comments can feel less than useful or, worse, dismissive.
- Avoid confusing the writer's project(s) with your own. If you find some argument or line of reasoning facile, for example, focus on ways to strengthen the elements in question rather than on your own objections rooted in content. It is one thing to say, "A respondent might claim Point X here is facile because of Reason Y, so it might make sense to give some additional consideration to the reasons you offer (or do not) for Point X." It is another to say, "Point X doesn't make any sense at all to me, as I prefer Point Z." Too much of the latter can feel to a writer as if the commentary is aimed at making their writing and thinking more like your own rather than helping them to effectively articulate their own ideas toward their own ends.
- Read your commentary on others' writing through at least once as if it is being applied to your own writing. Ask yourself if you would take it as constructive and helpful. Imagine, too, that the critique is coming from somebody you respect, somebody whose opinion matters to you. Would the comments read as meaningful? Encouraging? Hurtful? Useful? » Read more
I wrote the following little plugin to allow me to tell Pelican where I want article summaries to begin and end:» Read more
from pelican import signals from pelican.generators import ArticlesGenerator SIGIL = '<!-- summary -->' SANDWICH = '<!-- /summary -->' def runme(generators): for g in generators: if isinstance(g, ArticlesGenerator): for a in g.articles: sigil_start = a.content.find(SIGIL) if sigil_start > -1: sandwich = a.content.find(SANDWICH) if sandwich > -1 and sandwich > sigil_start: a._summary = a.content[sigil_start+len(SIGIL):sandwich] else: a._summary = a.content[0:sigil_start] def register(): signals.all_generators_finalized.connect(runme)
In 1992 Jorge Durand, a social anthropologist and geographer at Mexico’s University of Guadalajara, coordinated a series of in-depth interviews with Mexican migrants who had experienced the hard journey to the United States. One of these migrants, a man named Aurelio, crossed the US border dozens of times, only …» Read more
I'm writing a Python command-line program to generate dot-density shapefiles from OGR-compatible datasources. I used to generate dot-density maps in one shot using a custom Python script and Cairo to render data and base layers. But my workflow …» Read more
Page 1 / 8 »