F*ck Leetcode! Why Roy’s Story Matters

in #leetcodelast month


image.png

Today, let’s dive into something that’s been buzzing around the tech world: the case of Roy and why it’s a wake-up call for our industry. This 21-year-old has inadvertently pulled back the curtain on just how broken the tech hiring system has become, and it’s a conversation we desperately need to have.

Don’t get me wrong; I’m not saying you should ditch your textbooks and stop honing your abstraction skills. Keep building those fundamentals! Maybe sprinkle in some math to keep things spicy. And practicing on platforms like Leetcode or Codewars? Go for it! Think of it as a daily brain workout, just like hitting the gym.

# Example: A simple Leetcode-style problem
def sum_two_numbers(a, b):
  """
  Given two integers a and b, return their sum.
  """
  return a + b

But here’s the kicker: coding interviews are about SO much more than just Data Structures and Algorithms (DSA).


We’ve reached a point where students and junior engineers are pressured to grind Leetcode problems into oblivion. We’re talking about spending countless hours solving often esoteric problems with little practical application. Is this really the best way to assess someone’s potential?

Sure, patterns exist, and pattern recognition can be trained. But creating a societal mental model that tells aspiring developers that DSA prowess is the only key to landing a job is insane. We’re essentially turning them into algorithm-solving robots!

When AI can do better

Think of the Engineers who built ChatGPT. I’m pretty sure part of them was also fed up with how stupid these interviews were and they felt motivated to automate the solving problem issue. Maybe not fully solving it but getting closer to it


And here’s the funny part: the very big companies that champion this Leetcode-centric approach are often the first to complain when a “David” comes along and disrupts their carefully laid plans. Why is that? Perhaps because they’ve become so focused on theoretical knowledge that they’ve lost sight of practical innovation.

Roy’s story marks the slow, but potentially powerful, uprising of Gen Z against the old Goliaths of tech. He’s become a symbol, whether he intended to or not.

Mark my words: if he gets crushed by the system, he’ll become a martyr. If he survives and stays true to his path, he’ll be an inspiration to a new generation of developers.

What truly makes a great software engineer? It’s understanding tooling, grasping system design principles, and possessing a healthy dose of intuition. It’s about being able to apply your knowledge to real-world problems, not just solving abstract puzzles.


Some argue that this situation will force companies back to in-person interviews. Maybe…for the giants with deep pockets. But there will always be pragmatic companies that value practical skills over theoretical hubris.

And let’s be clear: if you’re applying for NASA, you absolutely shouldn’t be cheating! The stakes are incredibly high. But the level of scrutiny should match the importance of the role.

It’s sad, and frankly a little comical, to see these massive companies leveraging capitalism to create the illusion of exclusivity.

They want you to believe that only the “best” get in, when in reality, a handful of PhDs are doing the heavy lifting while the rest are building upon existing patterns or, let’s be honest, centering divs.

But here’s where things get really messed up. The speed with which AWS and YouTube moved to try and silence Roy is alarming. AWS not only rescinded his job offer but also allegedly influenced Columbia University to expel him. How messed up is that? He’s just a kid! And you’re treating him like a criminal? This speaks volumes about what these companies truly value.

And YouTube’s immediate censorship of his video? What happened to freedom of expression? Who gets to decide what’s right and wrong? A centralized group of corporations?

Again, I’m against cheating. Practice relentlessly! Your brain is a muscle. But the actions of AWS and YouTube reek of Aaron Swartz all over again. They seem determined to crush this kid.


Roy’s story is a stark reminder that the tech hiring system is in dire need of reform. We need to move away from the Leetcode obsession and focus on assessing practical skills, problem-solving abilities, and genuine passion for technology. We need to create a more inclusive and equitable environment where talent is nurtured, not stifled.

What are your thoughts? Is the Leetcode grind doing more harm than good? Let’s discuss in the comments below.


If you liked this content I’d appreciate an upvote or a comment. That helps me improve the quality of my posts as well as getting to know more about you, my dear reader.

Muchas gracias!

Follow me for more content like this.

X | PeakD | Rumble | YouTube | Linked In | GitHub | PayPal.me | Medium

Down below you can find other ways to tip my work.

BankTransfer: "710969000019398639", // CLABE
BAT: "0x33CD7770d3235F97e5A8a96D5F21766DbB08c875",
ETH: "0x33CD7770d3235F97e5A8a96D5F21766DbB08c875",
BTC: "33xxUWU5kjcPk1Kr9ucn9tQXd2DbQ1b9tE",
ADA: "addr1q9l3y73e82hhwfr49eu0fkjw34w9s406wnln7rk9m4ky5fag8akgnwf3y4r2uzqf00rw0pvsucql0pqkzag5n450facq8vwr5e",
DOT: "1rRDzfMLPi88RixTeVc2beA5h2Q3z1K1Uk3kqqyej7nWPNf",
DOGE: "DRph8GEwGccvBWCe4wEQsWsTvQvsEH4QKH",
DAI: "0x33CD7770d3235F97e5A8a96D5F21766DbB08c875"