You can press Q while using cmd tab to quit that app entirely without leaving the cmd tab interface, which is a fast way of cleaning up at the end of the day / when project switching.
(apologies if this was _precisely_ what you referring to, but commenting in case you meant you then closed each app individually with cmd q, then returned to the cmd tab interface)
> Standing-only escalators had a "throughput" of up to 151 passengers per minute, while an escalator where commuters were still allowed to walk saw around 115.
Your thought experiment's completely right, but in real world circumstances, once an escalator is above a certain height, people rarely use the walking lane:
> But a 2002 study of escalator capacity on the Underground found that on machines such as those at Holborn, with a vertical height of 24 metres, only 40% would even contemplate it [walking up]. By encouraging their preference, TfL effectively halves the capacity of the escalator in question, and creates significantly more crowding below, slowing everyone down.
Transport for London should politely refrain from any statements like that, I believe. They hardly can allow people to enter the platform because there's no space to fit the crowd. There's sea of heads almost every morning in front of most popular stations' gates. Not because they have a gates issue, or any other unusual problem - they are just regulating flow that way. So, I'd kindly ask them start modernizing platforms to allow more throughput in the first place. Then let them experiment and play with statistics, by all means.
Not OP, but I can recommend the handy https://github.com/kynan/nbstripout which acts as a git filter which makes version control ignore cell outputs.
With that approach, though notebooks are clean they're still fairly poor for easily evaluating diffs between versions. If code review / diffs are more important than preserving the notebook, then you could use a post save hook to convert notebook input to a .py file and output to .html:
it really depends on how fast you shove it into the application. Since TV can vary from region to region by upto 7 seconds. But from seeing it on the apps end, to sending the tweet less than 2 seconds.
Would love to know if anyone has a more elegant solution