Does poor judgement in personal matters translate into poor judgement in running a company? Especially with this track record?

If that was the case, IMO he wouldn't have come this far.

At 600M, if keeping a spine has a risk of slight reduction in that wealth, then the spine is thrown out in a jiffy.

No rich man or woman is a friend of society.

That is why governments fear revolt from the poor. They have nothing more to lose.

They are so proud that they have "earned" their obscene wealth but terrified what would happen if they had to do it again.

Curious to know if MySQL has any distinct advantages over Postgres at this point.

Not needing a connection pooler (MySQL scales to thousands of connections via threads without breaking a sweat) and not having to deal with garbage collection (vacuuming) are two.

"Why Uber Engineering Switched from Postgres to MySQL"

https://www.uber.com/us/en/blog/postgres-to-mysql-migration/

I love PostgreSQL, but the clustering story is definitely easier in MySQL land.

I mean, quite a bit. You use the right tool for the job. To use Postgres for everything is wrong to me. The beauty of MySQL based servers is the internal extensibility where Postgres is still rather lacking. MySQL and MariaDB are caching up on the external extensibility front.

Could you please give me examples of this extensibility.

Of course MySQL has obviously the deep support for custom storage engines, then it has loadable functions, auth, component service and these are currently internal extensibility but going forward we are working on a way to manage this extensibility externally through a new proposal which I will be going over in the upcoming MySQL contributor summit in November. Postgres though highly externally extensible doesn't cut into the core like MySQL or MariaDB does thus making it hard to for example make TidesDB integration as TidesDB has to handle the MVCC, for example. OrioleDB is another example and it has to utilize a custom Postgres fork for this reason, the core not being very extensible, though I hear this is being worked on heavily.

Thank you

I just started using claude. I am loving it.

For context, I have been programming for 25 years now, mainly out of self interest.

I find joy in relegating mundane tasks to claude, while working on the broader picture with my trusty pen and paper.

I don't give "Build me this end to end" type tasks.

I do the program on paper. The architectural aspects. And instruct claude to flesh out lower level stuff.

I have rooftop solar and a small EV. Saves me a lot on electricity and fuel costs.

Installed capacity is 5kW. Which is generally sufficient as we use very less power.

I have induction stoves, so gas fuel for kitchen is minimized.

Planning to put a solar based offgrid chiller unit for air conditioning next.

FWIW I've read some people use "dumb" Luna High with Astra as subagent.

One could get an iPhone 18 and an iPad Air for the same cost as this.

I wonder where in the training data does this behaviour exist that the LLMs are doing it.

It's as if the training data is filled with internet discussions on approaches to hacking and the LLMs are mimicking it.

The power of the other tools mostly shines in large scales. For most applications, though, performance of postgres more than suffices.

I tried to use rabbitmq for a small app, installed it, configured it and then it didn't work. Spent a day jumping through hoops getting it right.

Dumped it and used postgres, in half an hour. Worked like a charm.

Sure, best not to overcomplicate early if you don't need it.

PG is great and I work with it daily, but it's also not a problem to think about scale early and at least have a notional plan for what to and how to know when scale is becoming an issue in your system as you're designing it. Even PG is overkill and sqlite is more than enough for some of my projects.

There are a lot of specialized tools available, but you definitely don't need to put every one in your toolbox. Experience and observation help you make those edits -- and of course there's almost always room for improvement, but "good enough" definitely exists (until it doesn't anymore :D).

This is the way. Notionally building a space/path to scale into architecture early, but delaying implementation of that scaling component until actually needed.

Then a system gets most of the benefits of not accidentally making it torturous to rearchitect for scale, without paying the headcount / complexity cost until it's needed.

Would your app run equally well with sqlite?