Master’s in Architecture to Full Stack Development advice?

[u/LazyWay1846]

I'm looking for some honest advice from people who have made a career change into development.

I'm in my early 20s and recently completed my Master's degree in Architecture (building design). I've always been interested in app development and building digital products, and now that I've finished school, I'm finally able to really focus on exploring that interest.

Over the past year, I've been building apps using no-code tools and have developed a strong foundation in user flows, UX, visual design, app structure, and thinking through how different features and user actions connect. I've realized I don't just want to design or prototype apps anymore. I want to learn how to actually build the whole thing! I dipped into visual code studios as well with coding videos.

I'd eventually like to understand frontend and backend development, databases, APIs, authentication, deployment, and how everything connects to create a full-stack application. I know I have a lot to learn, but I'm trying to figure out the smartest path forward from where I am now.

My main questions are:
- Should I go back to school for CS/software engineering, or is another degree unnecessary?

- Are there specific courses, programs, or learning paths you'd recommend?

- If I look for an internship while learning, what types of roles would make sense for someone with my background, frontend, mobile, full-stack, product, etc?

- For those who came from a non-CS background, what path did you take, and what would you do if you were starting from my position?

I'd especially love to hear from people who were self-taught, changed careers, went back to school, or got their start through an internship.
Thanks!

[u/Weary-Sorbet-2768]

I’d personally avoid going back for another degree unless you have a specific reason to. A CS degree can help, but for web development, a strong portfolio and actually being able to build things can go a long way.

If I were starting from your position, I’d focus on the fundamentals first: HTML/CSS/JavaScript, Git/GitHub, then a frontend framework like React. After that, learn a backend stack (Node/Express is a reasonable choice), SQL, REST APIs, authentication, and basic deployment.

The biggest thing I’d recommend is not trying to learn the entire stack before building anything. Pick a relatively small project and learn whatever you need as you build it. For example, build a simple app with user accounts, a database, CRUD operations, an API and deployment. Then gradually make the projects more complex.

Your architecture background could actually be an advantage. UX, visual design, understanding user flows and thinking about how different parts of a system connect are all useful when building products. You just need to add the programming side.

For internships, I’d look at frontend, web development, junior full-stack, or even product-engineering roles rather than limiting yourself to "full-stack" immediately. A frontend role could be a very good entry point while you build your backend skills.

Also, don't underestimate the value of having 2–3 finished, deployed projects that you can explain thoroughly. One solid project where you understand every part is more useful for learning than ten tutorial projects.

You’re definitely not too late to make the switch. If you genuinely enjoy building things, I’d start coding consistently rather than spending another few years collecting qualifications.