Scrum was introduced in the 1990s and became a sensation in the early 2000s. Back then it was marketed as the cure for everything that was wrong with waterfall: slow delivery, rigid plans, unhappy developers. Companies embraced it, created new roles like Scrum Master and Product Owner, and treated it as if it were the universal recipe for agility.

Twenty years later, the verdict is clear: the promises didn’t hold up. Scrum didn’t make teams faster or more adaptive. In many places it became the opposite.

Scrum assumes that a sprint backlog should remain fixed. That might sound logical in theory, but in reality requirements shift every few days. What seemed like the top priority at the start of the week can already be irrelevant by the end of it. The result is wasted work and frustrated developers.

It also lives in an awkward middle ground. It’s not fully planned like waterfall, but it’s not truly flexible like kanban either. You don’t get the clarity of one or the flow of the other. Teams are left with the worst of both worlds.

The ceremonies were meant to improve communication, but they quickly turn into a drag. Daily stand-ups, planning, retrospectives… they eat time without producing much value. Too often they become status update theater. And the roles that were supposed to help—Scrum Masters, Product Owners—end up adding bureaucracy instead of removing it.

Retrospectives are a perfect example. They’re supposed to drive continuous improvement, but in practice they repeat the same obvious points, produce action items no one follows up on, and force people into artificial formats that feel childish. Problems that could be solved on the spot are postponed for the sake of “the process.”

Another hidden cost is how Scrum erodes expertise. The culture of “everyone has a voice” sounds inclusive, but it often means specialists get drowned out. After explaining the same things over and over, they get tired and stop fighting. Wrong ideas end up implemented just because they surfaced in a meeting. Over time, that builds technical debt.

Scrum was sold as agility, but in practice it slows teams down and rewards process compliance instead of outcomes. It optimizes for running Scrum itself, not for delivering value.

Scrum had its moment, and maybe it helped the industry break free from waterfall. But it hasn’t aged well. In today’s environment it produces waste, bureaucracy, and demotivation more often than it produces working software. It’s time to admit it: Scrum is a failed experiment, and we should move on.

So my phone was stolen on the 7th of this month and the person immediately shut it off, he then turned it on the 17th when and I got a location and the phone went into lost mode, the person then turned the phone was again and has not turned it on since, yesterday my dad got multiple SMS that my phone has been located and to sign into my iCloud account using the link to get the location, I knew it was a phishing link but I wanted to try and get the source code so that I could maybe do something to track the person, I did not entry any of my account's detail and when I tried to inspect the page, it redirected to the official apple's find my page, I have been able to intercept part of the source code and had gotten basic information about the website, could anyone please help me?

Server: Cloudflare
CF-RAY: 974529b93bb99822-MRS

Anyone else spend way too much time figuring out code someone else wrote?

Wrote this after another late night trying to debug something with zero comments or docs. Turns out this problem is costing way more than I thought.

Pretty eye-opening stuff if you're tired of archaeology expeditions through old codebases.

Most retro tools feel bloated or paywalled. We built a free, lightweight retro tool at EvolveDev, no setup, just share a link and run.

Curious: do you like simple tools for retros, or do you prefer structured ones (Miro, FunRetro, etc.)? And what’s a dealbreaker for your team?

Guess many heard of this

You’re Not Imagining It: AI Is Already Taking Tech Jobs

But I google jobs in India, i found this

Small cities see 50% H1 rise in IT hiring in a jobs twist

India’s Tech Jobs See 20% Growth in 2025, AI Roles Surge 75

Written in Rust, the PyApp utility wraps up Python programs into self-contained click-to-run executables. It might be the easiest Python packager yet.

August 2025

I wrote this blog when I tried to understand how I/O in Linux works and how can we make syscall to it in mordern software applications. AI experts predict Large Language Models (LLMs) become the wrapper of traditional programming language in this AI hype. Why do we still need to know about low-level Linux syscall when programming, which is pretty boring .... I argue, not just because you can "do" the job by vibe coding is not that you good at it. Understand the whole techstack from the top to the bottom is what make you good at what you do, and it is actually fun too.