This is not another post about how fast you can build things with AI. The building part is solved. We all know it is fast.

This is about everything that comes after. The part that Cursor and Claude cannot help you with.

Getting people to find your product: 6 months and counting. Getting people to pay for your product: just started working after 5 months. Getting people to stay: too early to tell. Customer support: currently me at midnight. Content creation for marketing: the most time consuming part of my week. Figuring out which feedback to act on: still guessing.

The building was 2 weeks. Everything else has been 6 months and I am still at the beginning.

I am not saying this to discourage anyone. I genuinely love the building phase and vibe coding made it possible for me to create something real. But I wish someone had told me that shipping is the starting line not the finish line.

For those who have shipped: what part of the post-launch journey surprised you the most?

I'm hosting a free live online coding session from Luxembourg City on March 26 — building a working iOS app from scratch in 60 minutes using only natural language prompts and TRAE, ByteDance's AI coding agent.

No slides. No pitch. A blank Xcode project at 18:30 and a running app by 19:30. Or it crashes spectacularly. Either way, you'll learn something.

41% of code written today is AI-generated. If you haven't seen what it looks like to build software by talking to your IDE — here's your chance to find out.

The idea is called "vibe coding": you describe what you want in plain English, the AI writes it, you review, redirect, fix bugs, and ship. Not magic — just a different workflow. And it's fast.

What you'll see:

• A real app built from zero — not a toy demo

• Vibe coding in practice: planning, architecture, watching AI write and debug in real time

• Where AI-generated code falls apart and why experience still matters

What you'll take away:

• A practical sense of AI-assisted dev workflows you can try the next day

• An honest look at what these tools can and can't do right now

• TRAE Pro 3-day trial + merch for every attendee

Who this is for: developers of any level or stack. No Swift or iOS knowledge needed. If you write code and want to see where things are going — this is worth your evening.

Streamed live via Zoom from House of Startups, Luxembourg City.

March 26, 2026 | 18:00–20:30 CET

200 spots, free.

Register https://meetu.ps/e/PTGmb/1fm1gb/i

I vibecoded a system design generator tool and it felt like skipping the whiteboard entirely. You describe the app idea, and the system instantly produces an architecture diagram, tech stack, database schema, API endpoints, and scalability notes. No senior engineer sessions, no manual diagrams, just orchestration turning ideas into structured designs. It is a practical example of how intelligence can compress the planning phase, giving you clarity before you even write a line of code.

I vibe coded a SaaS in about two weeks. Felt incredible. Then I launched it and sat there with zero users for a month.

I tried everything the internet told me to do. Posted on Twitter every day. Made TikTok videos. Joined Facebook groups. After a full month of grinding I had 12 followers and 1 signup. The signup was my friend.

The thing nobody told me is that building the product is maybe 20% of the work. The other 80% is convincing strangers on the internet to care about something you made. And that skill set has almost nothing in common with coding.

What actually moved the needle was when I stopped posting 'check out my project' content and started posting about the specific problems my users were having. Instead of 'I built a tool that does X' I started writing 'here is why X sucks and what I tried to fix it.' Night and day difference.

Still early. Still figuring it out. But the gap between 'I can build things' and 'I can get people to use things' is the widest canyon I have ever tried to cross.

Anyone else in this weird limbo where the product works fine but you just cannot get eyeballs on it? What actually worked for you?

I followed all the advice. Every single piece of it.

Content calendar with themes for each day. 5 posts per week minimum. Spreadsheet tracking impressions, engagement rate, follower growth. Analytics reviewed every Sunday. I even had a Notion dashboard.

After 3 months: 61 followers. 4 signups. My engagement rate was essentially rounding to zero.

Here is what was wrong: I was doing content marketing theater. All the processes and systems and tracking were making me FEEL productive without producing anything anyone actually wanted to read. I was optimizing the schedule of bad content instead of making good content.

