Skip to main content
How to Graduate from the University of Waterloo's Computer Science Program with the Least Amount of Effort : r/uwaterloo
Go to uwaterloo
r/uwaterloo
• 4y ago
ConradIsMyDaddy
cs alumni '22 || what is the definition of a basis?

# How to Graduate from the University of Waterloo's Computer Science Program with the Least Amount of Effort

Advice

hello r/uwaterloo!

my name is u/conradismydaddy and i recently graduated from the University of Waterloo (class of 2022 holla) with a Bachelor's Degree in Computer Science 🎓

i got accepted into the University of Waterloo in 2017. i actually got rejected from CS at first, rather I got accepted into CFM and then conveniently switched in to CS after 1st year (i heard they're tryna block off this loophole now). getting into the University of Waterloo Computer Science program was a dream come true... for my parents. i personally didn't care for it too much, i kinda just did school because i just thought thats what everyone had to do. so ever since first year, my mission has been to graduate from this school with the minimum amount of effort. and i came here today to say that despite a few minor speed bumps, that mission has been completed.

so as a parting gift, i wanted to share with yall my Lazy Man's Guide for Graduating from the University of Waterloo Computer Science program

now, if you’re on a quest to maximize your CS education, to learn as much as you can, to make the most out of your tuition money, to absorb as much knowledge as you can from Waterloo’s world renowned CS program, to be able to say at the end of the degree that you’ve masted the art of Computer Science - this guide is definitely not for you

this guide is for those of you, who just like me, just don’t really care that much. this guide is for those of you who have found themselves stuck in CS and realized midway through that you don't even really like the field. this guide is for those of you who are kind've dumb, suck at coding, and don’t know how to write a proof for their life. this guide is for those of you whose parents forced you in to CS even tho your true passion is league of legends or psychology or some shit. this guide is for those of you who just wanna get sick co-ops and make bank as a FAANG software engineer, and don’t care about all this education stuff. this guide is for those of you who want the allure of a Computer Science degree but don't really want to put in too much work. this guide is for those who just want to get this school shit over with.

to those of y'all who this guide might apply to, for whatever reason you're here, whether it's a good reason or stupid reason, to those i say: welcome, i applaud your mission and i am here to help you achieve it.

i am going to split my guide into the 3 parts of your degree that you are going to have conquer: 1) The Mandatory CS courses (1A -> 3A), 2) The Elective CS courses (3B onwards), 3) The Breadth and Depth Electives (every term)

# Preamble: The Heuristics

since this a guide to graduating with the least amount of effort, the rest of the guide is going to be based off these 2 heuristics:

Heuristic #1: a pass is a pass - the goal is to pass, nothing more. there is no need for getting high grades. that means that 50 (or in some cases 60) is the magic number.

Heuristic #2: your time outside of school is more valuable - time is precious and any amount of time we can save from doing school stuff is a W

under these 2 heuristics, i argue the optimal path towards graduating is to go with the Bachelor of Computer Science with absolutely No Specialization program plan. this is because, as we will see later in the guide, the freedom that we get from not going for any minors or options or specializations will, if used wisely, save us a lot of time and effort.

again, if none of these heuristics resonate with you to any extent, or you're realizing that hacking your way through a university education is completely stupid and a waste of time and money - i completely agree with you. but i already spent 5 years doing it and figured i might as well share in case somebody else wants to do the same. so this is your last chance to turn back. if you're still with me, take a seat and make sure to drink some water while you read this.

# Part 1) The Mandatory Courses (1A -> 3A)

we begin with the mandatory courses. this is the hardest part of the degree, and unfortunately its unavoidable. in the vanilla Bachelor of Computer Science pathway, you will have mandatory CS, Math and Stats courses chosen for you up until 3A. so if you want to graduate with a CS degree, your first 4-5ish terms are likely going to be your roughest. but fortunately, if you can see the light at the end of the tunnel, if you can stay strong and muster your way through, the rest of your time in university afterwards should be a breeze.

