4:25 Wake up five minutes before alarm. Make coffee, continue work on infrastructure challenges facing VWRR course.

6:00 Put out call to France, download virtual machine containing complete build system for robotics platform.

7:50 Shower.

8:30 Get in car, drive to campus.

8:45 Spend 15 minutes reviewing materials for Intro.

9:00 Intro. Answer one question, mini-lecture takes 45 minutes.

10:00 Fight technology more. Same story as the last two weeks.

10:55 Head into class. Eat leftover Halloween candy.

11:00 Admit massive fail to students. Technology won. Goal: do cool stuff with computing. Offer alternatives.

11:20 Bring huge tub of LEGO robots into class. Situation apparently salvaged.

12:30 Eat lunch while talking with friend about pending laptop purchase.

13:00 Student with questions about pending PL course.

13:15 Begin work on letter.

14:00 Student with questions about research. Completely fail to print copies of key papers to give to student.

14:40 Overrun into next meeting. Soda, conversation with faculty mentor.

15:30 Continue working on letter.

16:00 Conversation with new sysadmin about backups.

16:40 Continue working on letter.

17:00 Print letter on letterhead for mailing tomorrow. No envelopes left.

17:20 Talk to choir director about missing rehearsal. Obtain 35MHz oscilloscope for testing and possible rehab.

17:45 Head home. Stop by Obama HQ to see how things are going.

17:55 Home. Eat leftovers. See wife unit.

18:00 Begin testing software for LEGO Mindstorms.

18:30 Fail. Put out call to England for possible help.

19:00 Continue to fail with software.

19:15 Confirm fail with England.

19:30 Head back to OHQ. Make calls, stuff envelopes… just do stuff.

23:00 Head home. Pet neighbors cat.

23:15 Time to sleep fast.

4 Responses to “a day”

  1. Nikki says:

    How the devil do you pull off 4 1/2 – 5 hours of sleep a night?

  2. Greg Marra says:

    It sounds like you’re using Naos.

  3. Matt says:

    @Nikki:
    Consider that all my days aren’t like this, but some of them do seem awfully long.

    @Greg:
    1. I don’t know what Naos is.
    2. Therefore, you’re talking crack.
    3. Therefore, Naos == crack.

    I guess. ?

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">