Working from home already blurs the line between personal space and professional time. For one software engineer, that line didn’t just blur, it disappeared completely after a single good deed.
What started as a quick, harmless favor for a neighbor turned into an unexpected flood of requests, interruptions, and assumptions that his time was somehow… public property.
At first, it was manageable. A knock here, a quick question there. But when those small asks turned into a steady stream of strangers expecting free tech support during his workday, things started to feel less like neighborly kindness and more like unpaid labor.
And when he finally said no, the backlash was immediate.
Here’s the original post:
A few months ago, the situation was simple. His neighbor, an older man living a couple floors down, needed help setting up a printer. It took ten minutes. No stress, no expectations, just a straightforward favor between neighbors.
That should have been the end of it.
Instead, it became the beginning of something much bigger.
Unbeknownst to him, the neighbor had been enthusiastically spreading the word throughout their 20-unit building.
Not just that he was helpful, but that he was basically a “tech genius” who fixed things for free. It wasn’t framed as a one-time favor. It sounded like a service.
And people listened.
Soon, there were knocks on his door at all hours. Not just quick printer setups either. People came with cracked phone screens, ancient laptops, lost photos, and vague complaints like “it’s just slow.”
The requests weren’t occasional. They started interrupting his actual workday.
That’s when things shifted from mildly annoying to genuinely disruptive.
He began turning people away, politely at first. He explained that he was a software engineer, not a repair technician, and that working from home still meant working.
But the message didn’t fully land. Some neighbors seemed confused, others a little irritated, like he was refusing something he had already agreed to offer.
The real breaking point came when the original neighbor showed up again.
This time, it wasn’t a quick fix. The laptop he brought was, in his own words, “literally falling apart.” This wasn’t a ten-minute favor. It was a full repair job, the kind that professionals charge for.
So he said no.
He told him clearly that he wasn’t doing tech support anymore and suggested taking it to a proper repair shop. That should have been reasonable. Instead, it sparked a confrontation.
The neighbor accused him of not being “neighborly” and dismissed his job entirely with the classic line, “you’re just sitting at a computer all day anyway.”
From his perspective, this wasn’t a big ask. From the engineer’s perspective, it was yet another boundary being ignored.
That’s when the response got sharper.
He told him they weren’t friends, just neighbors, and that his professional time wasn’t a public resource.
It’s a blunt statement, but also an honest one.
And that’s where the tension really lies. The neighbor seems to view help as something communal and freely given, especially when it appears easy or quick. The engineer, on the other hand, sees his skills as part of his profession, something that takes time, focus, and effort, even if it looks simple from the outside.
There’s also a common misunderstanding at play here. People often assume that if someone works with computers, they can fix anything tech-related.
But software engineering and hardware repair are very different skill sets. It’s like asking a surgeon to fix your broken glasses just because they both involve precision.
More importantly, there’s the issue of consent.
Helping once doesn’t mean agreeing forever. And it definitely doesn’t mean agreeing to help an entire building for free, especially without being asked.
What makes this situation frustrating isn’t just the requests themselves, but how they were created. The neighbor didn’t just ask for help.
He volunteered someone else’s time and skills without permission, then acted surprised when that generosity didn’t extend indefinitely.
And once that expectation was set, it became harder to undo.
Here’s how people reacted to the post:
Many people shared similar experiences, especially those working in tech, where a single favor quickly snowballs into ongoing unpaid support.
Others pointed out the risk of liability, once you touch someone’s device, you can end up being blamed for future problems.
A common theme was clear: boundaries aren’t rude, they’re necessary. Especially when someone else keeps volunteering your time for you.
At the heart of this story is a simple but important idea. Kindness should be a choice, not an obligation.
Helping a neighbor once is a generous act. Being expected to help everyone, anytime, for free, is something else entirely. The moment a favor turns into an expectation, it stops feeling like kindness and starts feeling like pressure.
Maybe the real lesson here is that setting boundaries early isn’t unfriendly. It’s what keeps good intentions from turning into long-term frustration.
So what do you think? Was he right to shut it down, or could he have handled it differently without burning bridges?
