Ask HN: Any tips for a college freshman enrolled in computer science?

This may sound a little bit ridiculous, but if you’re really into computers: Grab a 6502, build a computer yourself - the chips are cheap and overall availability is good. Try writing a small operating system, an interpreter like Basic or Lisp or a game. After you accomplished that you already know more than most CS grads and the knowledge will be so fundamental that it will help with everything else coming to you in future.

Are there any that you'd recommend?

> One more thing: be social

This is really important. I didn't appreciate it at the time. Get to know people in your classes, not just your roommate. Join a club, or check out greek life if that appeals to you. If you weren't very social in high school, now you're in a new environment. Nobody knows you, and nobody cares about high school anymore.

If you're introverted it can feel awkward but you're rarely, probably never again, going to be in such a diverse group of people who are all about your age and stage in life. Certainly not for four years.

Tired of recruiters asking me if I had a BSCS, I went back to college after years working in IT.

Had a conversation with the other seniors in a CS 300 class one day, I would say a few of them were in the top half of the class. Was talking about software version control. "What's that?" they all said. "You know, like git", I said. "Git?" they said. None of them knew what software version control or git was.

I would suggest that if you have a class where you learn say C++, toward the end of the class, or right after the class, write your own C++ program - doing whatever you want it to do. If you take a graphics class where you learn OpenGL, write your own program using OpenGL - doing whatever you want it to do. You tend to learn these things more doing it.

A lot of people are flooding open source projects with AI right now, but that aside, also if you just learned C++ or Java or whatever, look at actively maintained open source projects on Github or Ubuntu or Debian or freedesktop.org or whatever. Look through bug reports. Try to reproduce them. If you reproduce, you can reply to the report with what versions you are using (latest is best usually) and that you reproduced it. You can try to fix the bugs too. One thing with this is - it's similar to what an intern or associate/junior SWE would be doing at a company. If you submit a pull request and it gets accepted - it is like what you are doing at a big company.

Years ago I went to a Debian bug squashing party. I didn't know if I'd know anyone there, but getting there I did know one guy who did IT work in my city. Anyhow, a lot of the people there were pretty good. I remember a fellow named Daniel talking and he seemed to know a lot. Plus others. Then someone else walked in and everyone started saying "Pablo is here". It was a fellow named Pablo who was doing a doctorate in computer science at Columbia, They were all looking toward him and curious what he was working on. It seemed like they thought he was one of the most knowledgeable person there, among a group of knowledgeable people.

The point of this is - it was a group of people who were pursuing technical knowledge, and who respected technical knowledge. This guy Pablo from what they said was very devoted to this, and they respected him for it. This kind of social reinforcement is important too - it's talked about all the time, how being in San Francisco or YC or whatever with like-minded people pushes people ahead. I have seen it in many circumstances. Being part of one or more social groups like this focused on getting technically good and eventually trying to get to be a SSWE in a FAANG or whatever is something that helps. It can be easier to find in some places than others, but there are hackers everywhere.

Actually learn to code instead of just prompt. Get any internship you can as early in your college years so you can understand if you like working in the industry before getting to far along. Once you have an internship take it seriously. Just because the company or team you are on is terrible its much better to be in a position to get a return offer instead of being desperate to find a job upon graduation.

Interns that I have seen be successful at Amazon do the following:

1. Show interest in the process.

2. Work really hard to unblock yourself. (You should feel like you're stuck a lot of the time. If you're not the project is too easy)

3. Learn when to get help to unblock yourself.

4. DO NOT tell anyone on the team or adjacent to the team you are on that you are not interested/ would not accept a return offer. This will guarantee no offer. Our best intern did this. (If you are skilled everything will turn our fine but it is nice to have options)