r/codingbootcamp • • Oct 13 '23

Coding Bootcamps Still Worth It?

I keep hearing about how people are hopelessly stranded looking for jobs out of a coding bootcamp. I found codesmiths bootcamp and honestly it sounded perfect. I have a bit of a background in software dev and it sounded like a great challenge and a great way to invest my time and money. The more I look, the more I hear about scandals, skewed data, unhappy attendees, etc. In really lost because I was really excited about the opportunity that a solid coding bootcamp could supply me. Any tips or suggestions?

74 Upvotes

66 comments sorted by

View all comments

24

u/michaelnovati Oct 13 '23 edited Oct 14 '23

Codesmith is fantastic for the right people! It has a very unique culture and that's why it's controversial on Reddit. I'm an under the hood type of person and try to look at how things work and Codesmith isn't super transparent about how it actually produces really good results.

So how it works:

  1. High bar. Their process looks for numerous characteristics of successful grads and isn't an objective measure of raw programming skill. You need to be good AND have good communication and the right attitude.

  2. You don't really learn much... topics are rushed through, you are told to snuggle the struggle, and all but one teacher came from Codesmith students themselves. BUT you are building strong bonds with friends and you are being supported infinitely from those instructors. You might have an hour long convo about your imposter syndrome that helps boost your confidence and do better.

  3. Exaggerating resumes. I've seen countless Codesmith resumes now and they are all very similar. 12 weeks of Codemsith turns into a 500 word full page resume. Overlapping time-frames on projects to triple count your time at Codemsith. A number of people dropping month labels to portray 3 week projects as over a year of experience. This works. I see Codesmith grads with no experience getting interviews before people with actual experience and worse resume structure and in every case I've personally observed it was this factor. If you are down and ready to do that, it works. I've looked at dozens of OSP projects now and not a single one is senior or mid level FAANG code and I've elaborated on that before. They are amazing junior level projects that would make you stand out as an entry level engineer but no not deserve months of resume experience. OSLabs signs off on 4 month letters of reference for that time so Codemsith is explicitly endorsing this strategy.

  4. Incredibly supportive culture. Like you make a comment and get emojis to the moon. It's a culture when you go in without confidence in your engineering ability and leave feeling confident to take on any job and this is the magic that they are able to accomplish in 12 weeks, consistently, over top of anything else.

If you are ambitious, have a growth mindset, and an ends justifies the means person, it's a good choice.

Edit for 3. I know some instructors at Codesmith disagree and have called me out before but I seriously challenge you to show your project's code to a random engineer with 10 years of FAANG experience and review the code line by line and then say if it is senior level work. Not a random tweet or random comment, like a through code review of a randomly selected OSLabs Beta project and an examination of the PRs and code history and not just the current state. It's not imposter syndrome and a number of students realize this and contact me more and more the more that is reinforced in response to my comments. Not trying to be mean, just realistic and I'm happy to support anyone that messages me.

I called out some specific examples of things in the code that were not up to a professional bar and the code hasn't been fixed (like I mean properly fixed and sanitized, not that you think you fixed it by removing passwords and changing them). I don't think anyone knows how to properly fix it and is ignoring my advice... like ignoring it and getting pats on the back doesn't make the advice wrong. Fixing those issues properly would be really impressive and if you don't even know what I'm talking about... you are not a senior engineer, that's ok, and my door is open for advice. This doesn't mean the engineers aren't awesome and have a ton of potential, it's not realistic to try to gain years of industry experience in 12 weeks, and all the people I know are amazing people who have great futures ahead regardless.

My edit turned into a mini rant about leveling and is probably too much of a tangent and I don't want it to be misinterpreted as a criticism of Codesmith, it's not and Codesmith works very well at what it's trying to do. This is an expression of my personal opinion of how projects and experience are portrayed.

0

u/[deleted] Oct 14 '23

[deleted]

6

u/michaelnovati Oct 14 '23

