> “As an aside, I think there may be an increased reason to use dynamic interpreted languages for the intermediate product. I think it will likely become mainstream in future LLM programming systems to make live changes to a running interpreted program based on prompts.”
Curious whether the author is envisioning changing configuration of running code on the fly (which shouldn’t require an interpreted language)? Or whether they are referring to changing behavior on the fly?
Assuming the latter, and maybe setting the LLM aspect aside: is there any standard safe programming paradigm that would enable this? I’m aware of Erlang (message passing) and actor pattern systems, but interpreted languages like Python don’t seem to be ideal for these sorts of systems. I could be totally wrong here, just trying to imagine what the author is envisioning.
What stack are you running? How do you guarantee sequential consistency of order numbers across your app server regions, cache layers and data lakehouse?
This. My new Samsung T7 SSD overheated and took 4T of kinda priceless family photos with it. Thank you Backblaze for storing those backups for us!
I missed the return window on the SSD so now have a little fan running to keep the thing from overheating again
Just another plus one for cast-iron pans and wooden spatulas. We’ve been using those for over a decade, 20 bucks each, never needs replacing, works for everything.
We switched from gas stove to induction and now they work even better since the handle doesn’t get as hot and it’s easier to control the temperature.
The whole seasoning thing is extra credit, the only failure mode I’ve seen is trying to fry an egg on a completely unseasoned pan, which just means some extra soaking and scrubbing is needed. The pan seasons itself after a few uses. Hand wash the pan instead of sticking it in the dishwasher, done.
According to Alan Kays 1971 description of Smalltalk:
“An object is a little computer that has its own memory, you send messages to it in order to tell it to do something. It can interact with other objects through messages in order to get that task done.”
Smalltalk concepts heavily informed the Service Oriented Architecture (SOA) tenets, e.g.
1. Services are autonomous - Cohesive single responsibility.
2. Services have explicit boundaries - Loosely coupled, owns its data and business rules.
Choosing good service boundaries is really crucial for a successful, resilient, maintainable system.
Interesting deck that shows moon caves are not a new concept at all. I’m surprised this hasn’t shown up in more sci-fi movies by now… slides 11 and 16 are quite compelling!
Now how do we know there isn’t anyone there already… ;)
We (the tech community) have spent 10+ years “growth hacking” entire populations, scaling up the web backends and personal devices capable of connecting that relentless growth into “users’ attention”. All that attention has to come from somewhere. There are only so many hours in a day; more virtual = less RL, human attention is a zero sum game.
Nice website with Ames Unitary Plan Wind Tunnel history: https://www.nasa.gov/nasa-ames-unitary-plan-wind-tunnel/