There was practically no responsibility taken by the author, all blame on others. It was kind of shocking to read.

Anyone using these tools should absolutely know these risks and either accept or reject them. If they aren't competent or experienced enough to know the risks, that's on them too.

▲

throwaway041207 4 hours ago | parent | next [-]

And it doesn't even have to do with these tools in the end, this is a disaster recovery issue at its root. If you are a revenue generating business and using any provider other than AWS or GCP and you don't have an off prem/multi-cloud replica/daily backup of your database and object store, you should be working on that yesterday. Even if you are on one of the major cloud providers and trust regional availability, you should still have that unless it's just cost-prohibitive because of the size of the data.

	▲	pixl97 3 hours ago \| parent [-]
		Like, shouldn't they teach the 3 2 1 rule of backups in school by now?

▲

gigatree 3 hours ago | parent | prev [-]

The point of the post was to warn other people building with agents, especially using Cursor or Railway, not a public reflection

	▲	dymk an hour ago \| parent \| next [-]
		It was also to put Cursor and Railway on blast and complain about how they should have safeguarded him from putting a gun to his database and pulling the trigger.
	▲	simonjgreen 2 hours ago \| parent \| prev [-]
		Perhaps they should include a warning about learning systems design and architecture too then? It’s very incomplete.