from 1A to 3A, you should be taking the required courses in the suggested sequence. you don’t really have a choice here. given this limited freedom, this part of the guide is going to be a bit more suggestive. you are obviously going to have to take these mandatory courses, study, and pass them. BUT, the good news, is that these courses are basically the same few courses that thousands of waterloo students have taken year in and year out for decades, so the path to passing these courses shouldn't exactly be a mystery.

given this fact, one easy resource you can take advantage of is past resources. there's no reason to ever go into a course in the dark. a simple search for the course you're taking on google/reddit/chegg/coursehero/github should yield multiple results of past guides, notes, midterms, assignment answers. often times courses change their syllabuses and thus these things can become outdated, but more often than not these resources are going to have some very accurate reflections of what you will face in your course. past exams are my favourite resource for studying for exams. why try and waste time learning all the possible content when you can just practice the types of questions that you know are most likely to be asked? a tip for past exams, is to try and find students a year or two above you who can send you their crowdmarks. the more recent an exam is, the more accurate of a reflection it will be on the exam you will get. github can also be a goldmine, i basically got carried in courses like CS 241, CS 350 through various github repos (shoutout Robert Xu).

now, it's great that there's a boat load of past information out there on the courses. however, you can find as many past midterms and assignments as you want, but those alone won't be enough to save you. you're still going to have to put in a bit of work yourself to learn at least some of the material and do some of the assessments. in fact, most professors i've talked to are completely aware of the github repos available online, and express little to no concern for them because they know that if you completely rely on them you have no shot at passing the mandatory exams.

so while past resources are very helpful, i still think there is another resource that can be potentially even more valuable. and that resource, is the 1000 other math/cs kids taking the exact same courses as you at the same time.

my biggest tip for surviving the mandatory courses with minimum effort, is to make friends in your courses. this way, you never have to do an assignment completely on your own ever.

