doink   (it's one of those things about nothing)
homus || backlog || elsewhere || huh?
 

Tuesday, February 29, 2000
but isn't sand the cure for the common cold? (guilty, as charged.)
(12:23:22 AM)

they don't fool around about fooling around in the uae. yikes.
(12:14:50 AM)

Monday, February 28, 2000
if i like to wear a big white cowboy hat while i code, does that make me weird?
(10:21:54 PM)

have you ever had one of those days where you had a ton of high-priority things to do, but you couldn't get to any of them because you kept getting sucked into meetings, and then getting even more high-priority things to do?

i'm having one of those years.
(4:26:19 PM)

Sunday, February 27, 2000
ahhh, spring is in the air. sorta. at least it's time to start the draft for one of the rotisserie baseball leagues i'm going to do this year. back in the olden days (ok, 1994), we used to do these leagues by keeping track of scores in a big spreadsheet. it took hours each week to update the scores. now we just log into a web site; they do all the work for us, for free. technology is neat.
(6:17:31 PM)

Saturday, February 26, 2000
the common threads running through the posts by web designers and techies in the replies to the most recent story at the fray are somewhat enlightening. almost everyone echoes a sentiment that
  1. clients hire you for the creativity your previous work showed, then they proceed to ignore your recommendations,
  2. the end product is corporate-centered, rather than user-centered, and
  3. clients are always late delivering the stuff they're responsible for on projects.
thoughts on that:
  1. i've seen these 3 things to be true in almost every project i've ever worked on,
  2. almost every book i've ever read on software development management and best practices warns about the latter two, and
  3. why do we (as an industry, and as individuals) let this happen?
you'd think that we'd figure out some way to better manage the expectations, process, and results. maybe better sign-posting? in several of the books i've read, they recommend presenting a "client's bill of rights" and a "developer's bill of rights" before initiating a project. maybe this is the way. i'll give it a shot, and report here how it goes.
(5:42:22 PM)

(finally) saw american beauty last night. i've never pretended to be a movie critic, and i won't pretend to start now: i liked it. thought it was pretty cool, while mildly disturbing.
(11:55:59 AM)

Friday, February 25, 2000
amazon won a patent for affiliate programs. if they choose to enforce it, and it sticks, it will significantly impact the bottom lines of many companies out there.
(6:35:13 PM)

i want a robo-monkey! now!
(3:56:28 PM)

another one of my college buddies just got engaged. congrats, justin (and meg)!
(1:38:19 PM)

money is now officially growing on trees.
(11:39:53 AM)

Thursday, February 24, 2000
i've made the big switch over to blogger. i could write my own system pretty quickly, but it's just silly to any more. plus, now that gerns and matt are set up, they can do stuff, and i can help them out. and then we'll probably do some big ol' collabra-loggy kinda thing.
(9:36:47 PM)

why doink? why not!
(7:36:40 PM)

 
powered by blogger        copyright © 1973-2000, mike manning