I'm a CS student who's spent most of my time on algorithms and problem-solving, but I don't have web projects yet. Should I start with HTML and CSS or jump into a framework? I'd like to build a few solid full-stack projects for internship applications over the next few months.
How should I get into web development with a DSA background?
Asked by
++tumble!into~focus
Answers
Start with HTML, CSS and JavaScript, but don't wait until you've mastered every CSS property before building something. Learn the box model, flexbox, forms and basic DOM manipulation, then make a small page that takes input and updates what you see.
MDN has tutorials and references for those basics. After that, React will make a lot more sense because you'll have some idea of what the browser is doing underneath. You can learn more CSS as your projects demand it.
Reply to this answer
Don't start by picking a stack and staring at an empty project. Pick one thing a user should be able to do, sketch the screens on paper, and work out what buttons, forms and feedback each screen needs.
For example, a student resource tracker could let someone add links, categorize them and search the saved collection. Build the simplest working version first, then add a backend and persistent storage. That gives you actual decisions to explain rather than just a tutorial to reproduce.
++tumble!into~focus:
That makes the project feel a lot less vague. Would you worry about visual design right away?
n63!backup_slot:
I'd focus on making the flow clear and usable first. A simple theme or component library can help with the visual side later.
Reply to this answer
There's also a case for trying React early if that keeps you motivated. Just don't treat it as a substitute for the browser basics. When a component changes the page or handles a form, take time to understand the HTML, CSS and DOM involved.
Using AI to help with boilerplate can speed things up, but check the output and make sure you can explain and change it yourself.
Reply to this answer
For full stack, think in terms of one complete flow rather than three big projects at once. A form sends data to a server, the server stores it, and the page retrieves and displays it. Once that works, you can add features and learn a backend tool such as Node along the way.
Your problem-solving background will help, but you'll also be learning how requests, browser interfaces and persistence fit together. Those are different skills from solving isolated algorithm problems.
Reply to this answer
Add your answer
Answers are reviewed before publication.
mismatched-fasteners:
Fetch is a useful next step too. Try requesting data from an API and displaying it on your page before adding a framework.