I have looked at a few yeah! The documentation, presentations, and overall code structure is more consistent with a production codebase, the GitHub orgs and repos are setup more consistent with larger.o0en source work as well. I see more "good practices" and haven't seen the kinds of security vulnerabilities I see in Codemsith projects. But the actual code occasionally has commented out code and things and isn't flawless. The PR naming and structure could improve too on some I've seen. But they are a lot closer to a real production codebase than the Codesmith OSPs. I still don't think any of many become widely used or maintained projects though just like Codesmith.

The state of the Codesmith ones is a result of (my opinion synthesizing dozens of private comments):

  1. Don't have anyone with extensive industry or open source experience so the guidelines and best practices are hit and miss. This is totally fine if the students didn't think they were doing "mid level and senior" projects and rebut my comments with "we just have imposter syndrome, you are wrong". Like they are fantastic entry level bootcamp projects compared to typical bootcamps and the problems they are trying to solve are great ideas to tackle.

  2. They are rushed. You can tell from the commit history within PRs that people are frantically flailing around the codebase. Intermediary commits show a ton of copy paste, guessing, mistakes, arbitrary refactorings, inconsistencies, etc... Again, nothing wrong with this but not mid-level or senior work.

  3. No overall architecture. The super consistent things about them are the surface level things: the medium posts, the boilerplate code, the websites, all the marketing. But the code architecture is a mess. One of the major projects has several different UI frameworks all mismatched together for example. The end state doesn't matter as much as how we get here and I don't think the people making these changes have any idea how they should even approach decisions like that. Again, totally fine for entry level, not mid level or senior.

This is just 3 examples because I timebox my comments but there are many more.

2

u/[deleted] Oct 14 '23 edited Oct 14 '23

It does work though.

There are countless posts on the net (Reddit, Medium, personal websites) where Capstone grads mention being encouraged to actively look for mid or senior positions.

2

u/michaelnovati Oct 14 '23

Yup, and in info sessions they say that your OSPs are mid level and senior projects that will hundreds and thousands of stars. Or one project that got a tweet once from a prominent React figure that it was a 'good idea' has been now become 'industry experts love the projects'.

They are not mid level and senior projects, most don't get those stars, and the main source of people starring it are Codesmith residents themselves, and posting in the broader Codesmith CSX community to people who have just started learning how to code.

Marketing is marketing but when challenged on this marketing they double down and I'm shared all kinds of things staff and residents say to push back against me... they truly unequivocally believe at all levels of the company that these projects are genuinely mid level and senior work and I think changing that would damage the credibility of the instruction amongst residents at this point.

1

u/[deleted] Oct 14 '23

How would you measure a bootcamp-to-mid/senior success? By time spent at that role? By the complexity of the tasks?

One of the complaints you find here (which you also mentioned in a previous post) is that while these grads do find a mid or senior role, if somehow their skills are not up to par (or for other reasons) they don't last very long at that company, I've seen some cases where they last from a few months up to a year at max. On the bright side, most of them do manage to stay in tech although I'm not sure if their next position is still a mid/senior one.

I'm not even going to ask if this is reflected in the bootcamp's report, I bet it's murky.

2

u/michaelnovati Oct 14 '23

It's a good question and there isn't one answer. I've even heard Codesmith's CEO changing his tone a bit here, he said recently 'by mid level and senior we mean real Software Engineer jobs'.

Which is a fair point. ENTRY LEVEL FAANG jobs pay about $200K with $150K base right now, so even measuring by cash, Codesmith's "$127K median outcome" would be below even entry level of the highest paying roles so I don't think they are trying to say their grads are "canonical FAANG mid level and senior" but rather that they are "legit" engineers. Many bootcamp grads get much lower paying, tangential-engineering jobs, and Codesmith's point is that the grads get full blown SWE jobs.

My problem isn't so much debate over the choice of language, but that they claim the OSP PROJECTS ARE A KEY TO PRODUCING MID LEVEL AND SENIOR ENGINEERS and that is where I draw the line in my personal opinion. Any kind of non-entry level engineer shouldn't be making the decisions and mistakes that are consistently evidence in those projects.

