For the last two months, I’ve been exploring AI, LLMs, Tools, and everything, and I’m starting to use this knowledge to build incredibly more straightforward and FREE products.

And you know what? I’ve built one so far.

I have no coding experience or background (only charisma). So I barely found a VS code (tldr, coding workspace, tool to open my folders, check my code, and write it).

I’m really bad at it, but I did it. I spent 4 days, and to be precise, 2 hours a day, so I would say a full 10 hours to build the game.

Yes, I created a game. It's the first Belkins game.

52,872 lines of code

Super excited to share.

Vibe coding

Let me tell you, vibe coding is happening right now, big time. In short:

It’s a term popularized by Andrej Karpathy. The idea is that you:

• Speak or type a request like “Shrink the sidebar padding by half,” and your AI co-pilot updates the code automatically.

• Rarely check the diffs in detail. If you get an error, you feed it back to the AI with no comment, letting it fix itself.

• Rely on the “vibes”—the general direction—without micromanaging every line of code.

Yes, it’s a bit chaotic.

But for quick prototypes or weekend projects, it’s surprisingly productive (and fun!). The code sometimes bloats or goes weird, but hey—that’s vibe coding for you.

AI Coding

Another puzzle piece is AI coding—the overarching approach that allows non-developers (or developers who want more speed) or people like me to build functional software with minimal manual effort.

Now, I can build MVPs or mini-products that solve simple problems easily.

Tools like:

• OpenAI (GPT-based models)

• Anthropic Claude (3.5, 3.7 “Thinking” variants)

• Cursor or VS Code + AI plugins

…are accelerating the dev process beyond what we’ve ever seen. Instead of rummaging through Stack Overflow, you can:

1. Prompt the AI for a feature you need.

2. Accept (or refine) the code it writes.

3. Test quickly in a browser or local environment.

4. Iterate: Feed errors back to the AI until it “magically” resolves them.

Check this out: I’m coding 52,872 lines of code with no hands:

This video caught me listening to Nighwish. So here is Spotify, just in case.

And finally THE Game.

The Belkins Challenge

https://challenge.belkins.io

A browser-based interactive simulation that teaches best practices for scheduling qualified B2B appointments with challenging prospects.

You become me —Vlad Podoliako. You will attempt to secure meetings with leads by selecting the most effective responses in a simulated email conversation.

My favorite feature, and I’m really proud of it, is the Global Leaderboard, where you can compete with others players to get the highest score in all three current scenarios.

Overview

At first, I designed it purely for fun, but after spending a few hours, it started to evolve and has quite a potential, I would say. Now I see this mini product for:

• Educate users about the complexity and skill involved in B2B lead generation;

• Provide training value for SDRs and sales professionals;

• Generate leads by encouraging users to let Belkins experts handle this challenging task;

• Hire people who are successful with appointment scheduling;

• Create a viral marketing tool through social sharing.

Features

• Realistic Email Interface simulating actual conversations

• Multiple Difficulty Levels with three distinct prospect types

• Relationship Meter provides visual feedback on your connection level

• Detailed Analytics: track relationship scores and decision quality

• Real-time feedback on how prospects react to your approach

• Branching Conversations: Every choice changes the path

• Aggressive Rejection Detection: see what happens when outreach goes bad

• Ghosting Mechanism: If a player is annoying

How to Play

1. Choose a difficulty level (Easy, Medium, Hard)

2. Read the prospect’s initial email

3. Select the best response from the options

4. Monitor the Relationship Meter as you gain or lose rapport

5. Proceed until you (hopefully) set a qualified appointment

6. Review your stats, feedback, and final outcome

Game Scenarios

• Busy but Interested (Easy): They see potential value, but time is tight. Show your relevancy—fast.

• Skeptical Decision Maker (Medium): This IT Director wants hard ROI data. Provide specifics to build trust.

• Frustrated Gatekeeper (Hard): The executive assistant is fed up with SDRs. Prove your worth and respect their role if you want through the door.

