> UCLA has a notorious class called CS35L, which is a weekly series of time-consuming labs. This class, although painful, is what creates software engineers.
>
> In it, we learned how to use the command line (e.g. shell commands, scripting) and change management (e.g. Git), which is core to writing code in a collaborative professional environment. Lastly, we learned how to use basic software debugging tools.
That's just some of the superficial tools "lab skills" of churning out code.
Software engineering (for real, when it has to be effective over time) is a larger and more difficult space.
I think the three courses this person is talking about are all about passing a FAANG-like "coding interview" that is targeted at new college grads with no industry experience.
LLMs will now gladly launder open source software into churning out code, much faster than a new grad, and will even (statistically, emergently) apply more software engineering practice than these classes will teach you to do.
That's just some of the superficial tools "lab skills" of churning out code.
Software engineering (for real, when it has to be effective over time) is a larger and more difficult space.
I think the three courses this person is talking about are all about passing a FAANG-like "coding interview" that is targeted at new college grads with no industry experience.
LLMs will now gladly launder open source software into churning out code, much faster than a new grad, and will even (statistically, emergently) apply more software engineering practice than these classes will teach you to do.