Suppose I don't get a job after college (something Ive been stressing a lot about) and end up working a crappy job I hate. How can I turn it around and be financially free before 30? Are there skills that pay a lot, gigs you can do that can later end up as a business? If there's a lot of luck to it, can I increase my surface area of luck as some people say?
What should I do for my resume before trying to apply for SWE roles? I don't really have anything good but I do plan on joining a few clubs this upcoming semester.
im too worried about what project is good to make, how unique it is, how advanced it is, etc. how do I stop stressing over this and actually start one something without feeling like im losing time (im pursuing CS)
basically title. i've seen people say you should aim to do 1-2 new problems a day. and others say that you spend your time knocking out 4-5. Im a current student (rising sophomore)
Basically title. I have around 20 of the Neetcode 150 done and thats all i did so far (rising sophomore so just getting started)
Basically title. My goal is to start my own business and be financially free, but also be exposed to new opportunities.
Like there's so many technologies one has to learn? How do you go about learning all of them?
I'm currently a rising sophomore - had a lot of anxiety freshman year so I didn't do a lot, but I recently completed a personal project and made it installable from Github release page (which I think is my first positive milestone). However, im looking for advice on next steps.
obviously my experience doesnt cut it. So i'm looking for advice on what to prioritize this sophomore year to not fall behind. I'm going to be spending August learning Web Dev and completing the Javascript portion of the odin project.
Current concerns:
- Should I still apply to internships
- Should I do my research on what roles I want to get into or specialization something for later in my career?
thats kind of it.
Thank you for any critiques.
I'm currently a rising sophomore - had a lot of anxiety freshman year so I didn't do a lot, but I recently completed a personal project and made it installable from Github release page (which I think is my first positive milestone). However, im looking for advice on next steps.
obviously my experience doesnt cut it. So i'm looking for advice on what to prioritize this sophomore year to not fall behind. I'm going to be spending August learning Web Dev and completing the Javascript portion of the odin project.
Current concerns:
- Should I still apply to internships
- Should I do my research on what roles I want to get into or specialization something for later in my career?
thats kind of it.
Thank you for any critiques.
basically title. I mean ofcourse, if you want to revisit a topic there ARE going to be some questions you have to revisit. But is spaced repetition really necessary? Can't I just encounter a new problem after a new problem and slowly build up that intuition until I decide to revisit the topic? And if I did have to practice spaced repetition, would I have to revisit the same exact question, or just re-explore the same questions of the same topic (like spaced repetition for the specific question or any questions you did under a said topic?)
How do I do interview prep? I'm currently doing neetcode 150 and just sticking to 1 topic for like 2-3 questions and then switching. Should I be mixing in leetcode? And when do I start rubber ducking and/or considering different solutions/edge cases? And how do I study system design and architecture? Are there resources to use? Thank you.
Im building a basic note taking app in java swing, am i wasting my time with this technology?
Just a few questions about obtaining research experience as a rising sophomore. I'm assuming I can't be picky about pursuing my first research position, and that it would take a lot of cold emails to professors to land opportunities. so I have a few questions.
- Do I need to build projects in a field that I want to get into? (i.e. i've never built computer vision/graphics projects before, but they interest me)
- Should I target emailing other schools professors as well for a niche in computer science I want to research into?
- Or should I cast a wide net and also apply for research positions in labs that might need software implementations (do I have to prove my competence or show genuine interest?). Would applying software in separate fields look better on my resume than doing something related to computer science? (since it shows you can apply software to an external domain)
Appreciate any replies, thanks.
I've been stressing a lot about the "what if", like not being able to get an internship or getting a job after graduation. Does anyone have any words of wisdom?
How long does it take to build out a typical project? I've been seeing people say it takes roughly a few weeks, whilst I'm just learning Java Swing and basically making a basic notes editor on the desktop that's taken me roughly 4 weeks (and its not even close to being finished).
So I'm an upcoming sophomore, and I've been spending about 2 weeks building out a basic Java desktop app for my resume (I don't have much so far). The thing is, I've been hand coding it the entire time, and it's far from being fully fleshed out, since I spend about 3 hours a day working on it. I'm also learning web dev on the side through TOP, doing the exercises and projects. HOWEVER, I have friends who have been vibe coding their projects and then getting Claude to explain those same projects to them. Is this what I should be doing? Their projects look a lot more resume worthy than mine, AND they're using AI-assisted programs. I've just been hesitant because I enjoy hand coding and it at least lets me piece together the project step by step. If I SHOULD start vibe coding, how can I learn how to properly do it? How would I eventually learn how to call APIs myself, or how to use databases, or how to deploy projects, etc?
Basiclaly, if I start vibe coding, will I miss out on a lot of important learning concepts? Does it even matter?
Are interns expected to know all of this? I see all this random advice on instagram aboit all the things you have to learn, and they're coming from people who scored big tech or adjacent intwrmships.
How do you figure this out? I'm more concerned about the limitation of time (because I already know that building projects will tell you what you're interested in), because internships are hard to get by and people are stressing how you should niche down to optimize for specific roles. But how do you pick the kind of area of software engineering you want to do with such limited time?
Does anyone have/recommend any resources to learn about all this stuff? Are they asked about a lot in interview for internships? And I know I can google these topics and look up YT tutorials, but I don't what else there is to be covered so I was hoping people could have useful resources.
Everybody talks about how your 20's are the time for massive change and improvement, where you can explore, try to start a business, take risks, etc. But I always assumed that would be the case if you managed to get a good job out of college graduation. However, given the current circumstances, what is the worst that can happen if you DONT get one? I read a quote somewhere once, where if you can tolerate the worst, then thats just enough to keep you going, or something like that.