Best Practices for Success

1. Ask questions to uncover pain points before pitching

2. Provide relevant examples of Belkin’s success in similar cases

3. Focus on truly qualified appointments

4. Listen & respond to the prospect’s direct concerns

5. Avoid generic marketing fluff—stay concrete

6. Respect time by communicating concise value

7. Handle objections empathetically

8. Pick the right moment to ask for the meeting

License

© 2025 Belkins Inc - All Rights Reserved

Launch of a Paid Newsletter

I’m launching a paid version of my newsletter. Why?

1. Knowledge Sharing: I love building, teaching, and exploring. In the paid tier, I’ll show the nitty-gritty of my “Vlad is cooking” experiments—every prompt, every tool, and every trick.

2. The first edition. Will be about how I build this game. It’s already MASSIVE

3. Potentially, I’ll work on Closed podcasts & Videos: Exclusive discussions on AI dev, vibe coding, best B2B practices, plus potential live Q&As.

4. Community of Founders: I want to gather entrepreneurs who are building (or want to build) using AI, minimal teams, or unique new methods.

5. Support: A cup of coffee is my fuel to keep writing these newsletters with cup of cappuccino.

If you’d like to support me, consider subscribing. Let’s push these ideas further, and maybe we can all build the next big thing together.

Some thoughts

1. Most Code Will Be Written by Youth?

As code generation becomes easier, novices or time-rich folks might outproduce “official” engineers. Software might become dominated by youth culture—like social media. Are you ready for “software memes”?

2. The GUI Paradigm

We’re in a “CLI” stage of vibe coding, but we’ll eventually want a visual approach. Show the AI a design outcome, it automatically codes it. Fewer typed prompts, more “What you see is what you want.”

3. Less Open Source?

If code is auto-generated on the fly, do we rely less on existing libraries? Potentially, yes—disposable code might become the norm.

4. Post-Modern Software

With millions of vibe coders who haven’t “learned the rules,” expect chaotic UI/UX patterns. We might see a new wave of weirdly creative experiences.

5. The New Bottlenecks

If building is easy, the constraints move to “what to build?” or “how to differentiate?”. Everyone can create, so distribution and brand matter more.

6. Adaptive Software

Soon, we may specify outcomes, not code. If sign-ups drop, the app auto-adjusts steps. PMs shift from coding details to orchestrating results.

7. Software-Eating More Industries

Anyone with domain knowledge can vibe code their own specialized solution. More small industries get “eaten” by AI-driven tools.

8. Evolving Team Ratios

Dev:Designer:PM might change drastically. Cheaper code could lead to Jevons Paradox (build even more!). Or we shift resources to strategy, design, or distribution.

9. Vibe Marketing, Vibe Sales

Set a marketing or sales outcome, the AI handles influencer outreach, ad buys, lead gen, etc. Is that next? Possibly.

10. Bugs, Hacks, and Edge Cases

Vibe coding is fun, but the infinite edge cases in real software remain.

Will we trust AI to handle all the weird scenarios? This is the big question for large-scale products.

Post-Credit Scene

Finally, another post-credit scene.

• The state of AI: How organizations are rewiring to capture value

• Beat my record in Global Leaderboard in Belkins Challenge game

• Something to watch & listenYou Don’t Need More Money—Just A Better AI Strategy

• Still Skeptical?

  • Give Vibe coding a shot with Replit Agent or Cursor. Or read NicolasZu’s flight sim story—he built a sim purely with AI prompts:

• Paid Subscribers:

  • Wait for my first paid edition, where I explain in more depth how I built the game, what I used, and what it looks like.

  • Expect deeper dives into my exact prompts and architecture.md files, or how to handle advanced multi-user scenarios.

Thanks for reading—now go vibe code something amazing. Or try out challenge.belkins.io and see if you can handle my gatekeeping prospects better than I can.

Until next time—keep cooking.

Vlad