I Never Thought I'd Code — Until This One Moment Changed Everything

Introduction

Many people ask me how I learned to code, what resources I used, and what truly matters in programming. In this journey, I'll share:

• How I picked up programming
• How I think and develop things
• The best ways to find resources, ask the right questions, and build connections

A Bit About Me

Hello Everyone! 👋 I'm Anish Shobith P S, a passionate developer who has been building things for quite some time. Before we dive in, let me share how I observe the world and learn from my studies. While my focus is on Computer Science, the principles I follow can be applied to learning in other subjects as well.

How It All Began

I never had an initial interest in Computer Science. My first passion was something entirely different — architecture. It all started when I attended a wedding with my parents years ago. My eyes were drawn to a breathtaking dome structure above. Mesmerized, I asked my parents, "What should I do to create buildings like this?" They told me, "Civil Engineers build these kinds of structures." From that moment, I was set on becoming a Civil Engineer. That was probably in 3rd or 4th grade.

The Shift Towards Technology

In 5th grade, everything changed. I got my first phone, and rather than just playing games, I became fascinated with how it worked. I explored ways to install apps, tweak settings, and push the limits of what a mobile device could do. By the end of 6th grade, I finally got access to a PC at home. It had always been there, but I was never allowed to use it much. Once I did, a whole new world opened up.

Gaming & Problem-Solving

My brother and I played Dragon City on Facebook and later, Clash of Clans. These games stuck with me — not just for entertainment but for the strategy, planning, and problem-solving they required. They shaped the way I think, helping me see solutions that others often overlooked.

Hacking Curiosity & The Love for CS

With a computer at my disposal, my curiosity grew. I explored ways to increase internet speed, tweak system settings, and even mod games. This constant experimentation sparked my deep interest in Computer Science.

By 8th grade, I had my very own laptop. I wasn't just exploring software — I also wanted to share my knowledge. I started making YouTube videos while experimenting with my laptop. Of course, this led to bricking my system multiple times. Instead of panicking, I taught myself how to fix everything on my own. Each failure only made me more skilled, reinforcing my passion for learning and problem-solving.

The Turning Point: Discovering Programming in School

In 9th grade, we were introduced to C++. For the first time, I experienced coding in a structured way. Our teacher explained it so well that I was immediately hooked.

By the time of our final exams, we had two choices:

1. Pick & Code Programs — 14 predefined programs from the textbook.
2. Unseen Programs — Random problems given by the teacher.

Most of my friends chose the safe route, but our teacher pushed a few of us to try the unseen challenge. I was nervous but had no choice. I gave it my best shot — and I DID IT! 🎉

That moment was unforgettable. The joy and confidence I felt after solving that problem pushed me to explore programming even more. From then on, I loved experimenting, solving problems, and building things. Our teacher even gave us projects like CLI-based quiz apps, which I thoroughly enjoyed.

Choosing My Path

By 10th grade, coding was minimal — just HTML, CSS, and JavaScript. But by then, I was 100% sure I wanted to pursue Computer Science as a career. The only thing left was to tell my parents. I had always wanted to be a Civil Engineer, but now my heart was set on CS. I was nervous, but to my surprise, they were incredibly supportive of my decision.

Pre-University (11th & 12th Grade): Evolution of My Coding Journey

During my pre-university years, C++ was a major subject alongside HTML and SQL. Since I had already picked up C++ in school, I found it fairly easy. However, the biggest turning point in my journey came through Discord.

How a Game Led Me to Discord & Bots

Initially, I joined Discord for a Clash of Clans clan. Later, I joined another Clash of Clans community server — r/ClashofClans, one of the biggest at the time. Here, I noticed a Discord bot that could fetch Clash of Clans stats. I thought, "Why not make my own bot?"

Building My First Discord Bot & Learning Beyond Books

I was also into graphic design at the time but lost interest quickly. Instead, I focused on building my own Discord bot. However, I had no idea how to host it. Like any beginner, I turned to YouTube tutorials. That's when I found {TheSourceCode}, which helped me immensely. I also joined various Discord servers run by YouTubers, where I met people with real industry experience. These interactions taught me way beyond traditional textbooks.

Clash With Code: Learning Through Fun

Around this time, a few Discord friends and I started playing Clash With Code — a competitive programming game where you solve problems in 15 minutes. You could optimize for:

