Hours worked

[Jon Stratis]

I've been logging my hours for the first time this year, as my new company does verification for the PVSA . Assuming we bag at 9 PM TONIGHT like we plan, I'll have put in 171 hours during the build season. I should easily break 300 hours by the time we hold our end of the year banquet, and probably break 500 hours by the end of the calendar year.

[techhelpbb]

We either need to automate FIRST or automate our jobs more.
Then we can all marvel at the quality of the time spent instead of the quantity.

[Foster]

One year when I was doing both FRC and VEX I tracked 1200 hours in a single year. The real killer for time was events, show up at 7AM, leave at 10PM, four/five days in a row.

[GeeTwo]

Our team does track student time at the build site, though I don't keep the records. We have had six sessions of about six hours and about 15 three hour sessions, plus the 13-hour wrap-up session, for a total of 94 "whole team" sessions, which had an average of about 30 students and six mentors. Programming had a couple of six-hour sessions which had about eight students and one or two mentors. I get something like 3000 hours at the build site. Then there's the out-of-shop thinking, research, engineering, planning, buying, prototyping, programming, and scouting. My estimate is therefore 3946 hours.

[TCMJ1816]

Just ran the calculations for myself, I'm somewhere around 250 hours in the shop this build season. Taking a day off then its back to driving practice at 30 hours a week until at least week 6.

[stingray27]

I remember my senior year (which was the 2013 season), me and a few other members passed 500 hours each by week 7 of competition season. We have a time clock where we clock in/out and my exact number was 504 hours.

[seg9585]

I log hours volunteered to my company can provide a donation to the team.

Logged approx 175 hours from July-December 2014 running summer workshops, planning training sessions and a preseason build, and running 2x/week training sessions + mock kickoff.

Logged 168 hours from Jan 3 - Feb 13. Will be 40 more hrs Feb 14-17 (208 total). Then at least 2 competitions after that..

So that's approx 400-450 hrs/year

Yep, definitely don't have a life outside of robotics during build season, haha

[jagoldman]

My school has required sport credits and two years ago we got recognized. We require 110 hours to get the credit, but by the end of the build season the core group (including myself) easily surpass 200 hours. It is also easily the best 200 hours spent!

[The_ShamWOW88]

We're so small now compared to 10+ years ago (roughly 25 students) so we tend to know who's showing up and who isn't there.

We meet 4 days a week to try and not get burned out too quickly. Sometimes it works against us as we end up working 6 to 7 days a week in Weeks 5 and 6 but this year, we did pretty good with our timelines.

[Henksta]

We also clock in and out. Each kid ranges from 75 to 120 hours for the whole build season. Our team has somewhere around 25 students on our team so our total is > 1875 and the total is < 3000.

[mabster314]

This year, the students of team 2175 clocked a total of 4229:48:12 (hhhh:mm:ss) person-hours, or 176 days 5 hours 48 minutes 12 seconds, not including times where they forgot to clock in or out. Many of the people in the shop most often stopped clocking after they hit the lettering requirement of 120 hours, and mentors didn't clock, so the actual amount is actually significantly higher

[Jacob Bendicksen]

Team 1540 collectively spent 3100 hours in the lab in the past six weeks, not including mentors or people forgetting to log in/out. This works out to just under 100 hours/person.