Why 10x Factor exists
I started 10x Factor so one engineer's lesson becomes the default. This is the contract: what we measure, what we will not do, and the one thing I am asking you to do this month.
You know the moment. Another engineer shows you how the system actually works, and a year of confusion collapses into an afternoon. You ship differently after that. You think differently after that.
That gift is usually luck. A generous teammate. A post you happened to find. A review you were lucky to sit in.
I started 10x Factor to make it deliberate.
The bet
Engineers grow faster when they learn from each other, experiment in the open, and share until one person's lesson becomes everyone's default.
Learn from the people who built the thing. Build on problems you actually own. Share the work while it is still rough enough to be useful. Challenge a practice when you have a better way, and stay in the room when someone challenges yours. Teach, so the engineer beside you gets the year-into-an-afternoon you once got.
Do that long enough and knowledge compounds. The room gets sharper every month. Every member becomes a multiplier. That is the culture I want our names attached to.
Bring the thing that changed you
Bring the talk you wish someone had given you two years ago. Bring the architecture you are nervous to defend in public. Bring the experiment, the postmortem, the half-built tool, the question you have been carrying alone.
We will take it seriously. We will argue with it. We will try it on real work. When it holds, we will keep it, write down the gotchas, and hand the next team a practice they can start from.
You will get better here. Someone else will get better because you were here. Both of those are the point.
Go second
This post is me going first.
Your move is one public act this month. Propose a session. Publish a field note. Offer mentorship on something you have shipped, or ask for it on something you have not.
Choose the thing that would have changed your last year if someone had shared it sooner.
Learn. Build. Share. Multiply.
I will see you in the room.
Reactions
Discussion
No comments yet
Sign in as a member to join the discussion.
Keep reading
All stories
The Real AI ROI Playbook — How to Measure Engineering Productivity in the Age of AI
What factory electrification, the productivity paradox, and the theory of constraints reveal about measuring AI ROI in engineering—and how to build an operating model that delivers real economic value.

Your AI Coding Agents Are Faster. So Why Isn’t Engineering Getting Cheaper?
What factory electrification, the productivity paradox, and the theory of constraints reveal about measuring AI ROI in engineering.

We Didn’t Eliminate Data Engineering Work. We Just Turned It Into Paranoid Auditing.
On paper, our data engineering velocity is up 400%. We’ve compressed three-week ETL pipeline builds into a couple of days using autonomous agents. In reality, the time we spend untangling silent data bugs has quietly doubled. We spent the last three years building the most sophisticated data agents