|prev : next : index||SPEW|
I started work last Tuesday. My week in brief: setting up my computer and going to a meeting. Writing documentation and discovering my computer was unstable. Getting a temporary computer while they redid my original. Writing docs on the temp computer with no connection to the net and no company email. Getting the original computer back, setting it up, and finishing docs.
At some point during the week, I had a thought or two for journal entries, but I totally forgot what they were by the time I got home.
I've spent most of the rest of my time online, mudding--a substitute for a social life I supose. Since I'm around people all day at work now, though, I should be able to scale back my need for additional people contact.
I'm supposed to be cleaning/packing up my room--I'm switching rooms in my apartment, because I just have too much stuff now to fit in my current room (which is the smallest of the four bedrooms). But I haven't actually managed to make any progress on it. I just look at the room and see what a mess it is and find something else to do.
In fact, the same is true right now--rather than pack, I'm quite tempted to go into work and work on those documents I was working on. These documents are actually pretty interesting, because I'm trying to generate the outline of a talk (actually, probably two or three talks), and in the process I'm actually learning some things I didn't know, at least not consciously.
Also, it's interesting that the best way for me to think, or at least to organize my thoughs, is to write complete sentences. In this case, I really just need to generate an outline of points for the talk, but I ended up writing "the paper" version of the talk (all grammatical, transitions, etc.) first, then going through that and resummarizing it as a series of lists of points--which is still too long so now I'll go through and resummarize that.
This is, of course, the opposite of how most people would presumably approach it. In a way, it also reflects my classic coding style vs. other peoples'--I'm biased towards bottom-up programming, where you build all the pieces in detail from the moment you start--as opposed to top-down programming, where you layout the function of the program in a very concise form, and then refine it into more and more detail.
And of course, the use of complete sentences to help me organize my thoughts shouldn't be that surprising to you, since that's rather the premise of this collection of documents.