Shared Review

• Codesmith

  An incredible learning community

  - 2/8/2019

  

  Lee Rogers • Graduate • Course: Software Engineering Immersive Program • Campus: Los Angeles • Verified via GitHub
  An incredible learning community

  Overall Experience:

  Curriculum:

  Instructors:

  Job Assistance:
  I had a very good experience at Codesmith. There were a few areas where I personally saw some room for improvement, which I will discuss below, but overall it's certainly an excellent program. Here are my thoughts on its strengths as well as just some things to be aware of as you decide if CS is right for you.

   

  First off, the culture at CS is amazing. Everyone is super friendly and supportive of each other as they go through this sometimes stressful/intense learning process. While I feel lucky to have worked with such a great group of people at CS I also know it wasn't luck: CS takes an active role in shaping the culture, carefully choosing who to admit and then setting expectations about being empathetic and putting others before yourself. From there it takes on a life of its own, as the positive energy creates more positive energy. You will work many long, difficult hours at CS, but it won't really feel that way because it's such a supportive, fun environment to be in. The importance of this cannot be overstated.

   

  The other remarkable thing about CS, and this actually encompasses a range of topics, is how great it is at dealing with all the intangibles around coding and finding work. It's about turning you into a software engineer, which means shaping who you are as a person. They help you manage 'imposter syndrome,' while learning to accept and embrace the struggle that comes with working on difficult challenges. Beyond that they offer a lot of great advice on how to present yourself to maximize your odds of finding a good job, and what employers are actually looking for (as distinct from what they might say they are looking for), helping you to present yourself as that perfect 'fit.' There's a lot about managing people's perceptions... part of that is, frankly, helping you create the impression you have more experience/expertise than you actually have, without actually lying. If you wanted to be cynical you could call this deceitful... But let's be honest: this is the real world we live in. It's not fair, and people often make decisions for shallow, unconscious reasons. CS helps you find every possible way to prime employers' expectations to see you in a certain light and tip the odds of success in your favor.

   

  As we learned these psychological tricks I couldn't help but consider how the CS program was also trying to shape our own perceptions as students. They try to make you feel that upon leaving CS you are now ready for top-level coding jobs... somewhat regardless of where you may actually be in terms of your skill/knowledge level. I think the thinking behind this is that employers are hiring people based on subtle cues that they pick up from the applicant, and that if you are confident in your abilities they will pick up on that and will be more likely to hire you.  (And after that, you'll figure it out... It's what you did at CS after all.)  For this reason it's important that you see yourself as an advanced level engineer, and truly believe it. If you believe it, it will become true. Indeed every step of your journey at CS is about convincing you to believe in your own abilities.  

   

  Codesmith has a very specific teaching style, which they use in a sort of one-size-fits-all kind of way... Essentially they don't really 'teach' at all, but rather have you figure it out yourself. They feel strongly it's the only way to really learn this stuff. During the first part of the program there are lectures to provide a super high level overview of material (for example, the purpose of a framework) without getting into any actual specifics about the code. You are paired with someone to work on a related challenge and the two of you basically try to figure it out together.  This often involves using online tutorials or Youtube videos or whatever to try to figure out what's going on. In that sense you might think, "well this is what I was already doing before I came to CS!" 

   

  There are a few important differences though: You will work way harder than you would on your own, and you will be working alongside a great group of students in the same boat, all helping each other. Certainly no 'meetup' could substitute for the community of learners you'll find yourself working with at CS. So it's more that CS is providing an optimal environment for learning than it is that they're teaching you, per se. The students who figure things out first often end up showing the others what to do, so actually it is your classmates that do most of the 'teaching' in that regard... I think those students probably get the most out of the program, as teaching others is the best way to solidify one's own understanding. 

   

  It's worth noting that Codesmith is really not at all like the Hard Parts lectures. Those involve getting into the nitty-gritty of javascript, with the teacher typically asking lots of questions to students, really keeping you on your toes and making sure you're following along. (Will Sentance, the co-founder of CS, is particularly great at this) When I did the Hard Parts I thought "Aha! This is exactly what I need!" In the program itself, however, teachers don't really call on students much or get into many details.  It's more: here's a slide show for a high level overview... now go figure it out. One advantage of this is it's how the real world is: no one will be holding your hand. If you can do it here, you will be able to do it out there as well. But it can also be frustrating, especially if you were expecting to be taught how to code.

   

  Having worked as an educator, the traditional conception of education has three basic steps: the teacher shows students how to do something, the teacher assists as students try it themselves, and finally the teacher has students do it all on their own without help. (aka "gradual release of responsibility")  Udemy classes and other online tutorials typically don't get past step one, which is a major limitation on their effectiveness.  Codesmith, on the other hand, pretty much just skips straight to step three. It's basically a "sink or swim" approach.

   

  They emphasize that if you are struggling that is itself a success: You are training yourself to keep trying and not give up even when you feel stuck. ("Building that muscle") And I think there's something to that: Surely a big part of what employers are looking for is people with the patience, persistence and determination to work through difficult challenges. It can be frustrating though when you feel lost, because no one's going to really make sure you're getting it. Personally I found myself struggling a lot. 

   

  During the first part of the program Mondays start with an assessment that tests your understanding of the previous week's material, which you will then hear back about on Saturday. If you did not do well someone will go over the assessment with you before you leave for your (one day) weekend. Those one-on-one sessions can be very helpful... I would actually say those were some of the most productive times for me at CS in terms of furthering my learning. I do wish they had occurred in a more timely manner though.

   

  The latter portion of the program is basically all group work on projects. If you know enough to be able to contribute you can learn a lot because it's real coding, and the things you learn along the way, as you hit blocks and work through them, will likely stick. Personally I think I would have benefited more from more structured lessons, along the lines of Hard Parts, that drilled in all the basic skills until they're second nature, with such lessons gradually giving way to more independent work... rather than just being set loose on these big projects. "Rote learning" is not sexy by any means, but I actually felt CS could have used some of it.  There's just a lot of vocabulary and syntax you need to know. It seems like a 'boot camp' environment would be the ideal environment to really drill that stuff in.

   

  The CS curriculum provides a brief introduction to a number of coding areas, but they keep things moving along quickly. They want to get you working on the deep stuff that's going to look really impressive on your resume as soon as possible.  This points to an important distinction: the goal of CS is to not exactly to teach you how to code, but to help you land a great job. The two goals are of course related, but where they diverge CS is focused on the latter.  They want to help you come off as that 'rare unicorn' who has somehow taken to coding so naturally you could instantly move into working in super challenging areas. Employers will be so impressed at the challenges you've been pursuing that they will just assume you must also be solid on all the basics.  

   

  And, frankly, if you had to choose between being great at coding and having a great coding job, which would you choose? Probably the latter... the reason you want to be great at coding is probably so that you can get that great job. Well that's exactly what CS is going to help you do.  Along the way you will pick up some coding skills, but the idea is that once you get that great job you will essentially be able to figure out what you need to know on the job. This will be possible in part because you have confidence in your own ability to figure out whatever challenge is thrown at you. And in truth the coding skills required for success will constantly be changing as technology evolves anyway, so knowing particular skills is less important than having the confidence, patience and persistence to figure things out. So, the focus on just landing the job does make some sense.

   

  The mantra from CS instructors is 'trust the process,' basically implying 'we've got this figured out.' Along with that is the implication that the process only works if you 'trust' it... that is, you believe it will work. Apparently there was one cohort where one student felt strongly that Codesmith's approach to teaching was wrong and who managed to convince the rest of his cohort of this.  This cohort didn't get as much out of their time there and was then significantly less successful in finding work after graduation than other cohorts. I can believe it. So much of life is about attitude, beliefs, expectations, etc. So it makes sense that CS is very vigilant about keeping everyone onboard the program and clamping down on any sort of negativity or 'dissent.'  I think this is done with the best interest of students in mind. 

   

  Where it becomes a little tricky is if it doesn't allow for the curriculum or teaching methods to be questioned, thereby preventing improvements. I feel like more could be done to make sure everyone is progressing and to find ways to meet the needs of different types of learners. At no point, for example, do they ask students for feedback about how the program could be improved, which surprised me (also true for CS Prep, btw). I think they just don't want to encourage any negative thinking about the program, so that everyone will feel like they got the best possible education and therefore go into the job hunt with confidence. It's understandable, but I think they'd be able to make the program even better if they were soliciting constructive criticism to guide future iterations on the curriculum.

   

  Despite these concerns my experience at CS was overall very positive. Hopefully this provides a realistic sense of what Codesmith is all about to help you decide if it's right for you. While I heard other students privately raise some of the same issues I never once heard anyone say they regretted their decision to enroll. A number of people went so far as to describe it as a life-changing experience even. 

   

  Personally if I had to go back and decide whether to do it over again I think I would, BUT I would wait and spend more time studying before enrolling. I enrolled as someone without any computer science background, really only having done some Udemy classes, the Hard Parts lectures and CS Prep.  I knew the CSX material backwards and forwards and could write a 'reduce' function in my sleep, but I didn't know much beyond javascript. In retrospect I wish I had been more comfortable writing CRUD apps (if you don't know, look it up) before I got to CS, so I could spend less time learning the basics and more on the advanced features we were supposed to be working on. 

   

  As it was I spent a lot time during the day struggling with things far over my head, often feeling like I was spinning my wheels, while spending nights trying to catch up on the basics. I certainly learned WAY more than I would have just studying on my own for those 13 weeks. Coming out of it, though, I'm currently working on solidifying the skills I was introduced to at CS, that are listed on my resume, so that hopefully I will feel comfortable using/discussiong them in an interview situation. That's not exactly where I was hoping to be at this point, although I'm optimistic I will get where I need to be.

   

  I would especially recommend Codesmith to people who already have some computer science experience, whether from school or work. It is possible to come in relatively 'cold' and succeed (I saw people do it), but it's much harder. I would at least find out the frameworks/technologies/etc covered in the curriculum and try to do a Udemy class or something on each one before starting the program. You're going to be figuring most of it out yourself anyway, so might as well get a head start on that. 

   

  I am a very recent graduate and have yet to really begin my job search in earnest... So far the job search support does seem very good though. They definitely don't just forget about you after you're "done." If things go as they say to expect and I eventually land the kind of job they are saying we should be able to get, then by all means this program will have been worth every penny and more. Certainly many alums have done very well. 

   

  Overall, if you are looking to do a 'boot camp' style program (a term they don't actually use, btw) you should definitely consider Codesmith. It's not a boot camp in the sense that they're going to drill coding skills into you, but it is in the sense that it aims to shape you as a person, instilling you with confidence and a problem-solving mindset. They encourage you to think like a software engineer, and think of yourself as a software engineer... confident you can figure out whatever's thrown at you, because you've done it before. The idea is that if you can make that paradigm shift in your head, the rest (i.e. learning specific skills) will follow in due course.

   

  And in the process you will become part of a great community. It's a sometimes stressful, even grueling experience... but one that's also full of a lot of joy, camaraderie and discovery.  I know it's a time in my life that I will always remember fondly.

  This Review Is Helpful2

  Flag as inappropriate.

  Read More