Go to Post Being the GDC is not an easy job, anything can happen. Lunacy happened ::rtm:: - Conor Ryan [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 03-12-2016, 11:04
Harman341 Harman341 is offline
Registered User
FRC #0341 (Miss Daisy)
Team Role: Alumni
 
Join Date: Feb 2014
Rookie Year: 2013
Location: Philadelphia
Posts: 34
Harman341 is a glorious beacon of lightHarman341 is a glorious beacon of lightHarman341 is a glorious beacon of lightHarman341 is a glorious beacon of lightHarman341 is a glorious beacon of lightHarman341 is a glorious beacon of light
Re: Advice for new Technical Lead

I had a similar position on 341 my senior year and found out at roughly the same time (one week before build season)

My tips:
Watch gamesense's video on how to prototype, it's life changing.

If you think someone's idea is dumb, you probably don't understand them

Try your best not to build anything without teaching someone what you're doing

Always remember, as a build team leader, you have a lot of credibility. If you are about to do something stupid, nobody is going stop you.
-watch MAR champs F2, it was my idea to try hanging on one hook

As a follow up, don't worry about getting more credibility, you already have plenty, feel free to admit mistakes or that some/most of your ideas are bad.

If you need a good idea, watch videos of old matches

Always keep an eye on the room, who is there, who isn't, who looks like they're not contributing, who looks bored, who is telling the rookies to sweep the floor while they build fancy stuff. Those are all easily solvable problems, but addressing them can really change your team for the better.

Lastly, my biggest regret, it was said before, but it can't be said enough, ask your mentors questions. Here's why:
1-It makes them feel respected
2-You two will become friends
3-They will be happy that they taught someone about robots
4-You will learn about robots
5-You are less likely to do the stupid thing that everyone was going to let you do
6-Mentors also do stupid things, being friends makes it easier to stop them
7-Newer members will see you asking questions and do the same

Making this thread was a great start to your new job. Keep it up and you'll be fine.

Last edited by Harman341 : 03-12-2016 at 11:08.
Reply With Quote
  #2   Spotlight this post!  
Unread 04-12-2016, 12:15
DonRotolo's Avatar
DonRotolo DonRotolo is offline
Back to humble
FRC #0832
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Atlanta GA
Posts: 6,979
DonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond repute
Re: Advice for new Technical Lead

Delegate.

Surround yourself with teammates who know what they are doing, and let them do it. Learn from them and teach them, as needed, but let them 'own' their subsystem and be the expert.

This is how projects work in the real world: The Lead just keeps things moving and helps overcome problems, but doesn't actually own any of the subsystems. They're the players, you're the waterboy. Bring them water.

Your team has the depth and breadth of talent where this will work. A very small team may need something different.

Have fun, and please let us know in March how it worked out for you.
__________________

I am N2IRZ - What's your callsign?
Reply With Quote
  #3   Spotlight this post!  
Unread 04-12-2016, 12:37
Conor Ryan Conor Ryan is offline
I'm parking robot yacht club.
FRC #4571 (Robot Yacht Club)
Team Role: Mentor
 
Join Date: Nov 2004
Rookie Year: 2004
Location: Midtown, NYC
Posts: 1,889
Conor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond reputeConor Ryan has a reputation beyond repute
Re: Advice for new Technical Lead

Your success as a technical lead is not judged based on your performance this season, but on the success of the team in the seasons following your graduation.

Take time to ensure as many people as possible are engaged and helping the team move forward, the more leverage and man power you create the more your team will accomplish.
Reply With Quote
  #4   Spotlight this post!  
Unread 04-12-2016, 13:18
billbo911's Avatar
billbo911 billbo911 is offline
I prefer you give a perfect effort.
AKA: That's "Mr. Bill"
FRC #2073 (EagleForce)
Team Role: Mentor
 
Join Date: Mar 2005
Rookie Year: 2005
Location: Elk Grove, Ca.
Posts: 2,349
billbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond reputebillbo911 has a reputation beyond repute
Re: Advice for new Technical Lead

There has been a lot of excellent advice given thus far, I don't want to change any of it.
I will add: As tech lead, you will need to guide you team through successes and failures.
Successes are easy, identify what you did right and repeat it (or even improve on it).

Failures are even better. Yes, I did say that and I believe it.
We as humans always seem to learn more through failure than success.
Do this by anylizing the failure and don't repeat it. Figure out what caused it and figure out how to prevent it from happening again. Many times you will find that what you figure out will allow you to improve way more than your original approach would have yielded.
This applies to more than just design, it applies to strategy and game play too.
__________________
CalGames 2009 Autonomous Champion Award winner
Sacramento 2010 Creativity in Design winner, Sacramento 2010 Quarter finalist
2011 Sacramento Finalist, 2011 Madtown Engineering Inspiration Award.
2012 Sacramento Semi-Finals, 2012 Sacramento Innovation in Control Award, 2012 SVR Judges Award.
2012 CalGames Autonomous Challenge Award winner ($$$).
2014 2X Rockwell Automation: Innovation in Control Award (CVR and SAC). Curie Division Gracious Professionalism Award.
2014 Capital City Classic Winner AND Runner Up. Madtown Throwdown: Runner up.
2015 Innovation in Control Award, Sacramento.
2016 Chezy Champs Finalist, 2016 MTTD Finalist
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


All times are GMT -5. The time now is 18:28.

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