Factor

Learn. Build. Share. Multiply.

Engineers who make other engineers better

An invite-only engineering community where knowledge compounds into collective capability.

Request accessSee events
  • 10x Talks
  • Architecture Hour
  • 10x Labs
  • Build Night
  • Engineering Reads
  • 10x Hackathon
  • Architecture Challenge
  • Engineering Showcase
  • Failure & Learning
  • 10x Awards

Five pillars. One compounding loop.

See them on the calendar

Tech talks, workshops, architecture sessions, and engineering fundamentals.

  • Tech talks
  • Workshops
  • Architecture sessions
  • Fundamentals

Hackathons, experiments, prototypes, internal tools, and AI challenges.

  • Hackathons
  • Experiments
  • Prototypes
  • Internal tools
  • AI challenges

Engineering blogs, demos, reusable patterns, postmortems, and lessons learned.

  • Engineering blogs
  • Demos
  • Reusable patterns
  • Postmortems

Architecture debates, code reviews, design critiques, and why-do-we-do-it-this-way sessions.

  • Architecture debates
  • Code reviews
  • Design critiques
  • Why this way?

Mentoring, communities of practice, tech champions, and leadership development.

  • Mentoring
  • Communities of practice
  • Tech champions
  • Leadership

One talk. Five teams. A new standard.

We measure leverage, not attendance. Here is how a single 10x Talk can compound.

  1. Attend

    80

    A 40-minute deep dive on deployment pipelines fills the room and the call.

    $rsvp 80, recording shared, 212 replays

  2. Try

    15

    Within two weeks, fifteen people apply it to their own services and report back.

    $15 branches opened, 9 feedback threads

  3. Adopt

    5

    Five teams keep it. Their configs and gotchas get shared in the open.

    $5 teams, 5 pipeline configs merged

  4. Impact

    30%

    Deployment time drops by about a third on the teams that adopted it.

    $p50 deploy 42m -> 29m

  5. Pattern

    1

    The setup is packaged so the next team starts from working code, not a slide.

    $template deploy-pipeline@1.0 published

  6. Standard

    1

    The pattern becomes part of how we build. That is a 10x Factor outcome.

    $RFC-014 accepted into engineering standards

Monthly depth. Quarterly leverage.

Ten principles we build by

  1. 01

    Curiosity over certainty

    Ask why before accepting how.

  2. 02

    Depth over buzzwords

    Understand the technology. Do not just use it.

  3. 03

    Build over talk

    Ideas become valuable when we experiment.

  4. 04

    Share what you learn

    Knowledge kept private does not compound.

  5. 05

    Challenge respectfully

    Strong engineering needs disagreement.

  1. 06

    Automate the repeatable

    Engineers should eliminate toil.

  2. 07

    Measure impact, not activity

    Shipping more is not automatically better.

  3. 08

    Teach to multiply

    The best engineers make other engineers better.

  4. 09

    Fail safely, learn quickly

    Experiments should create learning.

  5. 10

    Leave it better

    Every system, process, and person should improve through our work.

Written by members

All stories

Put the Model Behind a Gate

AI should propose and deterministic systems should commit. Here is the architecture I'd hold every team to, the patterns that have held up, and what it changes for engineering leaders through 2028.

Nijel · Oct 2, 2026

communityleverageculture

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.

Nijel · Sep 29, 2026

Architecture Hour made us defend a boundary we had avoided for a year. We split the shared table the next sprint.
Jordan LeePlatform engineer, Architecture Hour host

Built by engineers. For engineers.

  • Propose a session
  • Start a sub-community
  • Publish your work
  • Run an experiment
  • Challenge a practice
Request accessAlready invited? Redeem your code