š 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.