Six more days until Fae Eye is out! I saw the galleys today, I'm bursting with excitement.
Ok, that sounded incredibly corny to me, and I said it. Still, it's not untrue.
In other news, Crowbar Girl is now at 75,000 words. Added another 1980 words today, which looks to be about how many I'm doing a day when I really get into it. I'd do more, but I don't seem to really hit my stride until about an hour after the kids are in bed.
Anyone else out there a writer with kids? I'm curious.
Showing posts with label About Bob. Show all posts
Showing posts with label About Bob. Show all posts
Monday, July 26, 2010
Friday, July 23, 2010
Pessimism as a Coping Mechanism
I've been getting advice from PJ lately about social media, and one of her comments was that she knew I was going to be published soon, so she was pushing me to go out and make connections.
I realized just today why I hadn't. I've been 'on the cusp' of being published for around five years. Worse, I seem to have started there. I've never received a form rejection from a publisher, and over half of the non-form rejections had suggestions, edits, and encouragement tacked on. I've been told that those are Really Good Signs. Almost There signs. Things that tell you you've almost made it.
With that in mind, around five years ago I went out and did just what PJ is talking about. Lurked on writing and publishing sites, commented cogently when I could, built up an online presence, such as it was. Then... Nothing. For five years, over and over, the same kind of responses. Tried for an agent, got similar responses. 'Great work, but not what we're looking for.' 'Really, really cool and well written, but didn't quite grab us enough.'
After a while, I wrote off the 'cusp of being published' as wishful thinking. Note; I didn't stop writing or submitting. On the contrary, I actively looked for venues and honed my craft. I improved; I can see problems with my earlier stories, I can improve them now. But all my writing time was taken away from work time, kid time, wife time and sleeping time. I wound up dropping the net-presence in favor of writing more, writing better, writing faster.
The whole time, five years, there was NO progress. I kept getting the same type of rejections. Part of the problem, I'm convinced, was the lack of rote rejections prior; if you're aiming at 10, and your first effort is '1', the next is '2', and the next is '3', you become convinced that you can hit '10' if you put in enough work. I started at '9' and saw a vague wobble between '9' and '8' (with one notable dip to '7') for five years. Very discouraging. By this past summer, I had hit a state where the only way I could cope was to tell myself that 'of course I'll get a rejection, but at least the feedback will be helpful'.
Then? Decadent. BOOM, published. It... Stunned me. A lot.
So, yeah. I'm still a little stunned. But I'm heeding PJ's advice as quick as I can.
I realized just today why I hadn't. I've been 'on the cusp' of being published for around five years. Worse, I seem to have started there. I've never received a form rejection from a publisher, and over half of the non-form rejections had suggestions, edits, and encouragement tacked on. I've been told that those are Really Good Signs. Almost There signs. Things that tell you you've almost made it.
With that in mind, around five years ago I went out and did just what PJ is talking about. Lurked on writing and publishing sites, commented cogently when I could, built up an online presence, such as it was. Then... Nothing. For five years, over and over, the same kind of responses. Tried for an agent, got similar responses. 'Great work, but not what we're looking for.' 'Really, really cool and well written, but didn't quite grab us enough.'
After a while, I wrote off the 'cusp of being published' as wishful thinking. Note; I didn't stop writing or submitting. On the contrary, I actively looked for venues and honed my craft. I improved; I can see problems with my earlier stories, I can improve them now. But all my writing time was taken away from work time, kid time, wife time and sleeping time. I wound up dropping the net-presence in favor of writing more, writing better, writing faster.
The whole time, five years, there was NO progress. I kept getting the same type of rejections. Part of the problem, I'm convinced, was the lack of rote rejections prior; if you're aiming at 10, and your first effort is '1', the next is '2', and the next is '3', you become convinced that you can hit '10' if you put in enough work. I started at '9' and saw a vague wobble between '9' and '8' (with one notable dip to '7') for five years. Very discouraging. By this past summer, I had hit a state where the only way I could cope was to tell myself that 'of course I'll get a rejection, but at least the feedback will be helpful'.
Then? Decadent. BOOM, published. It... Stunned me. A lot.
So, yeah. I'm still a little stunned. But I'm heeding PJ's advice as quick as I can.
Saturday, November 21, 2009
I write this, even knowing there's a slight chance he'll read it...
OK, for those of you who are unaware of why November's posting has been more anemic than usual, it's because November is NaNoWriMo. Almost all of my wordingyness is dedicated to that; I go elsewhere only when my hands hurt, or I'm so tired my brain won't fire right to type. Since essaying takes more than knee jerk reactions, I can't really do any in November. Well, unless someone asks really, really nicely.
However, as noted with my last post, sometimes something just HAS to come out.
Now, on top of NaNo, which makes sure I put out at least 50,000 new words once a year (inertia usually gets me another 50K before I slow down and start editing) I'm at Philcon due to the kindness of a friend. It's a very good opportunity to meet people in the publishing industry, which is a Good Thing for a variety of reasons I'll not go into here. Because a geek button got pushed. Which is odd, because I don't HAVE many, y'see.
So, I go to a panel for sci-fi newbies, because there are huge swaths of 'classic, everyone must read this' sci fi and fantasy that I've never read. My entry point into sci fi, y'see, was not magazines with stories, nor novels, nor even the considered-slightly-different TV shows of Star Trek and Doctor Who. Most authors who are my age write one of those as their entry point. My entry point into Sci Fi, y'see, was slightly different. It had Russian music and Japanese Animation and a really bad English script. Yes, I'm talking about Star Blazers. I watched it while reading Tolkien, back when my sister was still a baby and Carter was still president.
So it's not real surprising that my writing reminds some of Kurosawa does Anime. However, this is all a massive digression, because my geek out is embarrassing me. Ok, last person on the panel is Michael Swanwick. Now, I link to that list for an important reason, which I shall get to when my geeking out level drops a bit. Mr. Swanwick mentioned one of his books during the panel, but I'd not read the one mentioned. When I saw him, I remembered him from the "Where I Write" project.
Well, I talked with him a bit after the panel, mostly about being from an odd sci-fi entry point. He thought that was kind of neat, and a bit later during a "meet the pros" mixer I met Kyle Cassidy, who is the guy doing Where I Write, which is cool. Mr. Swanwick was there again, and had some very encouraging things to say about the feedback I've gotten from publishers and agents, as well as giving me some satori-moment-inducing advice on writing and pruning.
OK, I'm stalling again. In my defense, and since he said he has the same problem, perhaps he'll understand. I don't remember names. I took a notebook to Philcon with me specifically to write down names in, because I don't rememeber them.
The whole point here - I recall exactly ONE book I've read cover to cover twice in a row. I'll get to that in a bit. I know, I'm stalling. I'm Syndrome at the moment, ok?
Anyhow, I get home, sit down to write a little, and decide "y'know, I ought go look him up; perhaps I've read something of his and don't remember. He sounded very cool, perhaps I ought try out his writing; I'll certainly be trying the books he recommended." I go to his website. I go to his bibliography. Bones of the Earth, new one he mentioned during the panel, haven't read. Griffin's Egg, I've heard of, but don't think I read. In The Drift, don't remember the title, and book titles I remember (go figure, I forget my own name at times, but I can remember titles).
Iron Dragon's Daughter.
HOLY. There are authors I would like to and think I can someday match style-and-quality wise. Adams, Ringo, Jordan. There are authors I've been compared to, who I like, so I don't mind if I wind up more like them when I hone my skill to publishable levels (Cherryh). But Iron Dragon's Daughter is just way beyond anything I could write. I can't write that well. I just... I don't think I can. I mean, in part it's the prose, which is beautiful while still flowing quickly, but in part it's the story. When I try to do '10 words or less' on Iron Dragon's Daughter my brain just kinda short circuits. Um... OK, I just tried, and I can't name all the major components of the story in 10 words, and it's ALL 'surprising yet inevitable'.
And I got advice from him. And he gave me encouragement.
Definite Syndrome moment. "I'm still geekin' out about it!"
However, as noted with my last post, sometimes something just HAS to come out.
Now, on top of NaNo, which makes sure I put out at least 50,000 new words once a year (inertia usually gets me another 50K before I slow down and start editing) I'm at Philcon due to the kindness of a friend. It's a very good opportunity to meet people in the publishing industry, which is a Good Thing for a variety of reasons I'll not go into here. Because a geek button got pushed. Which is odd, because I don't HAVE many, y'see.
So, I go to a panel for sci-fi newbies, because there are huge swaths of 'classic, everyone must read this' sci fi and fantasy that I've never read. My entry point into sci fi, y'see, was not magazines with stories, nor novels, nor even the considered-slightly-different TV shows of Star Trek and Doctor Who. Most authors who are my age write one of those as their entry point. My entry point into Sci Fi, y'see, was slightly different. It had Russian music and Japanese Animation and a really bad English script. Yes, I'm talking about Star Blazers. I watched it while reading Tolkien, back when my sister was still a baby and Carter was still president.
So it's not real surprising that my writing reminds some of Kurosawa does Anime. However, this is all a massive digression, because my geek out is embarrassing me. Ok, last person on the panel is Michael Swanwick. Now, I link to that list for an important reason, which I shall get to when my geeking out level drops a bit. Mr. Swanwick mentioned one of his books during the panel, but I'd not read the one mentioned. When I saw him, I remembered him from the "Where I Write" project.
Well, I talked with him a bit after the panel, mostly about being from an odd sci-fi entry point. He thought that was kind of neat, and a bit later during a "meet the pros" mixer I met Kyle Cassidy, who is the guy doing Where I Write, which is cool. Mr. Swanwick was there again, and had some very encouraging things to say about the feedback I've gotten from publishers and agents, as well as giving me some satori-moment-inducing advice on writing and pruning.
OK, I'm stalling again. In my defense, and since he said he has the same problem, perhaps he'll understand. I don't remember names. I took a notebook to Philcon with me specifically to write down names in, because I don't rememeber them.
The whole point here - I recall exactly ONE book I've read cover to cover twice in a row. I'll get to that in a bit. I know, I'm stalling. I'm Syndrome at the moment, ok?
Anyhow, I get home, sit down to write a little, and decide "y'know, I ought go look him up; perhaps I've read something of his and don't remember. He sounded very cool, perhaps I ought try out his writing; I'll certainly be trying the books he recommended." I go to his website. I go to his bibliography. Bones of the Earth, new one he mentioned during the panel, haven't read. Griffin's Egg, I've heard of, but don't think I read. In The Drift, don't remember the title, and book titles I remember (go figure, I forget my own name at times, but I can remember titles).
Iron Dragon's Daughter.
HOLY
And I got advice from him. And he gave me encouragement.
Definite Syndrome moment. "I'm still geekin' out about it!"
Wednesday, August 26, 2009
How my mind works...
I'm perverse.
Now, you may all realize this. The folks following my blog probably do. If anyone ever winds up coming here who doesn't know me all that well, they may not get the point, so I'll have to spell it out. For those of you who were already aware, my apologies, I'll at least try to keep it entertaining.
When I say perverse, I mean perverse, not perverted. Not saying the latter is a bad thing, or even that I'm not, but that's not the point of this here diatribe. When I say I'm perverse, I mean that my interest in doing something is inversely proportional to the difficulty. If someone says 'come on, this will be fun, it's easy', I have no real interest in whatever activity they're endorsing, other than a possible basic interest in the scenery or terrain. If someone says 'don't even try that, it's impossible', my interest is peaked.
Now, there are some caveats. While I'm mildly attracted to gambling, I'm not really pulled to things like keno or Powerball (although I'll play the latter if the EV is close to positive). My definition of 'difficult' is not based on artificially generated odds. When I think 'difficult', I'm thinking about something that requires a great deal of skill, endurance, or personal effort to succeed. Marathons intrigue me. Games of skill will forever hold my interest. One of the attractions of writing is that while it's easy to do, it's hard to do right. Anyone can type words (or at least semi-coherent letter groupings) on a page; stringing words together so a reader is intoxicated and enlightened is hard. Doing so on a regular basis is an ongoing challenge that I can't walk away from.
I even know where it comes from, after a fashion. The root has to do with the juxtaposition of being a very bright and literal child and having parents given to particularly bad metaphor and hyperbole.
At any rate, what spawned this whole commentary lies here. Specifically the entry for the 18th, wherein Patrick reports that even the best of handshakes must fall far short of passionate.
Thanks, Patrick. Now I've got an unquenchable desire to write a passionate handshake. And I don't even have a story appropriate for such a thing.
Now, you may all realize this. The folks following my blog probably do. If anyone ever winds up coming here who doesn't know me all that well, they may not get the point, so I'll have to spell it out. For those of you who were already aware, my apologies, I'll at least try to keep it entertaining.
When I say perverse, I mean perverse, not perverted. Not saying the latter is a bad thing, or even that I'm not, but that's not the point of this here diatribe. When I say I'm perverse, I mean that my interest in doing something is inversely proportional to the difficulty. If someone says 'come on, this will be fun, it's easy', I have no real interest in whatever activity they're endorsing, other than a possible basic interest in the scenery or terrain. If someone says 'don't even try that, it's impossible', my interest is peaked.
Now, there are some caveats. While I'm mildly attracted to gambling, I'm not really pulled to things like keno or Powerball (although I'll play the latter if the EV is close to positive). My definition of 'difficult' is not based on artificially generated odds. When I think 'difficult', I'm thinking about something that requires a great deal of skill, endurance, or personal effort to succeed. Marathons intrigue me. Games of skill will forever hold my interest. One of the attractions of writing is that while it's easy to do, it's hard to do right. Anyone can type words (or at least semi-coherent letter groupings) on a page; stringing words together so a reader is intoxicated and enlightened is hard. Doing so on a regular basis is an ongoing challenge that I can't walk away from.
I even know where it comes from, after a fashion. The root has to do with the juxtaposition of being a very bright and literal child and having parents given to particularly bad metaphor and hyperbole.
At any rate, what spawned this whole commentary lies here. Specifically the entry for the 18th, wherein Patrick reports that even the best of handshakes must fall far short of passionate.
Thanks, Patrick. Now I've got an unquenchable desire to write a passionate handshake. And I don't even have a story appropriate for such a thing.
Wednesday, July 15, 2009
Regarding that last...
Specifically the part about enjoying or not enjoying reading.
I've often compared reading to eating. Some books taste good, but are essentially empty calories. Some books are good for you, but taste awful. Some books are the equivalent of a bag of chips; before you know it, you've eaten the whole thing. Others are like good toffee; difficult to eat too much of, because they're crunchy or chewy. Not only that, but every author has a different flavor, even two authors that are writing in what is ostensibly the same genre or subgenre, no matter how restrictive.
There are writers who write things that are good for you, tasty, and quick to read (does my adoration for Pratchett have an upper limit?). There are writers who write pure tasty treats with little redeeming value, or even with significant guilty pleasure factor (Justina Robson and John Ringo, I'm looking at you). There are the producers of filling, tasty food that lasts for several meals (Cherryh's Foreigner comes to mind). Then there are folks who write stuff that is good for you, and really ought to taste good, but is just so hard to gnaw through that it winds up being just not-quite-tasty enough to enjoy (*cough* Brin *cough*).
All that leads to two points I'm pondering now. The first; my recent worries were mostly based on too much not-quite-tasty in close succession. Two doses of candy, even knowing it's candy, still taste sweet. The second; juxtaposing my mental parallel between reading and eating with my mental parallel between writing and sex might explain things, not least of which why I married Yomiko Readman...
On that note, I'm fleeing before she catches me.
I've often compared reading to eating. Some books taste good, but are essentially empty calories. Some books are good for you, but taste awful. Some books are the equivalent of a bag of chips; before you know it, you've eaten the whole thing. Others are like good toffee; difficult to eat too much of, because they're crunchy or chewy. Not only that, but every author has a different flavor, even two authors that are writing in what is ostensibly the same genre or subgenre, no matter how restrictive.
There are writers who write things that are good for you, tasty, and quick to read (does my adoration for Pratchett have an upper limit?). There are writers who write pure tasty treats with little redeeming value, or even with significant guilty pleasure factor (Justina Robson and John Ringo, I'm looking at you). There are the producers of filling, tasty food that lasts for several meals (Cherryh's Foreigner comes to mind). Then there are folks who write stuff that is good for you, and really ought to taste good, but is just so hard to gnaw through that it winds up being just not-quite-tasty enough to enjoy (*cough* Brin *cough*).
All that leads to two points I'm pondering now. The first; my recent worries were mostly based on too much not-quite-tasty in close succession. Two doses of candy, even knowing it's candy, still taste sweet. The second; juxtaposing my mental parallel between reading and eating with my mental parallel between writing and sex might explain things, not least of which why I married Yomiko Readman...
On that note, I'm fleeing before she catches me.
Saturday, June 20, 2009
Reading and Writing (with a nod to Arithmatic)
First the Arithmetic nod; does anyone know a good reference for writing textbooks or reference books? A mathematician asked me to co-author. Meaning he wants to do the math, and wants me to do everything else from the non-math content to finding a publisher. Since most of what I've read on non-fiction indicates platform is king and god, and the mathematician has multiple (New Jersey large) school districts salivating over the idea of using the hypothetical book, the platform is solid enough I'm willing to give it a go IF I can find a good reference for writing reference.
That said, I've been having a problem reading lately. Formerly, the storyteller in me would consistently be telling more stories based on what I read. Sometimes those stories were fan-fic-esque, other times they were just inspired by the original. At any rate, I enjoyed the story as written, then riffed off of it.
Lately, however, I've been noticing a different pattern in myself. As I read, I'm actively noticing writing techniques. Foreshadowed twists are no longer surprising. Deus-ex-machina were never my favorite, but now I look on them as completely unsatisfying. Flat prose is no longer compensated for by originality, character or plot. Flat characters annoy me more than they used to. Lack of plot can still be excused on a first read, but I don't reread or recommend plotless books. Excessive political or other viewpoint evangelism is more annoying than it ever was.
I worry that I'm becoming a snob. More than that, I worry that what used to be one of my favorite hobbies is now rapidly becoming more a chore than a relief and release. I'm also worried that the few authors I could count on for a solid book with all the things I'm looking for and none of the things I'm avoiding are dead, dying, or succumbing to age.
Still and all, I enjoyed Vorpal Blade, and I'm generally enjoying Earth. I just noticed the flaws in each more than I would have five years ago. Or did I just notice myself noticing?
Meh. Either way, I'm off to write a bit, followed by going off to some conference with the aforementioned mathematician.
That said, I've been having a problem reading lately. Formerly, the storyteller in me would consistently be telling more stories based on what I read. Sometimes those stories were fan-fic-esque, other times they were just inspired by the original. At any rate, I enjoyed the story as written, then riffed off of it.
Lately, however, I've been noticing a different pattern in myself. As I read, I'm actively noticing writing techniques. Foreshadowed twists are no longer surprising. Deus-ex-machina were never my favorite, but now I look on them as completely unsatisfying. Flat prose is no longer compensated for by originality, character or plot. Flat characters annoy me more than they used to. Lack of plot can still be excused on a first read, but I don't reread or recommend plotless books. Excessive political or other viewpoint evangelism is more annoying than it ever was.
I worry that I'm becoming a snob. More than that, I worry that what used to be one of my favorite hobbies is now rapidly becoming more a chore than a relief and release. I'm also worried that the few authors I could count on for a solid book with all the things I'm looking for and none of the things I'm avoiding are dead, dying, or succumbing to age.
Still and all, I enjoyed Vorpal Blade, and I'm generally enjoying Earth. I just noticed the flaws in each more than I would have five years ago. Or did I just notice myself noticing?
Meh. Either way, I'm off to write a bit, followed by going off to some conference with the aforementioned mathematician.
Sunday, May 17, 2009
Apes & Angels
I'm sure many of you have heard the Pratchett quote which reads something like 'Man is the place where the falling angel meets the rising ape'. Quite a few people I know are enamored of the image. Most of them are religious sorts, which in and of itself is a touch ironic, given Pratchett. Most of those focus on the image of themselves being analagous to the falling angel. Divine, tragic, in some way better than the poor fleshly creatures they are surrounded by.
The relevant part they seem to miss? The ape is the one who is headed the right direction.
The relevant part they seem to miss? The ape is the one who is headed the right direction.
Tuesday, May 12, 2009
Teaching, Lies and Patience
As some of you may know, I'm applying for a teaching certificate. Some of you who didn't know are probably saying 'wait, isn't that putting students into Bob's Head on a regular basis?'. Probably, but Only a very specialized part of it that deals with Biology. Ok, that might not be better. Biological Science is one of those fields that squicks people. Still, High School Biology only leaves so much room for squick. In point of fact, my own preference is for less squick; molecular biology rather than zoology. Anyhow, I still remember enough to ace the Praxis general science test and score over 90% on the biology test, so I know the material. Now it's just a question of background checks and such. With the level of checking done in the past, I'm not too worried about that bit.
There are advantages and disadvantages to teaching as a career. One disadvantage is a comparitively low pay rate. One advantage is that pay rate increases reliably once you've achieved tenure. Another advantage is benefits. I was recently talking to my dad, who is due to retire from teaching in another half dozen years or so. I asked him how much he pays for health insurance. His response of 'Pay? You mean deductible?' floored me. I've been used to having half a grand or more docked from my pay each month to pay medical. Actually, if I add that money back onto the pot, it makes up about half the difference from my old job and a teacher's starting salary. Retirement benefits are another perk. The only 'retirement' fund available to me previously was a 401K. Employer-paid pension funds don't happen often for IT folks, and they don't happen at all for IT consultants. My dad's retirement is going to be better than what I was making at my last job, by quite a good margin. Don't get me wrong; I don't begrudge him that, but I've been employed for roughly 18 of the last 20 years and not once have I had an employer do more than 'matching funds, vested when you've been with the company longer than we keep employees'.
So yeah. Teaching looks better and better from an economics standpoint. Then there's the work itself. I hear a lot of teachers complaining about a lack of respect, but I can't think of a single person I'd be embarrassed to tell what I did for a living as a teacher. More importantly, I don't think there's a single person I'd need to tell what teaching is. You just say 'I'm a teacher', and they reply 'what do you teach', and you respond with a subject or grade level for elementary teachers. I've had hour long discussions with people about what a Project Manager does, and there are people who still think I wrote code for a living. Then again, that's a popular misconception: if you are in IT, anywhere in IT, you write code. The popular belief is that you also know how to solder, can't spell, live with your parents and are bereft of meaningful social skills.
OK, each of those is accurate in some cases. Some IT guys write code, although they're mostly in departments that have broken themselves off from 'IT' now. Some IT guys can repair electronics, although most of them realize that it's cheaper, more reliable and faster to swap out the broken part for a new one. More than one IT person I know of can't spell beyond a phonetic level, but that's by no means a universal trait. I know of a few IT folks who lived with parents until later in life, but that was mostly a cost-saving measure, not a social one. Finally, I've known IT guys with no social skills, but I've known many other professionals with no socials skills to speak of either. Actually a final note is that I've known nearly as many women in IT as I've known men, so they're not all 'guys', except in a metaphoric sense.
That actually leads into my next point, which relates to teaching. Terry Pratchett nailed it in The Science of Discworld, where he referred to it as 'lies to X', the most repeated version being 'lies to children' which are generally imparted by teachers attempting to get students to understand something at a basic level. People tell lies for a variety of reasons, but a very common reason is when they can't understand something and need a simplified version to grasp. In the case of IT guys, the original IT guys were a iconoclastic bunch, with the only unifying characteristic being that iconoclasty and a rather different worldview, one in which things worked if you follow rules. Minus the iconoclasty, that's rather the same as clockmakers and engineers, so the stereotype of the IT guy was born as a 'particularly weird engineer'.
Similar things happen with the sciences at a high school level. I realized once I was in college that High School Biology covered biology up until, say, the mid 1800's, with vague allusions to the 1900's. Bio I & II in college covered that same ground, but actually pulled in some information from the 50's. It wasn't until I hit junior & senior level coursework that I started learning things from my own lifetime. Quite often, they contradicted things that I had learned in High School, just as later discoveries contradicted things that were believed earlier. In some cases it was clarification rather than contradiction, but there were some contradictions. There were some huge ones in my physics courses, as I recall, and even some in my Chemistry courses, although I couldn't be sure; my High School Chemistry was too involved with making things go 'boom'. So there exists the very real possibility that I'll need to simplify things to the point of being incorrect in order to simplify them enough for students to understand. I hope not, but we shall see.
Either way, Teaching will be a different kind of career for me. My previous career, IT, is all about speed. Make it work faster, get it done faster. Cheaper is often a goal too, but faster is the name of the game, especially as a consulting IT person. For those in need of clarification, a 'consulting' IT person is one who doesn't work for the company he's supporting. He works for a dedicated IT company, which lives or dies based on the contracts it gets. Teaching isn't.
About speed, that is. Short of reverse engineering the brain and uploading memories, there's no way to speed up the learning process. So I'll be forced to slow down, from a tactical perspective. From a strategic one, too. Ask anyone in IT, and they'll have a plan for early retirement, if they plan for it at all. It may not be a good plan, but they've got one. Teaching, on the other hand, is a long term thing. It's a different way of thinking, one more suited to patience and contemplation. Those of you who have read this far might guess that I'm all about contemplation. Plus, there are summers off. To a guy who once had multiple employers seriously care that people were 'unproductive' during the 30 to 90 second periods when we were waiting for the phone to ring, the idea of two to three months of scheduled downtime is downright odd.
So yeah. I'm hoping that CE comes through soon, because all in all, teaching looks like a place I'd like to be.
There are advantages and disadvantages to teaching as a career. One disadvantage is a comparitively low pay rate. One advantage is that pay rate increases reliably once you've achieved tenure. Another advantage is benefits. I was recently talking to my dad, who is due to retire from teaching in another half dozen years or so. I asked him how much he pays for health insurance. His response of 'Pay? You mean deductible?' floored me. I've been used to having half a grand or more docked from my pay each month to pay medical. Actually, if I add that money back onto the pot, it makes up about half the difference from my old job and a teacher's starting salary. Retirement benefits are another perk. The only 'retirement' fund available to me previously was a 401K. Employer-paid pension funds don't happen often for IT folks, and they don't happen at all for IT consultants. My dad's retirement is going to be better than what I was making at my last job, by quite a good margin. Don't get me wrong; I don't begrudge him that, but I've been employed for roughly 18 of the last 20 years and not once have I had an employer do more than 'matching funds, vested when you've been with the company longer than we keep employees'.
So yeah. Teaching looks better and better from an economics standpoint. Then there's the work itself. I hear a lot of teachers complaining about a lack of respect, but I can't think of a single person I'd be embarrassed to tell what I did for a living as a teacher. More importantly, I don't think there's a single person I'd need to tell what teaching is. You just say 'I'm a teacher', and they reply 'what do you teach', and you respond with a subject or grade level for elementary teachers. I've had hour long discussions with people about what a Project Manager does, and there are people who still think I wrote code for a living. Then again, that's a popular misconception: if you are in IT, anywhere in IT, you write code. The popular belief is that you also know how to solder, can't spell, live with your parents and are bereft of meaningful social skills.
OK, each of those is accurate in some cases. Some IT guys write code, although they're mostly in departments that have broken themselves off from 'IT' now. Some IT guys can repair electronics, although most of them realize that it's cheaper, more reliable and faster to swap out the broken part for a new one. More than one IT person I know of can't spell beyond a phonetic level, but that's by no means a universal trait. I know of a few IT folks who lived with parents until later in life, but that was mostly a cost-saving measure, not a social one. Finally, I've known IT guys with no social skills, but I've known many other professionals with no socials skills to speak of either. Actually a final note is that I've known nearly as many women in IT as I've known men, so they're not all 'guys', except in a metaphoric sense.
That actually leads into my next point, which relates to teaching. Terry Pratchett nailed it in The Science of Discworld, where he referred to it as 'lies to X', the most repeated version being 'lies to children' which are generally imparted by teachers attempting to get students to understand something at a basic level. People tell lies for a variety of reasons, but a very common reason is when they can't understand something and need a simplified version to grasp. In the case of IT guys, the original IT guys were a iconoclastic bunch, with the only unifying characteristic being that iconoclasty and a rather different worldview, one in which things worked if you follow rules. Minus the iconoclasty, that's rather the same as clockmakers and engineers, so the stereotype of the IT guy was born as a 'particularly weird engineer'.
Similar things happen with the sciences at a high school level. I realized once I was in college that High School Biology covered biology up until, say, the mid 1800's, with vague allusions to the 1900's. Bio I & II in college covered that same ground, but actually pulled in some information from the 50's. It wasn't until I hit junior & senior level coursework that I started learning things from my own lifetime. Quite often, they contradicted things that I had learned in High School, just as later discoveries contradicted things that were believed earlier. In some cases it was clarification rather than contradiction, but there were some contradictions. There were some huge ones in my physics courses, as I recall, and even some in my Chemistry courses, although I couldn't be sure; my High School Chemistry was too involved with making things go 'boom'. So there exists the very real possibility that I'll need to simplify things to the point of being incorrect in order to simplify them enough for students to understand. I hope not, but we shall see.
Either way, Teaching will be a different kind of career for me. My previous career, IT, is all about speed. Make it work faster, get it done faster. Cheaper is often a goal too, but faster is the name of the game, especially as a consulting IT person. For those in need of clarification, a 'consulting' IT person is one who doesn't work for the company he's supporting. He works for a dedicated IT company, which lives or dies based on the contracts it gets. Teaching isn't.
About speed, that is. Short of reverse engineering the brain and uploading memories, there's no way to speed up the learning process. So I'll be forced to slow down, from a tactical perspective. From a strategic one, too. Ask anyone in IT, and they'll have a plan for early retirement, if they plan for it at all. It may not be a good plan, but they've got one. Teaching, on the other hand, is a long term thing. It's a different way of thinking, one more suited to patience and contemplation. Those of you who have read this far might guess that I'm all about contemplation. Plus, there are summers off. To a guy who once had multiple employers seriously care that people were 'unproductive' during the 30 to 90 second periods when we were waiting for the phone to ring, the idea of two to three months of scheduled downtime is downright odd.
So yeah. I'm hoping that CE comes through soon, because all in all, teaching looks like a place I'd like to be.
Saturday, April 25, 2009
Is this thing on?
Hello out there in the wide world. For those who used to follow me on LJ, welcome back, I'll try to post with more frequency here. For those of you just tuning in here at the new location, expect an eclectic mix of posts related to writing, philosophy, politics, pop culture, and whatever crosses my mind at the moment. I'll try to keep it interesting.
For any of you who might be of a literary bent, I may post snippets of my fiction; either parts of my currently completed works or portions of my WIP. The latter is likely an attempt to get feedback on some portion I feel needs work, the former is a blatant ploy to garner an audience of raving fans who would then entice some nice agent or publisher to contact me.
For any of you who might be of a literary bent, I may post snippets of my fiction; either parts of my currently completed works or portions of my WIP. The latter is likely an attempt to get feedback on some portion I feel needs work, the former is a blatant ploy to garner an audience of raving fans who would then entice some nice agent or publisher to contact me.
Subscribe to:
Posts (Atom)