Well, a minor piece can be pinned in front of a queen. It would be legal to move the minor piece in that case, but you'd most likely lose the game if both sides' material were even before the move. Pinning is a tactic, not a rule.
How's the bike infrastructure? Do bikes have to share the road with cars? Are protected bike lanes ubiquitous, or do bikers have to worry about being run over by a distracted driver?
There's a lot of empirical evidence that people will chose bikes over cars if the infrastructure made it safe and convenient, even with terrible weather. Paris, Copenhagen, and Amsterdam come to mind, but there are many more examples.
This is the correct answer. There are a few pockets in the USA where this is the case like parts of the Boston and New York metro area, but you have be flexible with your definition of "affordable".
And that's the point. These places are less than affordable because there's a much higher demand of people who want to live in these kinds of areas than the supply of them. We should build more!
> ... and just have everybody agree to shift their work day to 7:00 to 4:00.
That "just" is doing a lot of work in this phrase. We live in an interconnected society consisting of lots of quasi independent actors organized in families, office locations, schools, businesses, and many other organizations. Coordinating a change in operating hours for _everyone_ is deceptively difficult.
If a person with a school aged kid wants to individually go to work an hour earlier relative to the sun, you're proposing that he lobbies his employer to set work hours an hour earlier, then lobbies his kid's school principal to start the school day an hour earlier so he still has time to drop his kid off, and then lobbies his favorite coffee shop to open an hour earlier so he can still sip his latte while he walks into the office. The employer has to coordinate with all of the other employees, who have to coordinate with their spouses and families and kid's schools, and favorite coffee shops. The principal has to coordinate with all of the teachers and the parents of all the other kids. The communication complexity of this scheme is exponential. Of course, there will be many opinions about how smart and stupid this change would be, so we'd also need a way to incorporate all of this feedback to make a decision that everyone will follow.
It turns out that we've already developed a method to manage the complexity of gathering feedback and making binding decisions in coordination problems like this. It's called the political system. We elect representatives to the government. Those representatives make proposals, debate those proposals, and, sometimes, pass them into binding laws that everyone has (implicitly) agreed to follow.
So yes, you're right that is "all [we] are doing". It's just that when you live in a country of over 300 million people, the most practical way of having everyone "agree" to do anything is by using the pre-established political system and passing a law. It's much more practical to pass a law that shifts the official clocks back an hour than to mandate starting and stopping times for every single organization in existence.
Clear and descriptive function names, concise and non-clever code, and a judicious use of well-named and concise helper functions are all way more valuable than docstrings. IMHO docstrings should be used as a last resort if the problem domain is truly complex enough to warrant it.
Docstrings for trivial, well-named functions just get in the way, and if you feel the need to add a docstring to a complex function just after you've defined it, then I think that might be a hint that you should refactor the code to make it more clear and readable instead.
An ns docstring that describes the intent of the api and docstrings for the major public interface functions are a good idea, but a blanket "docstring for every function" rule is a crutch to make up for unreadable, poorly-written code.