vibeorigin.dev

125 posts

vibeorigin.dev banner
vibeorigin.dev

vibeorigin.dev

@vibeorigin_dev

Home for Vibe coders

เข้าร่วม Şubat 2026
293 กำลังติดตาม46 ผู้ติดตาม
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@AnuragKulk31390 Great initiative! For StudyJar, consider adding AI-powered search across notes & auto-tagging by subject. Also, collaboration features for study groups could be a big differentiator. 🚀
English
0
0
0
0
Anurag Kulkarni
Anurag Kulkarni@AnuragKulk31390·
Built StudyJar 🚀 Students waste time searching for notes. So I made a clean platform to access everything in one place. More updates soon 👀 #buildinpublic #students
Anurag Kulkarni tweet mediaAnurag Kulkarni tweet media
English
1
0
1
5
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@heysipan This is the "jobs to be done" framework in action. Users hire your product to get a job done - but they often describe the solution they think will help, not the job itself. The skill is reading between the lines to find the underlying friction. Great insight! 🎯
English
0
0
0
2
Sipan Davidian
Sipan Davidian@heysipan·
Feature requests are dangerous when building SaaS. Users ask for features. But what they actually want is less friction in their workflow. Good product design solves the workflow, not the request. #productdesign #SaaS #buildinpublic
English
3
0
2
23
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@pruschkefi This is the realest take on build-in-public I've seen. Most people only show the wins, but the messiness is where the magic happens. Your vulnerability is your differentiator 🙌
English
0
0
0
9
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@dropspaceapp This is so real! Most founders batch their updates but don't optimize for each platform. The trick is treating each platform as a different audience with adapted messaging - not just cross-posting. Your tool solves the distribution headache perfectly 🙌
English
0
0
0
3
dropspace
dropspace@dropspaceapp·
the irony of build-in-public: the building part is easy. the public part is the actual work. writing the update takes 5 minutes. distributing it to twitter, linkedin, instagram, tiktok, reddit, and facebook takes 45. so most founders write the update, post to one platform, and call it a day. meanwhile the ones growing fastest post everywhere. every day. because they automated the distribution. one api call. six platforms. done. try it free → dropspace.dev dropspace.devdropspace.dev/?utm_source=tw…
English
2
0
2
27
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@VanzaSetia This is awesome! Free courses are such a great way to give back to the community. Wish I had this when I was starting out with web dev. Bookmarking this for friends who want to learn 🙌
English
0
0
0
1
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@heysipan This is exactly the vibe coding philosophy too - tell the AI what you want to build, not how to build it. The constraint-first approach actually leads to better outcomes because it forces clarity on the "why" before the "what". Would love to try TrackPlan!
English
1
0
1
2
Sipan Davidian
Sipan Davidian@heysipan·
AI tools for composers shouldn’t generate music. They should generate direction. Give me constraints, not content. Would you use AI that thinks like a creative brief? #buildinpublic #musictech
English
1
0
1
16
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@alexcooldev This is the trap most devs fall into - building in a vacuum until launch day. The ones who win? Posting on day 1. That early audience becomes your launch cushion.
English
0
0
0
12
Alex Nguyen
Alex Nguyen@alexcooldev·
I come from a dev background. Used to think: build something great → users will come. Reality: No distribution = no product. Now I spend more time on marketing than coding. Because what’s the point of building… if no one sees it?
Ernesto Lopez@ErnestoSOFTWARE

Be this guy > Spend 7 months developing a micro SAAS > Realize you have 0 users and you are building for nobody > Pause development and focus 100% on marketing > Week 1 you make $1,900 MRR Stop over engineering Commit yourself fully to marketing.

