Respect the Rules or Rewrite Them—Which One Wins?
Read on Substack · 2025-02-26
Full article
The current experience of problems I've faced and solutions I've implemented and also thrive in real world for a fair amount of time, is comparatively less. But it's something.
I used to be annoyed by constraints. Wished there were more hours in a day. Wished healthy food wasn’t a whole mission to find. Wished stupid rules didn’t make simple things harder. I saw these as things in my way. Now I'm seeing them as the edges that shape what’s possible.
Constraints are everywhere. Time, money, physics, rules. Some are absolute. Some aren’t. The trick is knowing which is which. Early on, I had a decent sense of what to leave alone. If I couldn’t change it, I wouldn’t waste energy on it. But what took time—what still takes time—is figuring out what can actually be tweaked. Where the real levers are. What looks unchangeable but isn’t. That part only comes with experience, looking forward :)
There’s a difference between constraints and obstructions. Constraints are the structure. Obstructions are the clutter. Time and gravity are constraints—can’t change them, so we work with them. A policy, a process, an outdated habit? Those might just be obstructions. The hardest thing is spotting the difference. I wasted energy fighting constraints that I should have accepted. I also wasted time tolerating obstructions that I should have blasted through. Whatever experience I have, it is teaching me which battles to fight. Or at least, this is what I aim to learn from all my past and upcoming experiences. If something truly cannot change, it's a constraint. If it’s just difficult or inconvenient, it's an obstruction I might overcome.
Talk is cheap when it never faces reality. We've all spent months (years for many) in meetings and theory. Talking about ideas. Mapping out plans. It all felt productive. But speculation is air. Only execution brings weight. I learned more in one botched implementation/rollout than in endless strategy discussions. We implement (or ship) something, and within a day, the plan collided with constraints we hadn’t even thought of. Users did things we didn’t predict. All our talk had been shallow. We were armchair quarterbacks—people commenting from the sidelines, confident we understood the game, but never having actually played it.
Real lessons come from action. I forced myself, still do intentionally, to stop endless discussions and pull the trigger. Write the code. Publish the article. Make the shift. The moment I executed, I got feedback. Sometimes it hurt (quite a lot in the moment). Many times it humbled me. But it was always real. Only execution showed which constraints were concrete and which fears were ghosts.
Living with constraints means living with trade-offs. I used chase the “right” choice. The flawless plan and policy that avoids all pain. It doesn’t exist. Every decision lives under conditions that limit it. Limited time, limited information, limited resources. So every choice is flawed in some way. There is no optimal path, just a set of imperfect options. Once I accepted that, decision-making became simpler if not easier. I started looking for the least problematic route instead of a perfect one. Which outcome can I live with? Which problem can I survive? That became my guiding question (I still make these mistakes).
Good execution is mostly preempting where things will break, not just optimizing where things are working. The best operators aren’t those who make "correct" calls, but those who consistently avoid irreversible failure while stacking small survivable wins. Making decisions under constraints isn’t about perfection. It’s about survival. Pick the path that hurts least or yields more than it costs. Then commit fully. If it breaks, I’ll learn and adjust. But I won’t stand still fantasizing about a risk-free choice. There isn’t one.
I think constraints can feel like a cage. But they are also a forge—they apply pressure, force refinement, and shape raw ideas into something stronger. A startup with no money has to innovate. A writer with a strict form often produces more creative work than with unlimited freedom. A person trapped in a tough situation finds clever ways to adapt. Scarcity and limitations spark ingenuity. When resources were scarce, we found unconventional solutions. We cut features to focus on what mattered most. We automated tasks because we had no staff to spare. We all know this. These limits were painful, but they made us sharper. If we had endless cash and time, we might have been sloppy. The constraint of survival made us efficient.
However, not all growth comes from staying inside the lines. Some leaps require breaking constraints entirely. The biggest innovations happen when someone says, “We don’t have to do it this way.” But breaking a constraint is risky. Most constraints push back hard. I learned there’s a time to live within the rules and a time to rewrite them. The art is knowing which path to take.
The key is judgment. Optimize within constraints when the walls are solid. Squeeze out every bit of creativity and efficiency inside the box. Break constraints when those walls are paper-thin or deserve to crumble—when the reward outweighs the risk. Both routes require courage. Either you discipline yourself to thrive in less, or you dare to grab for more. I’ve done both. Sometimes you accept the rules; sometimes you change the game.
I’ve learned to respect the walls. They shape what’s possible. I don’t want to waste time fighting them, but I also don’t want to let them decide everything either. When there’s a door, I take it. When there isn’t, I try to build one. Not always clean. Not always smart. But we move. Without action, all of this is just theory. With action, even the hardest constraints become something to work with.
Goes without saying, with my current experience with the problems I've faced and solutions I've implemented and also thrive in real world for a fair amount of time, is comparatively less. But it's something.
Connected ideas
These links connect the published piece to working idea notes. The article text above retains its published wording.