• Fastest code
• Shortest code
• Reverse mode (where the answer is given, and you have to guess the problem statement)

This game was transformative. It improved my problem-solving speed, taught me coding tricks, and was a lot of fun. We would argue, discuss approaches, and push each other to improve.

The Big Decision: College & Entrance Exams

By 12th grade, I was 110% sure I wanted to pursue CS. But in India, getting into a top-tier university isn't easy. I had to appear for competitive exams like:

• JEE (for IITs, NITs, and top engineering colleges)
• KCET, COMEDK, and others for state/private universities

Unfortunately, I lacked proper guidance and didn't perform well. With bad results, I had no choice but to enroll in a private college in my city for my Bachelor's Degree in CS.

Covid Times & Beyond

Just before my 12th-grade finals, India went into lockdown. While I played games, I also focused on learning and contributing to open-source projects. A friend built a COVID stats API, and I managed its NPM module, which saw widespread use. This became one of my biggest early contributions.

Discord also helped me break out of my introverted shell. Initially, I just listened in voice chats, but one day I spoke — and never stopped. My communication skills grew, and I could hold long conversations.

My friends and I kept building Discord bots, challenging each other in coding battles, and working on projects. Eventually, I moved beyond Discord bots into automation and other fields.

University Life

I graduated in 2024 with a Computer Science Engineering degree from St. Joseph Engineering College. While I didn't obsess over CGPA, I focused on:

• Attending hackathons and tech events
• Building connections and networking
• Developing projects

Thanks to Discord, I had already overcome my fear of talking to people, though transitioning to in-person conversations took some time. With practice, that fear faded, and I embraced every opportunity to grow.

General Growth Tips

Attitude and Environment

• Focus Beyond Grades — Grades may open doors to opportunities, but after your first job, experience and skills matter far more. Prioritize learning and problem-solving over chasing perfect scores.
• Build a Strong Foundation — A solid foundation makes it easier to learn and grow as you acquire new skills. A weak base leads to knowledge gaps that become harder to fix later.
• Choose a Growth-Oriented Circle — Surround yourself with people who prioritise learning and growth. Exposure to different perspectives keeps you inspired and broadens your understanding of technology and industry trends.
• Create a Motivating Environment — Set up a workspace that energizes you — consider your desk setup, digital tools, and aesthetics. Refresh your setup regularly to keep things feeling new and engaging.

Can a College Environment Make the Cut?

Simple answer: NO! College environments often focus on academics and exams rather than practical exposure and networking. Instead, take proactive steps:

• Attend local tech events (even paid ones) — Great for networking and staying updated.
• Participate in hackathons — Hands-on experience and collaboration are invaluable.
• Join active tech communities — Engage in on-campus or online programming groups.
• Use platforms like Discord or Slack — Stay connected with peers and industry professionals.

What's Holding You Back?

Often, it's just excuses. If you want to grow, start taking action.

• Background Isn't a Barrier — A non-tech background isn't an excuse. Every field has a learning curve, embrace it and put in extra effort to catch up.
• Be Active in College Clubs — Engage fully in communities and clubs. Silence wastes the chance to learn and connect with like-minded peers.
• Invest in Hands-On Learning — Spend time and even a little money on hands-on experiments — hosting, configuring, and testing things on your own. It will teach you more than theory-based approaches.

How to Manage College and Other Activities?

• Balance Exams & Events — Plan ahead to make space for both.
• Complete Assignments in College — Saves time and builds friendships.
• Maximize Free Periods — Utilize breaks to free up time for projects.
• Plan Ahead for Events — Discuss plans with parents and teachers if exams overlap.

How to Learn Effectively?

• Learn from Official Sources — Use documentation and guides for accuracy.
• Build Projects to Learn — Learning happens by doing, not just watching tutorials.
• Prioritize Skills Over Certificates — Real skills and projects matter more than certificates.
• Move Beyond Basics — Tutorials cover only the basics; apply them to real-world scenarios.
• Engage with Developer Communities — Feedback and collaboration accelerate growth.

The Learning Pyramid

If you want to learn efficiently, focus on practice-based learning and teaching others — this ensures long-term retention and mastery of skills.

How to Ask for Help?

