Three months into my new job: an honest review of Le Wagon bootcamp
Tags: bootcamp, career, learning
Published: 2020-05-31 19:17:07

### Haha, Bootcamper!

![https://media.giphy.com/media/cO39srN2EUIRaVqaVq/source.gif](https://media.giphy.com/media/cO39srN2EUIRaVqaVq/source.gif)

Yeah well, hello there! Nice to meet you too. 

I indeed attempted [Le Wagon](https://www.lewagon.com/fr) bootcamp last winter in Paris. Before that I was an engineer in sustainability for buildings and urban planning. 

I had many ideas to improve my job that implied some sort of web apps: solar access maps, land use sustainability calculator… those kind of things. I though they were much more impactful than PTTs—not to mention apps seemed to be much more fun to build. Everybody was keen on it and I tried to learn on the side, but it always resulted in super clunky projects, never really working, never finished.

So felt I had to give web development a real chance. Two month for real, with mentorship seemed to be  all that I needed. Spoiler alert: it was.

### Woh 7000€! You kidding?

Ok, let's do some quick math here. Nine weeks of five days, we are down a bit more than 155€/day. Most professional trainings sold to companies are sold somewhere between 300€ and 1000€ per day and are absolutely nowhere near the quality. Hiring a high mountain guide in a small group will cost you between 100€ and 200€ per day. Definitely not crazy numbers at all. I mean you have to pay people at some point.

Now, I had a very decent engineer job, but with the training I made a net +600€/month that's only likely to increase faster than before. That's an return on investment of less than 10 months. Find me any investment that yields more than 100% per year!

Last but not least, I was fully subsidized anyways. In France we have access to fundings for these trainings that cover for the cost of the bootcamp and my salary during it (!). So I had pretty much free lunch here. The staff is very helpful in trying to get you all the subsidies they know of and try to get the bootcamp financed if you are motivated.

I understand you have to get that money out of somewhere and that might not be possible for everybody. People who need such training the most are probably not the one with enough money aside to get it. That's the very sad thing about it. But you can hardly blame Le Wagon for that.

All things considered, it's quite a fair price for what it is. 

### Seems to be a lot of hype around the startup/digital nomad trends…

It's a lot of code wrapped in a bit of hype. Just enough to get you pumped.

The "*it's more than code"* punchline is somehow true, but can be misleading. You get to meet a lot of entrepreneurs and people with all kinds of ideas. You discover the Basecamp/Github way of working. You get to work you ass off, in cool and relaxed environment. You get to work on super close deadlines while having fun and never being stressed. There are more events, party, drinks, yoga and crossfit classes than you can probably attend.

For a lot of people—me included—all of these extra are quite important because it raises the bar as to what work should be. Once you have experienced this kind of working conditions, there is no way back to bullshit management and powerpoint nonsense, working crazy hours in a glass building. It's definitely part of the *product* they are selling.

Yet don't be fooled, it's coding six to eight hours a day. Everything else is bonus, but the core is coding web products. If you are there to get a startup holidays or just look cool with a MacBook, you'll spend a disappointing amount of time scratching your head in front of a terminal.

### I want to be a dev, I don't want people on startup holidays slowing me!

While it's true some people come more out of sheer curiosity than anything, most have a career plan in mind. And even if, I have not seen a single person not doing its best to participate every day. In my project group we had a guy who was over 60 and certainly not looking for a developer job afterward. Still, he did his share of the work and never was like "*let me enjoy my holidays"*.

You have people with all kind of backgrounds, all kinds of experiences, both among the campers and the teachers. This raw diversity of skills, ages and genders is really great, especially at a time of your life where you need some fresh ideas on your job.

### I am an entrepreneur, will I have a startup full of investor cash startup after?

Well, no. It's a coding bootcamp, not a startup studio. Is this bootcamp still for you? Depends.

If you are the kind of entrepreneur who wants to build their product with their own hands, yes definitely. You will learn everything technical thing you need, you will have opportunity to pitch (your product or another), you will meet fellow entrepreneurs. One would say the bootcamp was ultimately made to bootstrap 100$ startups out of nowhere. Although, once again, it's code you learn, not marketing, accounting, PR, management or HR.

If you are the kind of entrepreneur who thinks his job is the raise to money to have other peoples do the work, you'll be disappointed. Not only Le Wagon's culture is overall cautious toward raising funds too early—if at all—but it is a **coding** bootcamp. 

I think a few people have found their co-founder at Le Wagon, during or after their batch. It's not guaranteed, but it's not a bad place to find like minded people at all.

### Meh, there are tons of free courses on the internet anyways. I can learn on the weekends.

Yup, see you in five years, when your hundredth unfinished side project will join the *"learn to build [banal app] with [shitty framework]"* graveyard. 

Where to even start with this one? 

First, Le Wagon staff is not stupid, they know people try to learn on the internet. So the prep' work you have to do before the actual bootcamp are free courses on the internet (Codecademy free tracks on Ruby, HTML, CSS and JS) and then you build on those basics. I would dare say that people who tried to  learn a bit  by themselves are the core target of this bootcamp and represent roughly 30% of the campers.

I'll get into more details as why, but still the structured learning path is in another league compared to anything I've seen for free on the net. The precise schedule is also key here. It makes sure that everyday clicks into the next one and it remove any sort of questioning on what you should be coding. You have much more brain available for coding this way.

Then you have all the *"in person" a*nd the *"get together".* You can ask any question, any time to a teacher whenever you feel stuck, you learn to code together and you learn when it's time to stop coding for the day and relax to be on top the next day. The social part not only is required to code professionally—you have to know how to code and ask questions in teams—but it helps a lot to keep the schedule and rhythm.

The internet wants you to think it's a matter of short tutorials. I tried and failed there quite a few times. And yet I have learned countless softwares by myself, from making maps for Quake 3 to making scripts for Rhino in my last job. I went from couch to running 50k/3500m+ in less than two years— training 6 days a week and losing 30kg in the process. I am not bragging, but just saying I can get motived at times and I have learned things by myself (and so can you!). 

Yet learning a job is not learning a hobby. It is very unlikely that you learn as much as fast all by yourself. I have nothing but the deepest respect for people who are self-taught well rounded devs. But for me—and I think a lot of people—the boost provided by the bootcamp was more than needed. I would still be stuck kluging useless code without it.

### Still, it is open to anybody, it must be pretty easy

Ooooh, be careful there. I had been doing a bit of programming in other language (scientific stuff) and I had tried to learn web dev' before. Heck, I already had my own site powered by Hugo, my own Ethereum smartcontract and I had *"learned Vue"®*. On top of that, I have always been quite good at school (again for the facts, no pride there). Should be a walk in the park, no?

Well, doing all the exercises everyday was quite a challenge, when I could do it all. The first ones are always basic applications of the day's concept. But then you quickly go into more complex katas, deeper OOP and MVC concepts. Try to write a class that count how many subclasses inherit of it without googling, you pros! Harder than you remembered, hmm? That was a second week exercise.

The last optional exercises are often pretty open ones. Like building a small game (snake game, space ship game etc.), building your own ORM, building some landing pages, wikis, jukebox etc. The more you do on these the better, but you're unlikely to be *"done"* there. 

As for projects? Sky is the limit and they will only grow bigger, from one day mini-app (which is quite challenging), to full weeks of group code, where not only everything is possible, but you are vastly encouraged to go beyond the platform app.

Truly, there isn't a single day where I didn't learn something.

### Woh, that sounds pretty hard after all. I am not sure I can do it.

Pretty much anybody can. I know they insist a lot on the fact that it is *"super intensive".* Don't get discouraged by that. It's more to tell people that it's not holidays, but it's nowhere near the kind of crazy work to get into top universities.

Then again, all the exercises are very progressive. There is something for everybody every day. The basics will get you through the essential concepts. And I've seen pretty much everybody doing their share of work during the projects.

Just expect a good eight hour day of training every day and you will be fine.

### So the course is THAT good? From what I remember, classes have never been that great…

Yes, the track is really, really good. I still teach a bit at the university and the track is nothing like the PPT put together the day before by some graduate student who is obviously more into science than into teaching (totally not me, I'm saying for a friend).

The big difference with other academic or professional training is that the course is a real product, refined over the years and the batches. They put into a nine week program the same amount of work you would put into a SaaS product or some high end holidays camp.

You learn with a really great web platform as a companion tool too, with all the exercises, classes, products, videos, resources, auto validations for your exercises, some quick test for refreshing your memory etc. It's really neat and all tailor built for the course. Again, nothing like what I have seen on the web. I still use it on regular basis to find resources, go back to some classes.

On top of that, everything is planned like it's you're in some sort of high end sport camp, both for the coding and all the other parties, drinks, conferences, demos etc. You might frown upon the relax part and yoga classes, but it is very important to get some time off screen if you want to be on top the next day and Le Wagon is really good at that.

There is also a full-time person dedicated to career and a full week for that after the bootcamp. You could call that customer success. Laugh at the wording, but very few professional trainings do that and again, it shows the spirit.

Really nothing is left unattended. It's do one thing and do it well. Nothing like I have seen before.

### Are the teacher as good as the course?

Mostly yes. Especially the more experienced teachers who are really good at giving some insights, while keeping everybody focused on the day's course and leave other questions for the next day. As I mentioned, a big advantage of the program is to weed out unnecessary questions and so that you can focus only on the most essential things.

It was a bit different with the less experienced teachers, although it was mostly OK. They didn't provide as much insight and are more prone to making mistakes. Some were harmless like *"Bootstrap is made by Twitter",* some slightly more problematic like *"webpack is a server"*. 

This a recurring problem with the scaling model of bootcamps. You need new teachers who know the course well to expand. Your best source for that are fresh grads who lack both a bit of industry and teaching experience. Nothing that ruins the experience or the training, though.

There was one exception to the overall great teaching: the JS teacher. He is a nice guy, but teaching is definitely not is thing. From the very helpful *"it's this way because it's this way",* to the endless anecdotes and missing some pretty important concepts (scoping, reference to functions vs. their evaluations etc.), this made for quite confusing days. The JS part being already quite short, this had some people just plain give up on JS.

One very important aspect, is how helpful and friendly the teachers and assistants are. I have never seen anyone being looked down with contempt, feeling dumb or inadequate because of a teacher. They really do their best to keep every single person motivated and this makes for a very nice atmosphere where we all try to get the best out of everybody.

During the project weeks, they also really, really work their ass off to help your group land a nice demo. It's really impressive to see how much they care about your project like it's their own. 

### Now give me some tech! What do you really learn?

You mainly learn to do all CRUD operations in an MVC pattern and use that to implement user stories using the github flow. 

You will learn to model your data, pull it to your model, decide how to route actions, process things in your controller and display things in your views. And you will do that **a lot.** You learn a bit about model, you play with it the terminal, you make a small controller and mix all of that together. And some SQL, mix together, rinse, repeat. And some front-end, mix together, rinse, repeat. Add some Sinatra, rinse, repeat etc. etc.

You will loop on every single part of the architecture until it is literally part of your brain. All of this culminating into Ruby on Rails app living on Github, to help fit all the pieces togethers.

Now this the one thing I was lacking from trying to learn alone. Not Ruby on Rails, but truly learning a solid architecture and good design patterns, leaving no dead spots: data modeling, routes structure, where to write which part of the code. It is a lot of pieces of puzzle to find out and it is a lot of work to put them all together—when I could even find the pieces.

I also want to stress that I am really, really happy with the coding style I learned both for Ruby, CSS and JS. Your learn to experience very clean code and maintainable code and aim for nothing less. I recently took the PWA course from Academind. The concepts were OK, but the style and structure of the app got me tilting, really (deep nesting leading to unreadable var names, global vars for states, reimplementing your own iterators…). I learned to expect more. 

This is typical internet solo learning: get fast to one precise feature, but at the expense of everything else. And then you are left with brittle app, that falls apart when you try to change a tiny bit of it. That's the difference between learning to build *that one* app or *that one* feature and learning the foundations to build *any app or features*—and to learn to learn the missing parts.

With solids basics, you can move to pretty much anything: new MVC frameworks, add some front-end technology, learn new paradigms etc. You can, but maybe you won't even need to, because with CRUD (and a bit more) in RoR, there is an awful lot you can build.

Whatever training you choose, definitely favor product, software architecture and clean code over any fancy technology name.

### Ruby? LOL! Gimme my React!

If you say so… but I've learned to love—and miss—Ruby 😇And no, it's probably not React you're after.

True to Le Wagon bias toward building products, you learn to spend as few time as possible on the code for shipping as much product as possible. And on that topic, Rails freakin' work. It's the typical thing to build a start-up on and for good reasons.

Rails brings you ton of autonomy in **every** district of the code. It is a framework in which you can truly be full-stack.  Lots of other hyped technologies will take care only of one part (often the front end…) and you will be left out tinkering with how to model and fetch your data, do secured operations etc. Rails makes sure you take care of everything.

The Rails ecosystem reflects that spirit and is much more sane than the *I don't need paradigms and design patterns, just give me my npm packages!* state of modern JS. Really, I am glad I can think outside of JS.

Which leads me to my second point: no, it's learning React you want, as it probably won't make you ship more finished, functional apps. What you're after is most likely good, modern basics s in CS, design patterns and software architecture. Again, Rails is not the main thing you learn, it is just tool that helps you implementing the MVC pattern and an excellent one to do so.

Le Wagon knows most people want to make functional app over learning any precise technology. It is actually quite a bold move by them to resist the temptation of stamping *"React"* all over their flyers and to stay true to their belief that Rails is both great for learning web dev and shipping products. 

Oh and by the way you get a free React course as a bonus, should you need it.

### Still that's not a lot of JS…

And on that I would agree. It's a hot and difficult topic about Le Wagon's track, probably one of the main source of complaints afterward.

On the one hand, your learn just enough to be dangerous. JS in Le Wagon's track is reduced to animations, hide show stuff etc. and add some useful packages (maps, calendars etc.). No state management, no routing or all that jazz. Plain ES6, precisely written and refactored, in a well structured webpack app. There is a long way you can go with all of this. It truly is a blessing that the scope of JS is actually reduced to the bare minimum, as the thing has tendency to spill all over the place for no good reasons.

On the other hand, I have seen teacher assistant—often fresh grads—being stuck with an npm package because they were trying to use an arrow functions in a place where proper function scoping was needed… and they had no idea what scoping even was. Now you can get quite some way in JS without caring about prototypal inheritance, but calling yourself *professional fullstack* with knowing virtually nothing about scoping, `this` and asynchronous code in JS… ugh 😫!  It is very unlikely you won't encounter any those in a doc somewhere.

All in all, the few JS I learned, I learned it well and I am super glad I wasn't trained only in JS. Still I could have used a bit more. The problem is, there is only so much you can fit in nine weeks. So what would I trade for more JS? That I don't know and I am glad I am not the one making these compromises 😛

### You need ten thousand hours to be a master. You know nothing Jon Wagon.

Fuck that rule, really. First the real rule is ten thousand [plus or minus ten thousand hours](https://www.theguardian.com/sport/blog/2019/may/27/sports-variety-better-early-than-sharp-focus-david-epstein-book). Then, you don't need to be a master to do a good honest work. You don't need to be Michelin three star to open a successful restaurant or be an olympian to be a great sport teacher. There is just an unlimited amount of simple and useful work to be done in web development, even if you don't have ["that special part in the brain to understand pointers and recursion"](https://www.joelonsoftware.com/2005/12/29/the-perils-of-javaschools-2/) (moron…😞).

Most importantly, it is misunderstanding the real benefits of the program. The important thing I learned at Le Wagon is what it really takes to learn to ship a product/feature, that is both useful and well written.  Now, I have a lot of bells in my head that rings *"Too much data manipulation in the front, let's look at the model", "Those routes are a mess", "My files are too long, not in the right place", "Waaaaay too much time on tooling, let's build things", "That code seems ugly"* etc. etc.

I know infinitely better how to balance my effort between learning a library, integrating it with into a workflow with the right tooling, fitting it into good design patterns and then freakin' ship product with it *(answers: very little, just enough, quite some time, a fucking lot).*

Recently I had a simple but quite interactive UI to build that made POST request to an API, so I decided to go with Svelte and little Node.js API for proxying. I think spent on 30mn learning the syntax, the equivalent of a whole day for tooling and refactoring my codebase and a full week to ship the actual thing. But more importantly, I instinctively knew when it was *"good enough"* and how much effort I should put on which part*.* Well written modern code definitely is one strong point of Le Wagon and that will be an advantage from day one at work.

Judging by absolute level at the end of the bootcamp is also totally misleading. It is not like it puts you *there,* at a given skill level and then you stop learning. Quite the opposite. It's more a matter of setting you on the right track than getting you somewhere. Le Wagon is a just pinch in your whole career. But a pinch in precisely the right direction and that's what was very important for me.

### You can really make apps after just nine weeks?

Yes, definitely, but just know that it is more *websit'ish* than *app'ish.* 

The typical thing you learn to build is an Airbnb clone, where people can login, post stuff, rent stuff, pay, see stuff on a map etc. That's the basic everyone knows how to do in full. After that, you are encouraged to go as far as possible beyond the platform app. Some of the best projects included speech recognition and auto-correction on the fly, small "click" games, beer recognition with your smartphone etc.

The typical thing you don't learn to do is making your own google map or video player (I mean actual engines), games with physic etc.

The bootcamp is really not geared toward mobile either. That is really a drawback here. With the same technology it wouldn't be hard to design for mobile first and add the tiny bit for handling offline (quite a few project are on mobile though). Especially since the whole program is quite good on UI.

Now don't get me wrong here. Since the iPhone, everybody wants to make *apps* and *website* seems like thrown out of the 90s. **But there is an awful lot you can build with a good dynamic website (ebay, amazon, google, airbnb…) and it is real software by all standards.

### So everybody is coding and has jobs after?

Meh.

![https://media.giphy.com/media/xT77XTpyEzJ4OJO06c/source.gif](https://media.giphy.com/media/xT77XTpyEzJ4OJO06c/source.gif)

Linkedin has been on fire in the few weeks after the bootcamp and since then, so jobs are not a problem. Coding…

Out of more than forty people of my batch, only six of us have regularly pushed code to Github since the end of the batch. Maybe some have changed account or are on Gitlab/Bitbucket… I doubt it and not possibly that many. Some might be stuck back to doing tutorials on their,  but that's definitely not what we were taught to do.

I have a gut feeling that a large part—and I am deliberately vague on numbers here—hasn't shipped a single line of code since the end of the bootcamp. And the Linkedin updates I have are only fueling this feeling, with most people having product  and growth jobs. But quite a few (six I know for sure, so probably a bit more) are already coding professionally.

That's puzzling and I would have excepted the opposite. Since a lot of people are at a turning point of their career, that they would need time to think and time to refine their skills would only be natural. That you stop building things when you learned to, when you absolutely have the skills to and you have projects to work on as teams is more of a mystery to me. Really, I have no explanation (nor real numbers).

You can hardly blame Le Wagon for that. We were told countless times to keep coding  and to ship features in group rather than learning new technologies.  

Yet don't get me wrong, you will only find super happy people who loved their times at Le Wagon and don't regret it a single day. You will also find lots a good devs who have been through the bootcamp.

So? Jobs: asbolutely. People: very happy. Github: mostly empty. Deal with that…🤷‍♂️

### Le Wagon, Le Wagon, Le Wagon…

Yup, it's a commercial brand. They know how to sell themselves and they definitely want the word of mouth to be spread. So you will hear *"Le Wagon"* a lot. It comes with a few advantages, especially on satisfaction: people better be happy with what they get for the price or the thing will quickly run out of business.

Usually, I am also not so keen on school corporatism (I always hated the happy few elite life of french engineering school). Here the raw diversity of backgrounds keeps things fresh and make for quite a nice community and also a very welcoming and open one. There are tons of jobs offer shared, help on code or career, you can easily find freelance to work on projects etc. I surprised myself here, attending some events once in a while and even liking it!

And while this alumni life is fun when you found a job, it is quite essential when you are in between your bootcamp and finding one. You can come work at the place with other people (at a very moderate price), you can work a bit as an assistant teacher or just come and say hello at the events. You are not left on your own once it's done and I never felt *"Your paid time is over, bye"*. Quite the opposite.

So no it is not some sort of open source collective or non profit, it is a commercial start-up. One with great people and a nice community around it. 

### So what you're doing now? Do you have anything to show.

My official title is Technical Project Manager at [Opendatasoft](https://www.opendatasoft.com/fr/). In practice I implement small apps on top of Opendatasoft platform, usually one pagers with a bit of logic to display datasets. It comes in either in full blown front app through our API or with the Angular widgets the dev team makes. My job typically involves some sort of mini-product design—although I have also implemented design specs.

I have been building a lot of COVID-19 dashboards for our clients (like this [one](https://www.lavoixdunord.fr/740341/article/2020-04-13/coronavirus-suivez-l-evolution-de-l-epidemie-dans-les-hauts-de-france) or this [one](https://newarkcovid19.com/data)). I have also built some boilerplate for an offline first app, so that we can store results of our API calls for offline use. I have been toying around with scrollytelling as well or building SPA around our API (which, for one, is a very valid case of using SPA !).

I got the interview for the job three days after the end of the bootcamp, was confirmed that I had it three weeks after that and actually started the job less than three month after the end of the bootcamp (time to finish my previous job, mainly). 

I am loving it so far and things are building up to get really exciting 🤞

### You happy? 🤷‍♂️

Yeah! 😊

I did a move that was in my head for so long and I am not even slightly disappointed (which is disappointing, I like to be snobish about my situation). Now I am in a company culture and an everyday job that fits me much better. It gave me a fresh start and so many opportunities.

Couldn't be happier!