Don't Tell Your Friends. Build Quietly, Launch Loudly.

When you start building something, the very first thing you'll want to do is tell someone.

Don't.

Or, more precisely: tell a lot fewer people, a lot less often, than you're about to.

This one felt counterintuitive to me for a long time, because building is exciting and sharing feels natural. But it's one of the most useful pieces of advice I could give someone starting out.

The trap of premature announcement

Here's what happens when you tell your friends and family about your project too early.

You feel like you've made progress. You haven't — you've just talked about it. Talking releases some of the same emotional payoff as doing, without the doing.

You now have to report back. Every family dinner from now on: "how's the app going?" Which, some weeks, is a lovely question and, most weeks, is like being asked to grade your own homework in public.

You collect a lot of well-meaning but not useful feedback. Your cousin's roommate's friend has "some thoughts." Someone forwards you an article about AI. Someone confidently tells you your idea already exists (it usually doesn't, or, if it does, it's not the same thing). Sorting all of that out takes energy you should have been spending on the actual product.

You get talked out of things. Not always overtly — sometimes just in the little raised eyebrows and "oh, interesting" tones from people who don't quite understand what you're doing. Enough of those and you start second-guessing decisions you had good instincts about.

Why it's especially fraught at our age

At 50, telling people you're building software is a specific social event. Some people will be very supportive in a way that also sounds vaguely like they think you're going through something. Some people will be openly puzzled. Some will pretend they get it and then ask, three weeks later, if you've quit yet.

None of that is malicious. But it's heavy, and it doesn't help.

You know what does help? Building quietly for long enough that when you do talk about it, you're talking about a real thing that already works.

The "quiet build" mindset

Building quietly does not mean secretively. It means with restraint about who knows what, and when.

• The people in your immediate circle can know you're "working on something," in the same casual way anyone works on any hobby.
• Real details go only to people who can actually help — a specific friend in the industry, a small circle of similarly-minded builders, maybe an early-user group who signed up because they cared.
• The wider announcement comes when the thing exists and works. Not when it's an idea. Not when it's a plan. When it's a thing.

That's the discipline.

What to do with the urge to share

You will still have the urge. That's fine. Redirect it.

• Write it down in a note. The urge to tell people is often really an urge to process what you just did. Writing gives you the processing without the exposure.
• Talk to the AI about it. Genuinely. Explain the win to it. Ask it what you should do next. It doesn't judge you and it doesn't put your ego on a scale.
• Join one small community of other builders and share there. Not because they'll be more impressed — they might be less impressed, honestly — but because they get it.

Save the wider audience for when you have something to actually show them.

Launch loudly (when the time comes)

The flip side is important: when you do have something real, launch it loudly. Full stop. No apologetic tone. No "hey, this is probably nothing but…" No burying the link at the bottom of a long post.

You spent months building something. You are allowed to make noise about it. In fact, the people who quietly built and then quietly launched almost always regret how quietly they launched.

The formula:

• Silent construction.
• Loud unveiling.
• Then back to steady, honest updates.

The 50-year-old bonus

At our age, we have a certain credibility when we speak up about something we've built. We're not seen as a kid chasing a trend. We're seen as an adult who committed real time to a thing. Use that. But it only works if you have the thing to point to.

The takeaway

The impulse to talk about your project is usually a symptom of how much you care about it, not a signal that you should act on it. Care about it privately for a while. Build the actual thing.

Then — and only then — go tell everyone.

They will be much more impressed than they would have been at "so, I have this idea...