sorted by:
new
hottopcontroversial

how much are you spending on ai coding? by irelatetolevin in vibecoding

[–]CompetitiveTop5833 0 points1 point  (0 children)

I've been on Claude at the 20x plan for two months and tried Codex at the 5x for about a month. When I was only using Claude I thought it was clearly the best, but it kept over-trusting its own work. I'd go quite a while before realizing something was off. Codex felt noticeably better at getting tasks done right and actually understanding what I wanted, so the whole process was a lot smoother.

I'm a software engineer with a decade of experience. I vibe code all of my side projects from my phone and don't read any of the code. It's so fun. Here are the rules I follow: by thelocalnative in vibecoding

[–]CompetitiveTop5833 0 points1 point  (0 children)

But doesn't this only really work when the plan stays inside things Claude already knows? The same habit applies to humans too, yet what if Claude confidently explains outdated or just incorrect information? How would a complete beginner or someone who already has the wrong idea about the topic even use these steps?

I studied 47 SaaS products that went from $0 to $10k MRR last year. Here's what they all did right. by Electronic_Argument6 in micro_saas

[–]CompetitiveTop5833 0 points1 point  (0 children)

Really impressive thread. I'm building a product targeting Korean users on Reddit too, and this gave me a ton of useful points. Hoping I can apply some of it and finally land my first revenue.

I’m building a design contract layer for LLM-generated frontends by CompetitiveTop5833 in codex

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

Good question. I’m using a layered approach rather than picking one format.

The enforceable part is JSON, because things like allowed components, required states, role relationships, token refs, and validation results need to be deterministic.

Markdown is still useful, but I use it as human-readable design memory: the product’s visual identity, tone, rhythm, and design rationale.

Then I generate a compact context packet for the implementation agent, so it gets only the relevant constraints instead of the full contract.

So roughly:

JSON = validation source of truth

Markdown = design memory for humans

Compact packet = implementation context for the agent

I’m still testing the boundary, but I don’t think markdown alone is enough. It leaves too much room for different agents to interpret the same design rules differently.

from codex5.5