From the article: "A conversation with Stewart Brand, one of the most influential thinkers and pioneers of our time, still known for his 1968 creation, the Whole Earth Catalog. We talk to him about his latest project: a book, being publicly drafted online, entitled 'Maintenance: Of Everything'"
I just finished the book. It's a great memoir, nicely blending her personal and professional lives. It has many deep "lessons learned" from a laser-focused science career filled with hardships and obstacles. (For details, see the reviews in the linked page.)
Karikó's straight personality, humbleness and extraordinary determination shines thorough the pages, and gives true inspiration to science fans.
> scientific evaluation shows that it's like: writes a program 80% of the time, the program compiles 20% of the time, the program works 5% of the time.
Does anyone have a clue why Booking is not paying since many months? Their revenues are growing, and claim to have technical issues with processing the payments. But to me it sounds strange that a critical technical issue with payments needs many months to fix. Any insights?
I was really hoping someone would reproduce the tests and validate the claims from Microsoft's "Sparks of AGI" paper [1]. This video just does that (and more).
Let me provide one imporant quote from the video (from 18:50):
"I personally reproduced every single example from Microsoft, and while all the capabilities of GPT-4 were not necessarily over exaggerated, but the difference between GPT-3.5 and GPT-4 does feel a bit over-inflated [...] one of my quibbles with the Microsoft paper: they give the impression that GPT-4 is an even bigger step for AI than I think is realistically true."
I live in Hungary, where I have this feeling of "fake state" getting stronger and stronger every year. I'm sure there are other similar countries.
One recent example: our education system has been neglected for long. Now, that we have an inflation of ~25% (inflation of food is around 50%), teachers literally can't make ends meet. They started to fight for themselves, and instead of taking the problem seriously, the government fights back with its power. (E.g. by firing or silencing teachers who demonstrate.) Teachers are leaving for other jobs in huge numbers. The buildings of even some of the best schools in the country are in catastrophic shape, on the brink of causing major damage to those inside. All this, because it is not a real priority to have good schools. This is only advertised, but it is a lie. The whole education system is gradually shifting into a mode of "baby sitting" kids while the parents work.
Another example is the prosecution system. Interestingly, they are very quick and effective in investigating the smallest wrongdoing if it helps those in power. If the investigation would hurt those in power, they very quickly abandon the investigation with funny and obiously fake reasons. Again: the prosecution system looks like a real one, but it's not. It has purposes different from what is officially advertised.
The closest advisor of the prime minister openly said this week, that "if you control the media, you control the thoughts of people". This, sadly, seems to be true. It really seems that the point of the government is not to run the country decently, but only to fake it. And it works.
You're spot on, I think. This is already happening, and disintegrates society. There are countries where an analogue version of this is already implemented: fake parliament with fake opposition, fake government, fake media, fake prosecutions, fake health care system, fake education system, fake state functions. By fake I mean: it looks like a real one, but it's real goals and purposes are very different from what is officially advertised.
It's scary to think about how AI will boost the already way too effective politics of "fake".
This is a great piece, revolving around finding satisfaction through scaling down desires, instead of accumulating more of wealth/success. The claim is that good feeling attached to success is almost always ephemeral. The text draws a rich context by providing many scientific, cultural/historical and religious references. The author also provides some kind-of-practical advice, distilled from their own life:
Sure, if you can do that, why not? I was also searching for a good explanation on I/Q data when I found this. I posted it since I found the page interesting, but also, I did not dive into the details. I'm more interested in the conceptual explanation, and not the hands-on details.
If you could add another (potentially better explanation), that could be beneficial for future learners (not necessarily limited to the HN community).
The piece builds a strong case for the coronavirus spreading pattern to be highly skewed. If true, this would explain several strange observations, e.g. why some families are not infected, even though one of the family members is.
And importantly, this article contains some great science education with real-world examples for key probability theory concepts.
I have a similar experience, though I stayed on DDG. It's a bit funny, but I built a habit to use !s. This means, I use DDG to use StartPage, which in turn uses Google.
Ok, I found the reference for this story [1]! It turns out I messed up some details, but the core of the story is true. (It was not a company but Alex Szalay [2] at JHU, and it was not an indexing but a layout issue.)
Jim asked about our "20 queries," his incisive way of learning about an application, as a deceptively simple way to jump-start a dialogue between him (a database expert) and me (an astronomer or any scientist). Jim said, "Give me your 20 most important questions you would like to ask of your data system and I will design the system for you. " It was amazing to watch how well this simple heuristic approach, combined with Jim's imagination, worked to produce quick results.
Jim then came to Baltimore to look over our computer room and within 30 seconds declared, with a grin, we had the wrong database layout. My colleagues and I were stunned. Jim explained later that he listened to the sounds the machines were making as they operated; the disks rattled too much, telling him there was too much random disk access. We began mapping SDSS database hardware requirements, projecting that in order to achieve acceptable performance with a 1TB data set we would need a GB/sec sequential read speed from the disks, translating to about 20 servers at the time. Jim was a firm believer in using "bricks," or the cheapest, simplest building blocks money could buy. We started experimenting with low-level disk IO on our inexpensive Dell servers, and our disks were soon much quieter and performing more efficiently.
There's an anecdote about Jim Gray: he was once asked by a company to help troubleshoot a performance issue in their database (this was in the 80s or 90s I guess). Surprisingly, he did not start by looking at any code, but went directly to the server room and listened carefully for a while. Then, he said what the problem was. (IIRC it was an issue with wrong/missing indexes.) They went to look at the code, and it turned out he was right. Everyone was astonished, how he did this. He was "merely" listening to the sound of the spinning disks while the problematic queries were running.