3 ms·
Not always. The bootcamp I worked for did 2 months of pure HTML/CSS/JS and then did a personal project for another month of which students almost exclusively us
by mettamage 3y ago
Not always. The bootcamp I worked for did 2 months of pure HTML/CSS/JS and then did a personal project for another month of which students almost exclusively used HTML/CSS/JS, some did React. Only in the final week did I teach React.
This was around 2017, most students didn't become React devs. Most students did end up in the JS ecosystem, but 30% did something else [1].
[1] When I say 30%, that's not an official statistics. It's just on my impression what I've personally seen from students who connected to me on LinkedIn. It's a guestimate at best.
- ukuina 3y agoWhich part of that curriculum was core CS?
- mettamage 3y agoNone of it, as those skills were not asked for by the labor market. And I tend to agree with it (as a CS bachelor and master graduate). What you need to learn is programming in a specific way. CS teaches a broad scope of things that are all helpful but they are not strictly necessary to know, especially not as a junior. I think doing a CS degree after having done web dev for 3 years in the field is a much wiser decision. For example, I never really had to know how a compiler works or assembly, but I know it. I only needed my data structures and algorithms knowledge once. My knowledge of UML? Meh And so on
- ukuina 3y agoYou are describing the distinction between a scientist/engineer and a technician. Technicians only need thin slices of knowledge about the underlying abstractions. The problem with _aiming_ only high enough to create technicians, though, is that you create a good chunk of _operators_, instead, who make do with both thin _and shallow_ slices of knowledge, making them poorly suited to any kind of generalization.