yep

Not just lanes! We have entire routes exclusive to bicycles and use bicycle lanes only as a fallback where there are none

Except with bicycles you very well can find a plane to jump out with no ground to be seen.

Your analogy is car brained and bad.

I live in germany and have an extremely safe bike commute.

I would not commute by bike in the US tho

US cities, infrastructure, and political attitudes are irreparably predisposed to support the dominance of the automobile. The problem here is simply not fixable on any scale larger than a neighborhood-level during any of our lifetimes.

Thats why we recommend obese people to walk first, even if they think they would enjoy running.

I'd say the electronic frontier foundation is the best candidate. They have been exclusively doing advocacy since forever

hundrets is a bit bold unless you include phytonutrients and subtypes per mineral.

twenty to thirty would be exhaustive.

5 minerals and 5 vitamins would be a good start

what if the plant is long dead?

Not really.

You could create several cohort with different co-controlled fixes for each: more calories, more protein, more fiber, more nutrients.

Then evaluate the percentage of successfully treated patients in each cohort.

It's of course a difficult study, since someone with a bad diet will lack practically everything, so more things will work than not. I'd also be curious to see how you would design a real food diet high in micronutrients without accidentally adding a bunch of fiber in the process

Most of these wouldn't qualify as "puzzles", would they?

I find it nice to learn new languages via data structure puzzles, because to me the data structures of a language feel like the grammar and once I have that down everything else falls into place

I disagree. Yes, you have to learn how to work with the basic data structures of a language, but 90% of programming, for most people, is not that. It's IO, error handling, db querying, logging, input parsing, parameterization, business logic, preserving backwards compatibility, persistence, state management, testing, mocking, benchmarking, build design (for lack of better term -- futzing around with Make/Gradle/Npm, Dockerfiles). All of that doesn't just fall out of learning DS/Alg's, it takes time to become familiar and fluent in how all these are done in your ecosystem.

When employers or team mates ask you if you "know" or "are competent in" Java they don't care if you know how to work with lists, arrays, loops, hashmaps and sets. Well, I mean, that's table stakes. They're asking if you're familiar with the idiosyncrasies of the language with respect to those above concerns.

Imo DS/Algs to an extent are a good prerequisite. Once you know them in one language that knowledge is portable enough to get you up-to-speed in $lang. Then, and no earlier will I start worrying about doing real things in my programs and the "idiosyncracies"

I think you overestimate the proportion of programmers who primarily work on corporate stuff.

And I'd rather have a child escape to the interwebs than needing to bear the suffering of a less-than-average childhood bluntly