Go to Post This whole experience, the entirety of what FIRST represents and promotes, is about inspiring individuals to make something more of themselves and creating a better world; when you consider this, our individual victories seem meaningless. - Dillon Compton [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

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 30-07-2007, 08:59
Andy Baker's Avatar Woodie Flowers Award
Andy Baker Andy Baker is offline
President, AndyMark, Inc.
FRC #3940 (CyberTooth)
Team Role: Engineer
 
Join Date: May 2001
Rookie Year: 1998
Location: Kokomo, Indiana
Posts: 3,410
Andy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond reputeAndy Baker has a reputation beyond repute
Send a message via AIM to Andy Baker
Re: The Honor Code of FIRST

Quote:
Originally Posted by Tom Bottiglieri View Post
Keep in mind that rules are not laws. Be careful with words like "illegal".
Also, some rules are meant to be broken; it keeps things progressing.
This is careless advice and should not be followed. Questioning a rule is fine. Stating that a rule should be changed is a freedom that we all have. If someone thinks a rule is wrong, they can argue their case properly and work hard to get it changed.

I hope this was what Tom was referring to, and just posted in haste.

Breaking a rule just because you think it is meant to be broken is not good advice.

Andy B.
Reply With Quote
  #2   Spotlight this post!  
Unread 30-07-2007, 11:21
Tom Bottiglieri Tom Bottiglieri is offline
Custom User Title
FRC #0254 (The Cheesy Poofs)
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2003
Location: San Francisco, CA
Posts: 3,182
Tom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond reputeTom Bottiglieri has a reputation beyond repute
Send a message via AIM to Tom Bottiglieri
Re: The Honor Code of FIRST

Quote:
Originally Posted by Andy Baker View Post

I hope this was what Tom was referring to, and just posted in haste.

Breaking a rule just because you think it is meant to be broken is not good advice.
I think my vagueness was confused for something else. Let me clear it up.

FIRST is supposed to inspire and prepare kids for a life and career in a science based profession. The last time I checked, the world wasn't "fair". People lie, cheat, and steal to get ahead in every aspect of life. I'm not saying this is justification to go out and break the rules; it is nothing even close to that. With that being said, people really just need to worry about themselves and their team. How far are you willing to push while still feeling comfortable? In reality, this is a question that only YOU are able to answer, and if you break the rules then prepare to suffer whatever consequences await.

What I do not like hearing about is the "vigilantism" that is going on at competitions. I don't care if someone broke every rule in the book... One team has absolutely no right to touch another teams property. Seriously, it's just a game. If everyone could just worry about how much fun they are having rather than how much they disagree with other teams, the program would be much better off.
Reply With Quote
  #3   Spotlight this post!  
Unread 30-07-2007, 13:18
Dan Richardson's Avatar
Dan Richardson Dan Richardson is offline
iR3 Creative
AKA: Dan Richardson
no team
Team Role: Engineer
 
Join Date: Feb 2003
Rookie Year: 2001
Location: Ft. Lauderdale FL
Posts: 1,116
Dan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond reputeDan Richardson has a reputation beyond repute
Re: The Honor Code of FIRST

Quote:
Originally Posted by Tom Bottiglieri View Post
I think my vagueness was confused for something else. Let me clear it up.

FIRST is supposed to inspire and prepare kids for a life and career in a science based profession. The last time I checked, the world wasn't "fair". People lie, cheat, and steal to get ahead in every aspect of life. I'm not saying this is justification to go out and break the rules; it is nothing even close to that. With that being said, people really just need to worry about themselves and their team. How far are you willing to push while still feeling comfortable? In reality, this is a question that only YOU are able to answer, and if you break the rules then prepare to suffer whatever consequences await.

What I do not like hearing about is the "vigilantism" that is going on at competitions. I don't care if someone broke every rule in the book... One team has absolutely no right to touch another teams property. Seriously, it's just a game. If everyone could just worry about how much fun they are having rather than how much they disagree with other teams, the program would be much better off.
Tho I conquer with the statement is always good to push the envelope I believe you have to stay within the rules and if you don't you better be prepared to face the consequences by whoever they come from.

If a team breaks every rule in the book then you better make sure they are held accountable. If you don't you taint the validity of the program it becomes a free for all the program disentegrates. Its absolutely foolish to just let teams go unchecked.

The fact of the matter is often times those responsible for enforcing the rules don't know them. Often times ( not every case ) robot inspectors, referees and field managers make up their own rules or don't know the specifics, mainly because they are improperly trained. Now granted many of them are innocent mistakes maybe a rule changed from year to year and made an honest mistake, but I strongly believe its responsibility of teams and volunteers to resectfully and properly rectify these problems. Otherwise the teams you compete against are cheated out a fair and balanced competitions.

I learned an important rule of thumb this year, as much as you want teams to do the right thing often they do not. Now acting like a vigilanty and pulling wires out of a robot to break it would be bad. Going through the proper channels approaching them with the rule book or making the robot inspector aware of the issue, that is what should be done. Many broken rules are accidental, misinterpretation of a rule, or failure to get all updates. But when faced with their rule breaking in the middle of competition its their reaction to this confrontation that reflects heavily on their honor and their integrity. If they refuse to acknowledge the rule, then it should be brought to the proper authorities, if they still fail to acknowledge I believe they should be disqualified from the competition and should be disqualified from all played matches.

I know this post is not as much about the key to the honor code which reflects on "fix it" windows and pre season building, but it is no less important. We all know teams do not follow the code and build parts before season, teams may even build entire drive assemblies preseason. Its unfortunate but true, do their need to be more checks and balances? Possibly, but within the current construct of FIRST I believe it to be nearly impossible.

Cheating is huge, in real life it can get you thrown out of your sport and quite possibly land you in jail. A rule is a rule whether you like it or not, what gives your team the right to pick and chose while the other 1350 teams have to follow it. So whether it be by the FIRST volunteers, or the FIRST community, teams need to be held accountable. If teams follow this advice and ignore the rules, accountability and integrity, I believe that this program would self implode quicker than it would be "better off."
__________________
CO-Founder of Robot in 3 Days and the Robot in 3 Day Challenge.



Last edited by Dan Richardson : 30-07-2007 at 13:27.
Reply With Quote
  #4   Spotlight this post!  
Unread 31-07-2007, 00:05
David Brinza's Avatar
David Brinza David Brinza is offline
Lead Mentor, Lead Robot Inspector
FRC #0980 (ThunderBots)
Team Role: Mentor
 
Join Date: Feb 2003
Rookie Year: 2003
Location: Glendale, CA
Posts: 1,378
David Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond reputeDavid Brinza has a reputation beyond repute
Re: The Honor Code of FIRST

Quote:
Originally Posted by Stud Man Dan View Post
<snip>
I know this post is not as much about the key to the honor code which reflects on "fix it" windows and pre season building, but it is no less important. We all know teams do not follow the code and build parts before season, teams may even build entire drive assemblies preseason. Its unfortunate but true, do their need to be more checks and balances? Possibly, but within the current construct of FIRST I believe it to be nearly impossible.
<snip>
A rule is a rule whether you like it or not, what gives your team the right to pick and chose while the other 1350 teams have to follow it. So whether it be by the FIRST volunteers, or the FIRST community, teams need to be held accountable. If teams follow this advice and ignore the rules, accountability and integrity, I believe that this program would self implode quicker than it would be "better off."
Hey, many of the rules can seem almost arbitrary and incompatible with the way some FIRST teams operate.

The "fix-it window" rule is a good example: last year you were allowed two 5-hour periods in which to upgrade, make spare parts or work on software. For some teams, that highly-constrained work period just couldn't work. If, during weekdays, the mentors couldn't show up until after 6 pm and the school or facility where you built the robot required you to leave by 9pm, you basically lost 40% of your fix-it window those days. FIRST could make it easier (and dare I say, more "fair") by allowing teams to have three "fix-it window" sessions with no more than 10 hours cumulative permitted. Under last year's rule, that wasn't an option.

Would you consider a team that worked 3 hours on two weeknights and four hours on Saturday to be taking unfair advantage of other teams? Could YOUR team rationalize this as meeting the spirit of the "fix-it window intent"? (I'm not saying that I know of teams that did this; we certainly didn't.)

As part of the FIRST community, we have the right (actually, the duty) to suggest that the FIRST rules have enough flexibilty to accommodate teams constraints without unduly penalizing them. Why put teams at a disadvantage via somewhat arbitrary rules intended to "level" the playing field?

Honor code is a great thing, but if some of the least enforceable rules seem arbitrarily over-constrained, the temptation to "skirt" them can drive teams down the path to rationalize their deviations from those rules. Once you start down that path, other rules can become victimized as well. I don't think that's where we want to go...
__________________
"There's never enough time to do it right, but always time to do it over."
2003 AZ: Semifinals, Motorola Quality; SoCal: Q-finals, Xerox Creativity; IRI: Q-finals
2004 AZ: Semifinals, GM Industrial Design; SoCal: Winners, Leadership in Controls; Championship: Galileo #2 seed, Q-finals; IRI: Champions
2005 AZ: #1 Seed, Xerox Creativity; SoCal: Finalist, RadioShack Controls; SVR: Winners, Delphi "Driving Tomorrow's Technologies"; Championship: Archimedes Semifinals; IRI: Finalist
2007 LA: Finalist; San Diego: Q-finals; CalGames: Finalist || 2008 San Diego: Q-finals; LA: Winners; CalGames: Finalist || 2009 LA: Semifinals; Las Vegas: Q-finals; IRI: #1 Seed, Finalist
2010 AZ: Motorola Quality; LA: Finalist || 2011 SD: Q-finals; LA: Q-finals || 2013 LA: Xerox Creativity, WFFA, Dean's List Finalist || 2014 IE: Q-finals, LA: Finalist, Dean's List Finalist
2016 Ventura: Q-finals, WFFA, Engineering Inspiration
Reply With Quote
  #5   Spotlight this post!  
Unread 31-07-2007, 01:20
Tim Delles's Avatar
Tim Delles Tim Delles is offline
Since 2001.
FRC #0078
Team Role: Mentor
 
Join Date: Dec 2004
Rookie Year: 2001
Location: Providence, RI
Posts: 1,002
Tim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond reputeTim Delles has a reputation beyond repute
Re: The Honor Code of FIRST

Quote:
Originally Posted by David Brinza View Post
Hey, many of the rules can seem almost arbitrary and incompatible with the way some FIRST teams operate.

The "fix-it window" rule is a good example: last year you were allowed two 5-hour periods in which to upgrade, make spare parts or work on software. For some teams, that highly-constrained work period just couldn't work. If, during weekdays, the mentors couldn't show up until after 6 pm and the school or facility where you built the robot required you to leave by 9pm, you basically lost 40% of your fix-it window those days. FIRST could make it easier (and dare I say, more "fair") by allowing teams to have three "fix-it window" sessions with no more than 10 hours cumulative permitted. Under last year's rule, that wasn't an option.

Would you consider a team that worked 3 hours on two weeknights and four hours on Saturday to be taking unfair advantage of other teams? Could YOUR team rationalize this as meeting the spirit of the "fix-it window intent"? (I'm not saying that I know of teams that did this; we certainly didn't.)

As part of the FIRST community, we have the right (actually, the duty) to suggest that the FIRST rules have enough flexibilty to accommodate teams constraints without unduly penalizing them. Why put teams at a disadvantage via somewhat arbitrary rules intended to "level" the playing field?

Honor code is a great thing, but if some of the least enforceable rules seem arbitrarily over-constrained, the temptation to "skirt" them can drive teams down the path to rationalize their deviations from those rules. Once you start down that path, other rules can become victimized as well. I don't think that's where we want to go...
Mr. Brinza,

That is an excellent point and i back you completely on this. Even for our team it seemed diffucult to organize everything and everyone for 2 - 5 hour sessions. It would be nice to see FIRST allow 3 days with no more than 10 total hours.

Great thinking
__________________
Timothy Delles - Clarkson University
2011 - Present: FRC Team 78 - AIR Strike
2011 - Present: VEX Team 78 - AIR Strike
2010 - 2011: FRC Team 3280 - Rhode Rebels
2001 - 2009: FRC Team 229 - Division By Zero
Reply With Quote
  #6   Spotlight this post!  
Unread 31-07-2007, 08:17
Taylor's Avatar
Taylor Taylor is offline
Professor of Thinkology, ThD
AKA: @taylorstem
FRC #3487 (EarthQuakers)
Team Role: Teacher
 
Join Date: Jan 2006
Rookie Year: 2006
Location: Indianapolis, IN, USA 46227
Posts: 4,569
Taylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond repute
Re: The Honor Code of FIRST

Perhaps instances like this are exactly what Mr. Bottiglieri had in mind.
However, I do agree with Mr. Baker in that if you find a rule to be asinine, let the GDC know, don't just pick-and-choose which rules you follow.
__________________
Hi!
Reply With Quote
  #7   Spotlight this post!  
Unread 02-08-2007, 18:36
AdamHeard's Avatar
AdamHeard AdamHeard is offline
Lead Mentor
FRC #0973 (Greybots)
Team Role: Mentor
 
Join Date: Oct 2004
Rookie Year: 2004
Location: Atascadero
Posts: 5,494
AdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond reputeAdamHeard has a reputation beyond repute
Send a message via AIM to AdamHeard
Re: The Honor Code of FIRST

Quote:
Originally Posted by David Brinza View Post
Hey, many of the rules can seem almost arbitrary and incompatible with the way some FIRST teams operate.

The "fix-it window" rule is a good example: last year you were allowed two 5-hour periods in which to upgrade, make spare parts or work on software. For some teams, that highly-constrained work period just couldn't work. If, during weekdays, the mentors couldn't show up until after 6 pm and the school or facility where you built the robot required you to leave by 9pm, you basically lost 40% of your fix-it window those days. FIRST could make it easier (and dare I say, more "fair") by allowing teams to have three "fix-it window" sessions with no more than 10 hours cumulative permitted. Under last year's rule, that wasn't an option.

Would you consider a team that worked 3 hours on two weeknights and four hours on Saturday to be taking unfair advantage of other teams? Could YOUR team rationalize this as meeting the spirit of the "fix-it window intent"? (I'm not saying that I know of teams that did this; we certainly didn't.)

As part of the FIRST community, we have the right (actually, the duty) to suggest that the FIRST rules have enough flexibilty to accommodate teams constraints without unduly penalizing them. Why put teams at a disadvantage via somewhat arbitrary rules intended to "level" the playing field?

Honor code is a great thing, but if some of the least enforceable rules seem arbitrarily over-constrained, the temptation to "skirt" them can drive teams down the path to rationalize their deviations from those rules. Once you start down that path, other rules can become victimized as well. I don't think that's where we want to go...
The fix it windows were definately intense for us this year. Luckily, due to severall machinist and CNCs working concurrently, we pulled it off.

Now to actually contribute; The rules that FIRST hands down are the rules. Complain on CD about them, or nitpickt he Q&A; but in the end, if FIRST doesn't change it, you just have to follow it. If it were to become standard practice for some teams to break some unpopular rules (that seem to have no rationale) that easily spread to rules that would have worse consequences if broken.

On the other hand, if the referees or field crew is insisting on a rule that is no place mentioned in ANY documentation, then go ahead and fight it. But even then, if the ref's are adament about it, you'll have to follow.



FIRST is unfair enough as it is; unfairly breaking rules because "no one" is watching will just make that worse.
Reply With Quote
  #8   Spotlight this post!  
Unread 13-09-2007, 09:21
Taylor's Avatar
Taylor Taylor is offline
Professor of Thinkology, ThD
AKA: @taylorstem
FRC #3487 (EarthQuakers)
Team Role: Teacher
 
Join Date: Jan 2006
Rookie Year: 2006
Location: Indianapolis, IN, USA 46227
Posts: 4,569
Taylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond repute
Re: The Honor Code of FIRST

FIRST has to include a couple silly rules each year so the IRI can make fun of them and change them.
__________________
Hi!
Reply With Quote
  #9   Spotlight this post!  
Unread 18-10-2007, 21:57
vivek16's Avatar
vivek16 vivek16 is offline
Whoa! college pilot.
AKA: vivek
FRC #2264 (trojan robotics)
Team Role: Alumni
 
Join Date: Jan 2007
Rookie Year: 2007
Location: plymouth, minnesota
Posts: 1,227
vivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond reputevivek16 has a reputation beyond repute
Send a message via AIM to vivek16 Send a message via MSN to vivek16
Re: The Honor Code of FIRST

I was first introduced to the honor code by CD. It was about 3 weeks into build season and I decided to see what it was. I was pretty amazed. I learned that FIRST is waay more than just a robotics competetion. No other activity that I have ever tried has an honor code like FIRST's.

-vivek

p.s. I am definetely going to have that talk with new members about the honor code.
__________________
"we don't build robots, we build people"
Reply With Quote
  #10   Spotlight this post!  
Unread 18-10-2007, 22:41
Ellery's Avatar Unsung FIRST Hero
Ellery Ellery is offline
Working on my 10 month old robot...
AKA: Ellery
no team (X-CATS - on Sabbatical)
Team Role: Leadership
 
Join Date: Jun 2001
Rookie Year: 1999
Location: Rochester, NY
Posts: 383
Ellery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond reputeEllery has a reputation beyond repute
Send a message via AIM to Ellery Send a message via Yahoo to Ellery
Re: The Honor Code of FIRST

"Ethics" nuff said.... Look it up.
__________________
Xerox Sr. Systems Engineer
Other jobs: Retired X-CATS Team Leader, Inaugural FLR MC and plain ol' nice guy
Team# 191 X-CATS - Est.1992 (www.x-cats.org)
"We don't just build robots we build people..."
Reply With Quote
  #11   Spotlight this post!  
Unread 31-07-2007, 08:30
Daniel_LaFleur's Avatar
Daniel_LaFleur Daniel_LaFleur is offline
Mad Scientist
AKA: Me
FRC #2040 (DERT)
Team Role: Engineer
 
Join Date: Apr 2005
Rookie Year: 2003
Location: Peoria, IL
Posts: 1,941
Daniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond reputeDaniel_LaFleur has a reputation beyond repute
Send a message via MSN to Daniel_LaFleur
Re: The Honor Code of FIRST

Quote:
Originally Posted by Tom Bottiglieri View Post
FIRST is supposed to inspire and prepare kids for a life and career in a science based profession. The last time I checked, the world wasn't "fair". People lie, cheat, and steal to get ahead in every aspect of life. I'm not saying this is justification to go out and break the rules; it is nothing even close to that. With that being said, people really just need to worry about themselves and their team. How far are you willing to push while still feeling comfortable? In reality, this is a question that only YOU are able to answer, and if you break the rules then prepare to suffer whatever consequences await.
Is the world 'fair'? No, absolutely not. But that does not mean that we cannot inspire these kids to be better than that. Lets change the world, 1 person at a time.

If you teach that lying, cheating, and stealing are acceptable ways to get ahead, than that is what these kids will do. I say, take the high road. Show them that lying, cheating, and stealing are wrong and will not be tolerated by our society (in this case, FIRST).


Quote:
Originally Posted by Tom Bottiglieri View Post
What I do not like hearing about is the "vigilantism" that is going on at competitions. I don't care if someone broke every rule in the book... One team has absolutely no right to touch another teams property. Seriously, it's just a game. If everyone could just worry about how much fun they are having rather than how much they disagree with other teams, the program would be much better off.
Here, I completely agree with you. 2 wrongs do not make a right. 'Vigilantism' is just plain wrong. If you see a team not playing by the rules, talk to them. If they dont care, let the proper authority (head referee?) know. Let the system work.
__________________
___________________
"We are not now that strength which in old days moved earth and heaven; that which we are, we are;
One equal temper of heroic hearts, Made weak by time and fate, but strong in will
To strive, to seek, to find, and not to yield. "
- Tennyson, Ulysses
Reply With Quote
Reply


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
Science National Honor Society Alex Burman Math and Science 1 12-12-2005 20:03
where can I find the code for the first 15 seconds? CompMaster Programming 2 16-02-2005 16:23
**FIRST EMAIL**/FamilyFun Magazine Offers Grants in Honor of Families That Volunteer Katie Reynolds FIRST E-Mail Blast Archive 0 15-11-2004 15:59
WRRF Code wrapper for Innovation FIRST Code FotoPlasma Programming 0 02-02-2004 19:28
National Honor Society DaveyPotter144 Chit-Chat 21 19-05-2002 02:24


All times are GMT -5. The time now is 22:58.

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