What are, according to you, the most interesting or most under-appreciated applications of VAEs? Please share below. Links appreciated. (I'm building a list for future reference.)
One thing that's under appreciated on the website of the demos is the Stanford demo where Ben showed uh anywhere between 3 to 25 images you can reconstruct that entire Stanford quad. But the thing is we had to show it from aerial view. But every single input image is been standing on the ground taking a picture from the ground. So, everything you see are generated but according to the laws of reconstruction.
The most successful skill is if you don't just have one, but you have variety and you can switch between them and you can use context to switch between those.
Facts and Fallacies of Software Engineering by Robert L. Glass. In essence, this is a book about an industry that refuses to learn. That was true 25 years ago when this book was published, and it's probably twice as true today. (Just think about all the AI adoption metrics being rolled out — back to productivity mistaken for lines of code produced, only more elaborate. And expensive). What I like about this book is that Glass doesn't present anything new. Quite the opposite, actually. Rather, it's about research lessons that we all should know, but tend to forget. Ever had to do an estimate, or plan according to a requirements spec? Or maybe you thought that enough eyeballs make all bugs shallow? Then this book is for you. A great work by a fantastic author.
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
For the first time, I ran all potential winners through Pangram, which is an AI-writing detector.1 So according to the machine (and to my ear), all of the winners are 100% human-written.
Some people think CI means you reject grammar books. I disagree. I often reference grammar materials and find these explanations useful. However, the focus of my learning is not to “master the rules”. Grammar resources simply help me notice and make sense of patterns in the language.
the ballerina and the kind of performer, that's the wrong reference class. Right now we have a lot of jobs where you have different tasks. So this is the task-based model jobs where you have like a lot of different tasks. So like a doctor, what is their job? They're filling out insurance documents. They're you know, going and like calling different pharmaceutical companies. And one of their tasks is to actually see the patient and talk to them, but that's like actually not the main part part of the job.
LLMs themselves are the perfect captive reader: they never get bored or confused, never miss a reference or have an emotional reaction, never ask themselves why am I reading this?, never close the tab.
And what this is is that in the guide level explanation, you explain your feature as if you were writing a guide as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.
AI today it's just starting to to become aware of you know the existence of of of language services and agents today like to use grep and awk and whatever you know to to find all the places where you reference a certain thing but it's not semantic search, right?
did you know that according to the legal documents you yourself signed, your company's literal charter that you have right now, and this is not some hypothetical future thing, you've already put in motion, a rule that says you have a fiduciary duty to say yes in this situation.
According to Harvard Law School, among venturebacked companies that have the standard best practices set up that you got from your lawyer, okay, only 20% of founders are still the CEO 3 years after going public.
Because when you believe in something, when you become obsessed with something, you sacrifice yourself to it. And that sacrifice actually feels like pain and stress and doubt. Not fun.
Awakening Your Ikigai by Ken Mogi. Perhaps a little over-simplifying when it comes to Japanese culture, but I appreciated the message of having a purpose. (B)
The big flaw is that it's justified through a fictional world. It's not justified through reference to the real world. It's not empirical in a way. It's not... Rand herself would say this. She's not writing about things how they are, but how they should be. That idealism just really undermines it as a mechanism to understand where we're actually living.
Almost everyone in the class said that the days were moving by slower. Then I would say, “Okay, so do you feel like the weeks are passing by slower, faster, or the same?” The majority of them said that the weeks were passing by faster. According to the laws of physics, I don’t think that makes any sense, but according to memory, it did because what happened was people were doing the same thing over and over in the same context.
So very important to keep in mind that Rus is not Russia because that was a self-name for all multiple groups on that territory. And Moscow doesn’t exist at the time when Kyiv emerges as the capital. The first reference to Moscow comes from the 12th century when it was founded by one of the Kievan princes.
According to my numbers, in the United States there will be a net of 3.24 million new low-skill jobs, but there will also be 4.7 million fewer people in the labor force.
The Linux Programming Interface by Michael Kerrisk – an exhaustive reference on how Linux works. There are about a million chapters, but every individual chapter is pretty short and I find it quite readable.
I particularly appreciated The Journey of Humanity because it is an ambitious and deep story about the past tens of thousands of years of economic development that is also well grounded in a growing economics literature into the deep origins of growth
Science journalist Jacob Ward warns about a future in which AI technology forms a tight cybernetic feedback loop with the biases ingrained into the human brain, pushing our day-to-day existence in frightening directions. It's sort of like a version of The Terminator in which Danny Kahneman plays a starring role. As longtime readers and listeners of mine know, a big theme in my techno-criticism is the under-appreciated degree to which technologies exert powerful, unintended consequences on our personhood and culture, so Ward's warning hits a sweet spot with me.
Free software is designed to be used commercially, but you have to do it correctly. This is a resource which is made available to companies who want to exploit it, but they must do so according to the terms of the licenses.
Sedgewick was more successful in developing his characters, and I also appreciated that he took regular tangents into other related and interesting matters like the Leadville mining boom, the growth of Los Angeles, and the business maneuvers of other railroad barons like Jay Gould and Collis Huntington.
I use Roam as my main note-taking app. While I only use very basic features such as bidirectional links and reference blocks, it works well enough for me.
I was disappointed. I love Tim’s work, but this didn’t deliver in the way his past books have. There’s zero thematic organization, so you can’t reference certain topics you want to learn more about except in a few cases. While this has some interesting pieces, I doubt I’ll refer back to it like I have with Workweek, Body, and Chef.
not only did I buy the canonical reference (The Rust Programming Language by Steve Klabnik, Carol Nichols and community contributors), I also bought an O'Reilly book with a bit more narrative (Programming Rust by Jim Blandy and Jason Orendorff).
I take my hat off to Hugh. This is one wine reference book that I have nothing to do with, and it is absolutely brilliant. It's very small—although, of course, it's been getting bigger and bigger as the wine world has expanded—and it does pack a heck of a lot of information.
Other frequently used programs include Dreamweaver and Fetch for my site; Chrome, iPhoto and Preview for reference hunting; iTunes, Spotify, and Downcast to keep me company.
The book is colorful and ludic which is a good idea for a "Beginner's Guide". The layout is attractive, there are many detailed examples. I like the pedagogy: the author wants you to learn by doing. However, the book is poor as a reference: the coverage is limited despite the 300 pages and the chapter summaries are strictly non-technical.
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.