The living archive

The best posts from the group, kept

Every week the posts that take off in the Vibe Coding is Life Facebook group are added here, with a summary, why each one landed and the best answers from the thread. See this week's roundup.

BeginnersWorkflowsSeptember 28, 2026

How do you get an AI agent back on track when it loses context in a long chat?

The post asks members who do not write code what they do when an AI agent loses track of a long chat and starts adding new bugs instead of fixing the old ones. It drew 299 comments. The most liked answers say to stop relying on long chats: keep sessions short, move project knowledge into instructions, skills and documentation files, and keep the code in GitHub so nothing depends on the chat's memory. One member disagreed and said newer models handle long conversations well, at the cost of more tokens.

76 reactions, 299 commentsRead

BeginnersMaking moneySeptember 28, 2026

Why do people keep saying a SaaS is impossible to vibe code?

The post asks why so many people claim a SaaS cannot be vibe coded. It drew 199 comments and the answers split three ways. Some members said the claim comes from developers who feel their livelihood is threatened. Others said a small SaaS is well within reach, but a product for thousands of tenants still needs systems architecture, security and planning that an agent will not supply by itself. A third group described SaaS products they have already shipped and run in production, and one member pointed out that sales and growth matter more than the engineering.

66 reactions, 199 commentsRead

BeginnersCommunitySeptember 28, 2026

Would you hire someone who cannot code but can build a working SaaS with AI?

The post asks whether members would hire someone who cannot write code but can build a working SaaS entirely with AI. It was the most discussed thread of the week with 499 comments. Answers ranged from a plain yes, on the view that directing AI well now counts for more than writing code by hand, to a firm no from engineers who expect a hire to debug, use a git workflow and work inside a team. Several replies landed in the middle: test how the person reasons through a problem, and keep a professional involved for the moments when something goes seriously wrong.

281 reactions, 499 commentsRead

Want your post in next week's archive?

Share what you built in the group. The ones that take off land here.

Join free on Skool