How does one become a slacker? Are slackers born or made? These might not be questions great thinkers ponder (I wonder if Aristotle was a slacker), but they are interesting nonetheless.
While I haven't done a comprehensive study on this, I know how I became a slacker. It happened in third grade. My teacher, Mrs. Butler, was teaching us double-digit subtraction; take the one ten and make ten ones, etc. I was always great at math, so this stuff was a breeze (31 minus 17? EASY! Give me something hard to do). She gave us a math test, and it had one section with five questions that looked something like this:
1) 43 minus 24
____
I wasn't sure what that line meant, so I did the math in my head and put my answer on the line. Easy stuff. Well, she marked all of my answers incorrect. Apparently, I didn't read the instructions, which said to show your work. With those incorrect answers, my score was low enough to warrant being put in the remedial group. I was pissed (well, as pissed as a third grader can get). I wanted nothing more than to be with those kids I knew I was smarter than, working on those "enrichment" worksheets with the tough problems (345 minus 167! Also, multiplication!). And yet, I was stuck with the remedial group, having stuff I already knew explained to me.
So I tuned out. Not consciously, of course. As an eight-year old, I still wanted to appease my parents in everything. I continued to pull down good grades (not that elementary school is tough) and be a good kid. But I never really had to try hard again (until sophomore year of high shcool), and because I "knew" that trying hard wouldn't really get me anything, I didn't. I spent class time doodling (8th grade social studies), talking (honors English), sleeping (AP Chemistry), or not present (honors American History).
Yet I graduated with a 3.85 GPA. All I was subconsciously learning was to work the bare minimum to get by. (Fortunately, college was able to coax a lot out of me. Learning that I wasn't the smartest man alive helped me focus on work I didn't like.) Are all slackers created by nuture? Or does nature take a part? I don't know.
Stay tuned for the thrilling conclusion of Slacker Nation.
For Part 1 of Slacker Nation, click here.
Showing posts with label article. Show all posts
Showing posts with label article. Show all posts
Friday, April 13, 2007
Friday, April 6, 2007
Slacker Nation: Part 1; or, The Definition
When I was young, adults made a big deal about slackers. They would conjure up images of a guy with longish hair (only long because he doesn't care about cutting it) with baggy, dirty pants (why wash clothes? They'll just get dirty again) who does every task to the minimum (so he can get back to "slacking"). I was told that becoming this man, this slacker, was the worst possible outcome of my life. I was young and impressionable, so I believed this.
Flash forward to high school. I took mostly honors and AP classes, but many of them were not hard. My honors history class was one of these. The teacher was smart and good, but he believed in homework. I don't, so I didn't do it. I got A's on all the tests, essays, and projects, but zeroes on all the homework, resulting in a B in the class. I tried to do the homework one time. I looked at the front page of the packet. On top was a big map of North and South America. The first question was "Mark on the map the location of the Panama Canal." This was a junior year honors history class. I threw out the packet. Did this behavior make me a slacker? I could've gotten an A easily if I had done the homework. But to me doing this homework was a complete and utter waste of my time. I'd rather read history books (which I did, often). I was troubled by this for a time, but never troubled enough to change my ways.
And now, present day. If you've read some of the past posts here, you'll see that sometimes I'm just unmotivated to do things. However, I'll go to town on certain things, like the cell-phone negotiation and the EBay stuff. Why do I have no problem working on these things, yet getting myself to write the basis for my website is hard as hell? A few years ago, I found an interesting article online called the Slacker Manifesto (pdf). The author brings up a few interesting points, but this is the most important one: slackers work hard only on what interests them (as opposed to Type-A people who can work their ass off on anything). This theory direction contradicts the message sent by my parents when I was young. I can be a slacker and still be a productive member of society. Sweet.
Stand by for Part 2 of this series, yet to be subtitled, where I discuss something else about slackers.
Flash forward to high school. I took mostly honors and AP classes, but many of them were not hard. My honors history class was one of these. The teacher was smart and good, but he believed in homework. I don't, so I didn't do it. I got A's on all the tests, essays, and projects, but zeroes on all the homework, resulting in a B in the class. I tried to do the homework one time. I looked at the front page of the packet. On top was a big map of North and South America. The first question was "Mark on the map the location of the Panama Canal." This was a junior year honors history class. I threw out the packet. Did this behavior make me a slacker? I could've gotten an A easily if I had done the homework. But to me doing this homework was a complete and utter waste of my time. I'd rather read history books (which I did, often). I was troubled by this for a time, but never troubled enough to change my ways.
And now, present day. If you've read some of the past posts here, you'll see that sometimes I'm just unmotivated to do things. However, I'll go to town on certain things, like the cell-phone negotiation and the EBay stuff. Why do I have no problem working on these things, yet getting myself to write the basis for my website is hard as hell? A few years ago, I found an interesting article online called the Slacker Manifesto (pdf). The author brings up a few interesting points, but this is the most important one: slackers work hard only on what interests them (as opposed to Type-A people who can work their ass off on anything). This theory direction contradicts the message sent by my parents when I was young. I can be a slacker and still be a productive member of society. Sweet.
Stand by for Part 2 of this series, yet to be subtitled, where I discuss something else about slackers.
Tuesday, April 3, 2007
Single Tasking
"Single Tasking" is an idea I produced for myself one morning last week.
When I get to work in the morning, I typically check the New York Post online for new Yankees articles. I also check a few webcomics. Sometimes those sites will link to other sites I want to check out. I'll fire up Visual Studio and Query Analyzer, bounce between them and Opera, then open Firefox for my FF-specific stuff. As a result, I do a lot of things, but I'm not terribly efficient at them. Even when I say "Enough!" and close FF and Opera, I still have multiple work things going on at once.
So I decided to say "Here's the feature/bug/whatever I'm working on, work on it til it's finished." I have to fight myself hard to not think about other things or check email or whatever, but I'll get it done. Then I have to repeat the process. It's totally against my nature to do this for some things (like writing an SQL controller class for my .NET app); I've always found decent productivity while having a TV on tuned to a movie that just came on that I've seen before (more on this later). However, that approach doesn't work when working on code.
After producing this idea, I realized that I'm totally not the first to discover it. ThatVoodooYouDo covered an idea I've been trying to incorporate into my single tasking. Steve Pavlina (that crazy dude) covers an idea called "Timeboxing" (sort of the inspiration for this blog) which sorta ties in with this.
Nevertheless, I've found my highest level of productivity on code during single tasking. How about you?
When I get to work in the morning, I typically check the New York Post online for new Yankees articles. I also check a few webcomics. Sometimes those sites will link to other sites I want to check out. I'll fire up Visual Studio and Query Analyzer, bounce between them and Opera, then open Firefox for my FF-specific stuff. As a result, I do a lot of things, but I'm not terribly efficient at them. Even when I say "Enough!" and close FF and Opera, I still have multiple work things going on at once.
So I decided to say "Here's the feature/bug/whatever I'm working on, work on it til it's finished." I have to fight myself hard to not think about other things or check email or whatever, but I'll get it done. Then I have to repeat the process. It's totally against my nature to do this for some things (like writing an SQL controller class for my .NET app); I've always found decent productivity while having a TV on tuned to a movie that just came on that I've seen before (more on this later). However, that approach doesn't work when working on code.
After producing this idea, I realized that I'm totally not the first to discover it. ThatVoodooYouDo covered an idea I've been trying to incorporate into my single tasking. Steve Pavlina (that crazy dude) covers an idea called "Timeboxing" (sort of the inspiration for this blog) which sorta ties in with this.
Nevertheless, I've found my highest level of productivity on code during single tasking. How about you?
Subscribe to:
Posts (Atom)