The online whiteboard of Kristofer Palmvik
The usefulness of domain knowledge suggests that human expertise will continue to be useful even as models get stronger. For many tasks, the human is the bottleneck, not the model, because the difficult part is in communicating to the model exactly what kind of solution the human wants. The information is “in the model” already, but it takes a very smart human to pull it out.
What happens when you challenge the received wisdom of Staging environments? What’s an even more effective way of testing updates without negatively affecting live customers? Here’s a few ideas.
Earlier today, I used Google Earth to conjure images of terrible things: office buildings on fire, mass destruction in San Francisco, a smoldering crater in place of the Eiffel Tower. I was able to because Google had just decided to integrate its AI image generator, Nano Banana, into the service, which has historically been used by people seeking satellite or aerial imagery of real-world locations.
A free, open-source way to identify color when color alone isn't enough. Each color gets a unique, memorable symbol. The full set covers base colors and combined colors built from their parent symbols.
The guard I wrote used a public 'data' listener on the idle socket. node-fetch@2 inspects socket.listenerCount('data') to infer stream state, and with my listener attached it observed a count greater than zero during response close and reported false ERR_STREAM_PREMATURE_CLOSE errors. Because it landed in a coordinated security release across 22.x, 24.x, and 26.x at once, the blast radius was immediate and wide:
Chrome Canary recently added new methods for streaming HTML into the DOM. The streamHTML method, for example, will stream the HTML into the targeted element, replacing any previously existing contents.
No Wi-Fi? Claude outage? Rolling blackouts? The end of civilization as we know it? With CrankGPT, you'll never be without the intelligence you need. We're no preppers, but with CrankGPT, we're prepared.
Pasting a massive AI-generated response into a chat or email where a human would write one sentence. It destroys the medium itself. Nobody writes essays in Slack. It's only possible because of AI copy-paste.
There is a yawning chasm opening up between…oh, let’s call them the enthusiasts and the skeptics, although the battle lines are drawn in many different ways. Both groups are tense, frustrated, and a little scared, and as a result, they have stopped talking to each other. Instead, they talk about each other — as roadblocks, as caricatures, as threats. It’s all, “THOSE people are AI-pilled and don’t understand software”, vs “THOSE people hate AI and don’t want to move fast.”
The defect is the missing relationship between the code and the minds that own it. Absence, negative space. This is the cord to pull: “I can’t vouch for this”, not “this is broken”. The response should be the same though: stop the machine, and swarm. Not async, and not one team member carrying the cost of honesty. Shared understanding is owned by the team, not any one individual, and the team should fix it together.
5303 links collected between and