For more than a year now I have been consistently working in a vibecoding format. During this time I have created several unusual solutions and finally decided to start showing them publicly.

These are small research pieces that can inspire and at the same time remain utilitarian.

As devs, we all know the struggle with code security scanners:

• Switching between IDE and clunky dashboards to check vulnerabilities

• Wasting hours sifting through false positives

• Getting vulnerability alerts with zero guidance on how to actually fix them

I stumbled on an IDE extension (ZAST Express for VS Code/Cursor) last week that s amazing for my workflow. The Proof of Concept (PoC) feature is what sold me instead of just flagging issues, it gives runnable snippets to validate the problem, plus clear fixes right in my editor. No context switching, no guesswork, and it s free to start.

Hey folks

Quick share: I got tired of bouncing between 10 different sites every time I needed a simple arrow or calendar icon. Felt like such a dumb waste of time.

I would highly appreciate some information how you keep costs low. What we are now going to do:

• Run everything on VMs

• Rent A100s through Google Cloud for Startups Program (if they let us do this)

• Switch to Haiku

What else can you recommend?

I just shipped my first production-level app with a team of Claude agents in the cloud and it took me exactly 2 months from idea to launch! Most of that time was spent trial-and-error figuring out the right roles for each agent and dialing in handoffs so things actually worked in a real production setting.

Curious to hear from others:

- How long did it take you to get your first production-ready (not demo!) vibecoding or Claude Code agent project finished?

- What were the biggest slowdowns, unexpected obstacles, or surprising time-savers along the way?

Hey Community!

Is anyone else here documenting their vibecoding journeys from ideation to launch? I'm especially interested in process & workflow description, pivots & fails, and lessons learned.

Thank you!

I'm obsessed with building Telegram bots.

There s just something magical about bots no UI, no App Store bullshit, no onboarding friction. Just clean logic, instant results, and users who actually use the damn thing.

I ve been coding little bots for fun for a while now, and recently I turned that into a real project Zapis BOT.

It s a Telegram bot for booking appointments aimed at solo pros like barbers, lash techs, nail artists, massage therapists, etc.

I ve tested dozens of wearable devices, syncing delays and clunky onboarding are still way too common.

As someone building in AI fitness tech,

I m curious:

On October 31, 2024, my entire world crashed. My developer left, and with that, so did my sense of control. It felt like someone had yanked the engine out of a speeding car, leaving me skidding on an empty highway with no brakes.

yo. so i made this janky Joust clone in HTML5 because, idk, i thought it d be fun. turns out?

i SUCK at it. like, embarrassingly bad. no matter how much i tweak the speed, controls, or gravity-- my reflexes just nope out.