I could see this being useful on the TabletPC or maybe on handhelds, where you rarely have a keyboard at your disposal. Heh, wonder how long before M$ "embraces, extends, and exterminates" this technology?
Why is it that there isn't enough time to do it right, but there's always time to do it over?
When I was a consultant I witnessed many cases of do it now quick & dirty; hardly anyone
wanted to take the time to do it right. Funny thing is that after all was said and done the
projects that were done quick & dirty ended up costing *more* than the projects that were done
right from the beginning, and took *more* time to finish. While I realize this is just my
anecdotal evidence, I noticed that the leaders of the projects that ended up being completed
on time and within budget spent more time up front negotiating clear requirements from the
customers, planning and *thinking* about the architecture which produced a cleaner design,
while the coders spent some time *thinking* about the code they were going to write before
they began coding. Result? Better design, better code, less panic at the end of the project
fixing design and code defects and adding in code for missed or misunderstood requirements.
Besides, doing it right doesn't necessarily mean taking a long time to complete a project -
how much time does it take to obtain clear requirements from a customer? How much time does it
take to think through the goals of the project and technology involved? Not every project
that's done right has to have everything completely specified according to the Rational
Unified Process & designed with Rational Rose... Also, how many quick and dirty projects
that crash and burn would it take to wreck a contractor's reputation? That will surely result
in less revenue over the long term.
Slashdot Mirror
How about: 11:23:58?
I could see this being useful on the TabletPC or maybe on handhelds, where you rarely have a keyboard at your disposal. Heh, wonder how long before M$ "embraces, extends, and exterminates" this technology?
So - they're firing all the PHBs then?
Why is it that there isn't enough time to do it right, but there's always time to do it over? When I was a consultant I witnessed many cases of do it now quick & dirty; hardly anyone wanted to take the time to do it right. Funny thing is that after all was said and done the projects that were done quick & dirty ended up costing *more* than the projects that were done right from the beginning, and took *more* time to finish. While I realize this is just my anecdotal evidence, I noticed that the leaders of the projects that ended up being completed on time and within budget spent more time up front negotiating clear requirements from the customers, planning and *thinking* about the architecture which produced a cleaner design, while the coders spent some time *thinking* about the code they were going to write before they began coding. Result? Better design, better code, less panic at the end of the project fixing design and code defects and adding in code for missed or misunderstood requirements.
Besides, doing it right doesn't necessarily mean taking a long time to complete a project - how much time does it take to obtain clear requirements from a customer? How much time does it take to think through the goals of the project and technology involved? Not every project that's done right has to have everything completely specified according to the Rational Unified Process & designed with Rational Rose... Also, how many quick and dirty projects that crash and burn would it take to wreck a contractor's reputation? That will surely result in less revenue over the long term.