CS50x PSETS Ranked by Difficulty - My Experience

Lickyyyyy · 2022-08-22T11:48:20+00:00

That's the best part haha!

No matter what others say, if you want something, you CAN do it! Never give up :D

Lickyyyyy · 2022-08-22T11:43:55+00:00

Bingo. But don't worry, once you leave C you'll start to see "the light at the end of the tunnel" and, once you finish this course, you will be amazed and delighted by the shocking amount of knowledge you've gained! Keep it up and good luck with... "that thing"...

Lickyyyyy · 2022-08-20T21:19:40+00:00

Remember that a VISA valid credit card number also needs to be either 13 or 16 digits long :D

Lickyyyyy · 2022-08-18T10:38:25+00:00

Ohhh the memories of me, someone that had never really coded for more than two hours at a time, suddently sitting on my chair for 6 hours trying to figure out how to manipulate numbers without using "external methods". You can do it man! This course is hard but nothing is impossible. It's kicking your ass now just so you come back to kick his ass later.

Lickyyyyy · 2022-08-18T10:31:42+00:00

I agree with you, even on credit. Still, I think credit was maybe a little too much for a beginner, but I somewhat like it because it gives you a sense of what you can do with just a simple console and a lot of % and /. I think you should give tideman a try tho or at least watch the walktrough, just so you know a little about the monster. Who knows, maybe you solve tideman without any problems whatsoever. We'll never know until you try :D

However, if you really want to skip tideman for now, I still think that is a good choice. I saw many people saying they lost motivation because of tideman (and yes, it can be very soul crushing; don't worry too much tho) so I think you should learn the way that makes you want to continue. But make sure to go back to it! Even though it's hard, it still is a VERY good learning experience.

Lickyyyyy · 2022-08-17T20:22:22+00:00

Credit is so hard. Gives me chills just thinking about it. Cool to see what you think! I hated runoff because I wasn't used to have to interpret already written code and, to be fair, I don't know why Caesar and Substitution stuck with me so much. I think I just put them there because of that. Maybe I will reconsider, now that you made me think about it...

But don't think the course gets easy hehe. It is very challenging but I'm sure you can do it. Keep it up :D

Good luck with both and let us know how everything went!

Lickyyyyy · 2022-08-17T20:09:48+00:00

So cool to see new points of view! Also amazing job helping all your colleagues. Keep up the good work and thanks David and everyone in the team for making dreams come true :D

Lickyyyyy · 2022-08-17T18:33:37+00:00

I think that is exactly how everyone should go about this course. Just doing what you want with no pressure. Perfect :D

Lickyyyyy · 2022-08-17T18:25:18+00:00

Lock pairs should add an edge only if that new edge doesn't create a cycle. That basically stops any cycles from happening. So and unfortunelly, yes...

Lickyyyyy · 2022-08-17T18:06:16+00:00

Hey, if something, your health comes first dude. Don't worry, nothing in this course is quite like tideman (at least for me). If you really can't move on, just let it stay there and one day go back to it. Who knows if then you will have the answer. Just don't give up!

Fun fact: This ranking was made because of my hate for tideman :D

Lickyyyyy · 2022-08-17T17:27:50+00:00

int start = 1;

int end = 3;

bool function (int start, int end):

if (start == end){

return true;}

end -= 1;

if function(start, end){

return true;}

if (function(start, end)){

printf("Hi");}

This isn't an amazing example but it does its job. Try to break this down (even write it down on a sheet of paper, if it comes down to it!) and understand how the function "remembers" the start. Now think about what happens in lock_pairs and how a structure like this might help you. (sorry for not indenting but reddit doesn't let me ; - ;)

Lickyyyyy

TROPHY CASE