I've been building my app for 8 months now, and i ended up having 5 repositories
nextjs app
databases
customer facing API
node-sdk that wraps the api
react-sdk, for both reusing shared component and customer facing components
So i thought, it's gonna be great if i create a mono repo with submodules. But it was terrible. I realized that turborepo does not like external packages, and as i tried to reuse my own customer facing libs, the DX became terrible. It was very time consuming to ship a feature. Even when i wanted to use Codex or Cursor 3, it was not able to show git diff properly, also i was not able to use Cursor's cloud agents properly to ship complex features.
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?
Hey, I was wondering how many of you are coding from the phone - it's easier to do it with AI coding agents now, so I'm wondering how often developers are doing it.
Personally, I do some coding tasks daily from my phone and I'm curious how others are doing it?
Over the last few weeks, I reviewed more than 15 vibe-coded fintech and startup-style web apps.
The surprising part was this:
Even when teams were using AI coding tools, security agents, framework defaults, and modern deployment platforms, I still kept finding serious external security gaps.
Not always one-click hack type issues, but the kind of problems that slowly stack up into real risk:
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?
We ran a benchmark to see how well @Claude Code actually refactors legacy code alone and then redid the same test, but this time with code-health guidance via MCP server.
To limit any vendor bias, we used a public data set of 25,000 source code files from competitive programming, including carefully crafted unit tests.
We assessed agent correctness by running those tests.
We measured the Code Health impact using CodeScene.
(See our research Code for Machines, Not just Humans for more details on the methodology and data)
Claude Code that was MCP-guided achieved 2 5x more more improvements in Code Health compared to unguided refactoring.
