The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
These examples are liberally illustrated with links to musical excerpts that bring the subject to life (these are presented as hotlinks in the ebook; if you're reading the print edition, you can use the book's companion website:) https://web.law.duke.edu/cspd/musiccopyright/ Interspersed with these histories and analysis are lengthy, extremely on-point excerpts from THEFT!
Smalltalk Best Practice Patterns. True, Kent Beck is better known for his later work, which is excellent too. But Smalltalk Best Practice Patterns is particularly strong on coding style. I learned a lot by just reading the code examples. Small tweaks to names and abstractions add up. No one captures that better than Kent.
Paradigms of Artificial Intelligence Programming by Peter Norvig. Learning the AI described in this book probably won't land you a job today. But reading the code examples will transform how you think about source code. The book shines when it comes to code comments, a topic that I've never seen demonstrated well in other sources. Here we get to see how comments become valuable as a narrative that explains both intent and reasoning. Brilliant, just brilliant.
Um because if you didn't have that thousandx difference then you know you wouldn't have to do batching but you have to do batching of you know many examples or maybe many tokens at once in order to amortize that data movement
it probably took my whole career for me to fully understand how hard it is to hire someone who's not a product first individual and then get them to be good at it. I'm sure there there are examples, but it's got to be 5% or less of the use case.
I'm watching people write these huge markdown files to give the agent context. How about you write documentation to give me context so I can have fully working examples.
Now the thing is you can of course write examples in your documentation and Rust makes all examples into tests. This means that if you change the underlying code now your test fails. And so this means that you can't even you can't forget to update your examples in your documentation.
But a proof can reason about potentially infinite state spaces. So, it can tell you things about like every possible thing that could possibly happen in the entire universe.
So while vibe coding may be useful for short-term work, it’s not a suitable approach for anything intended to last longer than a tub of yogurt. Time saved is not strength gained, so I went looking for other examples about how to work with the machine.
Because the bacteria, even though they're individual examples of life, and I believe this the true unit of life, it's not DNA, it's not a cell, it's the biosphere. It's the whole community.
One of my favorite books is Extraordinary Popular Delusions and the Madness of Markets, published in 1841, and it chronicles how market mistakes form and grow, using the South Sea Bubble and the Tulip Bulb Craze as illustrative examples.
Identification of a Woman (Italy, 1982, CC) 3.8 Critics often point out various flaws in Antonioni films, but I’d rather focus what he does so well. He’s one of those directors that appeal to serious film buffs because the visuals are so brilliantly constructed. (Tarkovsky, Ozu, Kairostami, Hou Hsiao-hsien, and Wes Anderson are some other examples.)
Everything is negotiable. Challenge authority. You have the power in any situation. This is how to realize it and use it. A must-read classic from 1980 from a master negotiator. My notes here aren’t enough because the little book is filled with so many memorable stories — examples of great day-to-day moments of negotiation that will stick in your head for when you need them. (I especially loved…
This is a true marketing classic. Written originally in the '70s, this book has aged very well by explaining the most important part of your marketing plan: How you position your company and products. This book is filled with great examples that are easy to follow and understand. It all boils down to one thing: Be #1 at something.
Those who stick to the status quo will be left with average success at best. This book, by the one of the founders of Fast Company magazine, makes the case for this with some thought-provoking examples and stories.
If you're like me, I knew nothing about fonts, layouts or basic usage of text before I read this. This book uses great, full-color examples to explain the basics of designs. If you don't know the difference between a serif and a sans-serif font, this is a great place to start.
If you want to learn the art and science of copywriting, then this is the book for you. An expert copywriter for decades, Caples breaks down in detail what makes a great ad versus a failing one. It's loaded with examples and the kind of insights only a veteran can provide. You do need to provide a little imagination as he focuses on mail in based advertising in magazines, which isn't common today. But really, how different is that from downloading free whitepapers today?
If you want good, honest worked examples of practice problems, especially for calculus, it's hard to find a deeper well of examples than what this channel provides.
By contrast, humans can generally perform a new language task from only a few examples or from simple instructions - something which current NLP systems still largely struggle to do.
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.