still too cool for wordpress.
choose only one: latest; past; wednesday lite; superscribe.

<< February 18, 2003 >>

quick dream roundup:

i could do without the ppp.
* * *

i thought today was going to be horrible when after i commented out the debug spew in my driver, it didn't work. uncommenting it didn't help. then i remembered i turned off autoconnect. if i manually connected, it worked again.

i fixed some typos and thinkos, and now it works perfectly. i've got synce installed (thanks to libpoll), but i haven't gotten it to work yet. they need some help with their autofoo, though.

* * *

re-enabling autoconnect makes synce work:

jacob@wet-pants:bin$ ./pcp ~/bad_day.mpeg :bad_day.mpeg File copy of 425988 bytes took 0 minutes and 8 seconds, that's 53248 bytes/s. jacob@wet-pants:bin$ ./pcp :bad_day.mpeg ~/bad_day.mpeg File copy of 425988 bytes took 0 minutes and 11 seconds, that's 38726 bytes/s. jacob@wet-pants:bin$ _

yay.

* * *

i'm not really looking forward to tomorrow.

things went so well today - i fixed the last couple of bugs in my driver, i got synce talking to it, and multisync builds, dinner with phil and joe - that tomorrow can't possibly compete. sure there will be a new penny arcade and a west wing (although i don't know if i'll be able to stand watching the whole thing), but things just won't be as good.

i think part of the problem is the multisync code i read today. honestly, there is a reason the spacebar key is the largest one on the keyboard. use it. enter's also pretty big [ed: my generous use of <p> should make my views on this obvious]. also it looks like they've never seen any other app that had plug-ins.

but does this crappy (looking) code mean that it doesn't work? no. so it really shouldn't bother me.

i have been accused of being really critical of people and the work they do. i like to think that i'm being as hard on them as i am on myself, and as hard on myself as i am on them.

for example, when i write code, i imagine miguel looking over my shoulder and giving me a hard time for writing such crappy code. or i hear myself critiquing the code, as if i was reading someone else's code.

this can cause a big road block: i concentrate on writing great (perfect?) code instead of writing any code.

so, when i read code like multisync, it frustrates me that people can write really ugly code, but nevertheless write code that actually does stuff, while i can have such a difficult time doing this.

i remember this email app i used to work on, and re-writing it over and over again. i didn't get it right the first time (honestly i never really got it right) but i just chose a method of doing something and went with it until it turned out to be a bad idea.

theoretically i should be better off now: being able to see problems with some implementation well in advance should save me lots of time. but the crippling aspect of not being able to write any code is as frustrating as it is unproductive.

or maybe i feel bad because joe took me to the farm in halo tonight.

* * *