Don’t Just Eat and Complain: Why Engineering Culture Is Your Best Investment

“I can’t cook, but I can eat and complain” — that’s what my ex-girlfriend used to joke when we’d go to expensive restaurants and she wasn’t satisfied with the meal. It was funny then, but it’s become my go-to analogy for a problem that plagues engineering organizations everywhere.

You see it in every Slack channel, every stand-up, every retrospective. Engineers complaining about tooling issues, process friction, or that one flaky test that’s been failing intermittently for months. We’re all excellent at identifying problems — we can spot a code smell from a mile away, diagnose performance bottlenecks with surgical precision, and write detailed bug reports that would make Shakespeare weep.

But here’s the uncomfortable truth: complaining without action is just noise.

The Restaurant of Engineering

In this restaurant of engineering that is your codebase, your CI/CD pipeline, your development workflow — you’re not just the customer. You’re also the chef. You have the skills, the access, and often the authority to fix what’s broken. Yet how often do we default to being the diner who sends their meal back to the kitchen, expecting someone else to make it right?

I witnessed this dynamic play out recently in our engineering channels. A developer raised an issue about our code analysis tool flooding merge requests with duplicate comments, causing GitLab to freeze during reviews. Classic problem — everyone +1'd the complaint, but for a moment, nobody stepped up to actually look at the code.

Then something beautiful happened. Instead of waiting for “someone else” to fix it, a couple of engineers took initiative. They didn’t just identify the problem; they rolled up their sleeves and solved it.

The Mathematics of Scale

Here’s where the story gets interesting, and where engineering culture becomes a business imperative. We have hundreds of engineers. When one person experiences friction with our tooling, it’s not just one person’s problem — it’s potentially 200 or 300 people hitting the same wall.

Think about it: if a flaky test wastes 5 minutes of your time once a week, that seems trivial. But multiply that by 300 engineers, and suddenly you’re looking at 25 hours of lost productivity weekly. Over a year, that’s nearly 1,300 hours — equivalent to hiring an additional engineer just to compensate for the friction.

The ROI of fixing these “small” problems isn’t small at all.

As Theodore Roosevelt once said, “Complaining about a problem without proposing a solution is called whining.” In engineering, we have the privilege that we can almost always propose — and implement — the solution ourselves. We just need to choose action over acceptance.

The Long Game of Engineering Culture

The immediate benefits are obvious: fewer interruptions, smoother workflows, happier developers. But the long-term effects of a “fix it, don’t just complain about it” culture run much deeper.

When engineers see their colleagues taking ownership of shared problems, it creates a positive feedback loop. Problems get solved faster. Knowledge gets distributed more broadly. The entire organization becomes more resilient and adaptive.

More importantly, it builds the kind of engineering culture that attracts and retains top talent. Nobody wants to work in an environment where problems fester and finger-pointing is more common than problem-solving.

Making Small Steps, Moving Fast

One of our lead engineers put it perfectly after witnessing this problem-solving in action: “Making small steps makes you move, and at some point of your career you will see that making small steps but fast is what actually makes you very efficient.”

This resonates because it challenges the myth that only big, sweeping changes matter. In reality, engineering excellence is built on countless small improvements, each one making the next person’s job a little easier.

You don’t need permission to fix a broken build script. You don’t need a committee to update documentation. You don’t need a sprint planning session to submit a configuration change that eliminates annoying false positives from your linter.

Your Move

The next time you find yourself frustrated by a tool, a process, or a piece of code — pause before you hit send on that complaint message. Ask yourself: “Can I fix this instead of just complaining about it?”

More often than not, the answer is yes. And when you make that choice, you’re not just solving a problem — you’re modeling the kind of engineering culture that makes organizations thrive.

Because in this restaurant of engineering, we’re all chefs. We can all cook. And when we choose to fix rather than just complain, we make the whole meal better for everyone.

What problems are you complaining about that you could actually fix? I’d love to hear about the small improvements you’ve made that had bigger impacts than expected.