I had my pre-registration advising meeting today (hang on, I will connect these paragraphs), which was good but a little frustrating for reasons at the moment irrelevant. However, the point is that next semester I have to take a course entitled Seminar in Composition, wherein, if you can't tell from the title, we get to learn how to write a paper, and have to write one every week.
Going back to Phil and this article, which you should go read (especially if you're procrastinating or a programmer. Or a procrastinating programmer). Now, I am not a programmer, and the inner workings of most things computer related are to me a mystery I am content to leave alone. But this really jumped out at me. The writer here is talking about writing specs, which as far as I can tell from this article is something like a roadmap/plan about what you're going to code in your programming project, and why you should write one. He then goes on to say,
So why don't people write specs? It's not to save time, because it doesn't, and I think most coders recognize this ... I think it's because so many people don't like to write. Staring at a blank screen is horribly frustrating. Personally, I overcame my fear of writing by taking a class in college that required a 3-5 page essay once a week. Writing is a muscle. The more you write, the more you'll be able to write.
Which brings me back around to Seminar in Composition. And here, people, from the mouth of a programmer, of all types of people, is the reason why we have to take this class. Turns out it has all sorts of usefulness and real life applications, argh argh argh.
I really wanted to complain about it, too.
* I am studying for this test! I have a six page study guide that is mostly memorized already to prove it! I'm just taking a break. So nobody get mad at me. I will PWN this test with awesome strength.