[RosieA]

Hahaha, I see your point. But casually designing something that endangers people's lives really isn't much of a comparison.

yes, you can absolutely argue that developing the next piece of medical software for defibrillators is of equal importance, but if I'm sticking to coding front-ends of ecommerce shops and happy being great at that and staying on top of it as it grows... I'm not sure I see the point...?

[king_magic]

My point is this - what happens when some kid with 6 weeks experience leaves gaping security vulnerabilities in your ecommerce shop (yes, even with front-end code alone) that results in financial damage to your customers?

[RosieA]

If we're going for worldly examples to coding dangers: what happens when you're mechanic misses a screw when replacing your brake pads?

Firstly, if your a biz doing transactions, you better damn well be insured, just like your car, just like your health.

Secondly, your mechanic might be a junior, but little mistakes get left by the most experienced of people as well. Especially on things they think beneath them or simple. I hold no doubts that you and I have both at some point made a simple but critical mistake on the most "simple" part of a project. Its human nature.

6 weeks is a bit of an extreme example for someone to trust the building of a transaction site worth hacking, but even so I'm not sure that type of risk is something anyone can argue as a problem with bootcamps. What if I teach myself for a few weeks and want to start getting jobs and trying stuff out? Same issue, and some of the best developers I know in the world are self taught.

[socialmatchbox]

You are completely missing the point. You can't just say "So what if a mechanic forgets to check the brakes to make sure they work before setting a customer loose in a car that is going to run off a cliff and DIE."

Insurance can certainly cover the cost, but is it your company's official stance that it produces coders who need to be paired with supplemental errors and omissions insurance policies because they will crash your company's product or that it would be ok if they cause major problems?

I think you are somehow confusing graphic design with software engineering and programming here. Maybe what you should be telling people is that you are teaching people how to build brochure websites for a living. If that is it then your perceived quality or capability bar might not be objectionable.

[king_magic]

You're comparing really really really small apples to really really really big apples.

Your mechanic's mistake might result in a few people being hurt (a bad thing, of course). It's not going to result in serious damage to hundreds of thousands of people's financial lives. It's not going to result in massive privacy violations. Or sink a multibillion dollar project.

I also think you might be overestimating the benefits of "being insured" - these types of problems can destroy companies. Is one inexperienced coder likely to cause something like that? Maybe not - but an army of them? Much more likely.

I'm not saying people don't make mistakes. But I am saying these types of courses cannot possibility teach you enough to truly know what you're doing, and I as a hiring manager would not consider hiring someone with no other experience than your organization's 3 month course and a couple of side projects without the benefit another 2-3 years professional experience on top of that.

[RosieA]

> But I am saying these types of courses cannot possibility teach you enough to truly know what you're doing, and I as a hiring manager would not consider hiring someone with no other experience than your organization's 3 month course and a couple of side projects without the benefit another 2-3 years professional experience on top of that.

I've agreed with parts of this statement several times throughout the various comments on this feed. Bootcamps that send their students out into the world without a realistic idea of where they stand and how to progress beyond their current knowledge are doing an injustice to their students, and to the people who have to sift through their resumes. Its something we try very hard to to work against, and set realistic expectations for with our active students. Its partly why we built our own curriculums.

I think your taking the context of small apples and putting them in the context of MASSIVE apples. But I like apples, so lets not get them tied into this mess.

I'm still very confused what you're arguing, as you present problems with the bootcamp model, but then what is the solution? How did you learn to code, and how was it better? How long were you restricted to education-only projects before "being allowed" to work on real things?

Hiring managers and advanced software developers lead teams for a reason, to filter out people they cannot trust from their team. I would also say though that something we do is take passionate people and give them the tools to kickstart a new career. Yes it takes time, and experience and lots of learning beyond a 3 month course, I think everyone can be realistic about that, but to say someone "shouldn't be coding anything" because that's where they started? Can't agree there.

So again, how did you learn to code, and how was it better? How can the bootcamp model be adjusted to do a better job?