Go to Post If that many teams could do it successfully every match this year I will eat my robot. - Jay O'Donnell [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #39   Spotlight this post!  
Unread 06-12-2006, 15:46
mgreenley
 
Posts: n/a
Re: Ethics 101: To re-use or not to re-use?

Quote:
Originally Posted by Steve W
Could you please explain the differences in your statement between hardware and software. As I see it the argument holds equally true with either.
Please correct me if I'm off the mark, but I believe that Seanwitte is saying that by having code that can be built off of previous implementations, programmers can work on adding to the code rather than re-working it.

After reading the thread, I think that the machine part v. code is a faulty analogy because of the information they hold. Rather, I suggest that a source file is closer to the working-drawings that are used to build components. I say this because working drawings are a very information-dense format of representing the idea of a part; In my design class, I wouldn't throw out my drawings at the beginning of every project, rather, I re-work them to speed up the next project to allow me to work on something new. In the same way, the source code is a very information dense format of representing an idea of behavior. I think Seanwitte is saying that by having code modules already developed, instead of re-writing them, they can be tweaked to fit a new situation and then new code and new implementations can be built from them.

The analogy breaks down at the implementation stage, because machining a part takes more time than compiling a program; the information-dense idea to information-diffuse implementation divide is blurred.

However, consider a team that has a CAD file for a part. To make the part, they can enter this into a CNC, go to (Wawa/7-11/Subway/etc...), and retrieve their part. By having this, a team can plan new implementations without worrying about the base every year. Maybe they want to add a turret on their already developed frame? The programming analog here is adding a new function. By having a code base for managing joystick input to drive motor output (lets say the team wrote a piece of code to linearize the input to output and also added a deadzone on the joystick). This year, the team plans to implement the already-debugged code block, but also to add functionality for using the gear-tooth sensor and an accelerometer.

I think that this difference is key to why I am behind the conclusions Mr. Scheck draws in post #62

Last edited by mgreenley : 06-12-2006 at 15:54. Reason: Grammatical and spelling change
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Robot Ethics? negfrequency General Forum 33 01-06-2006 18:55
Does anyone else NOT use a long arm to place a tetra on top of the Goal? mad_cloversc General Forum 29 08-03-2005 00:44
Accelerometer Use Doug G Programming 2 15-12-2004 09:06
can we use? Allie Kit & Additional Hardware 5 13-02-2002 15:54


All times are GMT -5. The time now is 03:35.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi