Launch content
Launch for learning, not scale. One flagship event, one call to action.
The sequence below is in posting order (Brand & Community Plan §09: identity → credibility → announce → run). Each block says which channels it runs on. Fill [DATE], [TIME], and [VENUE] once Build Night #1 is set — they're the only brackets.
01 — The sequence
Launch announcement760 charsAll channels, Day 1. Mat's personal profiles first, then the community Page/Group/IG/X/TikTok within the same hour. Pair with shared/post-square-1080.png.
I'm building a community for people who want to move beyond consuming information and start doing the work: learning, practicing, building, sharing, and connecting. It's called The Work Behind the Luck. People may call the outcome luck. We focus on the work behind it. It is a practical community for learning, building, and creating opportunity. I host weekly Build Nights in person in the Philippines. Bring something you want to learn, build, or improve. Leave with progress and a next step. If you are an IT student, a developer, a career changer, a creator, or a business owner who is tired of watching and wants to build, this is for you. Beginners welcome. Everyone participates. Reserve a seat at the next Build Night → workbehindtheluck.com — Mat
Founder introduction886 charsMat's personal channels, Day 1 or 2. Crosspost a shortened version to the community Page. Pair with a casual founder photo.
Quick introduction, since a lot of you are new here. 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. I also have ADHD and a graveyard of unfinished side projects, so I know what it feels like to watch every tutorial and still not have a thing to show. This community is partly how I make myself finish things. The Work Behind the Luck is the room I wished existed: bring something real, learn one useful thing, work on it with help, and leave with a next step. I host it weekly, in person, in the Philippines. I will post what I learn and what I build here, including the parts that did not work. If you want to build alongside, reserve a seat at the next Build Night → workbehindtheluck.com
What is The Work Behind the Luck?888 charsCommunity channels, Day 2 to 3. Pair with shared/post-portrait-1080x1350.png or instagram/carousel-cover-1080x1350.png (one pillar per slide).
What is The Work Behind the Luck? A practical community for learning, building, and creating opportunity. In plain terms: I host weekly Build Nights in person in the Philippines. You bring whatever you are working on, get help in the room, and leave with a next step. Five pillars run through everything: Learn. Practice. Build. Share. Connect. If an activity does not help members do at least one of those, it probably does not belong here. Who it is for: IT students, developers, early-career professionals, career changers, creators, founders, and local business owners who want to use AI and other practical tools to get better and build useful things. What it is not: an AI-news feed, a lecture series, or a room where people talk about building without building anything. No promises. The work improves readiness. Reserve a seat at the next Build Night → workbehindtheluck.com
Community mission post827 charsCommunity channels, Day 3 to 4. Pair with shared/post-square-1080.png.
The community's mission, in one paragraph: Help people build the skills, projects, habits, confidence, visibility, and relationships that prepare them for opportunity, and help them create new opportunities for one another. The philosophy behind the name has four parts. Preparation: learn continuously, practice deliberately, improve judgment. Opportunity: share work, solve real problems, meet people, 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 does not wait. Members make opportunities for each other. You cannot control every opportunity. You can become ready for more of them, and create more chances for them to appear. That is the work behind the luck. Join the next Build Night ↓ link
Invitation to join753 charsAll channels, Day 4 to 5. Also send as a personal DM/email to the founding-member list. Pair with facebook/event-announcement-1200x630.png.
You do not need a finished idea or advanced technical skills. Bring one thing you want to learn or improve, and be willing to work on it. That is the whole entry requirement for Build Night. If you are a student or early in your career: bring the project you keep meaning to finish, or the portfolio that is still a blank page. If you run a business: bring a real operational problem. I will help you clarify it, explore responsible AI or software approaches, and find a realistic next step. If you have experience: 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. Seats are capped so everyone gets help. Reserve a seat at the next Build Night → workbehindtheluck.com
First discussion question457 charsFacebook Group first, then X and IG as a question post. Day 5. Founder replies to every answer within 24 hours.
First question for the room: What is the one thing you want to finish, improve, or learn in the next 30 days? One line. Be specific. "Finish the portfolio site" beats "learn web dev." "Automate the weekly inventory sheet" beats "use AI for my business." Reply below and tag what kind of help you need: feedback, a pairing partner, a mentor, or just accountability. Then find one other reply you can help with. I will use these to plan the first lessons.
First educational post1053 charsMat's channels, Week 2 (credibility week). Crosspost to community Page and DEV.to. Pair with shared/post-portrait-1080x1350.png.
AI does not replace judgment. It raises the value of it. Here is what I mean, from a real session this week. I asked an AI model to write a function that deduplicates customer records. It produced clean code in seconds. It also treated "Maria Santos" and "Maria Santos-Cruz" as the same person, and it dropped records with a missing email instead of flagging them. Nothing in the code was wrong. The judgment was missing. The model does not know that in this business a missing email means "walk-in customer," not "bad data." You do. That knowledge is the part you are paid for. So the workflow that actually works: 1. Write down what "correct" means before you prompt. Edge cases included. 2. Let the model draft. 3. Read every line as if a junior wrote it. Because one did. 4. Test the edge cases from step 1. 5. Keep the parts you understand. Rewrite the parts you do not. AI can accelerate the work. You still own the judgment. That is not a limitation. That is the job. Build Night is where you practice exactly this. Join the next one ↓ link
First project / build post1100 charsMat's channels + DEV.to, Week 2 to 3. Screenshot of the real site, unfinished parts visible. Pair with facebook/project-showcase-1080x1080.png.
Build in public, update 1: the community site. I am building workbehindtheluck.com in the open because that is what I will ask members to do. Stack: Next.js (App Router), Tailwind, Prisma on Neon Postgres, tRPC, Clerk for sign-in, Resend for email. Deployed on Vercel. What works today: the Start Here page, the event list pulled from a Google Calendar, and RSVP with a seat cap so Build Night does not overbook. What does not work yet: member profiles are half-built, the blog has two posts and one of them is a test, and the photo consent flow is still a paper form. The waitlist logic took three tries and I am still not sure it is right. What I learned: the calendar sync was the easy part. Deciding what a "member" is was the hard part, and I changed the data model twice. I should have written that down before I opened the editor. Next step: finish member profiles so people can list "I am learning ___ / I can help with ___" on the site, not just in the group. If you want to see it come together or push on what is wrong, reserve a seat at the next Build Night → workbehindtheluck.com
First event announcement (Build Night #1)632 charsAll channels, Week 3. Replace [DATE] [TIME] [VENUE] [LESSON TITLE]. Pair with facebook/event-announcement-1200x630.png; story version on shared/story-1080x1920.png.
Build Night #1. [DATE], [TIME] [VENUE], [CITY] Capacity: 15 seats Bring something you want to learn, build, improve, or launch. Leave with meaningful progress, useful feedback, and a clear next step. What to bring: a laptop if you have one (pairing is fine if not), one thing you want to work on, and the willingness to name a next step before you leave. Beginners welcome. Everyone participates. Seats are capped at 15 so everyone gets real help. RSVP on the site and you will get a confirmation and a reminder. If it fills, join the waitlist and seats are released as they open. Reserve a seat → workbehindtheluck.com/events
Welcome video script (TikTok / Instagram, 30 to 45s)943 charsType-first: record as talking head or screen-record the site with the on-screen text. No B-roll needed. 30 to 45 seconds. Use PINNED.tiktok caption.
[on-screen text: People call it luck.] People call it luck when someone gets the job, ships the thing, lands the client. [on-screen text: This is the work behind it.] They did not see the learning, the practice, the rough drafts, the people who helped. [on-screen text: The Work Behind the Luck] This is The Work Behind the Luck. A practical community for learning, building, and creating opportunity. [on-screen text: Build Night. In person. Philippines.] We meet in person for weekly Build Nights in the Philippines. Not a stream. You come and do the work in the room. [on-screen text: Bring your project. Leave with a next step.] Bring your project, work on it with help in the room, and leave with a next step. [on-screen text: Beginners welcome. Everyone participates.] You do not need a finished idea. You need one thing you want to improve. [on-screen text: workbehindtheluck.com] Seats are capped. Link is in the bio. Come build.
02 — Introductory DEV.to article
#career #beginners #webdev #programming
Your degree got you the interview. This is why it isn't getting you the job.
I'm in a lot of Facebook groups. Dev groups, IT groups, job groups, here in the Philippines. And there's one post I see more than any other. It goes like this: > BSIT graduate. Certificates in [list]. Looking for work. Willing to learn. Please DM. Hundreds of them. Good people. Nobody replies. If that's you, this isn't a post telling you off. Nobody told you this part, and it isn't your fault that they didn't. So here it is. ## What the degree actually proved Your degree proves you can learn. That's real, and it's why you got the interview. But the person hiring isn't asking "can this person learn?" They're asking "can this person do the job on Monday?" And for that, they want evidence of **experience** — and they will take a small amount of real experience over a long list of credentials, every time. "But I'm a fresh grad, how am I supposed to have experience?" This is the part nobody explained. Experience doesn't mean years. It means something much more specific. ## What "experience" actually means Experience means you've been inside a project at the moment it stopped working because of something *you* did — and you got it working again. That's it. That's the thing. Not the years. Not the stack. The moment. Somebody who has had that moment a few times is someone I can put on a real codebase. Someone who hasn't is someone I have to protect the codebase from, no matter how good their grades were. It's not personal. It's the job. ## Why tutorials don't give you that Your portfolio probably has projects in it. A todo app. An e-commerce clone. A weather dashboard. You followed the tutorial, it worked, you pushed it to GitHub. Here's the problem: in a tutorial, every problem is already solved. Someone chose the data model so it wouldn't need to change. They picked the examples so nothing surprising would happen. You typed along and it worked, and at no point did you have to *think* — because the thinking was done before you arrived. That's not a criticism of you. That's what tutorials are for. They're training wheels. But nobody takes the training wheels off, and then you're 24 with a degree and six projects that all prove the same thing: you can follow instructions. Companies already know you can follow instructions. That's what the degree said. ## The day you become hireable Let me describe it, because I think most graduates have never been allowed to have it. You're building something real. Not a clone — something uncommon, where nobody has written the tutorial. You're about halfway through. And you realise the data model is wrong. A thing you thought was one-to-one is actually one-to-many. Or you need a field you didn't plan for. Or the whole shape of one table has to change. So you write the migration. You change the schema. You run it. And half the site stops working. Pages that have nothing to do with the thing you changed are throwing errors. Something that worked yesterday doesn't. You don't know why. There's no video to rewind. You're going to spend the next two days reading your own code, reading error messages properly for the first time, learning what a foreign key actually does when you delete the thing it points at, and figuring out exactly what you did wrong. When you come out the other side — and you will — you have something no tutorial can give you. You've been in the hard middle of a project and you got yourself out. That's the day. That's the experience they mean. Everything after it is easier. ## What a project like that looks like You don't need something huge. You need something with a few specific properties: 1. **Uncommon.** Pick a domain where you can't find a step-by-step. A scheduling tool for your aunt's salon. An inventory system for a sari-sari store. A tracker for something you actually care about. If the tutorial exists, pick something else. 2. **Real data.** Not three sample rows. Enough that when you change the shape of it, it hurts a little. 3. **A mid-project change.** Don't plan it perfectly. You can't. Part way through, you will need to change the data model — let that happen. Write the migration. Break it. Fix it. 4. **The boring parts.** Login. Deployment. Error states. A README. The last 10% is where most portfolios quietly stop, and it's exactly the 10% an employer checks. 5. **One real user.** Your aunt. The store. You, for a month. Somebody who will tell you it's broken. And then: **finish it.** Smaller and finishable beats big and abandoned. Cut scope until it can be done by Thursday. Imperfect ships; broken doesn't. ## What to put on the application instead Stop leading with the certificate list. Lead with: - **The link.** It's deployed. It works. Anyone can click it. - **The README.** What it is, what it's built with, how to run it. - **Two paragraphs about what broke.** What you changed, what fell over, how you found it, what you'd do differently. This is the part that gets you the interview and then gets you the job. It's the evidence that you've had the day. An honest write-up of one hard thing you fixed is worth more than ten tutorial repos. I promise you that from the hiring side of the table. ## You don't have to do this alone That hard middle is also the part where most people quit, because at 11pm with half your site broken and no one to ask, it feels like proof you're not cut out for this. It isn't. It's the job. It just helps enormously to have someone in the room who's been there. That's why I'm starting **The Work Behind the Luck** — a practical community for learning, building, and creating opportunity, with weekly **Build Nights**, in person, in the Philippines. You bring the project and build it with people around who can unblock you when it breaks, then leave with a next step. In person on purpose: on a video call, most people end up watching someone else do the work. In the room, you do it. It's free. It's not a course, and there's nothing to buy. If you've got a half-built project and a job search that's gone quiet, you're exactly who it's for. **Reserve a seat at the next Build Night → [theworkbehindtheluck.com](https://theworkbehindtheluck.com/events)** And if you're further along — if you've had the day I described, more than once — your experience belongs in the room too: [theworkbehindtheluck.com/get-involved](https://theworkbehindtheluck.com/get-involved). People may call the outcome luck. We focus on the work behind it. — Mat *Mat Mozer leads a platform engineering team, builds products on the side, and interviews a lot of engineers. He founded The Work Behind the Luck to close the gap between the degree and the job.*
Title76 chars
Your degree got you the interview. This is why it isn't getting you the job.
Tags38/120
career, beginners, webdev, programming
Cover alt text103 chars
A laptop with a failing migration in the terminal, a notebook with a crossed-out data model next to it.
DEV.to is the original for this article: leave canonical_url empty in the front matter. If it is later republished on theworkbehindtheluck.com/blog, that page should set its canonical to the DEV.to URL, not the other way around. Only set canonical_url on DEV.to when cross-posting something the site published first.