My Life, the Universe, and Everything

[lydamorehouse]

For the month of February I'm going to have the weirdest schedule.  Mason has Inter-Session at his school.  Inter-session is Crossroad's answer to not having a traditional summer vacation.  Mason has three weeks off from school now, will again in May, and then have the month of August off.  There are school programs if people have work issues, but we've always found a lot of value in the whole idea of taking time off to do the nothing Shawn and I remember fondly doing a lot of in the three months of summer vacation.  Other Crossroad's families take vacations.  For instance one of Mason's good friends is flying to New Zealand right now.

As you know, I've started a new job. I didn't feel entirely comfortable telling my new employer that I'm planning on just blowing off work for an entire three weeks (though I will feel *just fine* about it come May, because then I will have worked there a lot longer.)  The point is, I've agreed to work a bunch of evening hours.  Tonight I'll be at Roseville from 5 to 9.  I'll be at Maplewood tomorrow night, and then back to Roseville Thursday night (which I belatedly remembered is supposed to be Wyrdsmiths.)

Working nights is weird.  I'm sure I'll have other observations about it, once I've done it a few weeks in a row, but I think I sort of kind of like it.  What I like about it right now is that I feel like I have the day off, even though I don't.  For instance, I have the whole day to get stuff done. I'm sure I'll be super productive and do ALL THE THINGS.


(Miss Ball's opinion about how well that'll probably work out.)

But today is the day that I usually meet with some member of my writers' group to parallel play.  In other words, we sit together and write.  It's kind of our answer to the solitary life of a writer.  And, it can be a lot of fun, because you have an audience who understands when you'd rather be playing Solitaire or can't remember a synonym or just want to read the cool line you just wrote that you're super-proud of.

In other news: last night, Shawn and I finally saw "Elysium."  That's the science-ficiton film with Matt Damon and Jodie Foster? The one where the rich people have moved off Earth to a kind of Niven-esque ring world/L-5 colony?  Yeah, that one.  The one that looks super gritty?  Yeah, it was grim.  About as grim as I expected it to be, but it totally pushed some of my class buttons (in a good way.)  I long ago confessed to naomikritzer that a science-fiction trope that ALWAYS works for me is "stop the line"/labor strike stories.  They'll show up as Very Special Episodes on shows like Battlestar Galactica or Star Trek and every damn time (even though it's essentially the same story) I'll get little tears and my eyes and secretly think it was the BEST EVER.  "Elysium" isn't quite that story made large, but there're elements of that trope in the movie... particularly the end, which I won't spoil beyond that.

There was a surprise character moment for me in "Elysium."  There's a mercenary/thief/fence-type named Spider who is pretty loathsome when you first meet him, but it becomes clear throughout the course of the film that he's weirdly... altruistic and kind of has been all along if you think about it for a few minutes.  He was my FAVORITE character, honestly.

So thumbs up?  Maybe.  I wouldn't necessarily tell you to go out of your way to see "Elysium," but I wouldn't warn you off it either.  I ultimately enjoyed it.  But Shawn had to look away several times because it was so gritty-dark and the beginning is so unrelenting that she kept asking, "Should we turn it off? Is this just going to be AWFUL??"  I'm glad we stuck with it, but, see: I can't exactly recommend it without reservations.

We were able to watch a movie like that last night, though, because Mason was PASSED OUT.  He'd had a sleepover the night before (Sunday to Monday, because of Inter-Session) and I kind of intentionally ran the kids around on Sunday.  Mason's buddy is a bit of a couch potato otaku, which are in point of fact MY people, but Mason can get irritable and restless if he sits ALL DAY.  So we let them game well into Sunday night and then yesterday I got them involved building marble towers (those Rube-Goldberg-type things) and then took them sledding at the St. Paul Country Club's golf course hill.



So, yeah, there's a date stamp now.  That's not from my camera, but from the stupid Mac iPhoto.  (Man, I hate Macs. I don't know why people are such proponents.)  At any rate, they had a lot of fun, but the rest was that Mason crashed sometime before dinner and we couldn't even rouse him to eat.  So, he slept until this morning--a whopping 13 and a 1/2 hours!  I told him he's getting practice in for being a teenager!

Comments

[seawasp]

I've been a Mac proponent for the simple reason that virtually *EVERY* bad experience I've had with computers has been Windows (and before that DOS) systems. Macs have always worked for me, easily, intuitively, and reliably. When I move from one Mac to another, the move is literally as easy as copying my old disk drive to the new computer -- no reinstalling applications, hoping I can find the registration numbers etc., etc., and so on.

So, that's why I tend to be a Mac proponent.

[lydamorehouse]

TBF, that's my problem in reverse. Macs are not intuitive to me because I cut my teeth on PCs. I know what to do with a PC. I know how to download things and know where they go... not on a Mac. I have no idea what the hell even happens in a Mac.

So, yeah, it's about what you're used to, for sure.

[seawasp]

Well, I cut my teeth, so to speak, on a DECWriter II terminal connected to a PDP 11/70. My first personal computers were Ataris (Atari 800, then later on Atari ST). My encounters with PCs and Macs were roughly equal when I went down to Pittsburgh, and I was pretty much neutral on both (since I was still using my Atari), until I started working in the university computer labs, and found that 85% of the "I'm having problems" calls on computers were Windows machines (and they tended to be PITA problems), 10% were on UNIX machines, and 5% were on the Macs. I then found that I, also, had a lot fewer issues figuring out what to do on a Mac than I did on a PC.

And I virtually never saw the equivalent of Blue Screen of DEATH on a Mac, while it was a common occurrence for Windows machines.

[lydamorehouse]

Yeah... see. I BROKE this MacBook Pro. So, that was dead easy for me. I broke this MacBook so badly that I froze the Genius Bar folks' diagnostic computer. And when I asked if I'd done anything, the guy just shrugged and said, "Meh, it's a Thing That Happens."

I have never been afflicted with a PC Thing That Happens. I usually, in fact, have to go to great lengths to destroy my PCs, having to drop frozen turkeys on them (true story) and carry them around by their screens until the screens separate and I drop them down a flight of stairs (slightly exaggerated, I just dropped it on the floor, I just happened to hit the exact spot where the hard drive lived.)

Re:

[seawasp]

Interesting. Opposite experiences. I've had PCs freeze and dump their hard drives without warning, destroying everything on them. I've had them lock up in the middle of completely routine tasks. I've had them just SUDDENLY start acting insane -- failing to do things they did just fine yesterday -- with no one, not even experts, being able to figure it out (in fact, I'm in the middle of one of those at work now; they're going to migrate me to another PC just to get away from whatever the heck this is).

The problems I've had with my Macs have been minimal.

And getting a NEW one? There's no comparison. Windows it's a multi-hour pain in the ass bringing old stuff over, having to re-install all my apps (and hoping they still all work. Mac, it's copy the old disk over to the new one, bingo, everything works.

[mariadkins.livejournal.com]

I think I'm in love with Miss Ball.