the more that we see actors looking to weaponize without any very good maps of how and what they are doing or what kinds of unexpected repercussions might happen, the more we can expect not simply increased risks of tension and worry, but also people screwing up, doing dumb stuff.
there are people who are really big on road maps and there are people who are really big on iteration. I I think the honest answer is you've got to do both. You can't over-index on either.
You know, obviously, we patch our games and that’s where we fix a lot of bugs, but if you really wanna run a game like Overwatch or World of Warcraft successfully, you need master level engineers who have architected the client and server in such a way that you can hotfix the game on a dime.
World of Warcraft, when we made it, there was no CFO at Blizzard. You don’t need a CFO to make World of Warcraft. You need artists, engineers, designers, producers, and an audio team.
And we failed horribly, and we had the best of the best on that team. And it’s because everybody was too much of an expert on how to make a groundbreaking phenomenon MMO.
And what makes an MMO, massively multiplayer online game, massive is having the other people there. And they’re so important or else the world feels kind of wrong and dead. But the concept that we have to force you to interact with them to do anything is very off-putting to a lot of people.
If you get really good at coding that means you have to be really good at general purpose problem solving. So that's a skill, right? And that just maps into other domains.
used to be let's say in the Google world right I knew you were interested in shopping if you click the shopping tab I know you're interested in maps if you click the maps tab, we can measure clicks. Today, it's just all conversation. And so, it's actually harder for us to tease apart what is the user intent.
The World Atlas of Wine has unrivalled maps. Hugh did a fantastic job, the real spadework, of getting some top quality maps of the world's classic wine regions and many of the new ones. The original editions had Hugh's matchless prose, trying to encapsulate the spirit of each region in surrounding texts, but the maps are the thing, and some photographs.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.