Bootcamps vs. College

There are several factors that don&#x27;t enter this analysis.<p>1. Bootcamps can be selective over a range of non-academic criteria such as interview skills, personal hygene, and prior work experience. Or to put it another way, unlike a public university, a boot camp can select for culture fit both in its internal cohorts and in the workplaces it targets.<p>2. Bootcamps tend to attract people with previous work experience: someone more likely to have several years of working to keep a roof over their head than a recent CS grad. There&#x27;s a difference between a junior programmer with their first real job and a junior programmer who has spent six years working crappy jobs [or good ones].<p>3. Bootcamps have much more latitude to train for employment and employability. Listening to Jeff Meyerson&#x27;s hours of bootcamp love songs, those interviews have left me with the distinct impression that doing so is common.<p>4. Bootcamp grads may come out with a stronger alumni network that can provide recent feedback about interview processes like Triplebyte&#x27;s. Going in with some idea of what&#x27;s coming is likely to produce better results.<p>5. Bootcamps don&#x27;t have to report their &quot;failures&quot;. There&#x27;s no independent oversight or accountability of the sort common in university education. A &quot;C student&quot; may simply find it impossible to graduate a bootcamp. The bootcamps are free to shape their &quot;graduate&quot; pool however they wish.

<i>How is this possible?</i><p>I think one key aspect that is missing is that boot camp graduates aren&#x27;t straight off the barista lineup. I took one at age 28 after having worked in a technical role in finance since undergrad. The average age of my class was probably 29. Beyond just time in the workforce, I had a double major in math and economics with a minor in applied statistics. Had I dropped &quot;Behavioral Economics&quot; and taken &quot;Data Structures&quot; along with some other random course, I could have switched my Econ major to a minor in CS. Many people in my class were of a similar background.

I have a slightly more pessimistic view of the situation:<p>Sure, bootcamp grads can write a web application just fine; after all, it&#x27;s usually only CRUD. But what <i></i>value<i></i> are they bringing to an organization? Why would I pay them the same amount as a college graduate who undoubtedly has more total knowledge not only in CS, but in other areas as well? Ideally, a college should expose students to a diverse range of knowledge, each tidbit providing additional value to an organization. If I just wanted an application constructed, I could offshore the job and get it done cheaper.<p>Yes, a well-run bootcamp might be a better __coding__ education than a computer science degree, but coding is the easy part. There are other valuable skills that aren&#x27;t being taught (i.e. the ability to communicate clearly, how to do research, how to learn independently) that make an organization strong.<p>We aren&#x27;t in the coding business, we&#x27;re in the building business. Code is simply a means to an end.

Companies focus too much on attracting talent, not enough on developing it.<p>If both of these screened avenues of entry to software development are as promising as these metrics indicate (each with their pros and cons) here are some potential larger takeaways for companies:<p>1) Invest in the continuous development of your employees, regardless of their background and seniority<p>2) Hire for teams, and diversify teams with both CS and BC grads<p>3) Hire more people in general (maybe on a probationary period)<p>Fit to small teams with the goal of cultivating experientially diverse teams, and spend significant time developing employees - junior and senior.<p>Any intellectual work should involve continuous learning and development. If the company&#x27;s focus is restricted to current projects, or on the bottom line, or if managers enforce strict division of labor, an organization will warp to optimize for those metrics and become less adaptable to inevitable changes in the market (or within the company) and the company will fail to compete - or at minimum incur major opportunity costs.<p>What these metrics suggest is that if you take relatively successful candidates and invest in their individual development, both in depth and breadth, that investment will pay off. You&#x27;ll create engineers who find better solutions to problems and - more importantly - who find better problems to solve.

I&#x27;m in the process of hiring a junior position and have no bias towards college grads or bootcamp grads. The only negatives towards boot camp grads I&#x27;ve seen so far is:<p>1) One candidate had no idea what the terms &quot;Class&quot; or &quot;OOP&quot; even meant. I&#x27;m FINE with them not understanding stuff like sorts&#x2F;advanced data structures, but he ACTUALLY had 0 idea what an int was. No lie!<p>2) I wish there wasn&#x27;t such a heavy reliance on MongoDB in most of these programs. Some do have SQL as well, but I feel like 80% of workplaces will be dealing with SQL, so I&#x27;m not sure what the focus on Mongo is all about if the purpose of these programs is to make you hireable. I think it&#x27;s that it&#x27;s an easier concept to relay since you&#x27;re working with JSON everywhere already, but I&#x27;ve seen a bunch of people have a very strong bias towards Mongo to the point where they seem to not understand why you even would use SQL.<p>3) This part might get me in trouble here, but we are a small company in NJ and budgeting 50k for the junior 0 experience position. Most of these bootcamps in Brooklyn or Manhattan instill that you minimum should be making 60k and not to even look for anything else. I disagree with that personally, but I realize it is possible for grads to make this (especially in NYC). I&#x27;ve just come across a few that scoff at us for the pay we have, and I do understand it, but some of my higher ups who don&#x27;t really feel comfortable with the bootcamp concept don&#x27;t think they are worth it.<p>Obviously there are a lot of pros with hiring them as well. I think typically they are the more qualified candidates skill wise. None of the ones we&#x27;ve come across have been a great fit so far though, but I think it&#x27;s because of how close to NYC we are. These programs are based there, and we have trouble competing with the salaries there. That&#x27;s why we have been having more luck finding college grads from the NJ area though, they don&#x27;t have these kind of higher expectations.

I&#x27;m happy to answer any questions about this (I expect it to be controversial). When we started Triplebyte one year ago, I was pretty skeptical of bootcamps. Doing credential-blind interviews and seeing what some bootcamp grads can do, however, has won me over. Clearly there are a lot of bad bootcamp grads (and probably a lot of bad bootcamps). But the model is working really well at the top.

