undefined

points

[-]

The problem is that everyone has a different opinion. If you let a single user drive the design then that single user might love it, but everyone else will hate it.

Bespoke designs are often really terrible. Have you ever shopped for a house?

You know immediately when the previous owner had their stupid whims indulged by contractors with dollar-signs in their eyes. The house is ugly, non-functional and is not going to get the sellers price.

The next owner will undo nearly all of the work, and the contractor will cash in on both ends.

As engineers, we like to think we're the contractor in this scenario. But it's actually just an LLM.

by cushychicken2 hours ago|

prev|

[-]

Personally I hate how badly internal users are served by the majority of their systems and am willing to take some calculated long-term governance risks

This, I think, is the LLM/vibe coded app’s current place to shine.

Most internal systems don’t need massive concurrency or redundancy. It’s a webapp that reduces coordination cost between 20ish people. That’s something you can typically vibe code and deploy for ten bucks a month, and create real value.

by tardedmeme3 hours ago|

prev|

[-]

Is CRUD low stakes? Even if all you do with the employee database is read and write employees, losing it or corrupting it is disastrous, potentially business-ending.

by jeremyjh1 hours ago|

parent|

[-]

Some of it is, certainly, and those are the ones we’re supporting this way. I’m not talking about systems of record - more like custom project and task coordination systems that would alternatively exist in spreadsheets, in Monday.com or wedged into some larger system that is a poor fit and functions largely through side channels.