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.
the jev release is giving react major version drop vibes. just a massive crashing wave, everyone rethinking fundamental stuff and thinking through the implications of a novel new primitive.
I do not think those running the government testing understand what is going on, and believe they are reacting basically on vibes and what various trusted people tell them.
It's important to do things fast You learn more per unit time because you make contact with reality more frequently Going fast makes you focus on what's important; there's no time for bullshit
AI may help an oil company emit less pollution per barrel of oil. But if the company is producing more barrels than it otherwise would have, total emissions can still rise.
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.
if you are using these systems right you can just grow more quickly you can build more things you can take on more stuff so you know I would be surprised actually if we ended up with like net fewer
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
Yeah, I mean I think if you looked at what is important in AI systems these days, you would want to know things like the bandwidth between you know your main memory system on your accelerator to the onchip memory to the um you know the multiplier unit or whatever. You want to know how much energy does it take to do a single multiplier operation.
I I think this is sort of the crazy thing about building on models. It's just so different than all the engineering that I've ever done. Like in the past when you built on systems, you built these like big beautiful systems and you really think about the system design up front. You have like a big suite of unit tests. You think about everything and you know, like a re-architecture is a big project.
LG or Mitsubishi air conditioning in EVERY room, both cooling/heating, every unit should have its own outdoor unit, or you get annoying things like you can't cool one room and heat the other at same time! I think they're called mono splits
LG or Mitsubishi air conditioning in EVERY room, both cooling/heating, every unit should have its own outdoor unit, or you get annoying things like you can't cool one room and heat the other at same time! I think they're called mono splits
We kind of expect that we can go to work and we can work really hard for eight hours straight during the day, but like the brain doesn't really work like that.
the problem with training models on maintainability is like the cost function of bad architecture and bad program design can't be evaluated by running the unit test because it hits you 3 to 6 months later
yes it will catch things and it will raise your floor but I don't believe like the model writing the code is the same model reading the code and if you ask a model hey is this code good it's going to be like oh yeah it's great comprehensive it's got unit tests
Then you had code review which gave you another level of feedback. You could roll out internally more frequently. And everybody was using Facebook for all kinds of stuff, personal and internal business stuff. So whatever feature you developed, people would start using it immediately. So you get another round of feedback. Then we had this phased roll out process where you'd start rolling your stuff out. If there was a problem, the blast radius would be limited to a a few million people.
So beforehand because of this social divide between programmers and testers. There was a lot of incentive for the testers to have their own language. This is my tool. I know how to run it. I'm going to run it.
Um but it would be possible and it would have been possible for somebody to disprove the erdos unit distance conjecture before we did using a general purpose model. And nobody had explored sufficiently what happens if I put $100,000 worth of compute into 5.5 what could it do?
rather than studying the specific diseases we think that by trying to understand inflammation more broadly that will make it so that other companies that can then use these tools can work on specific therapies.
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.
So, here I actually think it's even stronger. The thing with C++ is that if you make a mistake, right, in in JavaScript, maybe you take down your server, which is already bad enough, but in C++ when you make a mistake there, now it's actually a security vulnerability most of the time.
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.
So that's unfortunate, and that's why some environments like Go, for example, has has Go routines and green threads, which are really language emulated lightweight threads that kind of do what I'm talking about, but but at a much lower cost. But you avoid the function coloring. So there is a bunch of different things, but but you know, but for an environment that already exists like JavaScript or like C# and and the Windows event loop and and whatever, this this was the right solution.
And we we full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No. No one was going to come. It had to be open source. There was just no two ways about it, right?
So, if we're checking 99% instead of 100%, well, heck, that's better than the 0% that JavaScript checked, right? And it gives you like language features that no other languages can provide because they can't get to 100%.
As the software industry is largely driven by trends and fashion, React's "cool factor" led to a mass amnesia regarding how to make normal, well-designed web apps made of HTML with a sprinkling of scripting on top and everything became one big tangled, brittle mass of Javascript that completely keeled over when scripting wasn't available.
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.
Our market reach is far greater than any any TPU can any ASA can possibly have. And so if you look at our position, uh we're the only company that that accelerates applications of all kinds.
none of us wanted to go through that extreme but lots of time when you are under a lot of pressure and no time to react other than just to survive that scale that keep on coming at you, you have to make uh decision that increase uh speed and velocity because speed and velocity allow us to build quick enough to survive
Worse, you realize that the gazillions of unit, snapshot, and e2e tests you had your clankers write are equally untrustworthy. The only thing that's still a reliable measure of "does this work" is manually testing the product.
and even if you take a generous interpretation of 128 * 8 gig transfers, you're at 128 gigabytes a second for the same shoreline versus 2 and a half terabytes a second. There's a there's an order of magnitude difference in bandwidth per edge area.
Expectation: the age of the IDE is over
Reality: we’re going to need a bigger IDE
(imo).
It just looks very different because humans now move upwards and program at a higher level - the basic unit of interest is not one file but one agent. It’s still programming.
To be clear, speed in itself does not mean labor markets and employment won’t eventually recover, it just implies the short-term transition will be unusually painful compared to past technologies, since humans and labor markets are slow to react and to equilibrate.
elements, JavaScript reigns supreme. SvelteKit's efficiency and reactivity make it my framework of choice, and TypeScript's type annotations bring a welcome layer of confidence to my codebase.
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.
Data centers are so much more efficient with their water that they generate 50x as much tax revenue per unit of water used than golf courses in the county:
So the Navy hired the shoe runners unit from the SS, paid them money, and then gave them drugs, different kinds of drug combinations, methamphetamine combined with cocaine and chewing gum and all kinds of things. So this is a big thing, you know. And there are documents to it.
And it sort of fits with the way I think about physics in general, which is that I think information is primary, information is the most sort of fundamental unit of the universe, more fundamental than energy and matter.
I used to think it required more churn to get progress to stay on the leading edge of new stuff. And I wrote this before I experienced the indignity of the 2010s in the JavaScript community.
If a new monetary network with its own unit (i.e. not pegged to an existing currency as a credit rail on top of it, but rather a fully parallel system to central banks) is going to bootstrap from zero to massive, it requires upward volatility.
But the metaverse and 3D gaming in general needs something that's rather more powerful, more safe, more scalable, and more capable than JavaScript because the metaverse is actually a more difficult technical problem than a webpage.
As a Python and JavaScript programmer my favorite models right now are Claude 3.7 Sonnet with thinking turned on, OpenAI’s o3-mini-high and GPT-4o with Code Interpreter (for Python).
But really the software engineering agents I think can be done faster sooner than any other agent because it is a verifiable domain. You can always unit test or compile, and there's many different regions of it can inspect the whole code base at once, which no engineer really can.
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.
Before this book I used to think that Javascript is "bad" or a "hacky" language. This book changed my perspective, understanding some tradeoffs and some remarkable strengths of this weakly typed language that is starting to take over the world. Note that this book is now dated
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.
when you send someone a link to a post, they can't read it without loading the entire Mastodon frontend app into their browser, which will is a monster React codebase that will break if they have scripting disabled and also can take up to 30 seconds on older hardware.
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.)
What is the weakness of Google is that any ad unit that’s less profitable than a link, or any ad unit that kind of disincentivizes the link click is not in their interest to go aggressive on, because it takes money away from something that’s higher margins.
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
Yeah, it is interesting because, when people react against you by saying you are being arrogant about this, 99.999% of the time, all they mean is I disagree. That’s all they really mean, right?
Nelson Villoria estimates that for every 1% gain in Total Factor Productivity (inputs required per unit of output) in the US, croplands in the rest of the world shrink by 0.7%.
One thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.
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…
RSC is the future of React. The React team has made this very clear and we are lucky to be in touch with their amazing team members to help us along this path.
The drone-like architecture of the multicopters is simple, but as the rotors are responsible for keeping the unit at a constant altitude with hover power, they represent an energy-intensive version of VTOLs. Their range is, therefore, short, typically less than 20 miles.
I have argued that the probability of a bad equilibrium is only marginally influenced by the level of debt, but can be much reduced by a contingent rule making the primary balance react to an increase in debt service.
Multipliers are likely to vary a lot over time and space, but the bulk of the evidence is that they are different from zero, positive for spending, negative for taxes, and that they are stronger when monetary policy does not or cannot react to fiscal policy.
Arguably the single unit on this entire post with the most bang for the buck, the COROS Pace 2 is a full multisport watch that can do swim/bike/run/triathlon, but even more than that
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.
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. :)
I use a Chili Pad to be cold while I sleep if I can't get the room cold enough, which is great but loud (I set it up to have the cooler unit outside my room).
Visual Studio Code is the go-to editor for some complex languages like React using JSX or TypeScript and I finally agreed with Wes Bos that VS Code is better for development of React JS.
I really like Mac Minis for installations, especially since once we've got the headsets running we can unplug all external keyboards and projectors and everything, and it'll run as a self-contained unit for days on end (or until Apple decides it must interrupt with a request to update).
JavaScript allows us to mask network latency altogether. Applying this as a design principle should even remove most spinners or “loading” messages from your applications.
This is crucial for efficiency, because if you only have one example, or worse, no examples (in the case of code written preemptively), then you are very likely to make mistakes in the way you write it and end up with code that isn't conveniently reusable.
For text editing that is not specifically related to programming the Mac and iOS, I rely heavily upon BBEdit, where I do most of my Python, HTML, JavaScript and PHP editing.
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.