These results aren&#x27;t very surprising because this is about interviewing performance. The goal of bootcamps is &quot;teach you enough to get a job&quot;; they&#x27;re basically gaming the interview process by teaching to the test. University programs on the other hand are &quot;teach you CS theory&quot;; learning to interview well is up to the student and the specific school&#x27;s offering of interview training.<p>I think there&#x27;s a strong argument to make that university programs are too focused on theory, when the vast majority of their students are going to go out and get practical engineering jobs. I don&#x27;t want the pendulum to swing too far to the practical side, though, because then you lose the long-term benefits of getting a CS degree. Although, schools can certainly buff up their practical material.<p>Anecdotally; when I participate in hiring, I tend to discount the bootcamp grads. Maybe it&#x27;s unfair, but my experience hiring them has been that they know how to interview well, and know their tools well, but when you compare them a year in, they&#x27;re pretty far behind their university counterparts. I see a plateau, where it&#x27;s hard for a lot of bootcamp grads to move from doing generic web development to designing more challenging systems. Obviously it depends on the individual, but this seems to be a categorical struggle for bootcamp grads with little technical background. A lot of companies really just need more people doing web development, so being open to the bootcamp pool is essential, and ruling out bootcamp grads is silly.

It was not long ago that Computer Science degrees itself faced a similar challenge, against more well-rounded liberal arts programs, championed and prided by the Ivy Leagues. Today MIT and Stanford are ahead by the strength of their more “practical” engineering degrees. The data from Triplebyte supports the same narrative, just in greater granularity: businesses value practical skills.<p>There is value in being balanced and diversity, but this applies to teams, not necessarily individuals. Not everyone on your engineering team needs to be an architect. After your globally distributed, fault tolerant, realtime, highly available system is designed, somebody’s got to build it. And most startups or software teams have no business even trying to design such a system in the first place.<p>In the US, my generation was told we all needed four year degrees. We don’t. Some jobs and some roles certainly but the entire population of future adults?<p>There is an engineering shortage in the US because everyone was too busy getting four year degrees in more well rounded fields. Meanwhile Apple needs tens of thousands of engineers that could have been trained by two year vocational programs that the US was apparently above for our children, and thus cannot meet their business needs.<p>And yet this data from Triplebyte is incredibly encouraging because while we screwed up the educational policy, it may not be so difficult to fix.

I&#x27;d love to see some more mathematical analysis of these differences. In particular, I suspect that while the averages are similar, the distributions look extremely different.<p>Specifically, the average engineer out of either a bootcamp or college is pretty mediocre. But the top 10% of engineers are mostly college graduates and are definitely not bootcampers. This is because the best developers are overwhelmingly passionate about development and have been doing it since high school. If you love programming, you <i>might</i> go to college to get a firmer academic standing. You definitely <i>won&#x27;t</i> go to a bootcamp—if you&#x27;ve been programming for 5 years, a 3 week bootcamp makes no sense.<p>On the other hand, when it comes to the bottom tier I suspect bootcampers are a lot better. This is mostly because the bottom tier of CS graduates are atrociously bad. Regrettably, it is possible to graduate with a degree in CS without ever having written a single program by yourself. They slink by mostly through cramming for exams and &quot;collaborating&quot; with peers. My impression is that bootcamps are actually less tolerant of this behavior: you won&#x27;t make it through a bootcamp without ever programming autonomously.

It makes a lot of sense that bootcamp grads would outdo fresh college grads on &quot;web system design&quot;; they&#x27;ve presumably spent most of their bootcamp time focusing heavily on web systems. Stuff like load balancers&#x2F;reverse proxies, distributed message queues, noSQL DBs, etc. may be totally foreign to a lot of fresh college grads, while a bootcamp grad can probably be expected to have a not-too-shabby understanding of how those components fit together.<p>The &quot;practical programming&quot; bit is a little more depressing, though it does ring somewhat true based on what I&#x27;ve seen in real life. How people can spend 4 years programming and still consistently fail at building decent abstractions, I have no idea.<p>Also, where is the &quot;neither&quot; category? There are dozens of us... dozens!

Go to college. Life is long and it is not about passing your first interview. Real world is complex and ever changing. The point of going to college is not to acquire coding skills to pass the interview. It is about facing real world challenges: people, responsibilities, complicated decisions, uncomfortable situations etc. And hopefully at the end of it you are better prepared to take on life. It is a harder path than going to a coder factory. Take the hard path.

Bootcamper here,<p>Of course 3 months is going to get you running with a solid basic knowledge of your stuff.<p>In what world would low-level, algorithms and data structures be doable in 3 months?<p>Point is, I don&#x27;t think Bootcamps and Colleges are comparable.<p>It&#x27;s like being a woodworker and a forester..<p>There&#x27;s a place for each and it&#x27;s not the same positions...<p>Now, here&#x27;s my big question:<p>If your interview includes Practical programming, Web system Design, Algorithms and Low level system design...<p>What in the nine hells are you hiring for?<p>Had it been for a trucker position you&#x27;d be asking for &quot;driving license, laws and regulations, engine design and car physics&quot;..<p>For reference: <a href="https:&#x2F;&#x2F;i.imgur.com&#x2F;sh7LJgj.jpg" rel="nofollow">https:&#x2F;&#x2F;i.imgur.com&#x2F;sh7LJgj.jpg</a>

There&#x27;s something to be said about a person doing a bootcamp. Not only is it a drastic career pivot, but choosing to invest in yourself like that is a huge sign of maturity, growth mindset, and awareness. It&#x27;s no surprise that a bootcamp grad can quickly get up to speed in their first professional dev environment.<p>I did the WDI bootcamp through GA, and loved the experience. My motivations weren&#x27;t to become a full-time web dev, but to become a much better, more well-rounded product manager. It&#x27;s paid off 5x over so far.<p>There&#x27;s a ton of garbage bootcamps out there, and it&#x27;s unfair to lump them all together -- it&#x27;s unfair that these exist. period. While, you can&#x27;t replace the deep technical and theoretical understanding you get with a classic CS degree, if your goal is to build web apps, do you really need the formal experience, or can you learn that on the job?

there is a simple confounding variable here that unfortunately triplebyte can&#x27;t touch with a ten foot pole...age&#x2F;work experience<p>College is largely about transitioning children to adults (we can argue that separately) the personal and professional development that students go through over 4 years is vast. They are becoming adults in many frames, including understand the world and technology as systems. They aren&#x27;t just learning to code, they are learning how to think.<p>To the extent that I know (warning: anecdata) Bootcamps presume a lot more worldly knowledge, attract and expect more grown up students, get students with direct interest in web&#x2F;software&#x2F;apps, and are much more likely to get career transitioning students (from the people I know who have bootcamp&#x27;ed). They have a much broader knowledge base to build on which will help them in some areas and hurt them in others. I would be curious if Triplebyte has any data they can touch at all looking at that.<p>Simply said...a 22 year old college student with a CS degree and a 35 year old BC grad may look similar on metrics but function entirely differently as employees in both the short and the long term...caveat emptor, figure out what you need.