1. Describe Issues Clearly — Avoid general statements like "doesn't work" or "it gives a bug." Instead, clearly mention:
   • What you were trying to achieve
   • What specifically went wrong
   • Relevant context or error messages
2. Use Visuals Responsibly
   • Avoid phone photos; use screenshot tools.
   • Only include visuals if they add clarity (e.g., GUI issues).
   • For code, copy terminal output into Sourcebin or Pastebin.
3. Share Relevant Resources
   • If following a tutorial, share the link and relevant timestamps.

How to Learn Computer Science Effectively

The best way to learn CS is by building projects. It's not about just remembering concepts — it's about applying functionality in real-world scenarios.

For me, Computer Science isn't about learning everything first and building later — it's about learning by building. This method has several advantages:

• You learn how to apply your knowledge rather than just memorizing.
• You'll have a project by the time you finish learning.
• You save time by focusing only on what's needed.
• You'll encounter real-world pitfalls that theoretical learning often overlooks.
• You naturally pick up the fundamentals as you develop.
• You learn efficiently — focusing on what's required rather than learning everything and using just a fraction of it.

At first, progress may be slow, but with experience, you'll build smarter and faster. Learning through projects also teaches effective project management, helping you reduce unnecessary work and optimize your workflow.

My Problem-Solving Framework

When tackling a problem, I follow a three-step process:

1. Just Code It — Get the code working, no matter how messy.
2. Optimize Performance — Improve efficiency, change methods, and use better approaches.
3. Refactor & Clean Up — Improve readability, rename variables, and format code.

I automate this with tools like linters and Prettier to save time.

My Process for Building Projects

Research Phase

• Search GitHub with keywords related to my project (e.g., "next.js portfolio").
• Gather and analyze the best projects to gain insights.
• Look for well-maintained alternatives with clean code.

Bringing Things Together

• List all the useful features from the resources I gathered.
• Plan how and where to integrate them into my project.

Start Coding

• Implement features and functionalities.
• Adapt as needed — nothing ever goes 100% according to plan.

Navigating the Job Market: Reality and Challenges

• Outdated Interview Processes — Companies focus on traditional topics over modern tech stacks.
• Classroom Basics Aren't Enough — Practical application is key for placements.
• Understanding Over Memorization — Interviews test problem-solving, not rote learning.
• Competitive Job Market — Companies critically evaluate entry-level skills.
• The Importance of Self-Development — Self-driven learning bridges the gap between academia and industry.

Struggles

Like anyone else, I've had my fair share of struggles. One of the biggest challenges was the lack of a motivating environment. Most people around me were either focused on maintaining a high CGPA or just having fun, making it difficult to find like-minded individuals who prioritized real learning and growth.

While I had a decent CGPA, it wasn't high enough for many campus placements, as companies often set strict cutoffs. This meant I was automatically disqualified from several opportunities, even though my skills and experience extended beyond academics.

Watching my peers secure jobs while navigating the tough job market of 2024 — my graduation year — only added to the pressure.

Another challenge was my lack of interest in DSA and Competitive Programming. I found them monotonous because they often felt detached from real-world applications. Solving abstract problems without immediate practical use in a product or software didn't excite me, and as a result, I struggled with DSA rounds in many company interviews.

Despite these setbacks, I focused on building real projects, learning industry-relevant skills, and continuously improving. My journey wasn't the conventional one, but it shaped me into a better developer.

A Few Things I'd Like People to Consider

I demand that companies start listening to applicants. If someone struggles with DSA rounds or simply dislikes them, there should be alternative ways to assess their skills. There's a brilliant post by T3 Tools about different types of interviews — companies should consider giving applicants a choice so they can showcase their strengths effectively.

For those reading this: focus on skill development and keep practicing. It might seem overwhelming to keep up with the world, but you don't have to. Be yourself and excel at what you do — that's all that truly matters.

There are far too many exploitative internships out there — some ask you to pay for a certificate, while others expect you to work for free.

If you are good at something, don't do it for free.

Where I Am Now

A connection I made on Discord led me to a Software Development Engineer (SDE) Internship. What started as a gaming platform became one of the most valuable professional networks I've ever been part of.

If you have any queries or need guidance, feel free to join my Discord server and ask me anything!

That's my journey so far — from a curious kid fascinated by architecture to a passionate software developer. There's still a long way to go, and I'm excited for what's next! 🚀