One of the reasons that you don't see hotspot optimization as a thing that really matters that much anymore and one of the reasons I advise that architecture and and not making bad decisions is much more important is because a lot of libraries already have been optimized for you that you might use.
A big-enough random reversible circuit is plausibly a secure cryptographic permutation, a big-enough random irreversible circuit degenerates into having only a few possible outputs.
Performance tests are highly specific and dependent on the exact machine it runs on, the exact third party libraries and their versions that are used, the other components involved in the tests, such as the servers, and more.
we find that the performance on held out tasks decreases dramatically. Whereas if we um just take out a random 20% of the data that's less diverse than the most diverse subset, the performance um only decreases a little bit. And so this suggests that actually having really diverse data plays an important role in enabling it to generalize to new tasks.
It was just better than all the competition. It was faster. It was smaller. Um it was more interactive and it was also cheaper. So, it was like 10 times better at a tenth of the price of the of the competition, right?
That was always the idea, and that that goes back even to the predecessor of Turbo Pascal, this idea that it's not just a compiler. It's an experience, right? I mean, you don't just compile your programs. You also edit them. You also run them. You also debug them. You also have a runtime library. It all has to like fit together.
Um and then they can kind of suggest random things and it it but it it it um often I find that trying to chase them down and make them work and find they don't work, it wastes more time than it saves.
We show that equilibrium generically occurs at neither the Harberger nor Glaeser-Luttmer benchmark. Cost-minimizing suppliers drive allocations to vertices, not interiors. Corners are not an assumption but an outcome about what cost-minimizing suppliers choose. The correct benchmark is corners, not random, and corners generate qualitatively different welfare properties: losses far larger than either efficient or random distributions, and discontinuous jumps from small parameter perturbations.
but ice sort of forms through a process of random nucleation and then extension. And this is cool because you can uh modulate the like sort of nucleation the rate of nucleation and extension to then modulate the probability of ice formation.
If you're a paper towel demon and feel guilty about it, I can't recommend these enough. Perfect for cleaning counters and random floor messes (talking to parents).
Anna Karenina by Leo Tolstoy: Made the random choice to listen to this and loved the experience (especially for getting through some of the boring parts, sorry). Shout out Maggie Gyllenhaal.
If you do too much exploration, you can have your team feel a little bit too scattershot, just trying a 100 different random ideas. What's the through line? What's the strategy? How do you pattern match, you know, successes across them? And if you do too much in exploitation, which is often the MMO of growth teams, it can lead to this like saturation and stagnation where you're just locally maximizing a thing.
Tweets from 1765-1799 by a 4’9” hunchback physicist, friends with Goethe and Kant, admired by Nietzsche, Schopenhauer, etc. Such wonderful random thoughts, beautiful perspectives on thinking for yourself, observing nature, language, freedom, philosophy, religion, and more. Hundreds of initial insights, especially inspiring because they’re undeveloped.
A surprising number of my favorite books were not meant to be published. They were private notebooks, or fragments from works-in-progress that never got finished: among them Pascal's Pensées, Simone Weil's private essays, Lichtenberg's waste books, Herzog's Conquest of the Useless, Kafka's diary, Joubert's Carnets, Wittgenstein's Brown and Blue Notebooks, and Sei Shōnagon's Pillow Book.
A surprising number of my favorite books were not meant to be published. They were private notebooks, or fragments from works-in-progress that never got finished: among them Pascal's Pensées, Simone Weil's private essays, Lichtenberg's waste books, Herzog's Conquest of the Useless, Kafka's diary, Joubert's Carnets, Wittgenstein's Brown and Blue Notebooks, and Sei Shōnagon's Pillow Book.
A surprising number of my favorite books were not meant to be published. They were private notebooks, or fragments from works-in-progress that never got finished: among them Pascal's Pensées, Simone Weil's private essays, Lichtenberg's waste books, Herzog's Conquest of the Useless, Kafka's diary, Joubert's Carnets, Wittgenstein's Brown and Blue Notebooks, and Sei Shōnagon's Pillow Book.
A surprising number of my favorite books were not meant to be published. They were private notebooks, or fragments from works-in-progress that never got finished: among them Pascal's Pensées, Simone Weil's private essays, Lichtenberg's waste books, Herzog's Conquest of the Useless, Kafka's diary, Joubert's Carnets, Wittgenstein's Brown and Blue Notebooks, and Sei Shōnagon's Pillow Book.
A surprising number of my favorite books were not meant to be published. They were private notebooks, or fragments from works-in-progress that never got finished: among them Pascal's Pensées, Simone Weil's private essays, Lichtenberg's waste books, Herzog's Conquest of the Useless, Kafka's diary, Joubert's Carnets, Wittgenstein's Brown and Blue Notebooks, and Sei Shōnagon's Pillow Book.
This is getting easier in the lastest versions of Fedora and Ubuntu (e.g., Ubuntu 24.04 LTS) which are shipping system libraries with frame pointers by default.
And this is important, so yes, you should expect legs or jointed sticks, how many joints they're going to be? Anybody's guess. Do you expect humanoids, things with a sensing apparatus on top of a shoulder with two arms and two legs? That's probably a pretty random set of occurrences that led to that.
An eye-opening view on considerations going into building a widely used public API or reusable library. While the book focuses on the .NET framework, many of the conventions apply to maintainable and reusable components, in general. This book had an outsized impact on me as I read it when I was a mid-level .NET developer.
Physics hardly even acknowledges that the universe is random at its base. We like to think we live in a deterministic universe and everything’s deterministic. But I think that’s probably an artifact of the way that we’ve written down laws of physics since Newton invented modern physics and his conception of motion and gravity, which he formulated laws that had initial conditions and fixed dynamical laws.
It’s the fact that you’re a deterministic structure living in a random background. And also, all of that selection bundled in you allows you to select on possible futures. So that’s where your will comes from.
Friedman’s focus on the money supply has not held up, as Samuelson suggested, but the alternative Keynesian macro models recommended by Samuelson in the same interview have not done better and they were not outperforming simple random walk models of predicting the macroeconomic future.
Hell even worse, a lot of the libraries that underpin the fabric of what we all call the digital economy have trouble getting enough money to pay for food.
Did you know, the tests you write with react-testing-library look almost identical to the tests you write with vue-testing-library. Magic things happen when you don't test implementation details. :)
Most of the code I write is in C++, although I've written fair amounts of code in Java, Python, Perl, Self, Cecil, x86 assembly, and Pascal over the years.
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.