Step-By-Step Guide To Build An Impressive Software Project
Something that has made me really happy about the tech industry is that it’s becoming more and more centered around actually building projects instead of writing raw code that’s very disconnected from the real world. Back when I was at UCLA 7+ years ago, we were mainly writing small programs and scripts that ran in isolation from the command line. Things are a lot different now, both at universities and bootcamps. Students will actually build projects that can be deployed and shared, things that people can see and feel.
But here’s the problem: Almost all personal software projects are terrible. If you’re a junior developer, you might be experiencing the pain of this first-hand as you’re wondering why no company will hire you despite the 2–3 entire functional projects on your resume. The job posting wants X and you have built a couple working apps or websites that use X, why aren’t you getting the job?
The reason this happens is because there’s a huge gap between an impressive, meaningful software project and a functional one. 8–10 years ago, just getting something up and running on a public deployment that anyone can try was quite impressive. Nowadays, it’s meaningless as anyone can do it. The goal of this article is to help you bridge that gap by teaching you how to build software projects that actually have a chance…
