About

Showing posts with label Computer science in college. Show all posts
Showing posts with label Computer science in college. Show all posts

Monday, May 25, 2026

First Job in Tech. Everyone Celebrates. Nobody Warns You About This.

You have the offer letter.

After the campus interviews, the aptitude tests, the technical rounds, the HR calls, the waiting, the refreshing your email every hour, you finally have it. Your name. A company. A joining date.

Take a moment. You earned this.

Now let me tell you what happens next. Not the version from the placement cell brochure. The real version.

The Project You Get Will Probably Not Be the One You Wanted

You joined this company because of something. Maybe their cybersecurity team. Maybe their AI division. Maybe the product that made them famous. You read about it, prepared for it, interviewed with that picture in your mind.

And on your first week, you will be allocated to a project.

There is a reasonable chance it is not what you pictured.

This moment, quiet and undramatic as it sounds, is one of the most important tests of your early career. And most fresh graduates fail it.

Some of them speak up immediately. They walk into their manager's cabin or send an email explaining that this was not what they signed up for, or that they specifically wanted the product team, or that they feel their skills are better suited elsewhere. They frame it as self-awareness. As knowing their worth.

I have personally watched this play out. I have seen new hires, talented ones, ask to be moved to a different project because they did not like what they were assigned. Some were put on the bench immediately. Some were let go quietly. The organisation did not fight to keep them. Because in the first three months, you are not yet someone the organisation has invested in deeply enough to accommodate.

You are a new hire. You are being evaluated every single day, not just on your technical output, but on your attitude, your adaptability, your professionalism under conditions that are not ideal.

You are a small fish. They are a very large ocean. That is not an insult. It is just the geometry of where you are standing right now.

Survival Is the First Chapter. Not the Whole Book.

This does not mean you surrender your ambitions. It means you sequence them correctly.

The first step is survival. Do your job well. Whatever project you are on, find something in it worth doing properly. Every domain has depth if you look for it. Every project has a problem worth solving well. Show up. Deliver. Be the person your team can rely on.

This builds something invisible but enormously valuable: a reputation. Not a loud one. A quiet one. The kind where your manager thinks of you as solid. As dependable. As someone worth keeping and eventually moving.

You cannot skip this chapter. The people who try to skip it either get benched or burn out trying to fight a system that has no obligation to rearrange itself for a fresher.

Survive first. Grow next. In that order.

But Here Is What Most People Get Wrong After Getting the Job

They stop.

The reading stops. The learning stops. The curiosity that got them through college, that pushed them through late nights and difficult subjects, quietly switches off the moment the salary starts coming in.

I understand why. The job is exhausting. The commute is real. The social life after years of campus feels like something you deserve. And you do deserve rest.

But here is what nobody tells you: the first two to three years of your career are the single best time to learn you will ever have.

You have income but no dependents yet. You have structure but still have energy. You have exposure to real systems, real codebases, real infrastructure, things no textbook or course can fully simulate. And you have time outside of work that is genuinely yours in a way it will not always be later.

Most people waste this window. The ones who do not waste it are the ones you will look up to in ten years and wonder how they got so far ahead.

What to Do With the Time Outside of Work

Keep reading. Not casually. Deliberately.

Take the domain that genuinely excites you, the one that lit something in you during college, and go deeper into it now. Not to get a certificate. Not to add a line to your resume. Because you are genuinely hungry to understand it.

I will tell you what this looked like for me personally.

I was working in cybersecurity. My job had a specific scope. But outside of that scope, I kept reading. I explored areas of cybersecurity beyond what my project required. I picked up malware analysis not because my job demanded it, but because something about understanding how malicious code behaves at a deep level felt important and fascinating to me.

And then I went one step further.

I had always been drawn to quantum physics. Not as a career switch. Not as a plan. As a genuine intellectual curiosity that had lived quietly alongside everything else I was doing. So I followed it. I read. I explored quantum computing, the intersection of quantum mechanics and information theory, a field that most people in cybersecurity were not paying attention to yet.

That curiosity eventually led me to contribute to book chapters on quantum computing. Not because I had a master plan. Because I kept showing up for the things that genuinely interested me, even when nobody was asking me to.

