Mine "I you wait for the Ferrari, You may miss the Pento and You will end up walking" In other words grab what is here "now" while still setting your sight on the bigger prize.
"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 for things which aren't software, like user testing or business planning.
A former employer once got a present from I-don't-know-who. It was a bunch of magnetic labels with "empowering" words, with which the employees were supposed to build "motivating" sentences. These are the ones I can remember from the drinks fridge:
Actually I was thinking more in terms of pushing code into production that I haven't tested properly. In all other things I try to make a habit of embracing risk.
"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!"
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.
if you are asking us to give a quote then it can't be mine - it has to be a "quote"
i would therefore say "one moment in annihilations waste, one moment the well of life to taste" and it is quoting Fitzgerald's translation of Omar Kyham
i like that. it is funny that you say it. Sometimes we spend hours trying to figuring soemthing or days trying to get something (or someone in my case) and the minute you stop trying it all happens. I think by trying we are making it hard for "anything" itself to make it happen so just "let if flow"
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.