Borrowing a smart method without pretending you have the firepower behind it

By fast2future · June 5, 2026 · Build-in-public series

There’s a move almost everyone makes when they admire a more advanced operation: they adopt its language. The frameworks, the impressive vocabulary, the way the smart people talk. It feels like progress. It usually isn’t.

Picture the trap. You come across a frontier team whose approach you genuinely admire — a system that gets better on its own: it names its own limitations, writes its own success tests, proposes and validates small experiments, keeps the winners, and repeats. It’s a beautiful method, and you want in. The honest question underneath the wanting is this: what do you actually adopt — the method, or just the words that make you sound like them?

Here’s how to pull those two apart, and why it’s good news that you can.

Using the words is not the same as doing the thing

Say this one out loud, because it’s the sentence that keeps you honest: you can borrow a method’s vocabulary without borrowing its capability — and confusing the two is how you fool yourself.

The operation you admire is almost always better resourced than you are — a serious team with serious funding. You have far less. And you could absolutely start describing your work in their language — “self-directed,” “open-ended,” “adversarial co-evolution.” The words are free. But saying them wouldn’t hand you their compute, their team, or their depth. It would just give you a more impressive way to describe a small operation — which is a quiet form of lying, mostly to yourself.

So set a rule for yourself: borrow the method’s sound parts, never the vocabulary as a substitute for substance. You’re allowed to run the loop. You’re not allowed to talk like you’re their size. The good news is that the first one is where all the real value lives anyway.

Judge the tactic, not the valuation

Here’s the part that makes borrowing safe to do. A method’s worth has nothing to do with who’s funding it.

The best loops usually weren’t invented by the well-funded lab using them. Their core ideas — open-endedness, growing a diverse library of good solutions instead of hunting one perfect answer — tend to draw on research that’s been developing for years, well before any particular company existed. That matters enormously. It means you can adopt the tactics because they’re independently sound, not because a big funding round blessed them.

The discipline: judge a tactic on its own merit, not on the size of the operation using it. A good method used by a giant is still a good method for you. A bad method used by a giant is still a bad method. The valuation tells you nothing about whether the tactic works at your scale. Strip the prestige away and ask only: is this independently sound, and does it work with what I actually have?

What’s actually worth taking

Pull the prestige off a method like that and you’re usually left with a handful of tactics anyone can use today, at no cost, that sharpen the work you’re already doing:

1. Self-benchmarking. Before you act, write your own test: “how would I know this worked?” Work that grades itself against a real check sharpens faster than work waiting to be graded by someone else. It’s cheap, and it forces honesty about whether a thing actually moved the needle.

2. Quality-diversity. Stop hunting the one perfect article or offer. Cultivate a diverse library of good experiments and let the winners emerge from real results. (Honest caveat: this one only fully pays off once you can measure which won — so if your analytics aren’t live yet, adopt the structure and flag the dependency rather than pretending it’s running at full power.)

3. Propose → test → validate → keep. Small, cheap experiments, each validated against a real check before it earns a permanent spot. Nothing enters the library on vibes.

None of those need new money or infrastructure. They’re sharper versions of things most people are already doing halfway.

The honest anchor: a method needs a destination

There’s a seductive quality to language like “self-directed, open-ended, forever-innovating.” It can pull you into improving for its own sake — building an ever-more-elaborate machine that isn’t pointed at anything a real person needs.

So tie every tactic you adopt back to a single question: does this help a real person, and does it move you toward your actual goal? Open-endedness without a north star is just drift dressed up in impressive words. The method is the engine; the person you’re trying to help is the steering wheel. You need both, and the steering wheel comes first.

Why this is good news

It’s genuinely freeing to realize you don’t need a frontier budget to use a frontier method. The good ideas are mostly portable, mostly old, and mostly free. What separates operations isn’t access to the vocabulary — it’s the discipline to use the sound parts honestly and stay clear about what you actually have.

So borrow boldly from people doing better than you. Take their best method. Just don’t wear their vocabulary as a costume, don’t let a big valuation do your thinking for you, and keep the whole thing pointed at a real person. That’s how you get sharper without getting fake — and it’s within reach today, exactly as you are.