Ask HN: advice for taking difficult CS programming courses?
3 comments
Take the challenge, step up your game. Since you already know what difficult courses you have, why not work on them beforehand by studying for them or becoming the as best a programmer you can BE in the courses you are taking now.
I had a very basic programming course. Then an algorithms course. Then an Assembly course, then compilers, then OS. All were in different languages and there was very knowledge transfer. I don't think the number of courses matter as much as how well you understand the ones you have.
OS was my second best undergrad course, right after compilers.
I had a very basic programming course. Then an algorithms course. Then an Assembly course, then compilers, then OS. All were in different languages and there was very knowledge transfer. I don't think the number of courses matter as much as how well you understand the ones you have.
OS was my second best undergrad course, right after compilers.
Your grades will never matter.
However, the difficulty of the challenges you take on will make all the difference in the world.
Grad schools and employers want people who can take on hard problems, who can do so with autonomy, and who can get help when they need it.
Start practicing.
However, the difficulty of the challenges you take on will make all the difference in the world.
Grad schools and employers want people who can take on hard problems, who can do so with autonomy, and who can get help when they need it.
Start practicing.
Do you feel the program is flawed since it only has 3 programming courses before an OS course? I think the major reason is that students don't do well is because of lack of practice.
That could be true, or it could not be. I had more courses before my OS class, but strictly speaking, I didn't necessarily need to take them in that order.
Either way, it seems that the thing to do would be to get more practice independently. If you're really worried about that particular course, see if you can read up on some of the material beforehand. If the assignments are published somewhere publicly, you could even start on them early.
Also, dropping the course and re-taking it isn't really a dirty trick - they just took some more time to learn the material. You could do the same by getting a head start practicing it. If they finished with a 96% the second time, there's a good chance they learned more from it than someone who got through with a 50% and never touched the material again.
Either way, it seems that the thing to do would be to get more practice independently. If you're really worried about that particular course, see if you can read up on some of the material beforehand. If the assignments are published somewhere publicly, you could even start on them early.
Also, dropping the course and re-taking it isn't really a dirty trick - they just took some more time to learn the material. You could do the same by getting a head start practicing it. If they finished with a 96% the second time, there's a good chance they learned more from it than someone who got through with a 50% and never touched the material again.
Don't worry too much about grades. Take on the challenge.
Before taking up OS course, make sure you become proficient in C and understanding pointers.
If anyone did well in their respective OS courses could you provide some advices? I know that it varies from program to program but please share anything you can.