Some of the houses trumpeted as “good” look like econoboxes with a front door and a roof. Some houses claimed to have “beautiful 1/3 proportions” look tiny even though my eyes can see the second and third floor windows! A hedge line either side of your path to your front door turns your garden into useless wasted space.
By contrast the “multi mass” look actually makes the house look bigger and suggests it has multiple disconnected living spaces - which sounds lovely, no need to always be forced on top of each other.
What if the “single roof line” aesthetic is an accident? What if it’s from a simpler time when resources to build your farm house were limited so you had to be efficient? Adopting it as some kind of ideal ignores that it might’ve just been practical.
It seems taste is personal but criticism is universal.
Sanctimonious bastards, get off my over-manicured lawn ;)
Why does it matter that only the cut is imperfect? Isn’t an imperfect interleaving also expressible as a modification to the unevenness of that left/right pile split? It seems the “0110” system doesn’t track relative order of cards but only the landing of each card, which allows each left/right landing to be treated as an independent event. If there’s no dependency on card order, modifying the cut split is a simple way to express both an uneven cut and imperfect interleaving with one variable.
But that assumes the model is only tracking cards’ arrivals in the left and right piles, not their ordering relative to one another. I only got that from the article.
Am I missing something? Is it that the left/right split is actually only informative about the amount of mixing that has occurred under the assumption that the interleaving was perfect, and therefore if imperfect interleaving is possible then one must weaken that guarantee - which then requires a more complex tracking system?
To me it’s just a proxy for the amount of economic activity in a place.
Every time I go to Melbourne airport in Australia, I’m shocked that nobody - nobody - has their laptop out. In Sydney a few people do. But go to any airport in the US and if not a majority are on laptops at least a large minority seem to be..
So yes - airpods in ears, laptops in airports, city lights at night. Just a sign of how plugged in everyone is to “something” that’s happening.
It's totally incorrect to state that the area served by either Sydney or Melbourne airport has less economic activity than the area served by "any airport in the US", or even the vast majority of US airports, so whatever laptops-at-airport (and I suppose airpods-in-ears) is a proxy for it sure isn't economic activity.
The only small catch is that NSF did not acknowledge it was illegally withholding funds Congress authorized for the array. And so who knows what might change in the future.
Still Congress seemed willing to pressure the administration on the issue and was about to pass a law directly earmarking the project.
> Problem is now that those in power have managed to convince large fractions of the population that it's wrong to say mean things about sociopathic mass murderers and child rapists or the guy who is actively trying to kill you personally.
Actually, civil societies granted a monopoly on violence to the government which vests that in police and military. It’s a far better system than random justice because it’s predictable and you know upfront what’ll trigger it.
That system had its flaws, but despite that it was working pretty well until those flaws were found and exploited allowing it to be captured.
> PLEASE do not rest your killer argument for humans in software on us being the best quality gate
Rather than dismissing humans for quality control, we should take an asymptotic approach, where humans verify less and less as more verifications are automated, but are never out of the loop. Get down to 1% of the things, then 0.1%, then 0.01% and so on.
Automate all the linting you can before the agent is allowed to make a PR, make sure it passes the tests, add custom linting for dumb AI-isms you’re sick of telling the agent not to do - yes, you can lint for that fallback & backcompat code you never asked for, you just have the agent generate a script that walks the AST and flags the problem by line and file, then put that in your pre-commit checks - the agent treats it like just another lint error. Now you never have to review for that thing again.
But you still have value!
Even when you automated everything you can think of, there’s still tremendous value in human review. It’s your last chance to fully understand the implementation before it melds with the codebase. You also pick up more antipatterns to add to your automated reviewer (the automated reviewer is just a long prompt with an ever growing list of bullet points)
And the asymptotic nature of QC extends to observability and production. You cannot really ever automate a loop directly from observability to code fixes? Even when the agent presents a fix to an unhandled exception in production - if it was bad data, should you clean it in a backfill? If a key business metric dropped off a cliff because of a bug, should you add an alert once you fix the bug?
All things are relative.
reply