đ From âHello Worldâ to Hello React: My College Coding Chronicles
Just a few years ago, I was sitting in a college computer lab, proudly printing âHello Worldâ in C, thinking I had arrived. Spoiler: I hadnât.
đ The Starting Line: Confused but Curious
When I started my B.Tech in Computer Science, I wasnât totally new to codeâIâd dabbled in C++ and had made some static websites with HTML and CSS back in school. But like many students, I quickly realized that just knowing how to center a div
doesnât exactly make you âindustry-ready.â
After scrolling through one too many LinkedIn posts and YouTube videos titled âHow to Become a Software Engineer in 3 Months,â two golden rules kept popping up:
- Master DSA
- Build Projects
So naturally, I took the deep diveâinto DSA. My browser tabs read like a saga: LeetCode, GeeksforGeeks, random YouTube tutorials, and those âTop 150 Questionsâ sheets everyone swore by. I was solving pattern questions with the enthusiasm of someone convinced this would unlock the gates to Google. Meanwhile, my RAM was fullâliterally and mentally.
đĽď¸ My First âRealâ Development: College Curriculum Magic
In the 2nd semester, we had a course called "Web Development Essentials." Translation: HTML, CSS, and vanilla JavaScriptâserved with a side of broken styling and copy-pasted w3schools snippets.
But it led to my first proper group project: an income tax calculator website. It was basic, borderline uglyâbut it worked. Here it is in all its glory.
Our professor reviewed it and casually dropped a life-changing comment:
âNice work. You should explore React or Angular next.â
Boom. That one line sent me tumbling down the JavaScript framework rabbit hole.
âď¸ React, Repeats & the Tutorial Loop of Doom
Armed with YouTube and a never-say-die attitude, I began the classic React learning routine:
- Watch a tutorial.
- Build the exact same project.
- Add two âcreativeâ features like dark mode or a counter.
- Repeat.
I didnât know it then, but this loop was teaching me a lotâstate, props, routing, and most importantly, how to Google my errors like a pro.
Eventually, I stumbled upon the holy grail of full-stack web developmentâthe MERN Stack. MongoDB, Express, React, Node.js. Everyone on the internet said it was the real deal, so I jumped on the bandwagon. (Spoiler: totally worth it.)
đ¤ That Time I Briefly Dated Machine Learning
Around 4th semester, we got Python as part of the curriculum. Python felt like writing pseudocode that actually runs. I built a fun little Inventory Management System as final project Check it out here. using Tkinter and MySQL. Felt like magic.
Encouraged by that, I picked Data Science & Machine Learning as an elective in 5th sem. It started strongâbut quickly turned into Excel dashboards and copy-pasting Jupyter notebooks. No hate, but I wasnât vibing with it.
If Web Dev was a rom-com, ML was an awkward blind date. We parted ways peacefully. No hard feelings.
đ§Š DSA, We Meet Again
Like every college student, I had an on-again, off-again relationship with DSA. Iâd grind for a week, then fall back into watching frontend tutorials. But at the start of 6th semester, I came back with vengeanceâreviewed earlier topics and dove into advanced ones like trees, graphs, and dynamic programming.
It felt like unlocking cheat codes. Suddenly, problems that once looked impossible started making sense. Sort of. Sometimes.
đ Hackathon Magic & My First Break
Then came the highlight of college: a 24-hour hackathon. Fueled by coffee, chaos, and copy-paste, our team built Code with Companionâa real-time collaborative coding app. Check it out here. We actually won! đ
That project gave me two things:
- Confidence in my skills
- A talking point for my first real interview
Shortly after, I landed an internship as an SDE Intern at Scaler/InterviewBitâa turning point that marked the end of my âlearning in the labâ phase and the start of building for real users.
đĄ College Phase Recap
â Strengths:
- Endless freedom to explore (and fail gloriously).
- Time to jump between tutorials, tech stacks, and ten unfinished side projects.
- Learned how to learn.
â ď¸ Limitations:
- No idea what production code really looks like.
- Team collaboration meant âjust share the GitHub repo, bro.â
- Didnât grasp concepts like scalability, testing, or maintainability.
College didnât make me an engineerâbut it gave me a map and a flashlight. I didnât know the full path, but I could finally see the road.
đ Continue Part 2?
Check out Part 2 â My Internship at Scaler to see how it continues.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.