It is just going to be even more less important software.

There is a difference between writing for mainstream software and someone's idea/hope for the future.

Software that is valued high enough will be owned and maintained.

Like most things in our world, I think ownership/stewardship is like money and world hunger, a social issue/question.

Defining the spec is ofcourse also needed in an agile process.

The difference is when is this done; In a upfront discussion, while developing, or after user feedback.

For LLM we know it needs to be written down. (At least if we want human tracability)

And agile ofcourse is a shortend waterfall to get user feedback early on.

Giving enough context is important for every case.(humans and llm's alike)

It should be a setting (like macos) otherwise full control of all the devices is always at the mercy of Apple.

Yes, lets dismiss Japanese culture..

This isn't dismissing, this is respecting that this is a risk factor in involving Japanese contributors.

Please reread what you wrote and try to see if you can see how it comes off as at least culturally insensitive if not outright racist.

I live in Japan so I have seen what danieltanfh95 describes many times in person. Japanese people at work seem to have infinite patience with whatever random bullshit their company will ask for, but outside of work they get easily frustrated when things don't go the way they expect.

DB multi-master, or the DB not being responsible for primary key generation, is the use case, I think.

And then having uuidv7 as primary and foreign keys, can give you a performance gain.

Vimeo is not working to view random videos in the EU, I saw last week to my surprise.

https://help.vimeo.com/hc/en-us/articles/30298226209169-Chan...

Well, reality is more complex then this. It misses intersex as a biological option. Not common, but still, it is not in there, but reality for some humans.

It makes the rich less rich, the poor more poor.

Ok, but are humans not using predictions while reasoning?

And are LLM's unable to reason?

It looks nice. Are there plans to (try to) remove all the GET request parameters from the authentication flow? The Authorization request maybe seems one (the browser would need to support that, or use Javascript, or maybe a shortlived cookie) And also "8" GET tokens using the code, is potentially one?

I think you didn’t reply to what you intended.