|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
FRC booK behind the design
Does anyone here wish that FIRST would of kept going with the books that they made for 2006 and 2007 season, that had the team that had won certain engineering awards, and they showed what the teams did and thier process
I wish FIRST could start that again, i really enjoyed the books. Does anyone know why they stop |
|
#2
|
||||
|
||||
|
Re: FRC booK behind the design
I think enough copies weren't purchased to make a profit. I personally found them very interesting and helpful.
-Nick |
|
#3
|
||||
|
||||
|
Re: FRC booK behind the design
I am pretty sure the issue is someone needs to step up and do it. It is a huge amount of work and the authors of the previous efforts are super busy with other things.
|
|
#4
|
|||
|
|||
|
Re: FRC booK behind the design
It is a huge amount of effort. I'll poke the guy and see if I can get an update.
|
|
#5
|
||||||
|
||||||
|
Re: FRC booK behind the design
Here is what the Author, Vince Wilczynski, said in 2008:
Quote:
|
|
#6
|
||||
|
||||
|
Re: FRC booK behind the design
Quote:
In order to help move the process along, maybe the author becomes more of an editor. Teams can submit, or be invited to submit, high resolution photos and a substantial written narrative. The editors can pick which submissions will make the final copy, and re-write the narratives to align it with the production standards. Maybe Vince could be convinced to be Editor-In-Chief, and he can direct a team of editors to manage the process ? The e-book could have a standard template format for the whole production, and a template for a 1/2, 1 or 2 page team spread that focuses on a the teams effective design or strategy. The teams could submit a design or be invited to submit a design. It doesn't necessarily need to be a winning design but an effective design with merit. In other words there needs to be some editorial rigor to the process and not just a collection of not too useful information. I'm game. 2 cents. |
|
#7
|
||||
|
||||
|
Re: FRC booK behind the design
Count me in, too!
We have a great photography and writing team, and would be happy to assist. We have also published a couple of children's books, and are in the process of converting to e-books, so see that would be a great avenue for the behind the design series. Just my 2.71828... cents. Steve |
|
#8
|
||||
|
||||
|
Re: FRC booK behind the design
Quote:
http://frc-designs.com/btd.html Last edited by Starke : 01-10-2012 at 11:56. |
|
#9
|
||||
|
||||
|
Re: FRC booK behind the design
Quote:
Send me an email and we can get started! Looking forward to it! Matt |
|
#10
|
||||
|
||||
|
Re: FRC booK behind the design
I suggest FRC Designs launched Behind the Design and the e-book complement each other.
The e-book can be an electronic 'coffee table' e-book. The website can then have information in depth, and more.... |
|
#11
|
|||
|
|||
|
Re: FRC booK behind the design
I'd love to see something similar in concept to http://www.aosabook.org/en/index.html — but with teams and designs, rather than open source projects.
|
|
#12
|
||||
|
||||
|
Re: FRC booK behind the design
We (2338) own both books (at least 2006...). We often refer back to them for inspiration throughout the build season.
|
|
#13
|
||||
|
||||
|
Re: FRC booK behind the design
Still bummed 116 couldn't submit in 2007. We only attended one regional, and ended up with a Judge's Award for both our robot and outreach efforts, rather than a technical award so we weren't eligible to submit.
![]() |
|
#14
|
||||
|
||||
|
Re: FRC booK behind the design
Quote:
Matt |
|
#15
|
||||
|
||||
|
Re: FRC booK behind the design
The quality of the submissions is the important factor in success of a project like this. The books were awesome because teams took some time to provide good raw material, and Vince & Stephanie took the time to polish up some fantastic final chapters.
It is easy to say "we should do this! We'll post it on XXXX site!" but without the quality articles, this is just talk. How many teams take the time to create a submission worthy description of their robot and publish it? Overall system details? Details of subsystems? Documentation of iterations? Post-Mortem Analysis? This is a very chicken/egg discussion in my book... -John |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|