for the average person, Waterloo Math/CS courses are pretty difficult. but if you got into CS in the first place, you must be at minimum pretty smart already, and so is everyone else in your classes. your peers are going to be your biggest resource if you want to shortcut your way through your courses. you guys can form teams (doesn't have to be a lot of people, could just be you and 1 other person) that work together and help each other tackle your courses. you don't necessarily have to optimize here for finding the the smartest people to work with. from my experience, it can be better to work with people you actually enjoy spending time with, work well with, and have the same motives as. (***just make sure to be a little bit smart about how you work together. it's pretty hard to get caught for policy 71 but still be cautious***)

i'm assuming for this tip, that you aren't a genius that can do all the assignments alone, because if so, why are you even reading this guide in the first place? i'm also assuming that you can tolerate social interactions. i understand that some of you are shy or prefer to be alone, and some of you work better alone too. but i think it's generally the case that more things can get accomplished when humans work together towards the same goal.

you might be wondering, why make friends when I can just go to tutorials, office hours, piazza, etc.? going under the assumptions of our heuristics, these things just take up too much of our time if we're just aiming for a 50%. it's easier to just ask somebody in your class that knows their shit for help on a question that you're stuck on. obviously, you're gonna have to contribute to the team too and be that person once in a while who sacrifices their time to go to office hours and clarify an assignment question for your homies. don't be a freeloader. nobody likes freeloaders. if you are going to do so, make sure that you at least pay your friends back with an expensed Kinkaku dinner at the end of the term. ngl i had to shed out a few dinners in my time here. worth every penny.

the other thing you can take advantage of, is that most of the content you learn isn't exactly cumulative. i'll actually argue that most of the concepts you learn in your courses are never going to be used again ever in your undergrad. apart from a few instances, i never really had to revisit any specific theorems, formulas, or proofs from calc, lin alg, or stats. i never had to code again in racket or R. however, there are a lot of basic principles/skills that you learn and develop in these courses that are gonna be used everywhere. these include but are not limited to: general mathematical logic, writing proofs, debugging effectively, learning how to copy your friends answers without getting caught, etc.

so my next tip is to aim to understand the problem solving techniques, not to memorize the course content. again, following the heuristics i outlined, knowing the basics of putting together a proof is usually good enough to get you to 50%, and that's good enough for our purposes. don't sweat the small stuff. by paying more attention to the fundamentals and less to the surface level concepts, you can pass all your mandatory courses AND the latter elective CS courses with much less effort. i must add that this, by extension, means that you do not have to do every assessment that the prof assigns you. often times it makes sense to skip a random question on an assignment that's really tough and doesn't really tackle the core concepts of the course

some courses that I think are worth paying closer attention to are: MATH 135 for proof skills. CS 136 for C knowledge and general coding and debugging skills which will be really helpful for like CS 246 and CS 241.

some courses I think that are less useful and you will never have to think about again: CS 135 because fuck recursion (altho it might be useful for CS 341 when you do like BFS and DFS and shit), MATH 137/138 (i highly recommend doing MATH 127/128 instead btw, they're suitable for your degree requirements and not many people know that), CS 245, CS 251, CS 350. oh and MATH 239 (fuck this course it was good for nothing).

this tip about focusing on the fundamentals actually leads me to my next tip.

class is usually a waste of time. but there are a select few professors who have really good lectures which aren't a waste of time and are actually helpful.

this applies mainly to 1st year and 2nd year courses, because those courses in my experience are generally the ones with the best professors. guys like Carmen Bruni, Dave Tompkins, Dan Wolczuk, Alice Gao, etc. tend to teach the lower year courses, and they are going to be better at identifying for you what's fundamental for passing a course and driving them into you than you can yourself. i highly recommend diving through ratemyprofessors.com and reddit to get info on the best profs for your courses. don't waste your time going to classes if the prof sucks or you're just not going to pay attention anyways, but also don't waste your time trying to learn something fundamental when you can just drop into the lecture of an amazing prof who can bless you.

that being said, i would never recommend going to class 3rd year and beyond. some of you might even decide that you've got school figured out much before this, only you can really decide. the general expectation though, is that if you paid attention in 1st and 2nd year, you should already have enough skills to pass these courses without any hand-holding from the prof.

ok so those are my 4 main tips for passing the mandatory CS courses. in summary: take advantage of past resources, make friends in your courses, focus on the basics not the fluff, and consider attending the best profs lectures in 1st and 2nd year.

now onto the more fun and hacky stuff, the elective CS courses.

# Part 2) The Elective CS Courses (3B onwards)

once you've passed all the mandatory Math/CS/Stats courses, your life should get a lot easier. 3B onwards was pretty much a breeze for me. that's because if you're in the vanilla CS degree plan, you can literally pick whatever CS courses you want to fulfill your degree requirements. apart from the mandatory courses, you will have to take 6 CS electives. 3x CS 340-398 or CS 440-489, 2x CS 440-489, and my favourite, the 1x CS 440-498 or CO 487.

given that we're dealing with 3rd year/4th year level courses now, not all of them will be a walk in the park obviously. the University of Waterloo offers a lot of very exciting, very useful, very challenging CS courses like the big 3, AI, ML, concurrency, distributed systems, computer vision, and shit like that. but under the heuristics of this guide, we will pay no mind to these courses. after doing a ton of research over the years and through personal experience of trial and error, I think I've been able to identify the absolute easiest and most time efficient 3rd/4th year level CS courses that Waterloo offers, and i'm here to share them with you. of course everybody's definition of easy and time efficient is different, but i think there are a few distinct upper year CS courses that are vastly and universally easier than the rest.

there are 5 courses which in my opinion are the 5 easiest upper year CS courses in the entirety of the Waterloo course catalogue. i am going to refer to these 5 courses as "The Little 5". there's been enough discussion about "The Big 3", it's about time we go the other way around eh?

i've found that these courses all have a mixture of some or all of the following characteristics:

- little to no technical material (little to no coding, no math, no proofs, mostly common sense based)

- no lectures or unnecessary lectures (you don't actually have to spend much time learning anything)

- no exams, instead project based (projects are just way harder to fail unless every single one of your group mates are incompetent. you also avoid the very annoying "must pass the exam to pass the course requirement")

- coursework is done in groups (its almost impossible to fail a course thats based off group work)

now without further ado, here they are, "The Little 5":

CS 492 - Social Implications of Computing - this is the holy grail of CS bird courses imo. there is 0 coding, no exams, and the assignments are just writing english sentences. a significant portion of the grades breakdown does come from in-class participation, but you don't actually have to attend the lectures or participate because if you do well enough on the assignments, you can safely pass with a 50% and easily tank the participation mark. you can't fail this course.

(CS 492 is only offered in specific terms. if you can't take CS 492, i heard CS 490 and CO 487 were easy too, but those are redundant if CS 492 is being offered.)

CS 449 - Human-Computer Interaction - this is the other holy grail. there is 0 coding, no exams, and the entire course is done in a group, where you have weekly tasks. the weekly tasks are basically just writing stuff and drawing stuff, they are very untechnical and you will never have to look at the lectures to do them. the downside is you do have to meet with your group weekly because a prof/TA will come and check in with your group, which does takes up a bit of time. but regardless, you can't fail this course.

CS 445 - Software Requirements Specification and Analysis - this one is very similar to CS 449. it's a group based course with no coding, no exams and handwritten weekly tasks. except the tasks for this course are a bit more technical and a bit more annoying (you have to draw charts and shit sometimes, and sometimes you actually have to glance at the lectures to know what to do). there is a final exam, but it was worth very little (like 20%) and there was no requirement that you have to write the final exam to pass the course, so it's a very easy skip. in general, you can't fail this course.

CS 446 - Software Design and Architectures - this is yet another group project based course with no exam. except this one is mainly coding based. you're going to have to build an android app which is annoying. fortunately, that's all you have to do. there are no lectures, and nothing really outside just building your project. the final app doesn't have to be good so long as it fulfills some basic requirements. as long as you have a group of more than 1 person and can write some Java/Kotlin code that compiles, you can't fail this course.

CS 398 (soon to be CS 346) - App Development - this is a brand new course and a new hidden grail right now. it is ran by Jeff Avery, and will go by the course code CS 346 starting Fall 2022. this is to my knowledge, the only other group project based CS course that Waterloo offers, and it lives up to the hype. its basically the same thing as CS 446, you build a Kotlin project with your group and there's no exam. but since it's newer and masterminded by Jeff, this course has a much smoother ride. while in CS 446 you kinda just make an android app by yourself, CS 398 does a great job of holding your hand along the way while you build your project. it's also a much simpler project. for my term it was a simple note taking app. again as long as you actually have a group of human beings, you can't fail this course.

for the longest time I've had trouble finding a 6th course that has the characteristics I listed above, and I never ultimately did. I ended up taking CS 458 - Computer Security and Privacy to fulfill my final elective CS course requirement which was kind of a bitch, especially A1. if anyone has any input for other courses that might fit the bell as the 6th course, I would love to hear. reddit usually likes to point out CS 348, CS 349, or CS 370 as the bird upper year CS courses, none of which I can comment on because I haven't taken them. but i've heard good things about them from other people. the only thing is i kind've doubt that they will be on the same tier of easiness as The Little 5, sheerly because they have exams and are all mostly individual based. (although i heard CS 348 changed up the structure of their course and now has group assignments?)

alright so if you just take the The Little 5 + one more CS course, congratulations you should have completed all your technical degree requirements! now all that's left is my favourite part of them all: the breadth and depth electives.

# Part 3) The Breadth and Depth Electives

these are the courses that you have to take to fill up the rest of your 40 credits requirement beyond your degree requirements. this is the part of the guide where you have the upmost freedom to take whatever the fuck you want.

have you been a kpop fan for a while and wanna finally understand the words they're saying? take KOREA 101. want to learn more about the soundtracks from your favourite movies? take MUSIC 246. fuck it, if you like Harry Potter you can even take ENGL 108P.

there are a million ways you can complete this part of your degree. just make extra sure that while you pick your electives, that you are mindful of your breadth and depth requirements. this means taking 1 or 2 courses in all the different subjects that waterloo requires (for whatever reason), and also taking 3 courses under the same subject with 1 of them being 3xx or higher, or 3 courses under the same subject that form a prerequisite chain.

bird courses 🐦🐦 are a very commonly discussed topic on this subreddit. the issue is that a lot of people view bird courses as primarily a way to boost their overall gpa. however, we do not care about that for our purposes. for this guide, **"the birdiness scale" is simply gonna be a measure of a course's degrees of easiness and time efficiency. **of course under our heuristics, the goal for us is the find the birdiest courses of them all.

much like I had guiding characteristics for finding the easiest upper year CS courses, I have some characteristics that I've found common in all or most of the birdiest courses. now, easiness and time efficiency are very dependent on the individual, and when it comes to breadth and depth electives, it especially isn't easy to compare courses across different disciplines. these are the characteristics in courses that I personally find the birdiest. i also wanted to bring up a couple specific factors that you might overlook when deciding what courses are actually the birdiest for yourself.

- online courses are king (you can do the entire course from your bedroom whenever you want, you'll never have to worry participation marks and stuff like that)

- no exams (a lot of courses have that "must pass the exam to pass the course requirement" which can make the exam a do or die scenario, and ain't nobody got room for that kind of stress in their life)

- assignment based (its more time efficient to cough up an assignment that can get a 50% than have to memorize the content required to get 50% on a quiz/test/exam)

- least amount of recurring things: no weekly discussions, no weekly quizzes, no weekly assignments. rather fewer, but bigger evaluations, aka more big project based. (that way the amount of times in a term where you have to sit down and do work for the course is reduced greatly)

- creativity based, less textbook information retaining shit (it's way easier to fail an exam than to fail a creative project imo)

i personally think that the more subjective/creativity based courses like english or art can actually be birdier under these heuristics than a lot of the commonly discussed bird courses such as HRM 200 or ECON 101. this is because you don't have to spend as much time reading and learning about stuff, and instead you can just spend your time doing the assignments. of course, if you are not a good writer or a good artist, you probably won't get a good grade on these assignments. but that doesn't matter for our purposes of course. i've found that it's pretty difficult to write an essay that doesn't meet the passing requirements. pretty much as long as its written in english, meets the word count, and ran through grammarly one time, it should be good enough. who is the professor to say that you're opinions are wrong? who is the professor to say the painting you drew is bad? the point is, the more subjective a subject is, the harder to fail.

in addition, when it comes to these more creative based courses, assignments are usually bigger, and less frequent. that means all you have to do is, a few times a term, start the assignment the night before its due, and cough up something. it is a lot more time efficient to write an essay full of BS, or draw a painting full of scribbles than to sit down, read, and memorize enough facts to pass a test.

so that's my case for looking into more creative courses for your breadth and depth electives.

however, another factor that can definitely be important for determining the birdiness of a course for you, is your level of interest. writing an essay on the current technological landscape might in theory, be a lot quicker than memorizing the facts on different rocks. BUT, if you find writing boring and are actually very fascinated by rocks, then it will probably be easier to take the course you are more interested in. and of course, not all creative courses are easier than non creative courses. for example, i took MUSIC 275, a course on producing music in Ableton. if you've had no experience with music production or the Ableton software, learning how to put together an arrangement might be a lot more difficult for you than memorizing some facts on your favourite rocks.

so ultimately, when it comes to finding the birdiest breadth and depth courses, there is no hard guide really. there are a lot of commonly known bird courses, you know your CLAS 104, HRM 200, ECON 101, MUSIC 140, REC 100, etc. which you should definitely consider. but i encourage you to think about the characteristics that make a course birdy to you.

just for the sake of it, i'll drop some of my personal favourites out of the ones i've taken that you might not have heard of

GEOG 219 - How Pandemics Change the World - this is a new course that they started because of COVID-19, and man is it 🐦. there are weekly discussions, but you don't need to do them because they're only worth 10% of your grade overall. instead, there are just a few writing assignments, and some of them are extremely short (1 page double spaced). it was online and had no exam.

ENGL 119 - Communications in Mathematics & Computer Science - this is perhaps the most elementary course i have taken. this course is about writing in professional settings for tech people. so we focused a lot on writing proper sentences (subjects and clauses and what not) and our assignments were to make resumes and cover letters. no exam. i had a lovely experience.

ENGL 108D - Digital Lives - the assignments were just reflections on different articles on the topic of digital media, which i found fairly interesting. it was online and had no exam.

MUSIC 275 - Music and Technology - as mentioned earlier, a course just about making music. we had hella creative freedom so it was hella fun. basically just messed around with random sounds the entire course. the songs i made were not good at all, but good enough to easily pass still.

/endguide

# Afterword: Don't stress

when we're students, we tend to overly stress about... everything. our paleolithic nervous systems create fears out of thin air that we're going to fail a course or not going to graduate, etc. for whatever reason. these fears usually don't help us at all. if you have higher aspirations such as getting good grades, getting good co-ops, i can't help you there. hopefully there are other guides out there for that. but if you simply want to graduate, i can guarantee that if you follow this guide, you should be able to easily walk out of this school with a Bachelor of Computer Science Degree in your hands, while having saved a lot of your time, and having the ability to look back and say "damn, why did i even stress".

so seriously, don't stress, the point of this guide is so that you don't have to waste any time stressing about if you're going to graduate or not. you definitely will. all that stress is pointless when you look back.

i spent a shit ton of time in my first 2 years here stressing about whether or not i was gonna graduate

in fact, the only reason why i was able to come up with the contents of this guide was because i stressed so much in the beginning. i never coded at all outside of school, i hated math, and i was never interested in cs at all. i spent all that time obsessing over finding all these hacks to make Waterloo CS as easily doable as possible because actually learning CS was the last thing i wanted to do, and so hacking my way through was the only way i thought i could graduate. you can tell how obsessed i was just based on how fucking long this guide is.

in reality, if i just didn't stress as much as I did back then and decided to just study like a normal CS kid, i probably could've just graduated just like anyone else. but admittedly, all the hours spent creating excel sheets optimizing my course plan, all the research finding the absolutely best professors, all the smart friends i made, all the alumni i contacted to collect crowdmarks of past exams, all the research i did finding the birdiest courses of all...... all of it was wayyyyyy more fun to me than just sitting down and studying like a normal kid. it was kind of just like playing a video game.

either way, i'm hoping that i spent all that time stressing and obsessing so that you won't have to.

did i waste 5 years of my life and a shit ton of money? definitely. did i have one hell of a time doing so? fuck yeah.

it's been an absolute honour memeing with you ladies and gents these past 5 years.

i wish you all the best on your journeys, whatever they may look like.

peace,

u/conradismydaddy out ✌️

tl;dr --if you want to graduate from the University of Waterloo CS with as little effort as possible, follow these 3 steps:

1. stumble your way through your mandatory courses by taking advantage of past resources, making friends in your courses to do assignments with, focusing on the bare minimum material you need to learn and complete to pass the course, and committing time to the lectures of the very best professors.

2. once you're free from your mandatory courses, take "The Little 5" CS courses and coast your way through them.

3. fill your breadth/depth electives throughout your degree by establishing your criteria for what a bird course is, and stacking those courses. my recommendation is to take mostly creative based courses because they save time overall and although they may be harder to do well in, they are harder to fail.

**EDIT - fixed up some grammar mistakes, added notes under Part 1 that more recent crowdmarks are better than older ones, and that you should consider not doing every question on every assessment that the prof assigns you. also added a tl;dr for those who were asking for it

Join the conversation
Sort by:
Best
Open comment sort options
sushigobble
• 4y ago

Need this for every program.

epicboy75
• 4y ago
mech and potatoes

Who wants to do mech next 👀

SquidKid47
• 4y ago
tron 26

or tron please god

steven_0
• 4y ago
MOOCatronics

You don’t get any electives during the hardest semesters lmao.

SquidKid47
• 4y ago
tron 26

if youre talking about 2B im honestly looking forward to it bc the courses look kinda sick 🤡

steven_0
• 4y ago
MOOCatronics

The thing is if you’re enough of a psycho to look forward to 2B because you love math and embedded systems that’s awesome but it means you’ll likely dislike 3a and 3b (the other hardest terms) because they’re super heavy on mech stuff. Unless you’re William Melek’s dream student and actually still love all the elements of tron lmao. It’s pretty painful for 95% of the class, and there’s no real easy way out. Ie you could take a bird in 3b, but this won’t help much and you may not be as eager to do this as you think since there’s a very good chance you’ll be frustrated at not having the freedom to mostly take courses you personally find interesting. If you put in the work though, it’s doable.

SquidKid47
• 4y ago
tron 26

Unfortunately I fucking hate tron because I despise mech bs, I am going to regret not getting into CS until I die

steven_0
• 4y ago
MOOCatronics

Rip. This isn’t as uncommon as you might think though lol. Depending on how much you hate it though maybe consider transferring (Ie to se if your marks are good? I know like four people who did this but half of them were literally geniuses). If you decide to stay, pray that you get Kamyar “the GOAT” Ghavam for as many mech courses as possible lmao. Absolute legend.

SquidKid47
• 4y ago
tron 26

I've considered but for some reason never bothered. My marks were pretty good somehow but I remember the requirements to switch out being stupidly strict.

I guess Tron keeps more doors open for me though. I'll probably just look to specialize with CS/SE classes and call it a day. If I don't off myself in 3A/3B.

[deleted]
• 3y ago

Bro you'll legit still get related coops

1 more reply
1 more reply
More replies
More replies
More replies
More replies
More replies
More replies
1 more reply
More replies
More replies
kan829
• 4y ago

In keeping with your thesis, tl;dr. But having read the first few paragraphs I think you might be my illegitimate (also in keeping) son resulting from an East 2 kegger in my 1B term in the summer of 1986.

I'm BMath '90. The only two things I learned and applied to my career were:

a) If 50% is a pass, then getting 51% represents wasted effort.

b) "The time you enjoy wasting isn't wasted time."

Epilogue... I chose to retire at 48 (further in keeping with your approach) after being downsized from Blackberry.

Best wishes to you, my son.

ConradIsMyDaddy
• 4y ago
cs alumni '22 || what is the definition of a basis?

... dad, is that you?

kan829
• 4y ago

I'm expecting a card from you on Sunday. But I'll understand if you cannot be bothered.

I just noticed your PornHub hat. Now I'm crying. I'm so proud of you.

c_m_d
• 4y ago

Kanrad was your daddy afterall

More replies
wagwanm0n
• 4y ago

Lmk when the next kegger is

More replies
[deleted]
• 4y ago

Most effort u put in all course was in this post eh😭😂

ConradIsMyDaddy
• 4y ago
• Edited 4y ago
cs alumni '22 || what is the definition of a basis?

call it FUCKWATERLOO101

More replies
ApprehensivePaint128
• 4y ago

Anyone who needs this guide is most definitely too lazy to read that novel of a post

AdmiralG2
• 4y ago
dd fraud

I managed to skim it

kaifung31
• 4y ago

thank you to the bolded words

More replies
JavaGusLuna
• 4y ago

Saved this post. I don’t know how I got here. I’m a mom and I’m showing this to my kids - once they have been accepted into uni. Best advice ever!

ConradIsMyDaddy
• 4y ago
• Edited 4y ago
cs alumni '22 || what is the definition of a basis?

this is either really good parenting or really bad parenting. either way i wish you and your kids success!

JavaGusLuna
• 4y ago

C’s get degrees!

More replies
More replies
wagwanm0n
• 4y ago

Legend

Grammar-Bot-Elite
• 4y ago

u/ConradIsMyDaddy, I have found an error in your post:

> “course, so its [it's] a very easy”

It is the case that you, ConradIsMyDaddy, botched a post and ought to say “course, so its [it's] a very easy” instead. ‘Its’ is possessive; ‘it's’ means ‘it is’ or ‘it has’.

This is an automated bot. I do not intend to shame your mistakes. If you think the errors which I found are incorrect, please contact me through DMs!

ConradIsMyDaddy
• 4y ago
• Edited 4y ago
cs alumni '22 || what is the definition of a basis?

honestly im just glad there's only 1 error in the post and that you didn't call me out for writing the entire thing in lower case

epicboy75
• 4y ago
mech and potatoes

Damn ruthless huh

More replies
Startereclipse
• 4y ago

Ur actually my hero not even trolling, good luck with your future plans bro, u left the sub a bit better than when you found it, lub u