I'm in a school of engineering that is not specialized in computer science, so I only had a handful of software development projects. If I'm counting well, that is 2 group projects and 1 or 2 alone.
All of them consisted in building something from scratch. Never had to deal with legacy. Only a bit during an internship.
I actually find this question extremely relevant — most schools don't teach how to deal with existing codebases. They teach you how to build systems, but not how to deal with systems other people have built. It seems even companies don't let interns deal too much with legacy code because of the burden of "getting into it".
I think if it was the case, it would not only teach the student/intern new skills but also let them develop empathy as to why it is important to write good code in the first place.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm in a school of engineering that is not specialized in computer science, so I only had a handful of software development projects. If I'm counting well, that is 2 group projects and 1 or 2 alone.
All of them consisted in building something from scratch. Never had to deal with legacy. Only a bit during an internship.
I actually find this question extremely relevant — most schools don't teach how to deal with existing codebases. They teach you how to build systems, but not how to deal with systems other people have built. It seems even companies don't let interns deal too much with legacy code because of the burden of "getting into it".
I think if it was the case, it would not only teach the student/intern new skills but also let them develop empathy as to why it is important to write good code in the first place.