I've been out of university for almost a decade now. Your experience echo mine. I also started out in a local community college so I missed those first two years.
> Unfortunately, I came to discover that the SE program was generally considered “easier” than CS.
I also came to the same conclusion. At my alma mater the difference between CS and SE was only a few classes: Algorithms 2/3 and Automata Theory. So I switched from SE to CS as I felt it looked better on the resume.
> I discovered over time that none of my team members had written code outside of a homework assignment.
I also had the same experience. This was especially apparent in the CS undergrad capstone class. Which required working with a local company to develop some software. I ended up doing the majority of the prototype with .NET and AngularJS. Technologies which I was already experienced with from personal projects.
I've been out of university for almost a decade now. Your experience echo mine. I also started out in a local community college so I missed those first two years.
> Unfortunately, I came to discover that the SE program was generally considered “easier” than CS.
I also came to the same conclusion. At my alma mater the difference between CS and SE was only a few classes: Algorithms 2/3 and Automata Theory. So I switched from SE to CS as I felt it looked better on the resume.
> I discovered over time that none of my team members had written code outside of a homework assignment.
I also had the same experience. This was especially apparent in the CS undergrad capstone class. Which required working with a local company to develop some software. I ended up doing the majority of the prototype with .NET and AngularJS. Technologies which I was already experienced with from personal projects.