How boring should your team be

Re:How boring should your team be by jstimpfle on Saturday October 15, 2022 @07:35AM (#33213896)

For mildly interesting code that you can realistically write yourself, there isn't a strict need to share code and cross polinate. Every little shop has a certain budget to try out new things, play around, and learn. If we come up with more or less the same things, that's fine.

I'm much more fond of sharing ideas than sharing code. IMO developers' understanding is at least as important as the economics of crafting code.

[ Parent | on HN ]

Re:How boring should your team be by paulryanrogers on Saturday October 15, 2022 @10:53AM (#33215356)

> I'd bet that the majority of all apps that depend on Postgres would easily fit in RAM, forever. That could mean one could get rid of SQL, or could apply other simplifications.

My guess is you're correct, yet RAM stored DBs cannot guarantee persistence when things go wrong. Or at least they may introduce data loss if changes aren't fsync'd to durable storage or 2PC with replicas.

[ Parent | on HN ]

Re:How boring should your team be by jstimpfle on Saturday October 15, 2022 @11:33AM (#33215689)

It already simplifies some things if data is available directly from RAM. And many stores are even only, or mostly, read-only access.

[ Parent | on HN ]