Showing posts with label hard. Show all posts
Showing posts with label hard. Show all posts

Wednesday, June 9, 2010

What time is it?

I have a life-long animosity for alarm clocks.

This first became apparent when I was in first grade, and had to be up in time to get to school by Eight AM (I had been in an afternoon kindergarten class, blissfully free until 12:30.) I ignored my alarm clock completely, making my mother come time and time again to call, wheedle, and threaten me out of bed. When words alone did not suffice, she moved on to diplomacy by other means: tickling, dragging, repeated threats of ice cubes (I cannot recall whether these threats ever became reality, but from the force they carried I think they must have, at least once.)

Things did not improve with middle school.

Saturday, February 13, 2010

Why suffering?

I’ve been reading the Book of Job, looking for an answer.
This question has been asked by person after person, year after year, struck by fire or flood or disease or war. Why, why, why?
Usually, the question is addressed to God. If humans knew, why would they ask?
And yet we also offer our own answers, and sometimes accept them. Two of the standard answers go like this:
1) It’s our fault. We’ve done something wrong, or our ancestors did something wrong, and we’re being punished by God. This is the view expressed by Job’s friends, who tell him that he’ll suffer no more if he only repents of a wrong he doesn’t know he’s done.
2) It’s God’s fault. Usually for not being there. After all, if there were an all-powerful, good God, he would prevent suffering, right? Those who accept this answer see suffering either as proof of God’s non-existence, or as proof against God’s benevolence. Job’s wife expresses this approach when she tells him to curse God and die, since his suffering is, in her eyes, a demonstration of God’s injustice.

The marvelous thing about the book of Job is that it rejects both these answers. Job is not at fault– he is the perfect and the upright man. Nor is God at fault.

Wednesday, February 3, 2010

How am I supposed to answer that?

I'm taking a survey on undergraduate engagement. It's a pretty well-put together and thorough survey, designed to see whether college students are actually doing all those things that are reported to make college experience so great. It's useful information for my university, and for educators in general, but it's also a useful self-check for me, to see how I've been doing.

How often have I connected ideas from my different courses?
How often have I talked with my professors outside of class?
How often have I worked harder than I thought I could in order to meet a professor's expectations?

Most of these question are pretty easy to answer-- I either have or I haven't (although there is a four step scale: never, sometimes, often and very often.)

Here's the question that made me stop, open a new tab, and start writing this post:

How often have you "had serious conversations with students of a different race or ethnicity than your own?"

Tuesday, January 26, 2010

What If none of the answers is right?

A while back, I had to take a grammar tutorial, which also included a grammar quiz. The rules were fairly simple: just choose the sentence with no mistakes. I was doing great until I got to a question where this was the only grammatically proper answer:

"Because it is a Catholic country, its government is a democracy modified by authoritarianism."

I don't know about you, but I have some trouble saying that there isn't a problem with that sentence. It may be grammatically perfect, but there's definitely something fishy going on there...

Thursday, December 24, 2009

Why Procrastinate?

I asked an uncle of mine how to learn to get things done. He said:

"Why? The best talks I've ever had ideas for I've never given. Some of the best books I own I've never read. The only problem I've ever found with not doing anything is I never know when I'm finished...."

Wednesday, December 23, 2009

Why is writing so hard?

I just asked my Dad that question, and he had three theories, in quick succession.

1) Writing is hard because our fingers cramp up.

2) Writing is hard because we have too many words; if we wrote everything in binary, we'd only have to use 0's and 1's.

3) Writing isn't hard anymore, but we still think it is because we have the evolutionary memory of how hard it was for our ancestors who had to carve letters into stone: writing is easy, but we recoil from it out of instinct.

After we debated these responses, he settled on a more satisfactory, but less colorful answer: writing is hard because any type of writing requires careful thought in order to provide the meaning provided in conversation by intonation, hand gestures, etc. Good writing is especially hard because it requires even more careful thought, in order to be logically sound, to take other points of view into consideration, etc. Also, writing is hard because anything worth doing is hard. (My father points out that breathing is worth doing, but is not hard. So this last statement cannot in fact be taken as a universal.)