Not much to say
Mongoose solves the schema part, or typegoose is you want it to generate types on the go as well.
My problem with mongo is that I always end up realising the advantages of SQL down the line, but I guess many of those projects wouldn’t have gotten that far without mongo being so damn nice in the beginning.
You are completely correct, and to be honest I’ve tested commercial product features in prod as well on teams that have the capacity to handle it and make a living on it, unlike this maintainer.
I’m also experimenting heavily with vibe coding and I think it has many uses for a seasoned programmer while getting a lot of flak.
Of course there are issues and problems with it, but for me it had been helping out a lot.
For sure, the song of the hero who fixed the production bug is oft sang at meetings but the loser who prevented the bug to begin with gets no credit.
Classic “test in production” strategy, very solid!
To be fair they would have needed to spend time testing the manual implementation as well.
The problem I see mainly is that even if this rolls out perfectly, the erratic and changing nature if llms still make it pointless as a proof of concept. Next time Claude might fuck up in a fringe way that’s not covered by unit tests and is missed by manual tests.
On the other hand I guess I’ve been guilty myself on numerous occasions to implement fringe bugs into production code, but at least I learn from it.
Exactly, if there’s even the slightest risk that I’ll need to dust off the good ol ajax that’s a nope from me.
What about ImageMagick? I feel it does deserve to stay in it’s own comic strip.
Good call. At this point the jankyness of js doesn’t pose a problem and the ones that get enticed will learn about type safety, classes etc down the line.