There is nothing wrong with promoting perspectives that have political commitments; in fact, intellectual diversity requires this, because some viewpoints include political commitments.
The reason I say that is there's a lot of programmers who are not very good product managers. Software is product management. What should it do? Who should it do it for? How should it do it? How should it look? What are our priorities? What do we start with first? What does version one include? All of those skills are not easily or equally distributed across all programmers.
Those include that having that sense of purpose, making sure that you have a network of people, that you're socially connected as your age, and also remaining curious, open to new ideas. Those factors turn out to be almost as important as some of the physical things we do.
Like the thing that I think is most likely to be sort of the bottleneck in terms of like the AI are really good at verifiable domains but not not at doing the actual thing is just like big experiments. You only get a few tries um well a few is maybe a bit understated but like basically like historically R&D has been driven by doing near frontier scale experiments and that has been pretty important and like actually doing the one big training run where you decide exactly what to include in that.
I mean, you could argue that we we're already past peak truth on the on the on the internet, right? And now there's there's just more and more garbage every every day. It gets harder and harder to suss out the stuff that you do want to include in the training set in order to actually make something more intelligent.
My daily drivers now include Amp, Cursor, and Claude Code. I still enjoy notebooks, but only for data analysis, machine learning, or other exploratory workflows where the iterative, visual nature of notebooks shines.
My daily drivers now include Amp, Cursor, and Claude Code. I still enjoy notebooks, but only for data analysis, machine learning, or other exploratory workflows where the iterative, visual nature of notebooks shines.
My daily drivers now include Amp, Cursor, and Claude Code. I still enjoy notebooks, but only for data analysis, machine learning, or other exploratory workflows where the iterative, visual nature of notebooks shines.
And in fact, I do like Moana very much. It’s my favorite film out of Disney Animated Studios in the last decade, and even (barely) edges out Coco when you include Pixar in the mix
Oulipo's co-founder Raymond Queneau has a book to include here called Exercises in Style (trans. by Barbara Wright), which retells an intentionally banal story 99 times.
So AI consumes approximately 0.04% of America’s freshwater if you include onsite and offsite use, and only 0.008% if you include just the water in data centers.
Does part of your work include designing, architecting, building, or thinking about how systems work? This book is a snarky look at all the reasons systems fail. The author has clearly lived a life in systems design and has no qualms about calling out all the obvious and not so obvious reasons an complex or complicated system struggles. My main qualm was it offered few solutions while pointing out problems.
Despite my aim to keep this list purely about math books, I cannot help but include this one in the list. Simply put, it's one of the most enjoyable textbooks I've ever read, giving a very satisfying first-principles understanding of what thermodynamic concepts like temperature and entropy really are, and how we can to understand them.
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.
I use my knitr package to generate reports directly from code (literate programming); the "reports" may include homework, blog posts, websites, papers and books.
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.