This is basically a warning to every single person going through bootcamps right now: Your skills are not special. You can be replaced with ease. Unless you differentiate yourself through what you learn either at your job or after the camp and demonstrate it through your work then your job will be kaput. That&#x27;s basically what all of those Everyone Can Code advertisements were trying to achieve which is to make these skills a commodity.<p>Good luck.

This is the most honest comparison I&#x27;ve read so far.<p>I dropped out of high school because I was making good money by 18... kept working, saw my own limitations, and did a BS degree in 3 years, graduating at 26. That was 5 years ago today, actually :)<p>I see this same distinction in practice, thanks Triplebyte for quantifying it. If I were staffing an engineering team, I&#x27;d absolutely take junior engineers from bootcamps and senior engineers with university backgrounds. I like the surgical model from The Mythical Man Month, and have seen elements of it working by hiring junior test engineers of varying technical backgrounds and training them.<p>I think a BS degree in CS makes a lot more sense when you&#x27;re hitting the edge of your capability as an independent contributor--many may never need it, some will love going on a few year sabbatical and earning their &#x27;piece of paper&#x27; (as I did).<p>Biggest factor that gave me an edge was I had lots and lots of context for all the content of classes, and I took notes every single day, Beginner&#x27;s Mind style and didn&#x27;t try to test past intro classes... even CS 101 with Scheme. I was also able to work on my mentoring&#x2F;leadership skills with classmates.

I think a well-run bootcamp is a better coding education than college computer science. The only thing most grads have on bootcamp people is algorithm knowledge. This is easy to fix. Just teach algos in bootcamp. It really isn&#x27;t that hard to understand.<p>Ideal bootcamp:<p>-css&#x2F;html&#x2F;javascript<p>-angular or any mvvc data mirroring framework<p>-OOP and ntier patterns<p>-Stored Procs&#x2F;ORM&#x2F;SQL training<p>-Algos<p>-Webservices SOAP&#x2F;REST<p>The college grads I work with tend to have written a couple shitty programs that don&#x27;t really do anything, and their &quot;final project&quot; was hooking up a database to a business logic layer.<p>source: I have taught in bootcamps before and work with lots of new college comp sci grads now.

&gt; It backs up the assertion that algorithm skills are not used on the job by most programmers, and atrophy over time.<p>This was the most interesting part to me. I&#x27;d love to see more on this.<p>I&#x27;ve always found it silly to ask algorithm questions of senior engineers. There seems to be an exponential falloff of that knowledge as one gets further from graduation.

If I were stranded on an island with the laptop I used in college and a power source, I&#x27;d have a pretty good idea of how to stumble through:<p>- A multithreaded UNIX-like operating system with user programs, system calls, and a filesystem, with reasonable (if not entirely optimal) caching strategies.<p>- A TCP&#x2F;IP stack for that operating system.<p>- An authenticated encrypted channel over my TCP&#x2F;IP stack with forward secrecy by building a pseudrandom function up to a stream cipher, RSA with OAEP, Diffie-Helman, etc.<p>- Network services from the RFCs in C (we did a router and IRC).<p>- A high-level programming language with support for both functional and OO idioms based on the typed lambda calculus with recursion, lists, records, tuples, ref cells, subtyping, etc.<p>- A lexer, typechecker, and interpreter for that language using parser generator tools, a recursive descent parser, or a shift-reduce parser in a pushdown automata model.<p>- A formal specification of the evaluation and typing rules and a type soundness proof for that lanugage.<p>- A distributed KV store with Paxos, Raft, or Byzantine Generals running on my encrypted channel and written in my language (we used 0MQ and were given a 0MQ broker that could be told to drop messages for testing purposes).<p>- Greedy, dynamic programming, network flow, and ILP algorithms with proofs of correctness and efficiency.<p>My class work repositories put me about three quarters of the way there.<p>I&#x27;m sure bootcamps can teach people enough to tread water in a dynamic language web framework, and that meets real business needs and adds real value. But college is a chance to go deeper.<p>I know nobody is paying us to build our own lightsabers. But - and call me old fashioned if you&#x27;d like - I think a professional ought to be able to build his own lightsaber anyway.

I swear, articles like this are going to cause me to have an existential crisis. I started learning programming as a child in the 80s. More than 30 years later, I like to think that I&#x27;ve acquired a lot of valuable knowledge and experience across a broad range of topics, and yet... when I hear about people training for three months and walking into decent jobs, I start to wonder what actually differentiates me at all.<p>For the sake of my ego, I&#x27;d love to hear that these bootcamp graduates have shallow, fragile knowledge in a narrowly focused area.

I think the debate about Colleges vs. Bootcamps is an apples to oranges comparison<p>Algorithms are commoditized into libraries. Web design has been commoditized with templates.<p>Open-ended programming is still more complicated, but putting apps on the web today is easier than static HTML just 5 years ago. Parts of programming will continue being commoditized.<p>So if it&#x27;s easy to create something and put it out there, the great and all-important challenge that faces developers today is making it matter.

I wouldn&#x27;t be surprised that a bootcamp grad could beat a college CS student in practical web knowledge. Stanford has a web applications elective, CS142 [0]...in the previous years, it focused on Rails [1]; this year, it moved to the MEAN stack. In both syllabi, a week is spent on learning HTML&#x2F;CSS alone...this year, I believe they spend a couple weeks learning JavaScript.<p>This class is an elective, which means that students aren&#x27;t expected to know HTML&#x2F;CSS&#x2F;JS before taking it, though the core CS classes (Java, C) are prereqs. This also means that students who don&#x27;t take 142 could quite graduate without having any practical knowledge about web development.<p>That said, it&#x27;s not because the CS students couldn&#x27;t actually learn practical web dev, and as others have said here, the best bootcampers are often folks who have a STEM background already.<p>[0] <a href="http:&#x2F;&#x2F;web.stanford.edu&#x2F;class&#x2F;cs142&#x2F;" rel="nofollow">http:&#x2F;&#x2F;web.stanford.edu&#x2F;class&#x2F;cs142&#x2F;</a><p>[1] <a href="http:&#x2F;&#x2F;web.stanford.edu&#x2F;~ouster&#x2F;cgi-bin&#x2F;cs142-winter14&#x2F;index.php" rel="nofollow">http:&#x2F;&#x2F;web.stanford.edu&#x2F;~ouster&#x2F;cgi-bin&#x2F;cs142-winter14&#x2F;index...</a>

