View Single Post
  #4   Spotlight this post!  
Unread 16-01-2008, 23:08
Jim E Jim E is offline
Registered User
FRC #1523 (M.A.R.S.)
Team Role: Mentor
 
Join Date: Jun 2006
Rookie Year: 2005
Location: Lantana, FL
Posts: 188
Jim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond reputeJim E has a reputation beyond repute
Re: easyC vs Hardcoding

The real question is: Do those that use the enhanced tools of Easy C understand the operation of the sensors that are so easy to make operational?

FIRST has been about preparing students for engineering. Granted, most students do not have the time to digest all the technical information in the datasheets to understand with 100% clarity. Most of those datasheets are precise, but every sentence counts.

This year, we are experimenting with a cross between the two. Use Easy C to verify sensor operation, then teach the future CS programmers how it relates to a C compiler without the bells and whistles. If understanding is an issue, the Easy C code may accelerate the understanding.

When the competition draws near, perhaps the switch may be made to Easy C for competitive reasons, but at least those students who desired the more in-depth programming experience will have achieved their goals of understanding.

Any novice programmers should use Easy C. Advanced programmers should swallow their pride and recognize that Easy C will make the novices look like they have been coding for years, even if they don't comprehend the how it all works. I'm not an advocate for Easy C, but there are advantages to using it.

FIRST may be making another attempt to level the playing field for the game.
__________________
Team MARS = 1.523 AU from the SUN!

Jim E.