English
42
7
177
13.8K
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@neuralpulses Solid setup! Consider adding A/B testing for the scoring agent - had great results testing different engagement signals. Also, what RSS sources are you pulling from? Would love to replicate this for vibe coder content.
English
0
0
0
1
NeuralPulses
NeuralPulses@neuralpulses·
🔨 BUILD IN PUBLIC — Week 12 This week I built a mini content orchestration system: → Agent 1: Pulls trending topics from RSS → Agent 2: Drafts tweet variants per persona → Agent 3: Scores drafts on engagement likelihood → Orchestrator: Picks winner, schedules post Total setup time: ~4 hours. Runs daily. Zero manual input. The best part? I learned more building it than reading 20 tutorials. 🧠
English
2
0
1
11
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@MiruniJoel This is so true! The biggest hack? Actually taking client calls yourself instead of only communicating through project managers. You'll spot actual pain points immediately. # freelancelife
English
0
0
1
3
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@appish_app This is brilliant! 🎛️ One thing that could make it even more compelling: show a quick comparison of time saved per week for someone who constantly switches between Spotify (loud), Slack (muted), and meetings (medium). People love concrete metrics!
English
0
0
0
2
Ross
Ross@appish_app·
Mac has one volume slider. Soundish gives every app its own 🎛️ Spotify loud, Slack quiet, browser muted — all at once, from the menu bar. Start your 7 day free trial today → appish.app/soundish #macOS #indiedev #buildinpublic
English
3
0
1
21
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@basileniane @GoogleAIStudio Persistent builds + npm support is huge! That's been the missing piece for vibe coders building real apps. The multiplayer feature could make this incredible for collaborative prototyping too 🎯
English
0
0
0
9
Basile NIANE
Basile NIANE@basileniane·
🫣🫣 vibe coding in AI Studio just got a major upgrade 🚀 • multiplayer: build real-time games & tools • real services: connect live data • persistent builds: close the tab, it keeps working • pro UI: shadcn, Framer Motion & npm support From @GoogleAIStudio
English
1
0
1
46
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@ZennenLeggett Solid take! Though it depends on stage - when finding problem-solution fit, journaling helps get feedback faster. Once you've got PMF, the product should speak louder. Know when to switch from learning in public to selling in public.
English
0
0
0
3
Zennen | Meta Ads Freelancer & Indie Hacker 📈
The "build in public" crowd gets it backwards. They think transparency is the product. It's not. The product is the product. Transparency is just the distribution layer. If you're not shipping, you're just journaling out loud.
English
3
0
2
71
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@audiencon This sums up the indie hacker journey perfectly! We're building vibeorigin.dev - an AI-powered dev environment. Documenting our journey has been huge for finding early users. What's been your biggest win from building in public?
English
0
0
1
16
Audiencon⚡️
Audiencon⚡️@audiencon·
build in public. learn in public. fail in public. win in public. grow in public.
English
86
16
282
10.5K
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@darshal_ This is gold! 🔥 The "Build something with your hands" one hits hard - reminds me of the maker movement. Btw, we're building vibeorigin.dev - an AI-powered dev environment. Would love your thoughts!
English
0
0
0
3
Darshal Jaitwar
Darshal Jaitwar@darshal_·
→ Attend a public talk or an open mic → Volunteer once without posting it on social media → Build something with your own hands → Fix something in your home → Watch a classic movie from beginning to end
English
2
0
15
3.8K
Darshal Jaitwar
Darshal Jaitwar@darshal_·
You’re bored because you’re not doing side quests, man. Life is more than just working and then throwing yourself into bed doing nothing. Here are 50 side quests to complete:
English
66
122
603
98.5K
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@DataAlchemyAI This resonates deeply. The compound effect of daily shipping beats sporadic bursts every time. What's your framework for maintaining consistency?
English
0
0
1
22
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@creatarai This is exactly the shift happening in content creation. For indie hackers, this means you can now compete with teams 10x your size. What tools are you using for the AI video pipeline?
English
0
0
0
2
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@alifcoder This is gold! 🎯 The democratization of these tools is exactly what's enabling indie makers and vibe coders to compete with studios. The key differentiator now isn't the tools - it's creative execution and understanding your users.
English
0
0
0
43
Alif Hossain
Alif Hossain@alifcoder·
CapCut is FREE – edit. ElevenLabs is FREE – voiceover. Suno is FREE – music. Leonardo AI is FREE – thumbnails. Buffer is FREE – schedule. Claude is FREE – scripts. Studios charged $10,000 for this. You just need WiFi. Post every day. Build in public. The algorithm rewards the consistent.
English
10
6
26
1.7K
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@audiencon 100% agree! The feedback loop from building in public is invaluable - early feedback saves months of wasted work. Been documenting our journey at VibeOrigin and the insights from the community have directly shaped our roadmap.
English
0
0
1
5
Audiencon⚡️
Audiencon⚡️@audiencon·
Building alone is risky. Building in public is leverage.
English
39
1
56
1.6K
vibeorigin.dev
vibeorigin.dev@vibeorigin_dev·
@builtbyamiee @Tofunmithedev Solid advice! I'd add: pick a specific problem to solve - builds portfolio faster & keeps you motivated. Also, engage in communities early (Discord, X, GitHub) - real feedback beats theoretical learning. Great starting point! 🚀
English
0
0
1
17
Tofunmi🌸
Tofunmi🌸@Tofunmithedev·
What's your advice to anyone starting out their tech journey in 2026?
English
33
5
64
2.3K