Nobody tells a fresh graduate that this is possible. That you can hold a full time job in one domain while building genuine depth in another. That your curiosity is not something to park until you have more time. That the after-hours hours are where the interesting version of your career gets built.

The Reading Habit Is Not Optional

The professionals you will admire most in your field, the ones who seem to always know more, always see further, always have a perspective worth hearing, are almost universally people who never stopped reading.

Not just articles. Books. Research papers. Technical documentation. Things that are hard and slow and require you to sit with discomfort until something clicks.

Pick one book in your domain every month or two. Pick one research paper every few weeks. It does not have to be fast. It has to be consistent.

After two years of this, you will not recognise the gap between yourself and the people around you who stopped learning when the salary started. It will be visible to you. And eventually, it will be visible to the people making decisions about who gets opportunities.

The Job Market Is Wide Open. But Only for the Right Version of You.

People say the job market is tough. And in some ways it is. Competition is real. The bar keeps rising.

But here is the other side of that truth. Most people plateau early. Most people stop growing in year two or three. Most people become very good at exactly what their job requires and nothing beyond it.

The job market is genuinely wide open for the person who has kept going. Who has spent two years delivering reliably at work and building real depth outside of it. Who has followed a curiosity all the way to the edge of their comfort and then kept going a little further.

That person is rare. Organisations know it. Opportunities find that person. They do not have to chase most of them.

You can be that person. Not through intensity for a week. Through consistency for years.

A Note Before You Go

This article is the fourth in a series walking through every stage of the computer science journey, from the student choosing subjects in 10th standard, to the college fresher finding their footing, to you, standing at the beginning of your professional life.

If you missed any part of this journey, read them in order. Each one builds on the last.

If you are a student finishing 10th standard and choosing your path, start here: What every 10th standard student choosing Computer Science needs to hear

If you just finished plus two and are stepping into college: You Passed Plus Two. Everyone Is Celebrating. But Nobody Told You This.

And if you are in your final years of college, wondering what comes next in a world that never seems to settle: You Are in Your Final Years of College. The World Looks Scary. It Always Has.

The world does not get easier from here. But you get stronger. One deliberate year at a time.

Go build the version of yourself that the next chapter requires.

Saturday, May 23, 2026

You Are in Your Final Years of College. The World Looks Scary. It Always Has.

Stop for a moment.

Look around your college campus. Talk to your batchmates. Scroll through LinkedIn. Everyone seems anxious. Everyone is updating their resume, attending placement drives, comparing backlogs, whispering about the job market being tough right now.

And somewhere inside you, there is a quiet fear you have not said out loud yet.

What if there is no place for me out there?

I want to tell you something that nobody told me when I was sitting exactly where you are sitting right now. Something that took years after college to fully understand.

The world has never been stable. Not once. Not for any generation before you. And the students who came out of college strong were not the ones who waited for the world to calm down. They were the ones who stopped waiting.

Every Generation Got Their Version of the Crisis

In 2000, the dot-com bubble burst. Companies that were worth billions on paper evaporated overnight. Engineers who had joined startups with stock options and dreams woke up to find their offices locked. An entire generation of computer science graduates stepped out into a job market that had just collapsed. They were told the internet was a mistake. That the tech dream was over.

It was not over. It was restructuring. The ones who stayed curious came out the other side building the internet as we know it today.

In 2008, the global financial crisis hit. Banks collapsed. Recession spread across every industry. Students who were about to graduate watched campus placements dry up one by one. Companies rescinded offers. People who had worked for years lost jobs overnight. The fear was not just professional. It was existential. It felt like the floor had disappeared.

I know that fear personally. I was a student during that period. I watched my batchmates prepare resume after resume, attend interview after interview, and come back with nothing. The world felt like it was coming apart at the seams. Like we had studied for years and arrived at a door that no longer existed.

In 2020, COVID shut the entire planet down. Campuses closed. Internships vanished. Graduation ceremonies happened on a screen. An entire batch of students entered the workforce during a global lockdown with no roadmap, no precedent, and no certainty about anything.

In 2022, Generative AI arrived and within months began doing things that people had spent entire careers building. Writers, coders, designers, analysts. Every knowledge profession looked at these tools and felt the ground shift again. Students who had just chosen their specialisation started wondering if their choice still made sense.

