djantje

I just connected my Garmin watch to charge via usb, enabled disk access, going into folder GARMIN/Activity/ and uploaded one of the .fit files to claude web and asked a summary and graph, it seems I had a nice evening bike ride that day :)

Yes, but then when the wind doesn't blow, you miss upto 960MW of capacity, you can choose how to fill that; solar, coal, gas, waterpower, diesel, nuclear.

And the question is, are those wind turbines without subsidy?

Here in the Netherlands some big energy users like Aldel already have stopped, those big users are also good in up and down scaling energy usage on demand, and also those products have to come from somewhere else now, so in the end the question is about energy and availability.

Some (or a lot of) subsidies can be justified.

It is about functionality.

Functionality iterations or adaptations are just faster with good architecture and principles.

I also like the percentual change, that is a lot of comma's.

Its a collective emergency service, which can save lives.

If by law this service is required and you bill only the rides, you get this, high bills per ride.

It would be nice to see a chart of countries with cost of ambulance rides, cost for the patient and average response times.

Yes, but you can't sign the device, that is what Google and Apple do.

From fingerprint/face id to digital id..

Like banking apps are now using play protect/depending on Google.

(Just a matter of time Google/Apple will be a banks themselves, as is the danger with governments)

Ofcourse the world could be a more open place, but constraint, rules and control are too pleasing to not implement, sadly.

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..

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.

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.