Team Rocket Came Back Again, Phase 2 Ended, and I started to learn new things in tech

"Prepare for trouble!"

Team Rocket.

They always came back.

They changed their plans.

They tried new tricks.

Sometimes they failed in the funniest way possible.

But one thing never changed.

They kept looking for new ways to attack.

And honestly…

Today reminded me that the world of technology isn't very different.

Just when you think you've understood one kind of attack, someone discovers another way to break the rules.

⚡

Today I finally started working through Linked Lists on LeetCode.

After spending so much time with arrays, HashMaps, Sliding Windows, and Two Pointers, Linked Lists felt like entering a completely different route.

The data wasn't sitting neatly beside each other anymore.

Every node had to know where the next one was.

One connection.

Then another.

Then another.

At first, it felt slightly strange.

But after spending time understanding how the links actually work, I started seeing the pattern.

A Linked List is almost like Ash's journey itself.

You don't know everything that's waiting at the end.

You simply follow the next connection.

One node leads to another.

And eventually…

You reach the destination.

🧩

But today's most interesting discovery wasn't in DSA.

It came from the world of hardware security.

I started learning about an attack known as Row Hammer.

And honestly…

The first time I heard about it, I thought,

"Wait… an attack against memory itself?"

That's when things became interesting.

We've spent so much time learning about application security.

Web vulnerabilities.

Authentication.

Kubernetes security.

Cloud security.

But hardware has its own battlefield.

And sometimes the attack doesn't begin with an application at all.

It begins much closer to the machine itself.

Inside the memory.

🖥️

I won't go deep into the attack today.

That deserves its own episode.

And that's exactly where I'm planning to take it.

My Attack and Security series will eventually reach this topic, where I'll explore the concept behind Row Hammer, why it matters, and how security engineers think about attacks that happen below the application layer.

Because the deeper I go into security…

The bigger the battlefield becomes.

And then there was SentiOps.

Today wasn't just another day of coding.

It felt like the closing chapter of Phase 2.

The architecture has grown.

The ideas have evolved.

The things I initially imagined have slowly turned into something much more real.

And now…

Phase 2 is done.

🤖

If SentiOps were a Pokémon journey, I think Phase 2 would be the moment when Ash's team finally looks at the horizon and realizes something.

They've come a long way.

But the next region is going to be harder.

The opponents will be stronger.

The battles will be more complicated.

And Team Rocket…

Well…

They'll probably be waiting somewhere nearby.

😂

That's actually what makes SentiOps interesting to me.

The whole idea behind the project is about security alerts, incidents, observability, and eventually intelligent response.

But the world doesn't stand still.

New attacks appear.

New failure modes appear.

New vulnerabilities are discovered.

So the platform has to evolve too.

A security system that stops learning eventually becomes part of the problem.

Today, three completely different worlds somehow came together.

Linked Lists taught me to follow connections carefully.

Row Hammer reminded me that attackers can target layers much deeper than applications.

SentiOps Phase 2 reminded me that building a real system is a long journey where every phase prepares you for the next.

And strangely…

They all taught me the same thing.

Connections matter.

A Linked List is built from connections.

A production system is built from connections.

An attack can move through connections.

An observability platform finds problems by connecting clues.

And SentiOps is slowly becoming a system designed to understand those connections.

Everything is starting to make sense.

🧠

Tonight feels slightly different.

Not because I finished everything.

But because one chapter actually ended.

Phase 2 is complete.

The next chapter is waiting.

The Linked List journey has begun.

The security series has another attack waiting in the shadows.

And somewhere in the distance…

Team Rocket is probably preparing another ridiculous plan.

I guess that's the nature of this journey.

You don't defeat every challenge forever.

You learn.

You adapt.

You build better defenses.

And when the next attack arrives…

You are ready to face it.

⚡🚀

🧠 Tiny Crux Before Closing My Laptop

🧩 Linked Lists became the next chapter in my DSA preparation, teaching me to think about data through connections rather than simply positions.

🖥️ Row Hammer opened another door into hardware security and reminded me that the attack surface doesn't stop at applications, containers, or networks.

🤖 SentiOps Phase 2 officially reached its end, marking another major milestone in the project's journey and giving me a stronger foundation for whatever comes next.

🛡️ My Attack and Security series will eventually explore Row Hammer in its own episode, because understanding security means understanding how attackers think across every layer of a system.

🚀 The biggest lesson today was that security never really has an ending. The moment you think you've solved every problem, Team Rocket arrives with a new trick.

So…

Phase 2 is complete.

But the journey?

Not even close.

"Looks like Team Rocket's blasting off again!" 🚀⚡