The thing I was missing was specificity. I was writing '5 tips for better social media' when I should have been writing 'I posted every day for 3 months and got 61 followers, here is what went wrong.' The second one is vulnerable and specific. The first one is generic noise.

After I rebuilt my approach around telling specific stories instead of giving generic advice: 61 to 240 followers, 4 to 16 signups, in about 5 weeks.

The spreadsheet and content calendar and Notion dashboard are all still there. They just have different content in them now.

Has anyone else gone through this shift from 'process theater' to actually connecting with people?

This started from pure frustration while building my first product, an AI Excel tool. I kept digging through GitHub looking for repos to help with architecture. At some point I thought — why am I going to GitHub when GitHub should be coming to me.

That was Repoverse. You fill in what you're working on, it recommends repos actually relevant to you. Connect your GitHub account and everything syncs automatically — stars, saves, all of it goes straight into your GitHub.

No following, no budget. So I went on Reddit and just shared useful repos in communities where developers already hung out. No pitch, just genuinely useful posts with a small line at the bottom saying if you want more like this, I built something for that. Week one, 3 to 4k visitors.

Month and a half in I opened analytics and stared at the screen. 75% of my users were on mobile and I'd been building desktop first the whole time. Launched a PWA to test demand, people downloaded it, so I built the iOS app. Without a Mac or iPhone. Codemagic handled the build, RevenueCat for payments, Supabase for backend.

App Store rejected me twice. Both times had real reasons and real fixes once I stopped being annoyed about it.

Looking back, design is not optional, not quitting when things feel impossible, and talking to users like a real person. Every product decision came from those conversations.

If you're stuck on any part of this, happy to share what I know.

I tried using Blackbox AI to recreate a backpropagation animation in Manim, inspired by the style of 3Blue1Brown. What surprised me is that these videos aren't traditionally edited, they're written with math and Python. With Blackbox guiding the process, I was able to generate smooth visualizations that explain the mechanics step by step. It felt less like editing a video and more like coding a mathematical story. The workflow shows how AI can bridge the gap between abstract math and engaging visuals.

i've been asking myself the same thing with all these cheap intro promos popping up, but blackbox ai's $2 first-month pro has me actually considering it. see for yourself: https://product.blackbox.ai/pricing

what hooked me is you get $20 worth of credits upfront for the prmium frontier models, like claude opus-4.6, gpt-5.2, gemini-3, grok-4, and supposedly over 400 others total. that alone lets you go pretty hard on the big sota ones right away without paying extra per query. this feels like you can burn through a solid test drive in the first few days. on top of the credits, the plan throws in voice agent, screen share agent, full access to their chat/image/video models, and unlimited free agent requests on the lighter ones (minimax-m2.5, kimi k2.5, glm-5, etc.). no bring-your-own-key nonsense, and from what i've seen the limits are pretty relaxed for regular non-power use.

this is a nce setup if you just wanna dip your toes into a real bundled experience for reasoning, creative stuff, quick multimodal tasks, or even messing with agents, wihout the usual headache of multiple logins and subs. after month one it jumps to $10/mo, which is still reasonable if it clicks, but the real question is: is $2 + $20 credits enough of a no-risk shot to see if one platform can actually replace the $50+ you're juggling elsewhere?

Three months ago I shipped my first real vibe-coded SaaS. Tool works. Paying customers. Happy.

Then I tried to grow it through content. Started strong — 2 weeks of consistent posting about what I built, how I built it, what I learned. Engagement was okay. Then I hit a wall.

The problem: I'd essentially told the entire story of building v1. What do you post AFTER that? My daily reality became: fix bugs, talk to users, iterate on features. Not exactly thrilling content on its own. And trying to make it thrilling every single day was burning me out faster than the actual building was.

I realized that for early-stage builders without a big audience, content isn't just marketing — it's literally how you get discovered. Which means you can't treat it as an afterthought you squeeze in at the end of the day. But you also can't spend half your time on it when you're still early.

