Re:Overlapping Batches
by xiaoma on Tuesday May 13, 2014 @01:47PM
(#7739541)
This is how Hack Reactor has worked from the beginning. With its success and how well this has been documented around the internet, the Hacker School management most likely knew of it before emulating it now.
As long as there is sufficient staff to handle the increased number of students, I think there are only advantages to having overlapping jr and sr classes. Every student will get a chance both to mentor and to be mentored. Both are helpful for learning.
AppAcademy runs a cohort for 9 weeks of instruction time, then another 3~ish in the job search. They overlap them, so there's a bunch of experienced people to ask questions to.
Really, the best part of overlapping like that is that you aren't just accessing what the last cohort experienced, but the distilled wisdom they got from the cohort beforehand.
Having incoming members talk to existing ones is a very important part of maintaining and expanding institutional knowledge. It's especially important to foster communication in organizations with high churn rates.
Re:Overlapping Batches
by bcgraham on Tuesday May 13, 2014 @02:08PM
(#7739643)
I understood there were three batches of 60-65 people, three times a year, for a total of 180 or so people each year. Now there will be 35 new people every six weeks, for a total of 300 or 320 people each year.
I actually see being in the first rotation as an advantage! I get to start Hacker School with a core group of 35 people. I have an easier time getting to know everyone in the batch and all of the facilitators when there are only 35 of us. Then, after a few months, there are suddenly 70 people and I can see how Hacker School runs with a larger group.
I see being in the first rotation as an opportunity to experience all possible configurations of Hacker School. Furthermore, I'm excited to be able to help shape the culture by virtue of being part of the first group doing it this way.
Re:Overlapping Batches
by nicholasjbs on Tuesday May 13, 2014 @11:15AM
(#7738522)
No, since I expect our next batch will be our best yet.
That said, your point is true in two ways (though I don't think in the way you intended it). First, we try to make every batch better than the ones before it. That implies that it's always better to come to a later batch (I think it's certainly true that it's better to come to Hacker School today than a year or two ago). Second, every batch has been an experiment for us: we make lots of changes (big and small) and we never know a priori how well they'll work.
As long as there is sufficient staff to handle the increased number of students, I think there are only advantages to having overlapping jr and sr classes. Every student will get a chance both to mentor and to be mentored. Both are helpful for learning.
Really, the best part of overlapping like that is that you aren't just accessing what the last cohort experienced, but the distilled wisdom they got from the cohort beforehand.
Having incoming members talk to existing ones is a very important part of maintaining and expanding institutional knowledge. It's especially important to foster communication in organizations with high churn rates.
The total number of students isn't increasing. Two batches will overlap, but the size of the batches has been halved.
I actually see being in the first rotation as an advantage! I get to start Hacker School with a core group of 35 people. I have an easier time getting to know everyone in the batch and all of the facilitators when there are only 35 of us. Then, after a few months, there are suddenly 70 people and I can see how Hacker School runs with a larger group.
I see being in the first rotation as an opportunity to experience all possible configurations of Hacker School. Furthermore, I'm excited to be able to help shape the culture by virtue of being part of the first group doing it this way.
That said, your point is true in two ways (though I don't think in the way you intended it). First, we try to make every batch better than the ones before it. That implies that it's always better to come to a later batch (I think it's certainly true that it's better to come to Hacker School today than a year or two ago). Second, every batch has been an experiment for us: we make lots of changes (big and small) and we never know a priori how well they'll work.