I&#x27;m not sure that a comparison between bootcamps and college is viable.<p>College is not just about learning to code. You also learn to deal with professors and how to get the best grades out of them. You figure out how much you can drink without the glaring hangout that interferes with your morning philosophy class. You sign those forms to get credit cards that haunt you till you have a job. If you&#x27;re smart, chose a good college and get really lucky, you might actually learn something and get a job after graduation.<p>Boot camps are about learning to code, creating networks and passing interviews for tech jobs. You can&#x27;t pledge, or hang out with the furries, paint your face with your college colors for the football game at the weekend, or struggle figure out if your summer course fulfills the requirement for your social science elective.<p>These two places of learning can peacefully co-exist and each one has its purpose.<p>I even think that it would be good for some CS Degrees to walk into a bootcamp to explore something new and expand their knowledge.<p>Bootcamp replacing college? I don&#x27;t think so. Not till bootcamps have long lines of students trying to change their course selections at the registrar&#x27;s office.<p>There are some options that lie somewhere in the middle...

It&#x27;s not discussed, but I would guess that the best CS grads beat the best BC grads, but average&#x2F;bad BC grads beat average&#x2F;bad CS grads.

&gt; Bootcamp grads match or beat college grads on practical skills, and lose on deep knowledge.<p>I feel as though you are attempting to lower the bar of what is acceptable in order to sell something :). The word &#x27;practical&#x27; is thrown around in this article without much of a definition. Are we talking about making simple web pages?<p>I&#x27;ve just finished conducting a round of interviews for a junior level position, and based on this experience I highly doubt I will be considering bootcamp graduates in the future. As an example, for a question which involved sorting an integer array, and providing a method GetElementAt(index)....95% of the bootcamp applicants implemented sort within the GetElementAt method so that the entire array is sorted with every single call. A handful of CS grads made the same mistake, but most of them did not. Is this sort of oversight excused in the idea of &#x27;practical&#x27; programming? Or in your definition, is this considered deep knowledge?

After reading through all of the comments so far, my impression is that bootcamps are for training the developers whose jobs will be automated away in the coming years, and college is for training the developers who will be writing the code that automates those jobs.

Well this is interesting to me, as I&#x27;ve recently worked with a bootcamp graduate, and I&#x27;ve been looking over my brother&#x27;s shoulder while he finishes his CS degree at Columbia.<p>- Bootcamp lady was very able on the iOS project we were working on. She seemed to know where things were in XCode, and she understood Obj-C and Swift (no embarrassing questions about what classes are). She didn&#x27;t seem to know about other environments (and said so), but we were doing an iOS project.<p>- Ivy league guy seems to have touched every common language (c, c++, Python, HTML&#x2F;JS&#x2F;CSS, R, and more), along with common tools (vim, pyCharm, tmux, gcc, VC++, laundry list). I was surprised by how practical it was, actually. I thought it would be obscure algorithms the whole way, but I guess they take the theory and essentially force you to learn the practical aspects by implementing things in relevant stacks.<p>- Bootcamp lady was very good working in our little MVP team. Understood how common management ideas like Agile work. Conscientious with looking at the Trello board, asking questions in Slack. Not sure if this is just her personality, or because they tell you how software teams work.<p>- Ivy league guy had lots of group projects, but they tended to be dysfunctional. There was always someone shirking. Some people had no clue what was being built or how to compile it. There didn&#x27;t seem to be any management oversight, just blind &quot;let&#x27;s get this piece done&quot; type organisation.<p>- Degree guy has way more breadth. He was routinely looking at machine learning, implementing demos with scikit, setting up VMs for himself, looking at assembly, looking at SQL optimisation, and other diverse tasks. Bootcamp grad didn&#x27;t need this stuff, but also would need significant training to get to that level.<p>- Ambitions were similar. My background is in financial code, and they both want to do that. Bootcamp grad has quite a mountain to climb, particularly with things that take more explanation than MVC. She has a good attitude, so if someone would teach her she could do it. My brother is better positioned though, and would need less teaching to reach the same place.

&gt; This does not leave bootcamp grads equivalently skilled to university grads. If you want to do hard algorithmic or low-level programming, you’re still better served by traditional CS eduction.<p>Or, if I may suggest, a low-level&#x2F;algorithmic bootcamp.

Bootcamp without years if experience will not replace a Computer Science degree. It lacks the depth to build a solid foundation. While this is just an anectdote every company I have worked for refuses to hire bootcamp grads.

I think that both college and boot-camp styles of training have their place. I&#x27;d think my default inclination would be to want to hire the CompSci majors to do the deep-scope planning&#x2F;figuring and use boot-camp hires to do the grunt-work of supporting that vision.<p>It&#x27;s important to note that this is just my initial inclination. I have no expectation that there won&#x27;t be instances of boot-camp hires being better than CompSci hires in cases. It really comes down to the particular person, and hopefully any hiring process would do a decent job of evaluating each person.

Having interacted with a lot of both lately, my impressions are that bootcamp graduates focus on mostly on functional requirements.<p>They have a hard time identifying non-functional requirements, assessing and mitigating risk, and start getting confused when things go low level.<p>In my experience, all &quot;friendly&quot; technologies have sharp edges somewhere, where you start getting exposed to low level issues. When you face these issues, there&#x27;s no guarantee the answer will be in stack overflow and you will appreciate having learned some theory.

Bootcamps are filling a void which existed for a long time in the CS industry. Most of the time, A CS grad is hired to do a job that can be done by someone with little programming knowledge. I feel it is a waste of resources to hire a CS grad to do CRUD app with maximum 5 users on a very good day.<p>Now companies can use people from bootcamps for such kind of jobs and use CS grads for deep and high level stuff. Surely some top bootcampers will be able to do high level stuff too.

