About
Luck can influence outcomes. Readiness is built through repeated action.
I'm Mat. I lead a platform engineering team, build products on the side, and I interview a lot of engineers. Most people I turn down aren't short on talent — they're short on finished work they can show. That's what this community is for.
The Work Behind the Luck exists because the outcomes people call luck are usually preceded by learning, practice, projects, relationships, and follow-through. This community is where that work happens — together, in person, in the Philippines.
The philosophy of luck
You cannot control every opportunity. You can become ready for more of them — and create more chances for them to appear.
Preparation
Learn continuously, practice deliberately, improve judgment, and become more capable.
Opportunity
Share work, solve real problems, meet people, collaborate, and become easier to find.
Chance
Outcomes are never fully controllable; the goal is to create more chances and be ready for more of them.
Contribution
The strongest community doesn't wait for doors to open; members open doors for one another.
Values
01Useful action. Learning matters when it changes what someone can do. Another video is not always progress. Discussions should end in a decision, an experiment, or a next action.
02Build real things. Projects create experience. Experience creates competence. Competence creates opportunity.
03Craft and judgment. AI can accelerate work; people remain responsible for quality, ethics, privacy, accuracy, and consequences. AI should make you more capable, not automate thinking away.
04Finish and share. Small completed work creates more opportunity than private perfection.
05Generosity with standards. Help freely, give honest feedback, respect people's time. Someone who knows 20% can still help someone who knows 5%.
06Consistency over hype. Repeatable practice beats shortcuts, promises, and trend chasing. Small amounts of continuous work beat bursts of intensity.
07Evidence over image. Show projects, progress, lessons, and outcomes — not inflated claims. The industry used to reward patience; now it rewards evidence.
08Access and dignity. Beginner friendly, not standard free. Welcome beginners without lowering the expectation that everyone participates and improves.
09Curiosity. Questions are encouraged. Not knowing something is the beginning of learning, not something embarrassing.
10Accountability. Say what you are going to do before the next meetup, then attempt it. The next meetup starts by asking.
What it is
A place to learn by doing, receive feedback, and make measurable progress.
A bridge between education, real projects, careers, businesses, and local relationships.
A network where members teach, collaborate, mentor, hire, recommend, and refer.
What we expect
Bring one thing you want to learn, build, improve, or launch.
Do the work in the room — this isn't a lecture with networking at the end.
Give honest feedback and help freely when you can.
Name a next step before you leave, and follow through.
What it is not
Not a get-rich-quick, manifestation, gambling, or “secret to success” brand.
Not an AI-news feed, passive lecture series, or discussion group with no output.
Not a livestream. Sessions are in person, because people on a call end up watching other people do the work. Online is where members keep talking between sessions.
Not a programming-only group — developers matter, but the room is wider than that.
Not a sales funnel. Any future paid program must stand on its own and must not change the culture.
Not “ask Mat everything.” Mat mentors and guides; the room becomes peer-supported or it doesn't scale.
Not a replacement for professional education, legal advice, or guaranteed employment.
Offer something
If you can help someone avoid a mistake, see a better path, or finish a useful piece of work, your experience belongs in the room.
Ways to contribute
Tell us about yourself
Writing
Canonical on dev.to →Learn. Practice. Build. Share. Connect.
Join the community