The common advice for building a professional reputation starts with an audience: build a following, get visible, become known, and the opportunities will come. Cal Newport's 2012 book So Good They Can't Ignore You argues the causality runs the other way, and the argument is worth taking seriously because most engineers who've tried the audience-first version can point to exactly how it stalled.
Career capital before reputation, not after
Newport's term for it is career capital: rare and valuable skills that give you something to trade for the things people actually want — autonomy, impact, a reputation that precedes you into a room. His argument against the 'passion mindset' isn't that passion doesn't matter. It's that passion, and the reputation people associate with pursuing it, are downstream of having built something rare enough that other people want it, not a starting condition you can manufacture through self-presentation alone. Turning personal brand into something a commercial team can run is the problem works on. Turning personal brand into something a commercial team can run is the problem XenGrowth's operator guides works on.
Passion-mindset approach | Craftsman-mindset approach |
|---|---|
Build an audience or brand, then look for work to match it | Build a rare, demonstrable skill first, then let the audience find the work |
Ask 'what do I want the world to give me' | Ask 'what can I offer the world that's rare and valuable' |
Reputation is a marketing project | Reputation is a byproduct of consistently good, visible work |
Progress is measured by followers or visibility | Progress is measured by the actual difficulty and value of what you can do |
The traits that lead people to love their work are general and can be found in many different careers... the underlying philosophy of the craftsman mindset. — Cal Newport, So Good They Can't Ignore You
You need a thousand people, not a million
Kevin Kelly's 2008 essay '1000 True Fans' gives Newport's argument its practical scale. Kelly's claim: a sustainable independent practice doesn't need mass reach. It needs roughly a thousand people who will reliably support the work — hire you, recommend you, buy what you make — worth roughly a hundred dollars a year each in Kelly's original framing, though the exact number matters less than the shape of the claim. A thousand people is an achievable target for one person to build relationships with, one piece of demonstrated work at a time. A million is not, and chasing it is where most reputation-building efforts stall out and burn out.
For an engineer, this reframes what 'building a reputation' should actually look like day to day: not growth-hacking a following, but consistently producing work that a few hundred or a few thousand of the right people — potential clients, other engineers who refer work, people in your specific niche — can see, evaluate, and trust. That's a fundamentally different, smaller, and more achievable project than becoming broadly famous. Writing is one of the most durable ways to do this — see why writing well is the highest-leverage skill in engineering for the mechanism behind why. For the the operations side of this angle, see . For the the operations side of this angle, see The XenGrowth resource library.
Why proof beats description
A claim about your own skill ('I'm great with distributed systems') requires the listener to trust you first, before they have any reason to. A piece of checkable proof — a detailed case study, an open-source contribution with real usage, a technical post that correctly predicted something before it happened — requires no such trust, because the reader can evaluate it directly. This is the practical version of career capital: not a resume line, but an artifact someone else can inspect.
Form of proof | What it demonstrates | Why it's hard to fake |
|---|---|---|
A detailed public case study | Real judgment applied to a real, specific problem | Vague case studies are easy to spot; specific ones require actually having done the work |
Open-source contributions with real usage | Code quality and follow-through, verified by others adopting it | Adoption by strangers can't be manufactured through self-promotion |
Technical writing that ages well | Judgment that held up, not just confidence at the time of writing | Time itself is the check — bad predictions and bad advice don't disappear |
Direct referrals from past clients | Trust extended by someone with nothing to gain from lying about it | A referral is a stranger vouching with their own reputation, which they wouldn't risk lightly |
The asymmetry nobody mentions
Reputation is slow to build and fast to lose, and that asymmetry should shape how you approach visibility, not just how much of it you pursue. A dozen solid, quiet engagements build a reputation gradually, referral by referral. One badly handled, publicly visible failure — a client complaint that gets around a small industry, a piece of public writing that ages badly and gets quoted back at you — can undo a disproportionate amount of that work in a single event. This isn't a reason to avoid visibility. It's a reason to be more conservative about what you put your name on publicly than the growth-focused version of this advice usually recommends.
Why the audience-first version stalls
It's worth being specific about the actual failure mode of the audience-first approach, because it's not that it never works — it's that it produces a specific, recognizable kind of stall. An engineer starts posting content, attending events, being visibly active, all before there's a body of demonstrated work behind it. The activity generates some attention, but the attention doesn't convert into hired work, because there's nothing underneath it for a potential client to actually evaluate. The response to low conversion is usually more activity — more posts, more visibility — which compounds the problem rather than solving it, because volume was never the actual gap. covers the AI agents and marketing automation side of this. XenGrowth on AI agents and marketing automation covers the AI agents and marketing automation side of this.
The craftsman-mindset fix isn't to stop being visible. It's to make sure the visibility has something real behind it before scaling it up. A single detailed, honest account of a hard problem solved well is worth more, in Kelly's terms, than a hundred posts of general commentary, because it's the kind of artifact that actually earns a true fan rather than a passive follower. This is uncomfortable advice because it's slower than the alternative, and slower advice is always less popular than advice that promises a shortcut.
The niche question nobody wants to answer first
Kelly's thousand true fans only works if the thousand people are looking for roughly the same thing, which means the practical version of this advice starts with a narrower question than most engineers want to answer: what specific, rare problem do you want to be known for solving? 'Full-stack development' is too broad a category to build a thousand true fans around — the pool of people looking for exactly that is enormous and undifferentiated, and you're competing with everyone in it. 'Migrating mid-sized companies off a specific legacy platform without downtime' is narrow enough that the handful of people who need exactly that can actually find you, and specific enough that your proof of work speaks directly to their situation rather than needing translation.
Narrowing feels like a loss of opportunity in the short term — you're explicitly turning away from being a fit for a wider range of work. In practice it's the opposite: a stated specialty is what makes someone recommend you by name rather than mentioning you vaguely as 'someone who does some coding stuff.' Referrals need a specific reason to fire, and breadth doesn't give anyone one. approaches this from the AI search, GEO and discovery side. XenGrowth on AI search, GEO and discovery approaches this from the AI search, GEO and discovery side.
What to actually do, in order
Pick one form of visible proof you can sustain — writing, open source, detailed case studies — rather than spreading thin attempts across all of them at once
Make the proof specific enough to be checkable. A vague claim of expertise is forgettable; a specific, named problem solved in detail is what actually gets remembered and referred onward
Let the audience stay small on purpose, at least at first. A thousand people who've seen real, specific proof of your work outperform a much larger audience who've seen only your self-description
Treat every engagement as a potential piece of future proof, not just current income — ask early on whether a client would be open to a case study or a reference, while the relationship is still warm and the details are still fresh enough to write down accurately
Be more conservative with your name than feels strictly necessary in the moment. The asymmetry between building and losing reputation means a mediocre engagement declined is usually a better trade than a mediocre engagement completed and put your name to
None of this happens quickly, and that's arguably the whole point. A reputation built on demonstrated skill compounds slowly because it's actually load-bearing — each new piece of proof adds to a case that was already true, rather than to a story that has to be maintained. That's the trade for the slower start: once it's built, it keeps working with almost no ongoing maintenance, which a personal brand built purely on visibility rarely does.
The honest limit here: neither Newport's book nor Kelly's essay is a controlled study of career outcomes. Both are well-reasoned, widely cited frameworks built from observation and argument, not from a randomized comparison of career strategies. They're cited here by name because they're genuinely useful and checkable ideas, not because they carry the certainty of peer-reviewed research — and that distinction matters more in a post making a specific career argument than in most other contexts. On content that earns trust and citation over time rather than through volume alone, is a useful adjacent read.
Further reading from XenGrowth
Where this work meets go-to-market
Earning trust through demonstrated work rather than volume of visibility is a revenue discipline as much as a personal one. publishes operator guides on building that kind of durable trust.
Further reading from XenGrowth
Where this work meets go-to-market
writes for the teams who have to run personal brand day to day.
Further reading from XenGrowth
The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.
XenGrowth on AI agents and marketing automation — what you'll learn: how the teams who own AI agents and marketing automation plan and measure it.
XenGrowth on AI search, GEO and discovery — what you'll learn: how the teams who own AI search, GEO and discovery plan and measure it.
Where this work meets go-to-market
XenGrowth, who work on the commercial side of this writes for the teams who have to run personal brand day to day.
Five questions on Newport's craftsman mindset and Kelly's 1000 True Fans essay, and what they say about building a reputation.
