|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
I don't think being a rookie team has any effect on the programmers
Ok I have not shown much enthusiasm about the autonomous kit stuff. Its mostly for those rookie teams I am assuming? Well I am against that whole idea, kind of showing pity towards them... I may sound evil right now, but just because they are a rookie team, that does not mean that they can't compete with he veterans... IDK where this idea came from, but I don't like the kit idea that people are doing. This is not some government run multi billion dollar project... Software pretty much costs $0 for us, its all electrical and mechanic that gobble up the money, I don't get how being under funded rookie has ANYTHING to do with programming... Yea this challenge was for individual teams doing it by themselves, the prize is vanity and pride...
Yes I am a very opinionated guy that is not afraid to speak my mind... Don't hate Last edited by davidthefat : 09-04-2010 at 15:19. |
|
#2
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Often rookie teams lack programming experience and don't know where to start.
It's not even just rookie teams; sometimes teams just have member turnover problems and run dry. This is especially an issue when there aren't any software mentors to make up for it (like on our team). |
|
#3
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
True, but I was a rookie this year, I had no problem learning... Just Look at the $@#$@#$@#$@# API and documents... How is that hard? If you have ANY programming experience, you can easily use the API, its so well named and stuff, I just asked what the things were connected to and Bam, its in the API... People don't realize how important reading documents and the API is... Also the mentors had a "Let all the students do all the work and just assist them" type of mentality, I can say they were great, but they did not needed to help me directly with coding. Just some of my questions on technology
Last edited by davidthefat : 09-04-2010 at 15:38. |
|
#4
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
I truly do not understand why people continue to make the assumptions that people are as capable as them, have as many resources as them, are interested in the same things as them, etc... FIRST teams have diverse memberships, some with no mentors, some with mentors with no engineering experience, some with mentors who have put robots on Mars, some with whatever money they can scrounge, and some with enough money for full time paid mentors. Let's not make assumptions about other teams capabilities and help those that ask for it. I can't tell you how many times I actually helped myself by looking to help others overcome their problems. In complex systems you'll find that answering one issue for someone else may very well help you solve an issue of your own somewhere else. Last edited by sircedric4 : 09-04-2010 at 15:47. |
|
#5
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
I'm obviously bragging, but I wouldn't call either myself or the other programmer geniuses. We're certainly not expert programmers either. We just looked online for examples, copied them, and then dug into the API for more info. That worked for everything except camera code, which was a pain in the rear end, but that's another story. |
|
#6
|
|||||
|
|||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
I don't think that it's showing pity towards them at all. I think that everyone, including veterans, need a 'jumping off place' if you will, each year. The difference between the veterans and the rookies? The veterans have the previous year as a jumping off point, while the rookies do not. Over time, those rookie teams will take the new code that they have created each year, perfect it through iteration, and soon enough become veterans drawing on each year previous for improvement. Quote:
It's not being under-funded that has anything to do with programming, it is the lack of experience. Again, having no experience in this competition is the most relevant handicap (with regard to programming) that a rookie faces. The key to creating a sustainable team that can last until they are considered a veteran is to ease the transition into the competition. You wouldn't give the same job to a wily old veteran with many years experience in engineering as you would a new student, fresh out of school, would you? Obviously, you're going to need to show that new member of the community how to do it (adequately) at least once, and then let them find out through experience. Furthermore, they can build on that experience in the future to form their own methods for achieving the end product, in this case, a solid set of working code. In short, I must say that I disagree, and firmly believe that being a rookie team does have an effect on the programmers, as well as every other member of the team. |
|
#7
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
While I'm not sure I would have said it like that, exactly, I understand where you're coming from here. I've had the same thoughts recently, reading through topics here and interacting with the community. It seems there are far too many projects going on with the goal of eliminating the need for rookie teams to do programming.
It's not that I don't understand the intent of these projects. Many rookie teams don't have a good programming department, or have only one student who is responsible for doing all of the programming. It's nice for these teams to be able to make their robot do basic teleop stuff like driving and kicking/shooting/etc. But autonomous? In my opinion, that's a challenge best left as just that: a challenge. Let the challenge of autonomous be motivation for rookie team members to learn programming and join the ranks of the veterans. As the OP said, unlike the build team, we aren't limited by financial constraints. I'm not saying that releasing SDKs is a bad thing. It's awesome to see how different teams approach problems from different angles, and how unique program designs can make things easier in the long run. And don't get me wrong; 619 has its own framework that we intend to release later in the year. But perhaps we should be writing these frameworks not with the goal of making them "so easy to use a rookie can do it," but with the goal of helping motivated rookie team members learn effective program design as quickly and efficiently as possible. Rather than doing everything for them in some sort of black box, give them a nice inheritance tree to play with - one that effectively shows the benefits of oop while requiring the team to implement these concepts by extending the code given to them. Or provide a nice event handling system that shows teams how event-driven programming works while still requiring them to write, instantiate, and order the events. Right now, it's almost to the point that a team can call, "driveForward()," and the robot drives forward, and IMO that does not teach programming skills. One example of what I would say is going too far is "converting" other teams' code to a veteran framework without them explicitly asking you to do so. Sure; after spending a season designing an awesome autonomous framework you may think it's the end-all-be-all of FRC programming, and that you're doing every rookie team a favor by "porting" their code. But what seems like the best solution to you may not be the best solution for everyone - remember that, because you designed the system, your opinion of it is inherently biased. What if a rookie team would rather learn how to design an effective autonomous solution, rather than just letting another team do it for them? What if ease-of-use isn't the only concern here? And that's assuming your system even is the easiest to use; some of the SDKs I've seen around here look like they would make it harder than the default code to do anything more complex than simple driving, especially when they lack comprehensive documentation. Note: the above is not directed to any one team or framework. I've seen at least four or five teams releasing SDKs with the specific goal of reducing the number of lines a rookie has to write as close to zero as possible. Overall, I think the releasing of frameworks is fine, and it's certainly a great exercise for veteran teams doing the development. But teams need to keep in mind that their goal should be to help rookies learn how to program - not to do it for them - and that a system's users view that system very differently than the system's designers. That is all. Last edited by FRC4ME : 09-04-2010 at 15:50. |
|
#8
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
Of course you need to show them how to do it once. What concerns me about many of the veteran frameworks going around is that they take a "black box" strategy; rather than showing rookies how to do it, they try to remove the need for a rookie to learn how to do it. That, IMO, is a poor strategy. Perhaps I'm just misunderstanding how many of the SDKs work; I haven't personally used any of them but have only read their project description pages. Last edited by FRC4ME : 09-04-2010 at 15:49. |
|
#9
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
I do not see how a rookie team can "graduate" from the rookie status using development kits released by veteran teams... You are just keeping them there pretty much, they don't get the same experience and they need it too.
|
|
#10
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
Even more so, that how Autonomous Independent is called is by a reference somewhere you wouldn't normally look. I talked to a programmer at a regional who used Autonomous Iterative as his Autonomous Independent because he didn't see where Autonomous Independent was called in Robot Main. Last edited by kamocat : 09-04-2010 at 16:16. |
|
#11
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
Last edited by 45Auto : 09-04-2010 at 17:12. |
|
#12
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
Last edited by davidthefat : 09-04-2010 at 17:38. |
|
#13
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
Also, it is technically illegal to not make these resources available to the rookie teams if you make it in the offseason and intend to use it on your robot
|
|
#14
|
||||
|
||||
|
Re: I don't think being a rookie team has any effect on the programmers
Quote:
That said I don't really think one can expect the same from every rookie team as from a strong established one. |
|
#15
|
|||
|
|||
|
Re: I don't think being a rookie team has any effect on the programmers
Also I would like to ask what makes a team reach a "veteran" status?
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Any Programmers Have The Same Feeling As Me? | davidthefat | Programming | 23 | 16-01-2010 22:07 |
| Poll:What do you think the effect of G14 will be? | Bongle | Rules/Strategy | 19 | 17-01-2009 08:45 |
| Attn. Rookie Teams: Don't go quite to the max dimensions | sanddrag | Technical Discussion | 10 | 11-01-2007 12:54 |
| Has any one used Easy C and what do you think? | N3OW | Programming | 2 | 10-01-2006 16:31 |
| What do you think about the nationals being at Texas? | Hailfire | General Forum | 1 | 05-12-2002 19:42 |