u/DentistRemarkable193 wrote (the comment Michael replied to):
That’s nice that they offer coverage. Do you know if instructors mentor TA’s onto system architecture & the codebase? Is there enough there to even require an entire company’s engineering staff working on it? Maybe I’m missing something, but overall, it seems pretty simple to me.
u/michaelnovati replied · ★ FEATURED
I haven't seen a concrete trend myself. The instructors haven't worked in industry (only a handful ever had but all but one were return Codemsith alumni) and Codesmith's codebase can best be described as a big OSP project and in some cases, some OSP projects have had more people touching their code than the Codesmith codebase. Based on the problems with some of the largest OSP projects which have their history plain for all to see, you can imagine the problems with Codesmith's codebase.
I haven't seen Codesmith's codebase but just heard casually from people who worked on it and from people who saw this system design talk and approached me about it.
If you've talked to alumni about the big OSPs you'll hear about how each new group tends to fail to understand the existing codebase and instead just builds something new. For example, a project containing 2 primary UI frameworks because a new OSP group didn't understand the current one.
From what it sounds like, the Codesmith codebase is the same. New people don't understand and don't have time and don't have experience or training to be able to understand anything beyond a tiny codebase, so people kind of slap on their new feature so they can add it to their resume. This theory would explain 32 boxes and services for a system that needs one box.