4 ms·
When I was in college I needed to take two classes, one of which was a prerequisite for the other, within semester to graduate on time. The CS advisors adamant
by ALittleLight 4y ago
When I was in college I needed to take two classes, one of which was a prerequisite for the other, within semester to graduate on time. The CS advisors adamantly refused to add me to higher level class because I was missing the prerequisite class. Furthermore, the classes were taught at the same time to prevent people from taking them in the same semester, for some reason.
I talked to the more friendly advisors in the Philosophy department, who also had the ability to add and drop students from classes, and got them to add me to both classes I needed. I persuaded them not to worry about the overlap. I completed the semester by attending the higher level class except for exam days (I had to get a special dispensation to take one final early because their final exams were scheduled at the same time).
My point with this anecdote is that sometimes more powerful people try to impose a speed limit and sometimes you can get around them.
- Tyr42 4y agoI think the scheduling both at the same time might just be an "optimal" solution if you already know that people can't take them at the same time. That frees up other time slots for courses people taking either one might take.
- drekipus 4y agoThis happened to me twice. I'm actually endlessly annoyed at the whole college system being structured like this.
- bruce511 4y agoSo I get that college in the US can be expensive, hence the rush, but for me, one of the main benefits of university was time. My CS class very quickly divided into "those who could already program" and "first time programmers". (testing out was not a "thing" then - at least I never heard of anyone doing it for any class.) Interestingly it was more classification than groups. I spent time helping friends who were stuck, but I also spent a lot of time with other advanced students, in the lab, pushing each other. The assignments were trivially simply, so we just spent time making them more interesting. Because the course work was done quickly, we had a lot of time to go the extra mile. Time we wouldn't get later in life. The important things though, the theory, stuck with me, and even the early classes were valuable. Intro to programming only lasted a few months, then there was a lot more theory, and we could meld that into our code a lot more. I went into college knowing how to code. I came out knowing how to program, and there's a big difference. If you are in college today, funding aside, I'd say - don't be in such a rush to finish. Fill your spare time by sucking in riches, seek out every nugget, help others, be challenged, see the time as an opportunity, not a class to simply pass.
- bayindirh 4y agoThis is my experience as well. I was doing well in CS courses, but struggling in others, and didn't graduate early (well, didn't try to either). However, finishing whatever they threw at me allowed me to go ask for more, or try more harder things. As a result, I learned way more than curriculum offered, got way harder assignments and projects (like designing a compression algorithm from ground up as a graduation project), and satisfied much more overall. I continued my M.Sc. and Ph.D. at the same university (because I already had a job, and I just wanted to learn), and this head start (and being in good terms with the professors) allowed me to do similarly heavier curricula during these studies, too. It's worth it.
- jvvw 4y agoI'm in the UK and this studied in a system where you can't just skip ahead, but I also got so much out of sucking in the riches as you say and helping other students. Because I already knew the basics I could spend time really mastering every last part of the courses and it was wonderful (and also gave me space and time for lots of non-academic activities!)
- devwastaken 4y agoThis isn't possible anymore. The system has been fully automated.