Do you remember your college web programming courses? The curriculum is always woefully out of date and seems that traditional undergraduate programs don&#x27;t focus on updating it. This makes sense -- there are very few academic research areas that deal with practical web applications, and this is obviously mirrored in your undergraduate classes.<p>Don&#x27;t forget -- universities are also research institutions, while bootcamps are not, and the coursework will reflect this.

Bootcamps make people employable for sure, I work with a team of people mostly from Bootcamps. I think the problem with some of them is they don&#x27;t actually like programming. Learning new things and change is met with a lot of feet dragging. Don&#x27;t get me wrong, I know a lot of programmers that are just 9-5&#x27;ers. It just seems like anytime there&#x27;s any extra effort involved a ton of justification and selling needs to happen.

That&#x27;s because bootcamps specifically teach you how to pass interviews. I&#x27;m a senior developer and suck at interviews because I haven&#x27;t taken my spare time to specifically study for interviews. I don&#x27;t remember how to reverse sort a b-tree or whatever inane questions are asked because I don&#x27;t need to know that to do my job spectacularly. It&#x27;s actually kind of a joke that bootcamp grads interview better.

Thel real big difference that too often Americans forget is that college (and all the education system below colleges) gives you the structural mindset to break down complex problems and find solutions. They create your way of thinking and your rational side. Bootcamps, instead, just teach you how to execute some actions. It&#x27;s like the difference between colleges and industrial schools.

&gt; We’ve found bootcamp grads...worse at algorithms and understanding how computers work.<p>Solution: hire a college grad and send them to a boot camp.

One of my close friends said it best: &quot;savrajsingh, Lebron James doesn&#x27;t care if you start playing basketball.&quot;

Likely, you see more people getting a CS degree because they feel it&#x27;s a good job than the people going to bootcamps. The people going to bootcamps are more likely to be doing it because they&#x27;ve done some development and really like it.<p>Now, what bootcamps aren&#x27;t going to give you is the breadth of a CS degree. But if you&#x27;re getting a CS degree just for the money, you&#x27;re not picking things up very well either.<p>So, I can see where a certain % of CS students and bootcampers are roughly equivalent.<p>I feel if you&#x27;re very interested in CS and get a college degree and do really well in college, you&#x27;re going to come out ahead of someone taking a 3 month bootcamp. I also feel there&#x27;s more opportunity for CS degrees. ie, one probably isn&#x27;t going to see too many 3 month bootcampers doing real time development. (I&#x27;m talk real real-time, not that buzzword web real time.)

This is obviously comparing different things. Bootcamps and College are not replacing each other. But there is a difference between learning because you are hungry for knowledge (college) and learning because you are hungry for food (boot camp, you need to do your job). The former makes you better in the trade.

Could it be possible to combine both worlds? Getting a university degree by spending four years with a strong focus on practical skills and intense workload[1].<p>To my knowledge only the top tier of american colleges (MIT, Berkeley, Stanford, ...) come close to that achievement. But, in France, where I live; I had the opportunity to go to a private school &quot;specialized&quot; in computer science (Epitech, 42, if you wanna look it up), that was mostly an &quot;enlarged bootcamp&quot; from year one to year three. It was kind of funny, for me, when my peers from traditional schools ended up discovering version control in their final internship.<p>[1]: Once you replace the shitty paper exams by actual projects in programming classes, you&#x27;ll be amazed by how much you&#x27;ll increase student proactivity.

I started programming before college and I was always on my own. I never had a programmer friend until I started working. Although I was always able to get things done but the code I wrote is something that should never go into production. It took lots of mistakes, a lot of reading and shooting my own foot to finally start writing worthy code after like 2-3 years. (Although, there were code bases I worked with that were way worse!)<p>One thing I am curious about is, does a bootcamp make you proficient enough to avoid those mistakes and contribute directly to the application? I am pretty sure, it could have been a lot of help if someone could point out the mistakes I am making in my code, but I am not sure if it would have been enough.

My employer has been hiring a few people from some local coding bootcamps here in the Minneapolis area. Most of them are very decent at programming, so I&#x27;m not sure if they had any experience prior to their bootcamps or not, but I can&#x27;t say I have any complaints for those they&#x27;ve hired. Never had a fix any of their code since they&#x27;ve been on the job either. Sometimes they need more help since they didn&#x27;t get the discrete structures or software architecture knowledge that I did from my traditional CS degree. Honestly I think that should be something you pick up on the job or have been taught in high school (I&#x27;m biased of course).

The problem I have with bootcampers is that the bootcamps greatly over promise where they will be skill level wise when they finish, so expectations are way beyond junior developer roles. They also usually come out of bootcamps with a very narrow skillset; they can somewhat easily whip out a web app with a simple backend and rudimentary data sets using whatever framework that bootcamp focused on. Increase the complexity of the project even just a little and they get stuck.<p>There are some diamonds in the rough and some bootcamps are better than others but in general I&#x27;d much rather see someone who learned by hacking on things alone than a college or bootcamp grad.

I think there&#x27;s a great opportunity for bootcamps to help people like me. I&#x27;m currently a pre-sales professional, and have been for a few years now. I&#x27;m closing in on 28, and while I&#x27;ve been served very well by developing product expertise, my background isn&#x27;t in CompSci, and I&#x27;ve never actually formally learned to code. If I want to be a good Solutions Architect down the line, and I certainly do, this could be how I bridge the skill gap.<p>Sure, I could learn most of what I need to know on my own time, but this might be a great way to get it done quickly in a batch and then move on to applying it in a very practical way with my customers.

When you think about it as skills training vs. college I think it delivers on it&#x27;s promise.<p>In college, most people don&#x27;t declare a major until their Sophomore or Junior year, so the idea that competition is a 4 year degree is a bit misplaced. Code Schools don&#x27;t teach music appreciation, though there are a lot of musicians. Bootcamps offer an intensive at 40+ hours a week vs. a two hour class two days a week.<p>Can you deliver skills based training in 10 weeks? The placement rates would say yes. Do some schools focus on placement while others focus on taking tuition... That&#x27;s true as well.<p>Look to find the school that has a placement track record.

Programming isn&#x27;t all one thing. You have to have what amounts to an epistemology about the system you&#x27;re working on right now or you&#x27;re going to break things.<p>A degree improves the chances of this. About half of what I do is <i>teach</i> these things, on the job. Just being able to classify a systems error can be daunting - is it a show stopper, or an ignore, or something in between?<p>I see bootcamps as being fine for getting people into seats, but the rest takes a long time.<p>Finally, employability and what (IMO) CS&#x2F;programming should be about are diverging rapidly. This was not always so. This is starting to be a real problem.