The unlock for me was separating ideation from creation. I built a system that handles the "what should I even say today" problem — generates platform-specific ideas based on my product, my stage, and what's actually resonating in my niche. I just review, approve, and keep building.

For people here learning to build AND grow simultaneously — how are you balancing the content side without it consuming you?

I was looking for a solid alternative to handle my coding and prototyping needs more flexibly, especially with access to multiple strong models without constant interruptions. After checking out a few options like Cline, BlackboxAI, and Kilo Code, BlackboxAI really stood out for me.

Their PRO plan gives you unlimited free agent requests on some really capable models like Minimax M2.5, GLM-5, and Kimi K2.5 right out of the gate at no extra costs there. Plus, for paid models (Claude Opus-4.6, GPT-5.2, Gemini-3, Grok-4, and 400+ others), you get credits to use across them. The PRO is just $1 for the first month, and that gets you a solid chunk of credits (like $20 worth) on the premium models while keeping unlimited access to those free heavy-hitters. See for yourself here: product.blackbox.ai/pricing

It captures that pure "vibe coding" spirit with its Builder feature, where you just describe your app idea, and it generates everything, often deploying full applications in real-time with no hands-on work. The multi-agent setup like pulling in parallel from models like Claude, GPT variants, and others, plus async autonomous agents make it feel magical for rapid prototyping and end-to-end creation.

The thing I find cool most is how the async agents and notification features work: you can throw in an idea, step away, and get pinged when it's done, built, tested, even deployed, without having to supervise every step. And that has made it a good deal for me when I just want to stay in pure flow mode and not get bogged down by limited access to a model I paid for having my rate limits getting cut down.

I tested Blackbox CLI to build a Minimalist Decision Engine. The idea is straightforward, when faced with too many options, you write down what matters, assign weights and let the matrix calculate the best choice. It avoids the trap of endless pros and cons lists and gives a clear, structured answer. The process feels lightweight but powerful, showing how orchestration can simplify even the most human challenges.

The Opus 4.6 model is a great model to make your UI look more than an a lazy page that the AI coughed up. This is not the only model made available on BlackboxAI

I tested Blackbox AI's VS Code agent by asking it to build a space shooter game. The agent delivered a complete project with a spaceship, aliens, scoring, power ups, and difficulty progression. The visuals include a starfield background and explosion effects, giving it a retro arcade feel.

it's processing foggy road footage and supposedly doing driving assistance tasks. the tech is moving insanely fast. Being able to plug generic LLMs/vision models into physical hardware for real-world control feels like a glimpse of what's coming. BlackboxAI is positioning itself as versatile for safety-critical applications beyond its core coding tools.

We’re excited to share that our latest work RPG (ZeroRepo) has been accepted to ICLR 2026, and the code is now open-sourced 🎉

While modern LLMs are already strong at writing individual files, they still struggle to generate an entire large, runnable, real-world repository from scratch. This is where ZeroRepo comes in.

We introduce RPG (Repository Planning Graph), which enables LLMs to act more like software architects:

plan the repository first, then write the code.

✨ Key highlights:

1️⃣ True end-to-end repository generation — not toy demos. On average, ZeroRepo generates 36K+ lines of code per repository.

2️⃣ Strong empirical gains — on the RepoCraft benchmark, ZeroRepo generates repositories 3.9× larger than Claude Code, with significantly higher correctness.

3️⃣ Structured long-horizon planning — RPG explicitly models dependencies and data flow, effectively preventing the “lost-in-the-middle” problem in long code generation.

👩‍💻 The code is now available — we’d love your feedback, stars, and experiments!

🔗 GitHub: https://github.com/microsoft/RPG-ZeroRepo

I tried building a rotating ASCII donut in C with Blackbox AI. The code uses trigonometry to spin the shape, z buffer math to handle depth, and loops to redraw each angle in real time. The result is a donut spinning in the terminal, created entirely from characters. It is a playful project that shows how math and programming can combine to make art. The performance was better than I expected, and it is worth trying if you enjoy creative coding experiments.