> > 5) Avoid using abbreviations >>> >> >> I disagree. When coding with a non-IDE, abbreviations make life much >> easier. >> > > I agree with David, abbreviations are better. When I'm trying to get > something out of my head and into code, I don't want things getting in my > way. 2 things in this scenario get in my way. 1) autocomplete is slow 2) > typing is slow. > > Here's something else to think about on this issue. A good typist, > familiar with their material can type faster then most code completions can > operate. In studying data entry folks at UofP, I noticed something about > the auto-complete functionality that wasn't obvious to me before. It's not > how fast the code complete pops up that slow you down. It's the mental > shift from typing to reading that takes the most time. You always have to > verify that what the auto-complete is going to use is correct. This almost > always takes more time then typing it yourself (assuming an expert typist). >
My concern is not at all coding speed which mostly is faster than thinking speed (at least for stupid pea-brains like me). I am concerned about how intuitive the Lift API, hence how fast folks will be familiar with it. To be more precise: I like abbreviations for really obvious stuff like RequestVar (everybody would know VarIABLES). But I do not like ... well I cannot find an example right now for an abbreviation in Lift that I do not like => Thus I guess this is more a general principle and Lift behaves quite well in this regard. Heiko My job: weiglewilczek.com My blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