Hey, I wrote an algorithms book aimed at bootcampers! The epub is out today, print book to follow: <a href="http:&#x2F;&#x2F;amzn.com&#x2F;1617292230" rel="nofollow">http:&#x2F;&#x2F;amzn.com&#x2F;1617292230</a><p>I&#x27;m hoping this will be an easy to read algorithms book for bootcamp grads. Here&#x27;s a sample chapter for anyone interested: <a href="https:&#x2F;&#x2F;manning-content.s3.amazonaws.com&#x2F;download&#x2F;f&#x2F;a75f93d-81e7-4c32-b1b8-7033df6bbf36&#x2F;GrokkingAlgorithms_SampleChapter2.pdf" rel="nofollow">https:&#x2F;&#x2F;manning-content.s3.amazonaws.com&#x2F;download&#x2F;f&#x2F;a75f93d-...</a>

They definitely are comparable. But I think going to both would be best thing if there is time and strength. Just as I thought college gives you most of theoretical stuff. If you are not used to working on your own, on side projects and are taking college for granted, then you aren&#x27;t off to a great start. But if you are used to doing something besides college, whether it is paid job or some tinkering projects you do in free time that you later put on github, then need for bootcamp maybe isn&#x27;t present. So hitting it somewhere in the middle might be best...

I&#x27;m most curious to see what the stats are deeper into the funnel, specifically:<p>- At what rate do bootcamp grads vs new grads get offers (intro --&gt; offer at portfolio companies)?<p>- Is the above metric significantly different for different classes of companies (either segmented by company size, field, or &quot;CRUD-eyness&quot; of company?<p>As a former hiring manager at a &quot;much harder than CRUD&quot; company, I remember looking at some bootcampers and saying &quot;I wish we could interview these people, but the knowledge gap is just too significant&quot;.

Boot camps have their place, but they are not a replacement for a traditional CS degree. I have met good and bad programmers from both types of programs (some from well respected colleges who I still wonder how they exactly passed), but here&#x27;s the thing, I don&#x27;t care about practical skills. I care about the person being able to think.<p>All those concepts that they teach in CS isn&#x27;t about knowing the name of an algorithm, it&#x27;s about thinking abstractly. I honestly don&#x27;t care if a recent grad knows how to use IDE x or even much about source control. I can easily teach them that. I can&#x27;t easily teach a person how to understand pointers or pass functions as parameters. I don&#x27;t need someone who can write code; I need someone who can look at a problem and realize that we can cut the amount of work we have to do by understanding programming concepts at an abstract level. It is very hard to achieve this in a 12 week course. Can some people do this? Sure, they may have the background from a previous career that aids them in this, but they are the exception and not the rule.

We&#x27;ve hired a couple of junior developers lately that had no college experience but significant online training and the experience so far has been very positive.<p>Given how long it takes universities to update course materials, I&#x27;m not sure they can compete with this kind of education programme. It&#x27;s true that a lot of the fundamental computer science is missing but with senior devs on the scene, any gaps can be filled with an afternoon around a whiteboard.

One thing I realised my final year of University is how much marketing Universities do towards the job market.<p>They shop their students and curriculum around to employers all over the county (some on an international level).<p>There is going to be a lot of inertia involved when it comes to hiring from Universities that most Bootcamps don&#x27;t even consider or spend time doing. I don&#x27;t think they give universities any cause for concern, and wont, for some time.

So basically, the guy who builds a rafter is a woodworker, the guy who nailed the rafter to the structure is a woodworker and the guy who made the dining room table is a woodworker. Each guy is important, but the skill level and education time are different. Not every rough carpenter needs to have an extensive education in fine carpentry to be successful in their area of woodworking.

It&#x27;s hard to measure hunger. My intuition is that it plays a big role when it comes to finding success after going through a bootcamp.

when I read &quot;4 years&quot; I don&#x27;t remember doing nothing but code for all 4 years during my CS degree. Part of the appeal must be that you focus on just coding intensely for a short period of time. I&#x27;m thinking back on my 4 years at pitt.edu and my god did I waste a lot of time. If you distill it all down, maybe it does == 3 months at good camp.

I would love it if Computer Science grads took a boot camp course - one that covers css&#x2F;html&#x2F;javascript, any MVC framework, ntier patterns, ORM&#x2F;SQL&#x2F;NoSQL training. Because from my experience, they apparently don&#x27;t teach any of that in comp-sci school.

All you need to know: some companies can use bootcampers very effectively, some cannot. It all depends on what the company is doing. It&#x27;s evident that since many companies have found great success while employing bootcampers that the skills they provide are useful.

I think this supports the hypothesis that schooling (secondary, post secondary, bootcamps, whatever) is first and foremost a sorting mechanism. Bootcamps have discovered _one_ avenue for quickly assessing and sorting students into a career they can succeed at.

So triplebyte still can&#x27;t infer anything about how well a software engineer performs on their job from the metrics that they are gathering though if they&#x27;re basing performance on how well they do on their coding questions and interviews?

Bootcamps seem to encapsulate and accelerate the &quot;I taught myself to program in middle school and high school&quot; experience for adults who missed that boat - which is great.<p>The results make a lot more sense when you look at it that way.

I think this misses a huge point: College is a huge factor in social development; This is extremely important not only for developing software on a team, but to developing a healthy lifestyle in and out of the workplace.

Universities don&#x27;t necessarily teach students programming. They teach them Computer Science.<p>Bootcamps teach students programming, definitely not CS. I highly doubt they could teach a student 4 years of CS material in 3 months.

I would love to see a break out for people who are neither bootcamp grads nor college grads but who are completely self-taught, like me :)<p>Surely they&#x27;ve received some applicants in this category.

Triplebyte figured out in twenty minutes that I didn&#x27;t learn enough while getting a CS degree at CMU in order to get a programming job so... good luck to them.

This is neat, although as someone who attended neither (well, not for computers anyway) I guess I can&#x27;t do the solipsistic thing and look for myself.

I find the whole premise a bit amusing, because in my country the prime target audience for bootcamps are undergrad CS students or fresh graduates.

