u/SoManyCrafts wrote (the comment Michael replied to):
We actually do have all of those things at Codesmith as well. There is work done on narratives, there is an entire DSA course (and daily hack hours), there’s a system design section with tons of additional and outside resources. I don’t think you could say they are entirely diffe
u/michaelnovati replied · · edited ★ FEATURED
I chatted with someone about System Design and can use that as an example, please CORRECT ME IF THIS HAS CHANGED AND WILL EDIT IT
​
**Codesmith's System Design**
* 1 week long, fixed classes
* 2 hour lecture from Codesmith staff (not necessarily with industry experience) (entire cohort, 35 people)
* 3 hour working sessions working through problems and materials (unknown size)
* reading materials
**Formation System Design**
* Variable length until you passing system design mock interviews w/ senior/staff/principal level engineers (typically 4 to 6 weeks)
* Specific topics for the following depending on what you need to work on from the previous week, collecting feedback for all for next week:
* 1-2 weekly 1 hour workouts with a senior industry engineer working through a specific problem with 3-5 other Fellows
* 1 weekly 1 hour session reviewing a topic in more depth with a senior industry engineer
* 1 pair session working through a specific problem with another Fellow
* 1 weekly assessment to gather some additional benchmarking based on the areas you were working on
* practice and reading materials
So to clarify a typical person will do approximately:
* 4 to 12 1 hour problem workouts with a senior+ industry engineers with 3-5 Fellows
* 4 to 6 1 hour in depth topic sessions with 3-5 Fellows
* 4 to 6 1 hour pair sessions working through a problem with another Fellow
* 4 to 6 assessments
* 2 to 3 real mock interviews with senior+ industry engineer
* 40 hours of reading, videos, self practice