I'm in this university software engineering course, where the professor decides he need to teach us the entire history of software engineering.

Dude, we were taught how to use SVN in addition to Git. Huh? And for software development processes, we were taught a total of 7 of them. There're: code and fix, waterfall, prototyping, spiral, phased, agile and lean. And the tests are like "list 5 advantages and disadvantages for X, and compare them to the advantages and disadvantages of Y". Wtf dude. I don't mind memorizing things, but the things I learn aren't even relevant (except agile and lean). Nobody would be impressed if I say I know SVN in an interview. What am I doing with my life. Ok, back to cramming this shit cuz i need my GPA. Bye.

you can learn from fails in the past, so memorize why this old stuff is bad. and don't be surprised if there are still companys using SVN and are working with the waterfall model..

mankind has always improved over the history, so it is important what and how things had worked in the past. so be proud that you learn that stuff, even if it has not anymore that importance.. just my two cents

It sounds awesome.

@2erXre5 :( maybe I'll get what you said after I finished suffering

Lots of companies still use SVN. People only really talk about shiny stuff on the internet but there is plenty of this supposedly irrelevant tech that's still in use. Don't get me wrong the course is still probably garbage. But the topics aren't irrelevant

@tevyt pardon my ignorance but why would anyone still use SVN?

@donfour you know, out in the wild we have dinosaurs where it will cost too much to switch to other scm systems. maybe you have heard of the phrase "never touch a running system". that is applicable to a lot of areas including scm and build processes. I guess you still have to learn that in IT not everything is shiny as on a whitepaper. And often it is a matter of how much anything will cost and what the benefit your company has of that change. and believe me, that question of how much it will cost is a very important one when you will work for someone. because if you do work that is not paid by any customer you will not get your pay check at the end of the month. and changing an scm will almost never be paid by a customer directly but can be quite challenging. and btw, svn and cvs are not that old related to when git appeared on the stage.

@donfour what @2erXre5 said it can be very expensive and time consuming to switch any kind of system. imagine using svn for years you can't just get up one day and say you're using git. You'd need a good justification for the switch. Where I work now we're starting to use git for new projects but there are literal decades worth of work in Surround SCM that still needs to maintained. think of how much time it would take to move all that to gi, not to mention retraining staff to use git after using Surround for 10+ years.

Seems like something that would happen in an Indian engineering college.

@tevyt thanks for the answer. I still have much to learn!

@anirudhkhanna Chinese, so you're not far off😂