Back to Feed

Inclusion Isn’t Optional — It’s Strategic

Craft The Future
Author
May 16, 2025
1 min read

If your build culture doesn’t welcome others,
you’re not building community. You’re shipping into a vacuum.

Better tools come from better feedback.
Better feedback comes from more voices.
And more voices only show up when the space feels real, not just branded.


🧠 What To Do

  • Audit your docs, posts, and READMEs — drop gendered, ableist, or exclusionary language

  • Link out to one project by a builder from an underrepresented group

  • Don’t posture. Just be clear about the values behind what you ship

Inclusion isn’t a toggle. It’s how your stack listens back.


✏️ Builder Challenge

  1. Take one old post — a devlog, thread, or blog

  2. Rewrite it with inclusive tone, clearer context, and zero assumptions

  3. Then shout out one overlooked dev tool this week. Bonus if it’s built by someone outside your usual orbit

📖 Read: Staying in Tech When You're Marginalized


🛠 Want a second set of eyes?

Reply with your revised post or link drop — we’ll amplify a few that resonate.

Inclusive tools scale. Exclusive ones stall.

Build for everyone. Or build alone.

— /build