another day wasted
in order to alleviate the feeling of the subject line: what I've done today. Except that this list seems to reflect the dissipation and frustrated scramble that has been my life. I have too many big projects going on: moving [again] and thesis is too much to do at once.
- went to 9am makeup class that was made up because the prof was out of town
- planned final project for course with coding partner
- ate lunch
- made list of things to do for move
- filled out change-of-address form online
- made some tentative plans for this weekend, mostly moving. cancelled some others.
- went to a computing/funding meeting for all the students of my advisor: outlook not so good
- finished writing up my homework for class mentioned above
- discovered that my parse results from last week failed rather splashily
- went to see if I had any new comics [no, third week in a row now]
- discovered that not only I but somebody else discovered segfaults in the same parser
- downloaded new version of that parser, recompiled (ain't the guy ever heard of a clean target?)
- got myself dinner
- nope, that parser fix doesn't affect the splashy failure of my parser
- did the reading for tomorrow's 9am MT reading group
- got an email at 8pm announcing that the reading group was cancelled ([sarcasm]thanks for the prompt notice, mr. organizer[/sarcasm])
- wrote a long email describing the failure to the expert in another city. Frustrating to have to wait on his response
no subject
As someone who used to do professional development, i've learned some heuristics for who to take seriously as a coder, and who's a wanker that happens to use a computer.
Lack of a
cleantarget? Waaay up there on the list.You have my sympathies (both with the code, and with the feeling of absolute futility/overwhelming).
bleah.