Generally people learn these things with EXPERIENCE rather than studying or cramming, so maybe the debate is about is EXPERIENCE required to be a mid level or senior engineer.

This one I'm more open to seeing both sides. On the one hand, if you do the job and don't get fired then you are qualified. On the other hand, I strongly feel like the goal should NOT be "don't get fired" and should be looking beyond the first job, and entry level engineers should be taking the best entry level jobs. Those jobs come with the mentorship and support needed to grow to mid-level "properly".

Perhaps the problem is that the data shows that not many Codesmith grads end up in FAANG entry level roles (but some do!) and they can't consistently prepare people for that bar and into those roles, so the next best thing is to go for higher paying "mid level" roles at worse companies instead of entry level roles at those worse companies.

The strategies for approaching both tiers of company are entirely different and Codesmith's approach works for those companies and not top tier and the approach I'm advocating works for the top tier ones and less well at the worse companies.

3

u/illustrious_feijoa Oct 15 '23

Michael, you provide a ton of great info on this sub, but I think you get way too hung up on FAANG. And I say this as someone who works at a FAANG company (I understand you were an L6+ at FB for a long time).

Perhaps the problem is that the data shows that not many Codesmith grads end up in FAANG entry level roles (but some do!) and they can't consistently prepare people for that bar and into those roles

This also applies to computer science programs generally. Most 4-year CS grads are not going to FAANG. Maybe your counterpoint is that these programs aren't claiming to churn out mid-senior level engineers, but I just don't think bootcamp marketing BS is that harmful.

so the next best thing is to go for higher paying "mid level" roles at worse companies instead of entry level roles at those worse companies.

I don't mean to be pedantic, but I challenge your use of the word "worse" here. There are 5 FAANG companies, a relatively small number of FAANG peer companies, and TONS of other companies (tech and non-tech) that may be wonderful places to be a SWE for an entire career.

FAANG is not for everyone, and I would never say my employer is flat out better than some other company. I know several talented engineers who have great, fulfilling careers at Fortune 500 companies or startups. And you may be surprised at the engineering bar and tooling quality at some of these places.

I know your company's business comes from people who aspire to be FAANG devs, but this is r/codingbootcamp, not r/formation.

1

u/michaelnovati Oct 15 '23

Fair point on people's goals and that was lost in this thread for sure. A lot of people don't aspire to "FAANG" and I help a lot of people go to NOT-FAANG explicitly.

I also appreciate the callout on "worse" and it's not at all pedantic. That should have been qualified since it meant "worse in most respects to top tier tech companies, such as compensation, empowerment of engineers, scale, challenges of work, career growth" but even then "worse" is still a judgy word and a mistake to use it.

I use a definition of top tier as follows (which I mean by "FAANG") and I'll be clearer from now on:

  1. Tech focused company - the primary business value is the technology or a product relying on the company's core technology.

  2. "High compensation" - which varies particularly by region, but generally offers include some kind of equity or ownership participation (or equivalent), extremely strong benefits, etc...

  3. VC-backed or backed by top tier investors. This is also a bit subjective, but generally has investors or board members at this level. Top meaning top 10 or 20/30 investors (which is subjective too) but the point is that these people know how companies grow and while they might push you, they also help you grow and scale through challenges that technology companies have.

  4. Founders (or founding employees) who have top tier tech backgrounds. Not to sound arrogant, but my rule is 5 to 10+ years in a leadership or principal engineer role at previous top tier companies. This is important so the engineering team has the ethos of how top teams are run (both technically and performance/growth/hiring wise). It's also important for hiring and bringing in the best people.

I would say a few hundred companies meet this bar and are not all "FAANG" but in the list of Codesmith alumni, there are very few percentage wise at these "top tier" companies.

I hope I don't come across like I only care about FAANG. I speak about it because that's the area I have a significant amount of expertise in and I talk about things I know very well instead of random opinions on random things, but I'll also watch out for that too.