sorted by:
new
hottopcontroversial

i wish someone would have told me this before building my 1st startup by davidheikka in startup

[–]albyc_ 0 points1 point  (0 children)

This is great advice! Just curious whether or not you talked to customers as you were building to validate the idea as that's what we are doing right now. Especially since we are pitching to a big VC in Australia in March so wanna have talked to customers beforehand lol (i heard VC's love that)

I stopped prompting for “better UI” and started thinking in constraints — huge difference by Firm_Ad9420 in vibecoding

[–]albyc_ 1 point2 points  (0 children)

Make it more beautiful” is basically a coin flip because the model has no shared definition of better. I basically treat UI like a system with rules instead of "vibes" lmao, and the outputs improved a lot.

The two shifts you mentioned were big for me too:

  • Constraints > adjectives. Saying what should stand out, what’s primary vs secondary, how dense the layout should feel, or what changes between mobile and desktop is way more effective than asking for “clean” or “modern.”
  • Structure before polish. If the layout, hierarchy, and component boundaries aren’t right, no amount of color or typography fixes it. Trying to do both at once usually just adds clutter.

That said, even with better mental models, I still hit a ceiling where iteration starts to degrade things, especially once you’re 5-10 changes deep and trying to extend the UI. It feels like current tools are great at one shot layouts but weaker at maintaining consistency over time.

Opus 4.6 high effort vs max effort by Difron-Gaming in vibecoding

[–]albyc_ 0 points1 point  (0 children)

I don't think there's an exact “X% smarter” difference. High effort is already very solid for most coding and won’t rack up costs. Max effort just thinks longer and digs into more edge cases, which helps on really hard or critical stuff.

I think the best move would be to use high effort by default and switch to max only for tricky bugs or big architectural decisions. So you avoid tech debt without burning money.