Concerning the "coded in 3 minutes" in the subject.
I wouldn't want anybody to be intimidated by this.
I'm an experienced programmer. My customers come back for more.
Though others create in a different style, my design style might be a
yardstick.
I might code a similar solution in 3 minutes, maybe more. But--for
me--that might be after a period on pondering options: ellipses at
angle, images at angle, lines, single polygon, multiple polygons,
overlapping animated gifs, rebuilding images.... And I might try some
experiments or look at what others have done or see what images
components are available and so on. I might consider issues such as
stopping the thing. I might make some queries on this list.
For me the coding is a small part of the design process. For one
customer after a couple hours of research I coded up a solution in
seconds and my customer was very happy.
For some folks the script editor is where they explore ideas, allowing
the structure of code to help ideas come together. They might write a
few pieces that help in thinking about the rest. Code might move
around. I don't think we can call these folks slow coders; they are
using scripts to work with ideas.
Others need time, they don't get their best ideas on demand. Some
folks wake up in the morning with ideas or get them in the shower or in
traffic.
So, if making a clock takes hours staring at clocks or tinkering or
chatting with others or whatever, that is OK. We have different styles
and we are all learning and growing. Though there might be some who go
from challenge to script in 3 minutes, for most of us mere mortals the
total time to design is longer.
Dar
--
**********************************************
DSC (Dar Scott Consulting & Dar's Lab)
http://www.swcp.com/dsc/
A sponsor of RevCon West '05
**********************************************
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution
