I would say after a class, apply what you learned in class. If you learn Java, write a Java program you want to write. If you learn computer graphics and how

I would say after a class, apply what you learned in class. If you learn Java, write a Java program you want to write. If you learn computer graphics and how to do OpenGL transformations and rotations in C/C++, write (or help port) a program that does OpenGL transformations and rotations in C/C++. If you learn AI with deep learning, write a program that uses deep learning (even if it doesn't really work out, you'll learn a lesson where deep learning is applicable and where it is not). Some classes can be theoretical with toy examples, it's useful to bring it into the real world right after a class. Also you mention Github. Look at popular projects there that regularly merge in random pull requests (meaning pull requests that are not from the same core of 1-3 people). Look at what open issues the project has and what might be listed in their BUGS file. Fix a problem and put up a pull request. You will probably be fixing defects at a future job and this is not all that different than what you will be doing. They might have some advise if they use your pull request with some changes such as how to simplify it or use a particular coding style, and this is useful too. I say to look at popular projects there that regularly merge in one-off pull requests because some projects might be abandoned so you might not get this. You want to have some understanding of this - https://missing.csail.mit.edu https://missing.csail.mit.edu Your main problem will be getting a job after graduation with little experience. If you have an internship at a large company that is hiring between junior and senior year and they like you, you might have a leg up on getting a job after graduation. Also try getting internships in earlier years. If you can make small contributions without too much hand holding they might take a chance on you.