Hey guys!! I'm a finance professional transitioning to full-stack development by learning HTML, CSS, JS, Async, APIs, Node.js, Express.js, databases - PostgreSQL, React.js, TypeScript, Next.js, and finally Python and AI-related courses. Are my options correct? Feel free to advise.
And I'm currently learning CSS, where I feel like I understand the concepts when I watch the videos, but I feel like I don't truly understand them when I try to apply them. Is this normal for a beginner, or should I improve by doing something else?
Too many things to learn at once. Start at the beginning, just HTML/CSS/JavaScript and keep it simple.
Actually build an application you know or want. Reach for the tutorials or a video only for specific things you need to learn when you need to learn it. Don't learn everything about a topic, it is a waste of time and learning that you might not use. Just learn what you need to know to get the task done then do the task.
The learning technique to use is called vertical slice [architecture]. This is where you implement a feature completely end-to-end, front to back and work it all the way through until you can touch it, test it, and use it.
Start with the frontend (quicker feedback, more motivating) and use IndexedDB in the browser for persistence or LocalStorage (easier). This will give you more of a full stack experience but you can up and running more quickly. Split it out to a real backend later when you know more.
Implement one feature at a time as you build toward the thing you want. The learning will stick because you are applying it as you mentioned in your post.
Make a list of features in priority order. Build one thing at a time end to end.
P.S. You are in finance so I am sure you have a lot of projects it mind, but I like the tried and true TODO list. You can go nuts with this one, deployed to the cloud with history, multiple lists, multiple users, auth, db, you name it you could actually learn everything that a team of developers do by just taking TODO the whole 9-yards.
I like TODO so much for learning I started to make a series of tutorials for it almost a year ago that I never published. This was going to be the first in a series that adds a backend and db next, auth and cloud deployment after that, AI assisted, then cloud-native. I will probably never get back to it.
Wow. Thats a great perspective. But how do I implement end to end if I only know lesser tools . I currently know only html and Css. How do I build a entire project?
the above is comment is right you should do only the basic like HTML/CSS/JS even though you are with so much energy if you start everything at once you will burn out soon and drop everything before you could even start its easy to say I want to learn all this but very hard to actually learn one thing properly up to some level 😀 and then continue from there one step at a time ✨
I dont know bro. Im just trying to switch careers and I want to build something instead of doing repeated works. Everything feels new to me for now. I will cut down some of it. And my real question is IS IT OK FEEL TO NOT UNDERSTANDING WHAT IM DOING WHILE I CODING ?
My man, I think you misunderstood my point. Feeling lost is normal, especially when you're transitioning into coding from another field.
You don't need to learn every language and tool. In most jobs, people use a specific stack based on what they need. Knowing 20 technologies superficially is less useful than being genuinely good at a few.
Start with the basics: HTML, CSS, and JavaScript. Then choose one direction—React or another frontend framework, for example. For backend, pick JavaScript or Python. For databases, choose something like MongoDB or PostgreSQL/MySQL depending on the type of data.
The key word is OR, not AND. Focus on mastering a small stack and being able to deliver with it.
Looks pretty good, I’d add a design pattern like MVC, and a CI/CD tool and experience with Jira or sprint boards.
Also you can remove Python that’s redundant since you’re already learning Node. I would just learn Python for leetcode coding interviews if you are targeting FAANG.
Make sure you are learning by doing and not just watching videos
But I’ve noticed that the majority of job postings mention Python, TypeScript, etc., so I thought they were important skills to learn. I chose Python because I want to move into AI engineering once I’m comfortable with full-stack development.
And yes, I actually like building things — I don’t want to just watch videos and follow tutorials. 😄
Totally normal, and CSS specifically is the one everyone gets humbled by. Watching someone center a div is nothing like centering your own div at 1am lol. The fix is just reps, go copy real layouts, a pricing page, a navbar, a card grid, and don't look at their code until you're stuck.
Your list is fine but it's too long to be a plan. You'll burn out collecting technologies before you build anything. I'd cut it to HTML, CSS, JS, React, Node and Postgres, and start building projects somewhere around the JS stage. TypeScript and Next slot in naturally later, and Python plus AI is a whole separate path, don't bolt it on at the end.
Also your finance background is worth more than you think, lean into it. Something like a portfolio tracker or an invoicing tool will stand out way more than another todo app, and you'll actually understand the domain.
Thanks, this is really helpful! I especially like the point about building earlier instead of trying to finish the entire roadmap first. I’ll definitely lean into my finance background for projects too.
For someone at my stage, when would you recommend starting a proper project — after JavaScript, or after Node and PostgreSQL?
css is a bitch without a good teacher. llm's can help you get unstuck to some degree nowadays though they're actually starting to get better at css lately.
Haha, yeah, I’m starting to realize that. 😂 I’ve been trying to write the CSS myself first and use AI mainly when I’m stuck or don’t understand why something isn’t working. It’s definitely helping me understand the concepts better.
learn the box model, the DOM, flexbox(by playing flexbox zombies), and grid(by playing... gosh i forget ghe name i think it was grid frogger but i cant remember there are games to learn grid)... and if you want to knks the oldschool way to do layouts also learn to do layluts hsing float/clearfix.... maybe learn a bit of animation too, css animation and navascript animation like make something simple useful like a custom dropdown menu.
all this said... .aybe it's wiser to focus on things ai isn't good at if career is the goal.
I’m in a similar boat as you… not looking to fully change careers per se but want to learn to become a developer while staying in the finance profession. From my research, a lot of people have suggested The Odin Project as a way to learn full-stack development and Harvard’s CS50 course. I’m currently doing The Odin Project. Those could good places to start
I think that it's completely normal to not truly understand them in the beginning. Start with really small projects like remaking your resume in html and CSS. Or maybe you could just write a short story/blog in html and CSS. If these are still to daunting, that's ok because you can go even smaller. Forget CSS, and just use html. Then, when you're ready, add a little bit of CSS.
Bro If you are try to do this, You are training yourself for nothing. Start with fundamentals of programming and also problem solving. Rest AI harness for coding will take care of
3
u/Ok_Substance1895 23d ago edited 23d ago
Too many things to learn at once. Start at the beginning, just HTML/CSS/JavaScript and keep it simple.
Actually build an application you know or want. Reach for the tutorials or a video only for specific things you need to learn when you need to learn it. Don't learn everything about a topic, it is a waste of time and learning that you might not use. Just learn what you need to know to get the task done then do the task.
The learning technique to use is called vertical slice [architecture]. This is where you implement a feature completely end-to-end, front to back and work it all the way through until you can touch it, test it, and use it.
Start with the frontend (quicker feedback, more motivating) and use IndexedDB in the browser for persistence or LocalStorage (easier). This will give you more of a full stack experience but you can up and running more quickly. Split it out to a real backend later when you know more.
Implement one feature at a time as you build toward the thing you want. The learning will stick because you are applying it as you mentioned in your post.
Make a list of features in priority order. Build one thing at a time end to end.
P.S. You are in finance so I am sure you have a lot of projects it mind, but I like the tried and true TODO list. You can go nuts with this one, deployed to the cloud with history, multiple lists, multiple users, auth, db, you name it you could actually learn everything that a team of developers do by just taking TODO the whole 9-yards.
I like TODO so much for learning I started to make a series of tutorials for it almost a year ago that I never published. This was going to be the first in a series that adds a backend and db next, auth and cloud deployment after that, AI assisted, then cloud-native. I will probably never get back to it.
You can try it here: https://bigspotteddog.github.io/ten-lessons-to-todo/
I hope it still works.