I&#x27;m not sure why this is a surprise. Computer Science and Software Engineering are different things, the only common factor being programming.

Nice ad.

I wonder how many of the engineers at this weeks Google I&#x2F;O or the next Apple Dev conference went to bootcamps.

I believe not all bootcamps are equal.<p>Is there anywhere a curated list of good, recommended, worth your money bootcamps?

whether or not you come from a CS background, or a bootcamp background the proof is in the pudding: can you answer the whiteboard questions? if so, you pass, and nobody cares where you went&#x2F;did not go to school.<p>if that&#x27;s not enough, revise the whiteboard question.

What a load of crap.<p>What, they bred the capacity for abstract thought into you in college?<p>College attracts a generally higher quality applicant pool. You&#x27;re mistaking selection bias for an effect.<p>Let me tell you, I&#x27;ve interviewed programmers from all over. There are boatloads of people with CS degrees with close to zero capacity for creative thinking. There are also boatloads of CS grads who can barely code their way out of a while loop (true story!).<p>I&#x27;ve spent my career (no CS degree!) working alongside CS grads. I&#x27;ve gone further, faster, than most of them. I&#x27;ve had to deal with this kind of idiotic commentary over and over again.<p>CS grads are always surprised that I never got a degree (oh, I never would have guessed! you&#x27;re different, its those OTHER people without degrees who are idiots). Four years of school + the associated debt creates a big incentive to believe that you got a square deal out of college.

&gt; it still just seems hard to believe that 3 months can compete with a 4-year university degree.<p>Yes, it is very hard to believe. Impossible, actually.<p>&gt; Bootcamps, are intense. Students complete 8 hours of work daily<p>In-class time is not the gauge for college. Students are supposed to spend at least three hours studying for every hour spent in class. On top of that are office hours with the professor, as well as contact with the TAs or study labs.<p>If my courseload for a semester is Calculus 102, Theory of Computation, Algorithms 201, Principles of Programming Languages, and Computer Architecture, I don&#x27;t see how it is different than a bootcamp because a bootcamp is &quot;more intense&quot;. I don&#x27;t know how you can get more intense than juggling these five topics.<p>&gt; Traditional CS programmers spend significant amounts of time on concepts like NP-completeness and programming in Scheme...But it is not directly applicable to what most programmers do most of the time. Bootcamps are able to show outsized results by relentlessly focusing on practical skills...How to use an editor is something that a traditional CS degree program would never think of teaching.<p>Ugh.<p>I took a course in OS principles and then one in distributed systems. The first course covered mutual exclusion somewhat, the second much more. I spent quite a lot of time writing complex Java programs that handled mutual exclusion well. Guess what I am doing today, years after that course? Writing a complex Java program that uses mutual exclusion. I only took that second course because it fit my schedule, but it has come in very handy over the years.<p>Insofar as NP-completeness being &quot;academic CS&quot;, I have unfortunately seen too many bugs ( <a href="https:&#x2F;&#x2F;bugs.freedesktop.org&#x2F;show_bug.cgi?id=3188" rel="nofollow">https:&#x2F;&#x2F;bugs.freedesktop.org&#x2F;show_bug.cgi?id=3188</a> , <a href="https:&#x2F;&#x2F;sourceforge.net&#x2F;p&#x2F;jedit&#x2F;bugs&#x2F;3278" rel="nofollow">https:&#x2F;&#x2F;sourceforge.net&#x2F;p&#x2F;jedit&#x2F;bugs&#x2F;3278</a> etc.) where people did not heed the polynomial growth of algorithms.<p>They&#x27;re trying to dumb down what you can&#x27;t dumb down.<p>The reality can be seen if you look around a SoMa startup and wonder where all the grey-haired programmers went. Where did those programmers who were in their mid-20s in the late 1990s, programming for the dot-com startups, in an even more inflated market, go? Where are the grey-haired, balding programmers in your company?<p>And this bootcamp is the answer. Just look at the real estate prices and you know the market has heated up. Naval Ravikant turned down $600 million last year because he said there weren&#x27;t enough places to invest that. Despite talk of perhaps some cooling since the beginning of the year, things are pretty hot. So get some kid to go to a bootcamp for a few months. They can only get their hands on one real programmer, but they can hire a few of these bootcamp kids to do a few MVP&#x27;s, or maybe code some features up, which the real programmer will have to fix later.<p>What happens to these kids later, who have no foundation in what they&#x27;re doing, who have no deeper understanding of what they&#x27;re doing?<p>&gt; programming in Scheme...How to use an editor is something that a traditional CS degree program would never think of teaching.<p>That&#x27;s because a traditional CS degree program teaches you to write your own editor if need be. Stallman went to MIT and wrote Emacs, Bill Joy went to Berkeley and wrote vi.<p>What the hell point is there to teaching an editor? I was using Eclipse with Android plugins a year ago, now I&#x27;m using Android Studio. University is to teach concepts which will exist decades from now, not the Javascript library framework du jour.<p>The ones who will make out on this are the bootcamps, and the companies who can use these kids when the market is hot and will dump them when their usefulness is over. Just like what happened in 2000 (or 2008). You&#x27;ll see what your bootcamp and two years working at a failed startup amounts to when the economy cools, job listings dry up and the posted ones say &quot;BSCS required&quot;. Being able to cut and paste from Stack Overflow and use frameworks other people wrote and extended is not an educational foundation.<p>There are a lot of strawman arguments on the other side. Yes, the hardest working, brightest bootcamp graduate is probably better than the laziest, dullest person who managed to graduate from some third-rate college and get a CS degree. And so forth. None of that detracts from the point though.

This just in: web dev body shop is perfectly happy with bootcamp grads.

Also cheaper and faster, a good way to save tax resources maybe?

