21–30 of 36 posts
[After YC denial] "Over? Did you say "over"? Nothing is over until we decide it is! Was it over when the Germans bombed Pearl Harbor? Hell no! And it ain't over now. Cause when the goin' gets tough.... ..... .... the hackers get goin! Who's with me?? Let's go!"
I thought this was mine for years, but Chesterton beat me to it. Generally, if something is worthwhile, but not critical, it's worth spending the 20% of the time to get it 80% of the way there, and doing five such slipshod jobs, rather than one perfect one.
This is contrary to every reasonable software engineering practice, which is probably because it works better for things which aren't software, like user testing or business planning.
[After YC denial] "Over? Did you say "over"? Nothing is over until we decide it is! Was it over when the Germans bombed Pearl Harbor? Hell no! And it ain't over now. Cause when the goin' gets tough.... ..... .... the hackers get goin! Who's with me?? Let's go!"
Erm, didn't the Japanese bomb Pearl Harbour?
"If a thing's worth doing, it's worth doing badly." I thought this was mine for years, but Chesterton beat me to it. Generally, if something is worthwhile, but not critical, it's worth spending the 20% of the time to get it 80% of the way there, and doing five such slipshod jobs, rather than one perfect one. This is contrary to every reasonable software engineering practice, which is probably because it works better…
"It works in my machine"
I swore I would shoot the next person that said that to me. :)
Working on a few large projects I have realized that a system is never perfect, but a crappy business always has a crappy system. Happy company = happy system.
My 2 cents an most probably said by someone before me.