I remember the exact moment it happened.
I was sitting in my room, headphones on, working on a feature for a client. The Figma mockups were open, Xcode was running, and I felt like I was finally getting somewhere. I was 19, doing freelance iOS development, making money without a degree. Life was good.
Then I got the message.
"Hey, we're going in a different direction. We won't be needing your services anymore. Thanks for everything."
That was it. No warning. No two-week notice. No severance package. Just a Telegram message at 11 PM on a Tuesday.
The First 48 Hours Were the Worst
I won't lie. The first two days, I didn't do anything productive. I scrolled through job boards, stared at my bank account, and questioned every life decision that led me here.
The freelance dream they sell you online? "Be your own boss, work from anywhere, make six figures." Nobody tells you about the part where your only client drops you overnight and suddenly you have zero income.
I had about two months of savings. That was my runway.
What Actually Happened (Not the Instagram Version)
Here's what most "I got laid off" stories look like on social media: "I got fired, started a side project, and now I make $50K/month."
That's not my story. My story is messier and probably more relatable.
Week 1: Panic. Applied to everything. Freelance gigs on Upwork, full-time jobs I wasn't qualified for, random Discord servers looking for developers.
Week 2: Got ghosted by everyone. Started questioning if my skills were even real. Maybe the client fired me because I was bad?
Week 3: Finally got a small gig. Fixed a bug in someone's React Native app. Made $200. It wasn't much, but it proved I wasn't completely useless.
Week 4: Started building something for myself instead of waiting for someone to hire me.
The 5 Things That Actually Helped
1. I Stopped Applying and Started Building
This sounds backward, but hear me out. When you're applying to jobs while panicking, you make terrible decisions. You apply for roles you don't want. You undercharge. You accept bad terms.
Instead, I spent two weeks building a portfolio project. A real app, not a to-do list. Something that showed I could ship a complete product. It was a finance tracker built with SwiftUI and SwiftData.
That single project led to three conversations with potential clients. Two of them turned into paid work.
2. I Created a "Skills Inventory"
I sat down and wrote every single thing I could do. Not just "Swift" and "SwiftUI." I mean everything:
- REST API integration
- Custom UI components
- App Store submission process
- Figma to code translation
- Git workflow management
- Basic CI/CD setup
Turns out I knew way more than I thought. The problem was that I'd been defining myself by one client's opinion of me. When they dropped me, I felt like I had nothing. But I had skills. They were just hidden under panic.
3. I Set a "Minimum Viable Income"
Instead of trying to replace my old income immediately, I calculated the absolute minimum I needed to survive each month. Rent, food, phone bill. That was about 30,000 rubles (around $300).
This changed everything. Suddenly I didn't need to land a huge contract. I needed two or three small gigs. That's much more achievable when you're starting over.
4. I Told People I Was Available
This was the hardest part because it felt like admitting failure. But I posted in developer communities, told friends, and updated my profiles everywhere.
Know what happened? People responded. A friend from an old hackathon needed help with a SwiftUI project. Someone in a Telegram group was looking for code review help. My old college classmate knew a startup that needed a part-time developer.
The opportunities were always there. I just never asked because I was "already employed."
5. I Started Sharing What I Know
I began writing articles. Technical stuff, career stuff, things I learned from code reviews. Nothing went viral. But it did something more important: it showed potential clients and employers that I knew my stuff.
One of my Dev.to articles got noticed by someone who later became a client. They told me, "I read your article about SwiftUI architecture and figured you knew what you were doing."
Content is a resume that works while you sleep.
The Uncomfortable Truth About Freelancing at 19
Nobody prepares you for this part. When you're young and freelancing, you don't have:
- A professional network built over decades
- Emergency savings from years of work
- A track record that speaks for itself
- Confidence that comes from surviving this before
You're basically learning to swim by jumping in the deep end. And sometimes you swallow water.
But here's what you DO have at 19 that older developers don't:
- Time to recover from mistakes
- Low financial obligations (usually)
- Energy to grind when needed
- The ability to learn new stuff fast because your brain is still in "learning mode"
- Nothing to lose, really
What I'd Tell 18-Year-Old Me
If I could go back and give myself advice before that first freelance gig, here's what I'd say:
Never rely on a single client. Even if they're paying well. Even if they promise long-term work. Always have a backup plan or at least be building relationships with other potential clients.
Save more than you think you need. I had two months of savings and it was barely enough. Aim for four to six months. Yes, even at 19.
Build in public. Share your projects, write about what you learn, post your code. The visibility compounds over time and creates opportunities you can't predict.
Don't tie your identity to your job. I'm not "the guy who builds apps for Client X." I'm a developer who solves problems. Clients come and go. Skills stay.
Get comfortable with rejection. In my first month of looking for new work, I got ignored or rejected maybe 40 times. Each one stung a little less. By the end, I was treating it like a numbers game.
Where I Am Now
I'm still freelancing. I'm still 19. But things are different.
I have multiple income streams now. Client work, digital products, content. If one drops off, I don't starve. I learned that lesson the hard way.
I also stopped pretending everything is fine on social media. The tech industry has this weird culture where everyone acts like they're crushing it 24/7. They're not. Everyone gets knocked down. The difference is what you do after.
Getting laid off at 19 was the worst thing that happened to me that year. It was also the best thing, because it forced me to build a foundation instead of just standing on someone else's floor.
Quick Recap
If you just got laid off or lost a client:
- Give yourself 48 hours to feel bad. Then start moving.
- Build something. A portfolio piece, a side project, anything that proves you can ship.
- Calculate your minimum viable income. It's probably lower than you think.
- Tell people you're available. Swallow the pride.
- Start sharing what you know. Content creates opportunities.
The market doesn't care about your feelings. But it does reward people who keep showing up.
If you found this useful, I share more stuff like this on Telegram and sell developer toolkits on Boosty.
Top comments (0)