Best Practices in Rev development

[Joe Lewis Wilkins]

After spending many years using a variety of languages, and getting  
accustomed to declaring vars before using them, it was "convenient"  
to get a little sloppy now and then; but when it came down to doing  
something "for real", declaring vars definitely tended to promote  
more thorough reasoning and planning. So it took a little bit longer;  
one had a far better grasp as to what was being done, and it really  
did promulgate less buggy code and far fewer problems. Just not  
having to "type" the vars is good enough, and having the option of  
getting sloppy every now and then is nice. Of course, the ruler of my  
sun sign is in Virgo as is my Jupiter, so that fits in with my  
personality and way of doing things routinely.

Joe Wilkins

On Jun 20, 2007, at 4:21 PM, Mark Wieder wrote:

> Jacque-
>
>> 5. And finally, what's wrong with being lazy? :) The smart programmer
>> finds the easiest way to do things. That's what Rev is all about.
>
> And for me laziness is most definitely part of the solution:
>
> it's much easier for me to have the compiler tell me I've made a  
> typo and
> said "put 3.14159 into tPuckLocatoin" than to have to search  
> through my code
> and try to figure out why tPuckLocation doesn't have the value I  
> think it
> should. And it tells me at compile time instead of at run time, or  
> worse,
> when a client finds it at run time. Typing one line of code saves  
> me a lot
> of work down the line.
>
> And I like saving me work.
>
> -- 
>  Mark Wieder
>  mwieder at ahsoftware.net