Every single generation got their version of this.

And every single generation had students who came through it and built something real.

The crisis is not the exception. The crisis is the condition. The world has always been firefighting. It always will be. The question is never whether the world is stable enough for you to begin. The question is what you are building inside yourself while the world figures itself out.

What College Actually Gave You That You Might Have Missed

In your first two years, if you followed the path we described in the earlier articles in this series, you went deep into the fundamentals. Operating systems. Computer architecture. Data structures. Discrete mathematics. You built the floor.

But something else happened in those years that you may not have noticed. College opened doors to rooms you did not know existed.

Networks and security. Compiler design. Database internals. Computer graphics. Distributed systems. Artificial intelligence. Human computer interaction. Embedded systems. Each subject was a window into a different world. Some of those windows probably felt like walls. Dry, abstract, impossible to connect to anything real.

But one or two of them, if you are honest with yourself, felt different. There was a lecture, or a lab session, or a late night reading a textbook, where something clicked in a way that felt almost personal. Like that subject was speaking directly to you.

That moment matters more than your CGPA. More than your placement rank. More than anything your relatives will ask about at the next family gathering.

That moment is a signal. And your final years are the time to follow it.

Go Deeper. Not Wider.

This is where most students make the fatal mistake of the final years.

They go wide. They add certifications. They learn five frameworks. They do crash courses in whatever technology is trending on LinkedIn that month. They build a resume that is four pages long and an inch deep.

Employers see through this immediately. Every hiring manager who has interviewed a hundred candidates knows the difference between someone who has touched a subject and someone who has lived inside it.

Go deep instead.

Take the subject that lit something in you and push past the textbook. This is where foreign authors become essential. Not because your professors or local textbooks are wrong. They are often excellent. But a foreign author writing for a global research audience is writing about how that domain behaves universally. They are writing for practitioners in Boston and Berlin and Bangalore. They are not writing for an exam. They are writing for someone who wants to understand the thing itself.

Read research papers. Yes, they are dense. Yes, the first few will feel like reading a foreign language. Read them anyway. Start with the abstract and the conclusion. Work backwards. Look up every term you do not understand. The discipline of reading a research paper trains your brain in a way that no course ever will. You stop being a consumer of knowledge and start becoming someone capable of producing it.

Find the researchers, practitioners, and writers in your chosen domain who are doing the most interesting work globally. Follow them. Read what they read. Understand what problems they consider unsolved. That is the frontier. And the frontier is where careers are made.

Understand Your Limitations. Honestly.

This is the part nobody wants to hear. So I will say it plainly.

You are not going to be exceptional at everything. Nobody is. The students who pretend otherwise spend years chasing a version of themselves that does not exist, burning time and confidence in the process.

Sit quietly and ask yourself what you are genuinely good at. Not what you wish you were good at. Not what looks impressive. What you actually do well when nobody is watching and there is no grade attached.

Maybe you are someone who can read complex systems and find where they break. Maybe you are someone who can explain difficult things simply. Maybe you are someone with an unusual tolerance for ambiguity who can sit with an unsolved problem longer than most people can. These are not small things. These are rare things.

Know your strengths. Know your gaps. Be honest about both. And then build your final two years around moving in the direction your strengths point, while quietly working on the gaps that would hold you back.

This is not pessimism. This is navigation. A ship that knows exactly where it is can chart any course. A ship that does not know its own position cannot go anywhere with intention.

A Note on the Paths Around You

Look at your batchmates and you will see several different stories unfolding.

Some of them have parents, relatives, or working professionals in their life who have given them clear guidance. They already know which company to target, which role fits their background, which certification opens which door. This is a real advantage. If you have this, use it fully and be grateful for it.

Some of them are wired differently. They are not looking for a job. They are looking for a problem. They stay up late not studying for exams but obsessing over something that does not work yet and needs to be fixed. Some of these people will end up as entrepreneurs. Not because entrepreneurship was their plan, but because their curiosity would not let them stop at someone else's solution.

Both of these paths are real. Both produce extraordinary outcomes. But they are outliers. They are the minority.

Most of you are the general student. Talented, capable, uncertain, and trying to find your footing in a world that has not made it easy. And that is completely fine. This article is written for you.

