Use it to build one real project, get comfortable with Git and a second area of programming, and try one thing outside class such as a hackathon, open source or a small internship. Keep a weekly schedule of 15 to 20 hours and leave room to rest. You do not need to master everything this summer.
What people tell me
I just finished my first year of computer science. I passed my courses but I feel I only know basic programming from class. I have two or three months off and I do not want to waste them, but I also do not know what is worth doing. Some people are doing internships, some are grinding problems, some are learning AI, and I am confused about where to start.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- The best first-year summer produces one finished project you can explain, not five started courses.
- Learn Git and how to set up and run a project. These skills pay off every year after.
- Try one outside activity: a hackathon, an open source issue or a short internship.
- 15 to 20 focused hours a week is enough. Rest counts too.
- Write down what you did each week. It becomes your resume and your internship story next year.
The goal for this summer
After first year, you are not trying to become job-ready. You are trying to go from "I can write code for assignments" to "I can build a small thing on my own and show it to someone". That single shift makes second year, internships and projects much easier.
Pick one of three summer shapes
| Shape | Good if | Main output |
|---|---|---|
| Builder summer | You want to know what building software feels like | One complete project, deployed or easy to run |
| Foundations summer | Programming still feels shaky | Strong basics in one language plus DSA fundamentals |
| Experience summer | You found an internship or a small real client | Work experience and a reference |
Most first-year students should choose the builder summer and add a little foundations work. If you get an internship, take it and do a lighter version of the builder plan alongside.
What to learn, in order
- Git and GitHub. Commits, branches, pushing, reading a pull request. You will use this for the rest of your career. Git, properly explains the model underneath the commands.
- One language to real comfort. Whatever your university uses or Python or JavaScript. See the Programming foundations roadmap.
- One small area of building. A simple website, a command line tool, a small mobile app or a data notebook. Pick what interests you most.
- Light DSA. Arrays, strings, hash maps, basic recursion. A few problems a week is plenty now. The DSA roadmap orders the topics.
Skip, for now: advanced AI frameworks, three frameworks at once, and anything that only makes sense after you can build basic apps.
A 10-week summer plan
| Weeks | Focus | Output |
|---|---|---|
| 1 | Rest and set up | Editor, Git, GitHub account, one tiny repository |
| 2 to 3 | Strengthen your language | 20 small programs you wrote without copying |
| 4 | Pick and scope a project | A one-page plan: what it does, three core features |
| 5 to 7 | Build the project | Working core, pushed to GitHub weekly |
| 8 | Finish and polish | README, screenshots, deployed or runnable |
| 9 | One outside activity | A hackathon, an open source issue or a meetup |
| 10 | Review and plan second year | Updated resume, notes on what you want to try next |
A realistic week: 3 hours on four weekdays, plus 4 to 6 hours at the weekend. Keep one full day off.
Project ideas that suit a first-year summer
- A study planner that stores tasks and deadlines in a file or small database.
- A website for a student society or a relative's small business.
- A script that tracks prices or scores from a public API and sends a summary.
- A simple quiz app for a course you just took.
Choose something with a real user, even if it is only you or a friend. Real users create real bugs, which is where most learning happens.
One outside activity
Pick one:
- Hackathons: a weekend of building with a team. MLH hackathons lists many that run online.
- Communities: Google Developer Groups often run student events and study jams.
- Open source: find a beginner-labelled issue in a tool you use and try to fix it.
- Short internship: if a small company will take you, even for six weeks, say yes.
What a good summer looks like at the end
By the last week, check yourself against this list:
- You have one finished project on GitHub with a README someone else can follow.
- You can create a branch, commit, push and open a pull request without searching how.
- You have solved around 30 to 50 easy problems and understand why each solution works.
- You have done one thing outside class and met at least two people in tech you did not know before.
- You have a short list of what you want to try in second year.
If you tick three or four of these, the summer was a success. Nobody ticks everything, and that is fine. The point is to arrive in second year more confident than you left first year.
Common mistakes
- Starting three online courses in week one and finishing none.
- Grinding hundreds of DSA problems before you can build anything.
- Copying a tutorial project and calling it your own. Change it enough that you have to solve problems yourself.
- Not resting at all, then starting second year exhausted.
- Not writing anything down. By September you forget half of what you did.
Keep a summer log
Every Sunday, write three lines: what you built, what you learned, what is next. By the end you have a record that turns into resume bullets and a story for internship applications next year.
If you are still stuck
For how to split your time, read Should I spend my free time building projects, solving DSA, contributing to open source or networking?. If you want someone to review your summer plan, join Sefism. Learning is free, you get credits on joining and your first roadmap is free. As a member you can ask your own question and get a written answer for your situation.
Was this answer helpful?
Read next
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.