Side Projects Q&A and Videos

I'm sure Alex and Rahul talk about this in their Masterclass "How To Write Better Code Faster as a Software Engineer", but wondering how to write clean code, particularly in the context of someone who doesn't have technical people available to review my pull requests in my work or in side-projects. I'm sure this skill is almost entirely developed by working with talented people and writing a lot of code, but is there a place for resources like "Clean Code" the book or courses on Udemy?

I am looking for a Software Engineer role in big techs. They varied my experience in my previous company, i.e. I was part of three different projects, all of which used different tech stacks, and none of them was a development project. Now I am confused about adding projects to my profile because I do not have any projects related to development. I have experience in python that is related to Data Science. I would love some guidance on deciding on what to build and how to choose between web, front/back end, full stack, android, etc.

Hi guys to me the most difficult part of building an android apps is coming up with an idea of what to build. To me it feels like there are almost no android apps that I can build that are unique since it feels like almost any android app idea I come up with, someone else has already built it or used my idea. What is your guys advice on this situation especially when I'm trying to build an app with the goal of attracting a lot of users?

I have never contributed to open source but would like to start doing so. I believe this will make a huge difference in landing big tech jobs. Would like some references, steps, directions for beginners to get started in this journey.

When learning new things, I often find that I don't know this, don't know the best practice in that, and so on. If I go down these rabbit holes, a lot of time is spent and not much progress is made in the original project. If this is a scene at work, usually there are external factors to guide you not to go down these rabbit holes, be it the deadline on a task or advice from colleagues. But how to manage this while building side projects? Especially, time after work is equally precious that you sacrificed doing other things to build a skill, and progress gives motivation. But at the same time, going down these knowledge rabbit holes also builds knowledge, and be more niche. How would you trade off knowing everything vs progress in side projects?

Lately, I have been finding myself with a lot of free time and am unable to shake this feeling that I am not "doing enough." After finishing my school work, I usually just go to the gym, hang out with friends, or play video games. Is there anything else I can do to further improve myself as an engineer and set myself up for success later on? Perhaps some books or resources to read. I've tried working on some side projects, but honestly find it hard to follow through with them due to lack of urgency with no deadlines and prior fatigue from working on school assignments.

I've heard 1-1.5x your full-time rate is valid. I know this will likely be context driven, I'm specifically looking for longer-term hourly rates as opposed to short-term / project-based, but would be interested in knowing the differences if there are any. Thanks in advance folks!

Question was inspired by Alex's masterclass on side projects. In it, he talked about how he was able to get his role at Course Hero because it was a scrappy startup when he joined, and was willing to take bets. Do you have advice on how to find similar startups? And also connect with startup founders (and not get ghosted)? Some consequent questions: How do you know if a startup is scrappy or if it is shady/dysfunctional? Are there any resources on Taro to connect with founders? Thanks for any advice or help!

I'm a self-taught, aspiring Android engineer, looking to land my 1st full-time role. I have around 4 hours a day to learn software development, and I'm wondering how I can spend my time the most efficiently. Here are the 2 core things I want to understand how to balance my time between: DSA (data structures and algorithms) Building projects for portfolio

For context, I mainly work on the web-side, building customer-facing surfaces. I don't want side projects to be something like DSA where it's good for interviews and that's it. The concept of side projects makes me think of Flappy Bird when it came out. It seems like it started off as a side project, so this is all interesting to me and would love to learn more about the benefits.

My goal is to transition into a SWE role, but something I've struggled with is making the building of software projects more digestible. A lot of the time I'll look at some project I have to build, and I just don't know where to start or how to figure out what to do. Any tips on how to make this process less scary?

The applications our current team develop are targeted for individual users only and most of our projects are centered around building complex business logic rather than scale. So there is less scope to gain experience on concepts such as parallel processing, concurrency, caching or similar. What are my options to become really good at these skills if I am not working on these on a day-to-day basis?

Getting More Users Let's say I built a web app and got a dozen friends using it (a clean simple job board that removes all frustrations I face with other job boards like LinkedIn/Glassdoor/Indeed, my friends love it). How can I scale to 10k+ users? I saw the masterclass talk about SEO for getting more installs, but I'm unclear how to get more users for my web app -- I'm personally not interested in mobile dev and I'm more interested in backend heavy projects. I saw this question but I found the responses pretty unsatisfying - ### Getting more Interviews I also noted that in Alex's talk he talks about how people contacted him on his google play email for interviews. For web apps, how can I get more interviews? Is just telling it on the resume enough? Would recruiters even see the bottom of the resume with projects? (I assume most recruiters skim the latest job experience and then titles) Also what are the thresholds for "impressive" user counts? is it 50/100/1k/10k? Would love to hear stories on how people got interviews from having websites with tons of users!