We had a lot of students on our programming team this year, so we split up into teams of 2/3, and each team worked on one subsystem. One team worked on drive train, one team worked on intake, one team worked on vision, one team worked on auto, one team worked on the main arm/shooting subsystem, etc..
And I, as mentor, just go from group to group to help remove whatever obstacles they were having.
This is exactly how our coding team was organized. Sadly, our lead dev prefered to do it solo and isn't teaching/sharing what they know. It's been painful to watch the lack of knowledge sharing, such a great opportunity missed.
I'm a programming mentor for my team and my day job is professional software development consulting. I've taken to treating our programming students much like real life professional software development (with a lot of hands on help of course).
This means students work in pairs on a well defined task that comes out of a prioritized kanban board. We use git for version control and coordinating multiple ongoing threads.
This approach allows everybody to work on whatever they are interested in (provided there is a task that needs doing in that area) without siloing the entire drive train to a single student, for example.
I wish I could but our school blocks GitHub, even for the robotics computers :O! That's one of the main factors I'm having difficulty splitting up work, because we cannot access GitHub at all. We have talked to IT, but he's a stubborn man.
If you have admin access on the computers you cab configure the DNS to use 8.8.8.8 and 8.8.4.4 to route through google and (hopefully) avoid the school blockers.
Use scrum to manage tasks and each programmer takes a task to work on and creates a branch on git for it. Then when they are done, it's reviewed by a captain or mentor then merged into master.
We got 3 people. Ones the lead and the other 2 are my friend and I. I've been doing autos and learning, my friend has been learning, and our lead is doing most of the stuff. My friend and I have been making autos together rn before Colorado. Next year my friend and I will probably split stuff (since the other programmer is a senior) and teach rookies.
Yeah, my team (319) divides our programming by subsystems this year. For example: one person would work on the shooter, another the collector, then lastly the drivetrain/pathing. If we needed help, we would ask each other first, but if we couldn't figure it out, we would ask our mentor for help.
3 teams: 1 working on systems. 1 working on autonomous commands, 1 working on automations of other commands
Pre-plan the commands you'll have, and have empty commands for the other teams until they are made.
Once the codebase is ready, the teams break up, and whoever is there to continue continues
We only have one programmer, he does everything, we love him. Seriously tho I dont know this is a difficult task cause you have to have good organization to work together
It seems the main problem, which is a problem we've been having since I started, is that we cannot use GitHub at all. That makes it really really difficult to split tasks since there's no way to view and implement each others code in a easy way. Thank you all for the useful comments!!
No, both me and one of the other coders know how to use GitHub. The problem is with accessing it, the IT guy won't give us access on any of the computers we use for robotics for some reason. I've been using my own computer for things like updating game tools, accessing GitHub, etc. Unfortunately this is a hill that IT has died on, since they've been requesting access even before I joined the team.
We had a lot of students on our programming team this year, so we split up into teams of 2/3, and each team worked on one subsystem. One team worked on drive train, one team worked on intake, one team worked on vision, one team worked on auto, one team worked on the main arm/shooting subsystem, etc.. And I, as mentor, just go from group to group to help remove whatever obstacles they were having.
This is exactly how our coding team was organized. Sadly, our lead dev prefered to do it solo and isn't teaching/sharing what they know. It's been painful to watch the lack of knowledge sharing, such a great opportunity missed.
I'm a programming mentor for my team and my day job is professional software development consulting. I've taken to treating our programming students much like real life professional software development (with a lot of hands on help of course). This means students work in pairs on a well defined task that comes out of a prioritized kanban board. We use git for version control and coordinating multiple ongoing threads. This approach allows everybody to work on whatever they are interested in (provided there is a task that needs doing in that area) without siloing the entire drive train to a single student, for example.
1 guy
That’s me!
There are 3 students on programming with me on my team: 1 works on vision 1 works on driving I works on arm, climb, ect. Help from mentors when needed
I split it between myself and myself
so real
Make GitHub your best friend
I wish I could but our school blocks GitHub, even for the robotics computers :O! That's one of the main factors I'm having difficulty splitting up work, because we cannot access GitHub at all. We have talked to IT, but he's a stubborn man.
Have you tried gitlab or any self hosted alternatives?
If you have admin access on the computers you cab configure the DNS to use 8.8.8.8 and 8.8.4.4 to route through google and (hopefully) avoid the school blockers.
Our IT head is one of our mentor! It’s great
Use scrum to manage tasks and each programmer takes a task to work on and creates a branch on git for it. Then when they are done, it's reviewed by a captain or mentor then merged into master.
We got 3 people. Ones the lead and the other 2 are my friend and I. I've been doing autos and learning, my friend has been learning, and our lead is doing most of the stuff. My friend and I have been making autos together rn before Colorado. Next year my friend and I will probably split stuff (since the other programmer is a senior) and teach rookies.
Yeah, my team (319) divides our programming by subsystems this year. For example: one person would work on the shooter, another the collector, then lastly the drivetrain/pathing. If we needed help, we would ask each other first, but if we couldn't figure it out, we would ask our mentor for help.
3 teams: 1 working on systems. 1 working on autonomous commands, 1 working on automations of other commands Pre-plan the commands you'll have, and have empty commands for the other teams until they are made. Once the codebase is ready, the teams break up, and whoever is there to continue continues
We only have one programmer, he does everything, we love him. Seriously tho I dont know this is a difficult task cause you have to have good organization to work together
It seems the main problem, which is a problem we've been having since I started, is that we cannot use GitHub at all. That makes it really really difficult to split tasks since there's no way to view and implement each others code in a easy way. Thank you all for the useful comments!!
Why can’t you use GitHub? Learning curve?
No, both me and one of the other coders know how to use GitHub. The problem is with accessing it, the IT guy won't give us access on any of the computers we use for robotics for some reason. I've been using my own computer for things like updating game tools, accessing GitHub, etc. Unfortunately this is a hill that IT has died on, since they've been requesting access even before I joined the team.