Just writing hand wavily :)
2,681 karma · joined March 5, 2009
Before: Founder @ Steamship. Head of ML @ Instabase, YC Alum (S15), PhD @ MIT CSAIL, Google Research
Contact: - @edwardbenson - edward.benson@gmail.com
Websites: - https://edwardbenson.com - https://robotbookclub.com - https://kaya-lang.org
Just writing hand wavily :)
- You want to find the min/max of some probability distribution P(x)
- P(x) is too complicated to find a closed-form min, but you can draw samples from it.
- So instead, you carefully construct some OTHER probability distribution Q(x|θ) that you claim is structurally similar "enough" to P(x), parameterized by θ.
- Now you find the theta which minimizes the KL divergence KL(P(x) || Q(x|θ)), which is equivalent to delivering you the parameters of θ to Q(x|θ) that make it [approximately] "most" similar to P(x) without ever having minimized P(x)
It was a trick that came up a lot when AI consisted of giant Bayesian plate models for each specific task that you had to hand-optimize.
- Drag the password window around the screen furiously
- Press Ctrl-Alt-Del as you did it
I think it would just dump you straight to the desktop.
I remember doing it in Circuit City as a kid to access computers.
We’re in the nascent stages but I think there will probably always be a community of folks who want to add more nuance to the communication, whether it’s reveries that enact a mood or goal, tie-ins to other services, etc.
Eg imagine wanting to have your ChatGPT DnD master also keep some kind of score. It may be ultimately easiest to put a wrapper around a themed GPT window that imposes a predictable way to do that rather than require everyone to figure out how to prompt it correctly.
We wouldn’t bat an eye at using S3, EC2, and RDS as a host your own setup. The only difference here is that startups are moving faster than incumbents.
FWIW that’s one reason why Steamship (disclaimer: I’m the founder) aggregates all AI services under a single API key and interface. It’s to deal with the insane glue-code hassle of running this stuff on your own.
I was just watching some of the Windmill videos (they're cool!) and am fascinated by the interplay between visual code blocks and code.
Selfishly, I wish there was a water cooler where those of us wrestling with these dev ux interfaces could trade tricks & hazards.
We're a hosting platform for AI Agents and in practice that means keeping track of a stream of usage events across agents, microservices (equivalent of Fly's VMs), and third-party services (OpenAI, Eleven Labs, D-ID, Pinecone, Replicated, etc) that roll up into an itemized consumption bill.
It might be this is just a super-niche billing situation, but we also haven't yet found an open-source solution that fits. Fully agree that a query layer atop a time-series database is the style of product that we're craving.
Metronome comes very close, but since it's not open source we're hesitant to make the jump before it's a perfect fit.
Congrats on the launch! It looks very cool!
The Agent & Tools metaphor makes a ton of sense for its simplicity, but has yet to scale beyond very simple agents.
I’m long on it as a programming model, but a lot of work is needed.
There are so many cities I've always wanted to walk down the streets of!
Both hard disks fried at the same time.
1) Develop ops-related software 2) Package it in a single Docker image 3) Let folks spin it up on-prem
I think the fist person to write a playbook for this kind of SaaS is going to get a lot of readers. From the outside, it seems like such a well-designed product strategy: all the benefits of enterprise, without the heavy integration burden.
Longer term planning, memory, etc?
Steamship is building Vercel for AI -- a platform for hosting the next decade of AI Apps.
Whether you're building ChatGPT bots, LangChain question-answering APIs, profile picture generators, or storybook writers, Steamship can host and scale it for you.
We are a seed stage startup, with amazing backing, only 4 folks currently.
You can email me ted(at)steamship.com
Someone once told me a curation was impossible to copyright for similar reasons.
I would far rather ask AWS: "Which ALB threw the error for the request to /foo/bar" than figure out how to put the dots together and discover myself.
In retrospect, that initial `ship try` CLI & those initial packages had too many moving parts for a first launch.
Part of what we're trying to do with this Prompt API template is strip things down to bare bones so that we can nail the basic "clone -> modify -> deploy" flow before layering back on bells & whistles.
If you're ever up for another go, give us a holler and we'll jump in if you hit snags like that again!
More broadly: there are a lot of moving parts to a production AI backend: vectors, LLM chaining, long-running async tasks, persistent state, data conversion, etc.
We're working toward a framework that lets you snap together those pieces at hackathon speed... and then translate it into a multi-tenant, auto-managed infra stack out of the box.
Right now our examples are pretty simple. But you can chain prompts manually and/or pull in services like DALL-E or voice gen.
We're working on the rails to do that in a way that'll scale well cleanly across API users of your app.
Especially for the set of problems with "Step 1: Hosting embeddings for some large corpus", it feels like there's a really useful role for offering static query/AKNN search atop popular datasets.
Re: DSLs -- what's the famous saying? "All services that survive eventually grow large enough to re-implement email"? :) We hear you though; if there's a way to support a standard QL atop the domain we're serving, we'll give it a good look.
Totally fair! In our case we're just trying hard to maximize product iteration cycles before we build out billing, etc.
If we just provided a way to pass through your own OpenAI key, does that work better for you?
We're working on the mechanics of deploying and scaling all the amazing prompt-based backends everyone is building --- chaining, prompt-search-prompt, image & audio generation.
This link is a simplified hosting harness we built building & launching a Python + Prompt API endpoint.
Anything in particular thing stopping you from shipping it online? Or just that it's not necessary for your use?
(Context: I've been working on `Heroku for LLM apps` and trying to understand where the value/frictions are)
I'm in the AI space like a lot of you. And while I've found the rate of change exciting, I've also found it disorienting.
So I created this Substack to help me process it.
Rather than try to tell you EVERYTHING that's going on, I pick a tight theme, find 5 cool projects related to it, and then unpack what's going on through that lens.
My goal is for it to be an editorial, of sorts, for fellow builders & investors. And a celebration of awesome projects no matter how large or small.
It’s been mostly great. Only downside is the server-side swift community is smaller than others, so you don’t get the deep software library selection something like Python would have.