scott wrote:
> I like the second one too.

That didn't really seem hacky to me, actually. It was the obvious solution. 
Certainly the people who coded the hash in the first place knew there was a 
chance a collision would come up.  The failure there was having the program 
generating the hashes not checking that there was a collision.

> I think in any industry where you have complex projects that need to be 
> finished by a deadline there will always be less-than-optimal hacks to 
> get it "finished".  Usually if you had more time there would be a number 
> of things you could do better.

I had a friend who worked in theater production before programming. It 
always ticked him off when the boss gave a "deadline" and he'd bust butt, 
only to hear that it was more a "this is when we'd like it" than a deadline.

For him, if you didn't stop working and ship whatever you had at the 
deadline, it wasn't a deadline. When the curtain goes up in front of a bunch 
of ticketholders? That's a deadline.

Of course, games trying to hit the christmas season, or cars going into 
production, all count as actual deadlines, as do trade show demos in the 
computer business.

-- 
   Darren New, San Diego CA, USA (PST)
   "We'd like you to back-port all the changes in 2.0
    back to version 1.0."
   "We've done that already. We call it 2.0."

Post a reply to this message