The two big signifiers that something is "ready for production use" are: 1) it has been successfully been used in production at some scale for a while, and 2) it has some commitment to API stability. A 1 week old project on version "0.1.0" is neither, whether vibe-coded or not.

▲

brian_meek 2 days ago | parent [-]

OP here. I frankly stopped trying to add evals for the "ready for production" happiness Claude is trained to produce. I agree, not ready for production. I did though put a intention and effort into guarding against slop in implementation and tests. Sure I can still find it, but I believe the current state is solid enough to build on, and I will be doing so for some pet projects. I'll let you know what I find when using it in anger.

	▲	mort96 2 days ago \| parent [-]
		What do you mean by this? > I frankly stopped trying to add evals for the "ready for production" happiness Claude is trained to produce. It's your readme, no? Does Claude just go in and change it behind your back..? What's going on here, are you not in control of what you push to git? Moreover, what thought process makes you okay with lying in your readme just because the robot wanted you to?