I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far.
I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team? My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product. I'm curious what you all think, would you hire a vibe coder?
We now look at actual code less and less. What does your developer experience look like now that we are getting closer to a non-IDE world? I am using @Superset and am loving it so far. In my corporate job, I have 10-15 repos going at once and it's all super organized. What are you all using?
Hello everyone, Sumit here from the Himalayas. I hope everyone is having a relaxed weekend. My workflow with vibe coding has settled pretty well as I get more and more time out of desk while Claude Code builds the software. I wanted to offer any assistance to fellow founders. I have been vibe coding full-time for a little over 4 weeks. Wrote about it here. Please share your tools, or workflow and in particular what is not working for you. What is frustrating you in building software with vibe coding?
Every time I vibe code there is always this huge lift that I constantly have to go through. Authentication, billing, password resets, emails, signup, waitlist, landing page and when it s all said done and the app is ready then comes the marketing, the blogging, the social media automation, the product hunt launch etc etc etc . So much repetitive crap that I have to do just to get a simple app up and running. How do you guys handle all this?
Since I am a coder and a hammer sees everything as a nail, I decided to create all this code as a template so I can jump into building an app right away. There is actually a lot more than what I mentioned above e.g customer support, chat, roadmap for building in public, email flows and more coming.
I ve been testing the 'Free Tier' limits of the 2026 AI landscape. While everyone swears by Claude 3.7 or GPT-5.2, I m trying to find the 'Golden Ratio' for makers on a zero-budget.
My current findings for the Office Bee MVP:
The Brain: Gemini 3.1 Pro (via AI Studio) seems to have the highest 'Reasoning-per-Dollar' (free) for deep R&D.
The Frontend: v0 (Free Tier) for shadcn/ui components.
The Glue: Bolt.new for the initial scaffold.
The Challenge: Most 'free' models hallucinate complex state management in full-stack architectures.
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
I'm a senior developer in Seoul. My commute is long and the subway is always packed. Here's how I tried to make mobile development work and where it fell apart.
Seoul subway is not quiet. You're standing, one hand gripping a bag, the other holding your phone. Coding the traditional way IDE, terminal, file trees is physically impossible. The screen is too small, your fingers too fat, and the text too tiny to read without squinting.