Over the last three years at Code Fellows in Seattle (www.CodeFellows.com) we&#x27;ve seen the market change a lot for students, hiring companies and curriculum.<p>At launch, there was a lot of pent up demand. 400 people applied for a Ruby class of 25. Most that took that first class had been self taught and in the surveys said they had been hacking at projects for an average of 18 months. Code school was a way to speed their path into a professional developer role (note developer, not engineer).<p>The majority of students today already have a degree and are looking to switch careers, average age of ~30. They are looking for skills to transition so in that way, going back to college isn&#x27;t an option unless it&#x27;s for advanced degree. The same is true for the veterans that are transitioning to the workforce, they have been in a very structured environment and want to speed through job ready training vs. four more years at college.<p>&quot;Stack switchers&quot; tend to be the top of the compensation range. If you have 10 years of .Net experience and want to switch to iOS. You&#x27;ll earn top dollar. If you don&#x27;t have much real world experience you&#x27;ll land an entry level JavaScript job with that skill.<p>The needs of hiring companies has also shifted as the market has matured. There are more &quot;code school grads&quot; in the market looking for jobs, so the process of screening needs to be better, interviews need to be improved and tools like triplebyte.com improve transparency of skills. Hiring Junior developers has never been the preference for employers. Everyone would rather hire both skill and experience. But when you&#x27;re competing with larger companies in a hot job market, you&#x27;ll often take Junior talent that is a good culture fit.<p>By culture fit I mean a combination of past education, work experience and new skills. Combine that with work ethic and desire and you see why most of the strong code schools have a high (90%+) placement rate.<p>Curriculum have changed as well. Code schools have to be teaching at the front end of the hiring demand. Teaching an old tech stack where job postings are heading down won&#x27;t work. Review StackOverflows recent survey if you&#x27;re curious about stack preferences.<p>Code schools are also required to be licensed with each state where they do business. That&#x27;s a requirement not all schools follow. It&#x27;s really about consumer protection in that way so check with your state.<p>The industry is still immature and you&#x27;re correct that there isn&#x27;t any reporting standards, e.g. are placements rates reported at 90 or 180 days past graduation, etc? We&#x27;re working with a number of companies like the Iron Yard to standardize on reporting and moving to audited results over time. I hope that someday we can apply the same placement rate standards to other academic institutions. As a dad of college age kids that would be amazing (note the White House tried that two years ago with a scorecard and the Universities said no).<p>Regarding the debate of should everyone learn to code or no one learn to code? It&#x27;s a skill, it&#x27;s not for everyone. It&#x27;s a job that isn&#x27;t for everyone. There are a lot of online resources, information sessions and one day courses, start with the low risk version and see if it&#x27;s for you. With an average starting salary of $71k in Seattle, the compensation appeal is a strong draw for people outside of the tech industry. You may be drawn to the compensation just make sure that you are also drawn to the work.

I would love to add a few comments. I do not know about the specific CS program nor code bootcamp they are specifically are comparing about, but I can speak to a general CS degree and the general bootcamp education. Full disclosure, I am a founder of a coding bootcamp.<p>Nothing can replace a 4 yr degree with basis in theory and multiple subjects but bootcamps offer people a way to jumpstart a lagging career or make a step into a new one. Being hirable in this industry is saying something, and that is what a great bootcamp should do.<p>That being said bootcamps are teaching current real world and career-like solutions. Many argue that you don&#x27;t actually get the real-world experience in CS 4-year degrees due to behind the time curriculum (due to long approval processes that coincides with accreditation) and long and sometimes boring lectures without a lot of application. Bootcamps take a flipped classroom, hands on, and immersive approach. Less lecture, more project-based learning.<p>Many developers fall under the 41.8% group on the recent StackOverflow study of self-taught developers. A very large number of developers in the market are finding their skills in very non-traditional ways. What many CS grads learn is undoubtedly useful, I would never take anything away from that, but with software expanding into so many different fields, blurring the lines between who was traditionally an &quot;engineer&quot; and who isn&#x27;t, and with the increasingly rapid pace at which languages&#x2F;frameworks&#x2F;best practices are constantly changing, there are a lot more opportunities to contribute in code than by cooking up advanced algorithms with linked lists.<p>In fact, many of our partner employers were frustrated by the lack of applicable, modern technology competency by the CS grads they were interviewing. As only one piece of anecdotal evidence to this: we&#x27;ve had various CS grads take our programs because (as they described) they only learned languages that were not anywhere to be found in the companies they were interviewing with.<p>Companies are starting to recognize that those who apply themselves in a bootcamp are able to learn quickly and adapt to new technologies and projects easily. Employers are looking for someone to get the job done with the skill set that matches the technologies that they practice. Many employers don&#x27;t care if employees have acquired that skill set in a garage when they were 12 years old, at MIT, or at a coding bootcamp.<p>But, bootcamps aren&#x27;t for everyone, you really have to apply yourself and consume content quickly. But if those requirements are met, bootcamp attendees really can excel! I know because at ours we have had so many success stories just like the afore mentioned where a student truly applies themselves, lands an amazing job, or starts a hot tech company and truly changes the trajectory of their life. Plus it happens in a tenth of the time of a 4-year degree and at a fraction of the cost ;)<p>Bootcamps offer a more personalized mentoring. Being able to see delegates, resonate with students emotionally, pick up on subtle nuances of communication and respond appropriately is the very essence of education. I believe passionately that training and coaching are not about getting something from one head to another, but are an intimate dance that transforms both parties.<p>I hope that helps a bit.

Of course employers love bootcamps - they need business logic monkeys who lack the fundamentals and therefore don&#x27;t increase in value over time as much as the people who actually put in the time with said fundamentals.<p>It&#x27;s cheaper to have somebody who doesn&#x27;t have a real education.

So would the best of both worlds be the combination? Four-year CS program for the fundamentals and the deep knowledge, then the summer after graduating (or really, senior spring, when the coasting sets in) a bootcamp-style training on practical development?<p>I don&#x27;t think that a traditional CS degree makes you code enough to become a good software engineer. I certainly wouldn&#x27;t have gotten enough practice actually writing code if I just did my coursework and didn&#x27;t dabble in other things, like game development. Let alone other practical skills, like debugging&#x2F;profiling (barely touched upon), source control (likewise), testing (completely ignored), project management&#x2F;estimation (noop...).<p>I&#x27;m still amazed and horrified that I took a Data Structures and Algorithms course that required nothing beyond proofs and a little pseudocode - not a line of actual, working code. It could be tailor-made for really understanding memory-management or TDD.

&gt; How to use an editor is something that a traditional CS degree program would never think of teaching.<p>Of course not. Why would they ever do that. It falls into the same bucket as version control. It&#x27;s useful, but go learn it yourself because it&#x27;s not that hard.

&gt; Note: We are only accepting applications from programmers.<p>significant.