My hottest take is that it wasn’t anonymity, but auto correct, that spelled (literally) the end. Without autocorrect and auto-grammar, ideas were tagged with the credential/authority of “I can use they’re / their / there” correctly, which was a high ass bar.
One of the most curious things I learned about babies is that they are born with a walking instinct, long before they actually can walk. If you hold them up, they will move their legs in a perfectly correct walking fashion. But they lack the strength and agility to keep their body up. At around 3 months this walking instinct disappears, and then at around a year we 'relearn' to walk when we have the strength and agility to hold ourselves up.
But if we were on a planet with significantly lower gravity, humans would likely be walking very near immediately.
Unfortunately for the English majors, the poetry described seems to be old fashioned formal poetry, not contemporary free form poetry, which probably is too close to prose to be effective.
It sort of makes sense that villains would employ villanelles.
Not all regulation is bad, and some of it is wildly effective at not just achieving the letter of the law but actually solving the problem it was defined for. Good regulation IMO looks bad because you never hear of anyone being punished for breaking it because it is complied with.
The EU banned roaming charges in 2017. Most networks by then had already abolished them, but only because this change was coming. The UK then decided it was going to leave the EU, and pretty much overnight the major mobile providers reintroduced the roaming charges.
EU flight compensation rules are another great example - they don’t pay out often because what’s happened is the airlines don’t get delayed to that point as often as they used to.
Scotland has a “right to roam”, which can be summarised as “don’t be a dick and you can go anywhere you want outdoors”. So you can walk, camp etc pretty much anywhere (it’s a bit more complex). In theory this means I can just open a gate to a farm, and walk across their fields. In practice, this means that most popular walking paths have access routes maintained by landowners that people use.
On the flip side, the cookie banners are a perfect example of bad regulation. They’re super easy to (allegedly) comply with and the result is just an annoyance for some 300 million people and absolutely no change to company behaviour whatsoever.
My completely unqualified opinion is that this kind of behaviour is linked directly to intellectual ability. Returning the cart requires self-discipline but also implies a thought process around upholding and creating social order. Even fear of shame implies a desire to uphold social standing with others.
Whereas not returning the cart can only be explained in two ways: a thought process that says ‘not my problem’ (selfish, disorderly, bad for society) or no thought process at all, like an animal with no higher order thinking.
> The biggest problem at many parties is an endless escalation of volume. If you know how to fix this, let me know.
Ideally, a guest breaks a cheap glass. The sound is heard across the house. The helpers immediately spring into action, leaving their conversations behind, looking for towels and a dustpan. The people nearby go mute with sympathetic embarrassment. Much ado is made of finding every shard. Meanwhile you are laboring over a replacement drink for the guest, which you graciously present in protest to their apologies. The party resumes at 70% volume.
* The LLM has strong and deep rooted belief in its knowledge (that a seahorse emoji exist).
* It attempts to express that concept using language (including emojis) but the language is so poor and inaccurate at expressing the concept that as it speaks it keeps attempting to repair.
* It is trained to speak until it has achieved some threshold at correctly expressing itself so it just keeps babbling until the max token threshold triggers.
The leverage is that the activists will potentially be able to draw the ire of the government. Visa and MC get away with absolute murder in terms of the size of the fees that they charge in the US. Most developed countries don't allow that. The US government could easily regulate them (as they already do with debit card fees) or use anti-trust law against the obvious duopoly charging exorbitant prices. Because of this situation, Visa and MC have a very strong incentive to crack down on things the government doesn't like.
The unspoken arrangement is that the government allows them to keep charging a de facto sales tax on a massive portion of the economy as long as they cooperate and de facto ban things that the government wants banned but can't ban themselves due to that pesky constitution.
I have run into this. My notes: Google Chrome (Desktop & Android)
chrome://settings/content/notifications
Or Settings > Privacy and security > Site settings > Notifications Under "Default behavior," select: Don’t allow sites to send notifications.
------------------
Mozilla Firefox (Desktop)
Settings > Privacy & Security Scroll to the "Permissions" section, find "Notifications," and click "Settings…"
At the bottom, check: Block new requests asking to allow notifications.
------------------
Microsoft Edge
Settings > Cookies and site permissions > Notifications Set the default to block all notification requests.
------------------
Safari (macOS)
Safari > Settings (or Preferences) > Websites tab > Notifications Untick: Allow websites to ask for permission to send notifications
My lovely horse
(My lovely horse)
Running through the field
(Running through the field)
Where are you going, with your fetlocks blowing in the wind?
(All Summer)
I want to shower you with sugar lumps
And ride you over fences
Polish your hooves every single day
And bring you to the horse dentist
(My lovely, lovely, lovely horse)
My lovely horse,
(My lovely horse)
You're a pony no more
(You're a pony no more)
Running around with a man on your back
Like a train in the night...
like a train in the night
(I Love You Anyway)
My lovely, lovely, lovely horse
I had the same realization but with car mechanics. If you drive a beater you want to spend the least possible on maintenance. On the other hand, if the car mechanic cares about cars and their craftsmanship they want to get everything to tip-top shape at high cost. Some other mechanics are trying to scam you and get the most amount of money for the least amount of work. And most people looking for car mechanics want to pay the least amount possible, and don't quite understand if a repair should be expensive or not. This creates a downward pressure on price at the expense of quality and penalizes the mechanics that care about quality.
There's a pretty easy trick to nested comprehensions.
Just write the loop as normal:
for name, values in map_of_values.items():
for value in values:
yield name, value
Then concatenate everything on one line:
[for name, values in map_of_values.items(): for value in values: yield name, value]
Then move the yield to the very start, wrap it in parentheses (if necessary), and remove colons:
[(name, value) for name, values in map_of_values.items() for value in values]
And that's your comprehension.
Maybe this makes more sense if you're reading it on a wide screen:
[ for name, values in map_of_values.items(): for value in values: yield name, value]
^^^^^^^^^^^^^^^^^
/------------------------------------------------------------------------------/
vvvvvvvvvvvvv
[(name, value) for name, values in map_of_values.items() for value in values ]
Right. "Low confidence". Read [1] People who deal with intel data need to work with possibly wrong info. Most spy novels don't get this. Real military planning works more like: "Intel says the enemy is at A or B, most likely at A. How much resources should we devote to A vs B, or hold in reserve until we find out by encountering the enemy? What's our plan if we guess wrong?" Planning has to assume that intel might be wrong.
Go watch "A Bridge Too Far" (WWII). Read the story of the Son Tay raid (Vietnam). The many overestimates of Soviet capability during the Cold War. The underestimates of North Korean missile capability. Sometimes uncertain intel really works, as with the attack on the bin Laden compound in Pakistan.
Retrospective intel questions may never be answered. It's known that the US atomic bomb program had another Russian spy who is mentioned by code name in VENONA transcripts, but that spy was never identified. There are still arguments over whether the explosion of the Maine in Havana harbor in 1889 was an accident or a hostile act. It's still not clear why Turret 2 of the USS Iowa blew up in 1989. Huge amounts of effort were expended on all three of those questions, all of which were important at the time, and yet they remain unsettled.
That reminds me of a big company around that time. They changed master to main in git, which cost each engineer many hours on average, which translated into many engineer years (decades?) of wasted time.
It was in the
middle of a hiring spree. Why not spend that time interviewing black engineers instead?
[we were a thin-crust only type of place; we also used a little handful of cornmeal as it was placed in the brick oven to prevent the crust from sticking - it adds a little extra flavor and texture to the pizza :)]
In a pot, placed on medium-heat on the stove top, add:
- 2tbsp EVOO
- two twigs of fresh oregano, crushed or finely chopped (to express the oils in the plant)
- 1/4 white onion, minced very finely
- 1/4 yellow onion, minced very finely
- 2-3 squished cloves of roasted garlic (cut the top part from a bulb of garlic, add some EVOO and bake @ 400 for ~30(ish) minutes; be sure to do it in foil or the ceramic baking dishes for roasting garlic!)
- 1tbsp of salt mixed with black pepper and crushed red pepper flakes
Until onions are translucent and aromatic
Then add:
- 1 large can of Cento-brand peeled San Marzano tomatoes
Stir intermittently until sauce develops a deep red color and you can use it right away or keep it in the fridge!
- As it cools, add in a handful (1/4 cup) of freshly crumbled Parmesan cheese (you could see the cheese chunks as we applied the sauce to the dough so they weren't large pieces but little(ish) crumbles)
The name of the shadow kitchen is "Pasqually's Pizza & Wings". If you read the "Our Story" page on their website, it says that they "leverage the operational infrastructure of Chuck E. Cheese kitchens across the country".
Pasqually is one of the animatronic characters, he is a chef.
This is a problem so chronic across so many fields that I wish there was single term to describe it.
User POV :"Wow, provider is a really shitty entity and had no respect for my legitimate problem."
Provider POV: "We get a huge number of illegitimate claims identical to legitimate ones regularly, the system would collapse if we didn't do heavy triage, the problem is the level of abuse, not a moral bankruptcy on our part."
I suppose "this is why we can't have nice things" captures some of it.
From my notes. Maybe it's useful to someone. Not comprehensive as there are other brands and other iterations I'm sure. Many dpreview.com sample galleries show original filenames. Some forums list filenames, youtube descriptions can list model names, pdf manuals and manufacturer websites sometimes list the names. There isn't really a good list of these that I know of.
Perf reviews are a terrible abstraction. The ranking and self-scoring and meetings and goal setting and stomach aching could be boiled down to a 5 item list:
1. We want this person to leave. They probably should have been let go already.
2. We wouldn't mind if this person left, but we aren't going to go out of our way until there are layoffs.
3. This person provides adequate value, loyalty, and flexibility for their salary.
4. This person is a key contributor and should be advanced if possible.
5. We don't know why this person is still here, and we are terrified they might leave us when they realize how undercompensated they are.
That's it. That's all perf reviews are for. No one needs to be stack ranked or anything silly like that. HR is an abomination.
What's hilarious is they do have UI for it in about:config "dom.forms.datetime.timepicker". It makes me so angry that it's not on by default. It works fine!
Not OP, but also Mormon and served a mission with the same constraints.
The biggest reason for this was that the two-year mission is seen as the one window of your life when you dedicate all of your time to serving God. Before that and after that you live normally, but during that window you're as close as the LDS church gets to being part of a religious order of monks. You theoretically chose to go out there (though to be fair there's enough peer and parental pressure for young men that some don't feel there was a choice), and you're with a companion who also chose to serve. The concern was that too much time spent on communicating with and dwelling on home would distract you and your companion from that singular focus and waste the preciously short time that you have before you come home and get caught up in normal life.
Back in the 70s these constraints wouldn't have been a very big deal—most kids living away from home for college would have been in a similar boat, just less structured, and people expected communication across long distances to be slow and sporadic. Few would have paid for weekly long-distance calls in any case. But the church is pretty slow to change, so the rules stuck around longer than was likely healthy even as expectations around communication shifted with the advent of the internet.
At some point in the last 10 years they realized that the slow communication pattern is actually not healthy for kids who grew up with expectations set by smart phones, and the formal restrictions are all but gone from what I understand. We video called with my brother every week in 2017-2019, and many missionaries these days are on Facebook or similar daily.
> none of them could articulate what part of its feature set they actually needed to use.
Transactional DDL: migration errors never leave the database in an intermediate/inconsistent state.
Range types + exclusion constraint: just no way to do this in MySQL without introducing a race condition.
Writeable CTEs: creating insert/update/delete pipelines over multiple tables deterministically. Seriously though, the RETURNING clause is something I use all the time both in and out of CTEs.
Filtered aggregates and grouping sets: cleanly get multiple data points for a dashboard in one shot.
Unnest: converting arrays into a set of rows. Inverse of array_agg(...).
Types: arrays, booleans, IP/subnets, UUIDs (without binary(16) hacks), etc.
Materialized views: seriously, how does MySQL not have this yet?
Statement-level triggers: another option from per-row.
Row-level security: setting data visibility based on configurable policies.
I can cite specific use cases I've deployed to production for each of these and more.
One of my favorite gzip party tricks is that (ungzip (cat (gzip a) (gzip b))) == (cat a b). That is to say, the concatenation of two gzip streams is still a valid gzip file.
This hasn't ever been practically useful, but it means you can trivially create a 19-layer gzip file containing more prayer strips than there are atoms in the universe, providing a theological superweapon. All you need to do is write it to a USB-stick, then drop the USB-stick in a river, and you will instantly cause a heavenly crisis of hyperinflation.
