There needs to be a "portfolio" movement in software development degree programs. That, and a clearer distinction between a "cs" degree and "software engineerin

There needs to be a "portfolio" movement in software development degree programs. That, and a clearer distinction between a "cs" degree and "software engineering" degree. In, say, an architecture degree, students and professors understand that you will apply to positions with a portfolio. I think students are able to use work from the degree program in their portfolio. Their professors have portfolios from when they first applied for positions out of school, so they can help or at least provide examples. Currently, we just have a vague notion that you should have code or contributions on github, and that is for some reason not part of most degrees. Or, too many students get a cs degree and try to use it to apply for software development positions. In that case, yeah, you're going to need to self-study if you want to apply for positions you didn't actually get a degree is.