For the general student, the path is not glamorous. It is consistent. Go deep in what genuinely interests you. Read beyond the syllabus. Understand the global shape of your domain. Know yourself honestly. Build skills that are real, not skills that look good on a slide.

That is not a lesser path. That is the path that quietly produces the professionals that every organisation actually depends on.

The World Will Not Wait. Neither Should You.

There will always be a recession somewhere. There will always be a disruption rewriting the rules. There will always be a reason to wait until things settle down.

Things do not settle down. They shift. And then they shift again.

The students who come out of college ready are not the ones who had the best timing. They are the ones who used their final years to build something that does not depend on timing. Deep knowledge. Genuine skill. An honest understanding of who they are and what they are capable of.

The world was never going to hand you a good moment. You were always going to have to build your readiness during someone else's chaos.

So build it. Starting now.

And if you are reading this having just finished 10th standard and choosing your path, start with the foundation: What every 10th standard student choosing Computer Science needs to hear

If you just finished plus two and are entering college, this is the most important thing you can read before your first semester begins: You Passed Plus Two. Everyone Is Celebrating. But Nobody Told You This.

The next article in this series is for the student who has just graduated and is stepping into the job market for the first time. That one is coming soon. It will be worth the wait.

For now, you have your final years. Use them like they are the last time you will have this kind of freedom to go deep without the pressure of a deadline.

Because they are.

Thursday, May 21, 2026

You Passed Plus Two. Everyone Is Celebrating. But Nobody Told You This.

You did it.

Plus two is done. The board exams, the sleepless nights, the mark sheets, all of it. And now you are standing at the entrance of college, a computer science degree ahead of you, a head full of excitement and maybe a quiet fear you have not told anyone about.

Maybe you came from a Maths Biology background like many students do, switching tracks at the last moment because something about computers felt magnetic. Maybe you spent your plus two years dreaming about building video games, or making apps, or doing something with AI that you cannot yet fully describe. Maybe you watched one YouTube video about hacking and thought, that is it, that is what I want to do.

Whatever brought you here, welcome. You are exactly where you need to be.

But before your first lecture begins, before you buy your first programming book or download your first IDE, there is something I need to tell you. Something that most college seniors will not say out loud because it sounds uncomfortable. Something that took a mentor I know years of painful detours to understand.

The way most students spend their first two years of college is completely backwards.

The Excitement Trap

Here is what happens to almost every CS fresher.

They arrive at college buzzing with a specific dream. Games. Apps. AI. Cybersecurity. They have a target. They want to get there fast. So they open YouTube, they find a course on Unity game development or ethical hacking or Python for machine learning, and they start. They feel productive. They feel like they are ahead.

And for a few weeks, it works. Things seem to click.

Then they hit something. A concept that does not make sense. A problem that the tutorial did not prepare them for. A question from a professor that makes them realise they are holding a tool they do not actually understand.

They go back to YouTube. Find another course. Start again.

Three semesters pass this way. And by the time they reach their third year, they have touched fifteen technologies and deeply understood none of them. They can follow tutorials. They cannot think independently.

This is the excitement trap. And it catches almost everyone.

What the Internals Actually Are

I know a mentor who came into college from a Maths Biology background. No CS in school. Everyone around him had been coding since 9th standard and he felt like he was already three years behind.

He wanted to build games. That was the dream. So he started learning game development. But somewhere along the way, trying to understand why his code behaved a certain way, he stumbled into operating systems. Then into computer architecture. Then into microprocessors. He started understanding how a CPU actually executes an instruction. How memory is laid out. How a process is born and killed by an OS. How a program sits in memory and what it looks like from the inside.

And something shifted. The game development dream did not disappear. But something far more interesting replaced it: he could now see underneath the surface of everything. He understood why software behaved the way it did. Not just how to use it. Why it worked, and more importantly, why it sometimes broke.

That curiosity pulled him all the way into reverse engineering. Taking software apart to understand what it does at the machine level. A field that sits at the deepest intersection of computer architecture, operating systems, and raw analytical thinking.

He did not plan to go there. The internals took him there. And he has never regretted following that path.

This is not a unique story. This is how the most interesting people in computer science arrive at what they do. Not by targeting a destination. By following curiosity into the foundations.

What Your First Two Years Are Actually For

