Artificial intelligence has unleashed a torrent of cheating on campus and created chaos in the job application process, as both students and employers use large language models: the former, to write hundreds of AI-assisted applications; the latter, to screen those AI-written applications with AI-written filters, thus removing from the process of finding a first job those procedural frictions sometimes known as "people."
The US military is being run by a group that apes the Russians and not the Ukrainians—when we have in front of us one of the best statements of command principles I have ever seen from the latter.
The way to win at capitalism is to focus on what it actually does (make customers' lives better) rather than the socialist caricature of it (squeeze every penny out of them). The latter gets you 2x returns at best, whereas making new things for people can get you 10x.
So, it's hard to tell how much of like the loss of the past few years was AI versus the end of like zero interest rate policy and like the post-COVID crash. And I think it's more the latter, but like again, LLMs are still getting better.
I think there's a difference between being able to write lines of code in a particular language like Python or C++ and understanding how code, computer systems, products work. And I don't think the latter is going away.
It surely does not “produce” one quarter of world culture or intellectual activity (if the latter is defined as influential books, of fiction and non-fiction, politics, history; films, plastic arts, music, theater etc.)
What is happening is that GenAI's climate harm comes from the system design, such as Google's AI overview triggering constantly whether users want it or not, in addition to significantly worse digital bloat tools dominating overconsumption.
Laszlo and his team at Google reinvented the role of human resources. This book is a terrific overview of what makes Google Google, from culture, to hiring, to making decisions.
Levy was given unprecedented access to Google, and the result is what I consider to be an accurate depiction of how the company operates. A good overview of how Google product managers work.
So, giant eyeballs, they can either see very well, they can see a very long way in daylight, or they can see very well at night. And my suspicion is it's the latter. I think they're probably primarily nocturnal when they get that size.
This book gave me both insight and a deeper curiosity about the subject. This book introduces the SPIN model checker and exposes the reader to the nuances of verifying programs using SPIN. A nice feature of the book is how it explains concepts using thoughtfully developed, freely available tools (such as jSpin) that the author created for pedagogical purposes. It's a demanding book, but the content was interesting. The book presents details about concurrency, temporal logic, non-determinism, advanced SPIN topics, and even case studies. I've already written a few blog posts about the topics I explored while reading this book, and I plan to write more. Overall, it's a good book. I'm sure I'll revisit the latter half again.
a good overview of SRE at Google. For those who worked at places with oncall, much of the first part of the book will likely be very familiar. Keep in mind that your mileage might vary: what works at Google scale, might not be the ideal fit for your use case.
I stand in awe of what author Jackie Cummings Koski has done here. This is a comprehensive overview of what FIRE is and how it is done, fashioned in the famous "for dummies" template. I wouldn't have known how to even begin to pull this together, let alone gotten it over the finish line in such fine form.
My hot take is that JS has the lowest bar of entry to building and being productive (a good thing) but one of the highest bars of any language and stack to building high quality, stable, and reliable software. Very few devs have the expertise to pull off the latter
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.