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?
This is a feeling I completely resonate and empathize with - It's very common among earlier-in-career engineers. At a high-level, my advice is that any piece of software can be broken down into a series of steps. Here's a basic example with loading the main feed in the Facebook app:
And from there, each step can generally be broken down into more and more steps. For example, "queries the database for relevant items" can be broken down establishing a connection to the DB, formulating the query, running it, and then parsing the objects returned.
The end goal is to keep breaking things down until everything is atomic (i.e. can't be broken down anymore). From there, just go in order and tackle them one at a time.
Another dimension is that if you're working with the UI, you can also break things down visually. Take this Taro Q&A page for instance - You can break it down into a submit button, the header, the footer, the metadata on the question. Once you have split up this giant page into many "components", just start building them one at a time - Easiest to hardest, top to bottom, whatever makes the most sense to you!
I heavily recommend these other resources within Taro to help you with this problem:
Lastly, if you want very concrete, tactical help on breaking down a task/project, feel free to just share it within Taro (while obscuring company-specific details of course)! I'm always happy to come up with ideas on how to execute a project.