These scribbles, my kaleidoscope of thought, shall reveal the way I perceive the world.

When Bigger Stops Being Better

Published on: by Stefano Marinelli

6 min read

The reaction to my last blog post on IT Notes was significant. I received a wave of feedback - some constructive, some critical, but all of it helpful. However, some themes in the comments (primarily outside the Fediverse) were recurrent enough that I feel they warrant a response.

The first was about my decision not to name names. I understand the disappointment - a specific target can feel more satisfying. But naming the company would have helped no one.

Before publishing that piece (which had been in my drafts for over a year), I did my research and spoke with some of the people involved. They had already taken action by warning friends and colleagues, with good results. But they had no desire for public exposure. Many years have passed, and the company in question no longer has the relevance it once did.

Some readers understood my position, recognizing that naming them would have opened me up to legal trouble. But many others began citing US laws and constitutional amendments to prove that I could have named names without legal repercussions.

What many fail to grasp is that the world is not the United States. Not every country follows the same rules and laws. In some European countries, even true statements can be actionable if deemed harmful to a company's reputation. The burden of legal costs often falls on the defendant, regardless of the outcome. Truth is a defense, but it's an expensive one.

Furthermore, even if I were to win such a legal battle, it would represent an immense drain on my energy and resources. Cui prodest? Who benefits? Certainly not me.

There's a difference between being transparent and being a martyr. I share my experiences not to name and shame, but to illuminate patterns. If my story helps even one developer recognize red flags early, or encourages one entrepreneur to prioritize sustainability over a quick exit strategy, then the purpose is served. The goal isn't to destroy companies - it's to build better alternatives. Builders, not destroyers.

The Italian Problem That Never Was

The second recurring theme deserves a more careful response.

The assertion was that "stories like this can only happen in Italy because it's full of small, family-run businesses". This one, I admit, irritated me more - especially when it came from fellow Italians.

First: I have not only worked in Italy, and I never specified that the story was about an Italian company.

Second, and more importantly: the existence of small businesses is a strength, not a weakness.

Over my 20+ year career, I've worked with companies across different continents. The dynamics I described are universal. I've seen them in Silicon Valley startups obsessed with growth metrics, in European scale-ups playing the scalability game, and yes, in Italian SMEs. This isn't a geographic problem - it's a structural one, tied to how we measure business success.

Experience has taught me that large corporations create replaceable employees - mere cogs in a machine. In that model, the customer becomes a number, stripped of their essence. The company's relentless need for constant growth becomes a vise grip. The relationship is no longer about providing a service that enriches a person's life, but about becoming a kind of necessary evil.

The AI Generated Accusation

Then there was a third recurring comment: "AI Generated!"

It seems to be the fashion of the moment. Pointing at every text as AI generated, searching for details (even unfounded ones) in every corner of every sentence. This makes me smile. In one case, it was a person who instead regularly reshared videos and texts that were fake, obviously AI generated.

I write as I've always written. Being a non-native English speaker, my process often involves writing my notes or the full post in Italian first, and then translating it. The original Italian text is 100% mine. Of course, I use tools to check grammar and polish the final version. But the form, the thoughts, the experiences, the reflections? Those are mine. Earned through years of work, mistakes, and learning.

Perhaps the real issue is that we've become so accustomed to corporate speak, to sanitized PR language, to texts optimized for SEO rather than human readers, that when someone writes plainly about their actual, real life experiences, it feels somehow artificial. Real life is less realistic than the perfect, AI generated world.

That says more about what we've normalized than about my writing.

Back to What Matters

Let me offer some concrete examples of why small matters.

Last year, a small hosting provider I work with noticed unusual activity on a client's server at 2 and called them directly. A large provider's automated system would have simply shut it down (or worse, kept it running and sent a bill for the attack traffic). The small provider knew their clients by name, understood their business patterns, and acted with judgment - not just policy.

When a craftsman repaired my roof, as I wrote about a few months ago, he installed a permanent lifeline. Not because the contract required it, but because he cared about anyone who might climb up there in the future. An antenna installer, maybe. Someone we'd never meet. A large contractor would have done exactly what the contract specified. Nothing more, nothing less.

Consider my own field. I could recommend a managed Kubernetes cluster from a major cloud provider. It would be "scalable", "enterprise-grade", buzzword-compliant. Or I could set up a simple FreeBSD system on a modest VPS that the client actually understands and controls. The first option makes me look sophisticated. The second option actually serves the client.

The Myth

We've been conditioned to believe that scale equals quality. That "enterprise solutions" are inherently superior to "small business" ones. That a local craftsperson or a small firm can't possibly match the capabilities of a multinational corporation.

Often, it's the very opposite.

Scale brings standardization - which means one-size-fits-all solutions that actually fit no one perfectly. Scale brings layers of bureaucracy, where decisions pass through committees and approval chains, each step removing you further from the person who actually understands your problem. Scale brings quarterly earnings pressures, where every interaction is optimized for extraction rather than service.

Small brings accountability. When there are only three people in the company, and one of them is talking to you, that person cares about your satisfaction in a way no call center agent ever can. Their reputation is on the line with every interaction. Their business lives or dies by word of mouth, not by marketing budget.

Small brings flexibility. Without layers of approval, a small business can say "yes, we can try that" in ways that are literally impossible in larger organizations with rigid policies.

Small brings knowledge. The person who answers your call is often the same person who will do the work. Or at least knows them personally and can walk down the hall to discuss your specific situation.

I've seen this pattern repeated across industries. The barista who knows the exact temperature and length that his "friend of the bar" prefers. The small bakery that remembers you prefer less sugar. The independent bookstore that special-orders obscure titles. The local mechanic who tells you honestly that you don't need that expensive repair yet. The solo developer who maintains software for twenty years because users depend on it, not because there's a business case.

These aren't romantic exceptions. They're the backbone of genuine service.

Where Trust Lives

So no, I won't be naming names. And yes, I'll continue to champion small businesses - not out of nostalgia, but because I've seen, time and again, where real quality and accountability actually live. Not in the quarterly earnings report. Not in the hockey-stick growth chart. Not in the "enterprise solution" that requires tons of (expensive) certifications to configure.

It lives in the direct relationship between maker and user, service provider and client. That's where trust is built. And trust, unlike scale, cannot be automated.

It's earned, one interaction at a time, by people who know your name.