What the fuck are you afraid of?
Death? We’re all gonna die.
Bankruptcy? You can make it all back.
Shame? Everyone will forget in a week.
There is nothing to fear.
Most people quit too early.
Not because they’re not talented.
Not because the idea is bad.
But because nothing happens… at first.
0 users.
0 revenue.
0 validation.
Just you… and doubt.
But here’s the truth:
The first phase is always invisible.
You’re building skills.
You’re learning patterns.
You’re getting 1% better every day.
Then suddenly…
something clicks.
1 user → 10 → 100 → 1,000
1 video → viral
1 app → life-changing
People will call it “luck”.
But they didn’t see the boring days.
So if you're in the quiet phase right now:
Keep shipping.
Keep posting.
Keep building.
Because momentum doesn’t announce itself.
It just shows up one day.
And changes everything 💪
Mixed feelings working in Japan,
Spending there feels great and usually services are worth the money 😂
Although on average the salaries is lower than most developed countries,
stopped managing my own distribution.
handed it off to a team of agents.
they scout Reddit, schedule tweets, find reply opportunities, monitor trends. all 24/7.
I check in once a day, approve what I want, then get back to building.
this is how you ship multiple products as a solo founder.
My vibe-coded app just hit $1,000 in a single day.
Three months ago, I didn't know how to build an iOS app.
I still barely do.
People joke about vibe coding, saying that it writes slop code (as if junior-mid code is any better). Many people miss the point that some actually take it seriously and achieve pretty nice results.
I didn't have technical skills, but I always wanted to build things.
Not some random Notion templates as I did before (and still reached $30k/month xD), but real functional products written in code. Vibe coding literally gave me a cheat code that I can use in real life. I can turn all my ideas into functional products and make money from them.
It literally changed my life and now I can't stop.
For some AI is here to take their jobs, for some it's life changing opportunity and massive leverage.
@AbhiCodes15 None of it. Not everyone can code that much or having deep knowledge of algorithm or system.
Got hired by ITSM and Cloud infra related each once. B2B IT service still have lots of room to grow.
@StevenCravotta So true …it’s life and death depending on how we marketing the app.
I’m thinking of the best way for SaaS is to create a waitlist page first
and start marketing on day one.
The app space is saturated is a complete myth.
95% of apps have no idea about distribution.
The barrier to entry to BUILD apps has gone down to zero.
But the barrier to MARKET apps is still high.
If you know how to create viral TikToks, you can dominate.
The building part is solved.
The marketing part is wide open.
CANCEL your weekend plans.
You NEED to:
• Learn Claude Code
• Learn Cowork (build 1-2 practical workflows)
• Set up Perplexity Computer/Perplexity Finance
• Optimise Cowork (plug-ins + skills)
• Set up OpenClaw
• Test Google AI products (Nano Banana 2, NotebookLM & more)
• Experiment with basic agentic solutions (Manus)
• Use AI to create a business plan/strategy/context files
• Build an AI second-brain database (Notion)
• Experiment with Notion Agents' *brand new*
• Learn basic automation tools (MCPs, Zapier, n8n)
• Learn prompt engineering - the better you can communicate with AI, the better your Outputs
• Read AI articles
• Dive into robotics
• Research AI stocks/ETFs/investment arbitrages
You have way too much to do...
📁 Vibe Coding
|
├ 📁 Mindset
| ├ 📁 You don't need to know how to code
| ├ 📁 You need to know what you want to build
| ├ 📁 Think in outcomes, not syntax
| └ 📁 Ship first. Understand later.
|
├ 📁 Stack (pick one, don't overthink)
| ├ 📁 Cursor — for building full apps
| ├ 📁 v0 — for UI fast
| ├ 📁 Replit — for no setup
| └ 📁 Claude — for when you're stuck
|
├ 📁 The Loop (this is literally all of it)
| ├ 📁 Describe what you want in plain english
| ├ 📁 Paste the result
| ├ 📁 See what broke
| ├ 📁 Describe the fix in plain english
| └ 📁 Repeat until it works
|
├ 📁 Prompting That Actually Works
| ├ 📁 Be specific about the outcome, not the method
| ├ 📁 Include what stack you're using
| ├ 📁 Paste the error — don't summarize it
| ├ 📁 "Make it look like X" beats "make it beautiful"
| └ 📁 One change per prompt. Always.
|
├ 📁 When You're Stuck
| ├ 📁 Paste the full error, not just vibes
| ├ 📁 Ask "why did this break" before "fix this"
| ├ 📁 Start a fresh chat with fresh context
| ├ 📁 Revert to last working version
| └ 📁 Google exists. Use it.
|
└ 📁 The Truth About Shipping
├ 📁 Your MVP will be ugly. Ship it anyway.
├ 📁 Nobody cares about code quality at zero users
├ 📁 Feedback > perfection
├ 📁 Done > perfect
└ 📁 The builder who ships beats the one who waits