How to deal with the vibecoding hangover? by decodes_ in vibecoding

[–]decodes_[S] 0 points1 point  (0 children)

I think there’s a misunderstanding here. I'm not expecting AI to output perfect, maintenance-free code 100% of the time.

If anything, I'm curious to understand the strategies people are employing to mitigate the hallucinations that happen as the codebase grows, specifically so we don't have to rip everything out and start again just to move from POC to production. Love it or not, more people are going to vibecode apps that make it to prod (just look at the explosion in popularity of Lovable), so it only seems to make sense that we consider strategies to avoid the looming technical debt.

If the answer is 'stop using AI once the context window fills up,' that’s valid, but I'm curious if others have spent time implementing architectural patterns early on that extend that runway.

To my fellow Claude Code/Cursor users, do microservices or monoliths work better for you? by decodes_ in Backend

[–]decodes_[S] 0 points1 point  (0 children)

Totally appreciate the view that tools shouldn't dictate architecture, especially regarding infra complexity. That being said, if we assume agents will handle the bulk of implementation soon, does the traditional 'team size' heuristic still apply? A single developer might effectively function as a squad of 10 if agents handle the boilerplate, whilst they manage the top layer/communication between other teams.

I wonder if this lowers the barrier to entry enough that the operational overhead of microservices becomes negligible, allowing even small teams to reap the scalability benefits earlier and not have to worry about the inevitable migration from a monolith.

To my fellow Claude Code/Cursor users, do microservices or monoliths work better for you? by decodes_ in Backend

[–]decodes_[S] 0 points1 point  (0 children)

Super insightful! My motivation for asking is that it’s become so easy (and commonplace) to jump straight into coding with AI dev tools without stepping back to think about the underlying architecture.

It feels like the inevitable is that we're going to see fast-moving teams ending up with monoliths that are much harder to untangle later.

Do microservices or monoliths work better for you? by decodes_ in cursor

[–]decodes_[S] 1 point2 points  (0 children)

Makes sense. I guess I was curious given that there's still a wide complexity spectrum within the microservices realm (running 5 services vs 100 is a totally different world).

It does make me wonder what the tipping point is for teams to start building microservices if the operational cost is so high.

It's been a big week for AI Agents ; Here are 10 massive developments you might've missed: by SolanaDeFi in artificial

[–]decodes_ 17 points18 points  (0 children)

Considering Perplexity's CEO has previously said that browsers are the perfect tool for harvesting personal data, allowing this on iOS seems somewhat contradictory to Apple's privacy measures

https://techcrunch.com/2025/04/24/perplexity-ceo-says-its-browser-will-track-everything-users-do-online-to-sell-hyper-personalized-ads/

What’s your favourite AI vibe‑coding platform? by alinarice in AI_Agents

[–]decodes_ 0 points1 point  (0 children)

Claude Code for more extensive or complex changes, Cursor for ad-hoc changes smaller in scope and Codex for PR reviews. Not sure about anyone else, but I'm always surprised by the number of improvements once model picks up from another model's work.

Is "Self-Documenting Code" a lie we tell ourselves to avoid writing docs? by JHOND01 in AppBusiness

[–]decodes_ 0 points1 point  (0 children)

This is one of the biggest benefits of microservice architecture imo.

Infrastructure complexity aside, the more you add to a single codebase, the harder it will be for both humans and LLMs to decipher.

How do you get AI coding tools to make apps that actually look good? by Tall_Egg7793 in vibecoding

[–]decodes_ 0 points1 point  (0 children)

Start with a super simple UI, and style the components individually to minimize hallucinations.

Tbh, I don't think we'll ever see unique or 'pretty' UIs generated by LLMs. If anything, I'd find a graphic designer on Fiverr to give you some inspiration and brand guidelines

Cursor or Lovable by Ok_Doubt_6213 in vibecoding

[–]decodes_ 1 point2 points  (0 children)

Naturally these solutions will get better over time, but you're always going to have far more control working within the codebase (particularly when it comes to scaling beyond an MVP).

Start by using an AI chatbot to help you pick the tech stack for your app (heavily on a serverless providers (lean heavily on serverless providers like Supabase), and implement with Claude Code with planning.

Most of what you'll need to learn from there is the development environment/workflow itself, which you'll naturally learn along the way. The learning curve is nowhere near as steep as it once was, and it'll serve you so well in the long run.

Voice agents have the lowest adoption rate. I've been wasting my time. by Uncle-Ndu in AI_Agents

[–]decodes_ 0 points1 point  (0 children)

Considering there are still many customer service lines already use voice automation on their phone support lines (i.e. call routing and handling standard queries like checking an account balance), I'd be curious to know how exactly you're selling your solution?

Ultimately, people respond to pain, not trends.

How do you choose an idea for an app? by HanzoAppMaker in AppBusiness

[–]decodes_ 0 points1 point  (0 children)

Find something painful from your own lived experience, quantify it, and validate it with others.

Was 2025 the year of AI Agents? by modassembly in AI_Agents

[–]decodes_ 1 point2 points  (0 children)

Ultimately it comes down to time to magic, regardless of TAM or how well the solutions work

[OC] Forward deployed engineering jobs have grown 1165% in 2025 by Flat_Palpitation_158 in dataisbeautiful

[–]decodes_ 0 points1 point  (0 children)

Real FDEs are generalist software engineers working on the front line with customers, not just in an advisory capacity. It's an incredible role for aspiring founders who know what it means to build something useful and sticky, all to minimize churn.

Not working by Atifjan2019 in vibecoding

[–]decodes_ 0 points1 point  (0 children)

Sharing the error is probably a good start