3 ms·
None 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 i
by mettamage 3y ago
None 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.