In general, the air moves with the ground, so the earth's rotation does not affect airplanes.

However, rotation of the earth imparts a coriolis force on the air, which results in jetstream winds. Aircraft routes are optimized to use/avoid jetstreams for shorter travel times.

Both of these are film terms.

Also, thoroughly abandoned for half a decade. No recent camera support whatsoever, no feature updates.

I edit with Darktable, but organize with DigiKam. Not that Darktable is bad, but I prefer to organize my rendered JPEGs, not my RAWs.

Capture One or DxO. These are the only ones as good as Lightroom in their rendering. I'm afraid they are both much more expensive.

ON1, ACDSee, Luminar, Zoner, Silkypix, Radiant, RAW Power, Photomator are other options, but IMO have rather significant flaws that make them less good.

Frankly, Ansel is outdated by now. No color equalizer, no camera styles, no Sigmoid.

Mainline Darktable has overtaken it.

If he's so hung up on the open source process of Darktable, I can't wait to hear what he has to say about enterprise software, LOL.

I always keep very sparse notes with pen and paper. Once the dust settles, I transcribe them in full sentences into my digital journal.

This act of reconstructing a coherent narrative from disparate events is an enormously useful part of writing the journal.

That's a good observation. How would you teach an LLM the processes and conduct in your company? I suppose you'd need to replace code reviews and tutoring with prompt engineering. And hope that the next software update to the LLM won't invalidate your prompts.

It's not very different from documentation, except it's not used for learning but rather immediate application, i.e. it's something you must include with each prompt/interaction (and likely need a way to determine which are the relevant bits to reduce token count, depending on the size of the main prompt.) In fact, this is probably one of the more important aspects of adapting LLMs for real-world use within real team/development settings that people don't do. If you provide clear and comprehensive descriptions of codebase patterns, pitfalls, practices, etc the latest models are good at adhering to them. It sounds difficult and open-ended, as this requires content beyond the scope of typical (or even sensible) internal documentation, but much of this content is captured in internal docs, discussions, tickets, PR comments, and git commit histories, and guess what's pretty great at extracting high-level insights from these types of inputs?

Not to diminish Fairphone's accomplishments here, but beginning in 2025, the EU mandates five years of software updates for all phones sold in the EU.