Your first two years in college are not for specialisation. They are for building the mental infrastructure that every specialisation stands on.

Operating Systems. This is not a boring subject about memory management. This is the subject that explains why your phone slows down, why your browser uses so much RAM, how programs talk to hardware without destroying each other, and what actually happens when you double-click an icon. Every cybersecurity professional, every game developer, every systems programmer lives inside this subject daily.

Computer Architecture and Microprocessors. This is where you learn what a computer actually is, not a box running software, but a machine executing instructions one at a time in a very specific way. When you understand this, you stop being a user of computers and start being someone who truly operates them.

Data Structures and Algorithms. This is the grammar of programming. Not a specific language. The underlying logic of how problems are structured and solved efficiently. Every technical interview in every CS company in the world tests this. More importantly, it trains your brain to think in a way that no tutorial ever will.

Discrete Mathematics. Logic, sets, graph theory, combinatorics. Dry-sounding words that are the skeleton underneath databases, networking, cryptography, and compiler design. You cannot go deep in any of these without Discrete Maths underneath you.

These are not subjects to survive. They are subjects to inhabit. Sit with them. Ask uncomfortable questions. Connect them to each other. This is where the real education happens, not in the certificate courses you do on the side.

But I Still Want to Learn Programming

Good. You should. And here is how to do it without falling into the trap.

Learn one language properly. Not ten languages at the surface level. One language, deeply. Understand how it manages memory. Understand how it handles errors. Write programmes that break and figure out why. C is painful and perfect for this. Python is forgiving and useful. Either works. What matters is depth, not breadth.

Build something small and finish it. Not a grand project. A small working thing. A calculator. A simple text adventure. A tool that automates something annoying in your own life. Finishing a small thing teaches you more than abandoning ten ambitious ones.

And when you hit something confusing, something that does not make sense, do not skip it. That confusion is pointing you toward a gap in your foundation. Go back. Fill the gap. The students who do this in their first two years are the ones who seem effortlessly capable in their third and fourth years.

The Language Point, Again

If you read our previous article written for students finishing 10th standard, you already know this. But it carries even more weight now.

You are in college. You will write lab records, project reports, internship applications, and emails to professors. You will give presentations. You will sit in group discussions and technical interviews where what you say matters as much as what you know.

There are ideas in computer science, genuinely important ones, that are so complex they push the limits of what language can express. A researcher describing a new cryptographic protocol is not just solving a technical problem. They are also doing a translation job, converting something that exists in mathematics into something a human being can read and act on. That translation skill is rare. And it is worth more than most technical skills in the long run.

So speak in class even when you are not sure. Write your reports with care, not just to complete them. Read well-written technical blogs and notice how the author builds an argument. Communication is not a soft skill. In this field, it is a force multiplier.

The Real Question for Your First Two Years

Not "what technology should I learn?" That question leads to the excitement trap.

The real question is: "Do I understand what is actually happening inside this machine?"

When you can answer yes to that, every technology you pick up after that becomes easy. Because you are no longer learning tools. You are recognising familiar patterns in new shapes.

The students who ask the second question in their first two years are the ones who end up with options. Job offers. Research opportunities. The ability to walk into any room in this industry and hold their own.

You Are Not Behind

If you came from Maths Biology, if you have never written a line of code, if everyone around you seems to already know things you have not heard of, none of that matters as much as you think it does.

What matters is what you do in the next two years. Not how fast. Not how many technologies. How deep.

Go deep on the fundamentals. Let your curiosity pull you into uncomfortable subjects. Follow the thread wherever it leads, even if it takes you somewhere you did not expect.

That is how the best people in this field got there. Not by rushing toward the destination. By trusting the journey.

And if you are just beginning this journey and missed the note we wrote for students finishing 10th standard, start there first. It will give you the right context before everything we just talked about: What every 10th standard student choosing Computer Science needs to hear

The next part of this series is for college final year students and fresh graduates stepping into the job market. That is coming soon. But for now, you have everything you need to make your first two years count.

Go make them count.

ShieldBreak: When Microsoft Patches a Zero-Day and the Researcher Patches the Patch

ShieldBreak: When Microsoft Patches a Zero-Day and the Researcher Patches the Patch Category: Vulnerability Research | Windows Security |...