Build alongside people
Bring a small problem or a skill. Find common ground, agree on a manageable scope, and learn through useful work.
Phase one / The community
Different paths.
Something to build together.
For developers who want to make useful things, share what they know, and find their next step. Your current job title—or the absence of one—doesn't define what you can contribute.
What we want to make possible
A place to contribute and ask for help.
Share what you know
Explain a concept, review a project, or talk through an engineering decision. You can learn and help at the same time.
Prepare for what comes next
Practise explaining your work, exchange thoughtful feedback, and share relevant opportunities when you find them.
These are the activities we want to grow together. This is an early community, not a recruitment service or a promise of paid work.
How we show up
High standards.
Room to be human.
- Respect people’s circumstances. Different schedules, experience levels, and career gaps belong here.
- Ask clearly. Help thoughtfully. Share enough context for others to help. Feedback should improve the work without belittling the person.
- Make commitments you can keep. Agree on time, ownership, credit, and payment before a project starts.
- Keep private things private. Share your own work and information you have permission to share.
Getting started
Participate through GitHub.
Add the failure-company topic to a public repository and introduce your work in its README. Ask for help through issues, contribute through pull requests, and share progress on X or LinkedIn with #FailureCompany. There is no separate chat group to join.
A simple introduction
- What have you been learning or working on?
- What kind of work would you like to do next?
- What could you help someone with?
- What would you appreciate help with?
- How much time can you realistically give?
Share only what you are comfortable sharing. You do not need to explain personal circumstances or post your résumé publicly.