stanleydrew
Joined 17 years ago
Karma
8,502
Submissions
1,970
Member since
Apr 22
Recent submissions
Comment · 1 year ago
> Still, my point is that my parking space isn't actually mine, so I can't modify anything in the garage.
Presumably over time shared parking areas will get upgraded with charging infrastructure to keep attracting tenants.
Comment · 1 year ago
> idk why we need MCP servers when LLMs can just connect to the existing API endpoint
Because the LLM can't "just connect" to an existing API endpoint. It can produce input parameters for an API call, but you still need to implement the calling code. Implementing calling code for every API you want to offer the LLM is at minimum very annoying and often error-prone.
MCP provides a consistent calling implementation that only needs to be written once.
Comment · 1 year ago
Technically it's not really much different from just giving the LLM an OpenAPI spec.
The actual thing that's different is that an OpenAPI spec is meant to be an exhaustive list of every endpoint and every parameter you could ever use. Whereas an MCP server, as a proxy to an API, tends to offer a curated set of tools and might even compose multiple API calls into a single tool.
Comment · 1 year ago
> I have a silly theory that I only half joke about that docker/containers wouldn't've ever taken off as fast as it did if it didn't solve the horrible python dependency hell so well.
I don't think this is a silly theory at all. The only possibly silly part is that containers specifically helped solve this problem just for python. Lots of other software systems built with other languages have "dependency hell."
Comment · 1 year ago
> Is this just junior devs who never learned it
Seems more like it's fallen out of favor with senior devs who have moved to Go/Rust.
Comment · 1 year ago
What risk do you foresee arising out of perverse incentives in this case?
Comment · 2 years ago
Also means you're not having to do a bunch of isolation work to make the server-side execution environment safe.
Comment · 2 years ago
One of the design principles of sqlc is that SQL queries should be static in application code so that you know exactly what SQL is running on your database. It turns out you can get pretty far operating under this constraint, although there are some annoyances.
Co-founder and CEO at Riza, a company working on untrusted code isolation with WASM: https://riza.io / [email protected]
Previously COO at ngrok: https://ngrok.com.
I was the Founder and CEO of an MVNO/VoIP hybrid company called Charge (formerly known as Bolt): https://charge.co.
I worked at Twilio: https://www.twilio.com.
I wrote the original ruby library that wraps Twilio's HTTP API: https://github.com/twilio/twilio-ruby
Other projects include receive-only telephone numbers at https://oneway.tel and free HPKP report bin hosting at https://hpkp.org (now defunct).
[ my public key: https://keybase.io/andrewmbenton; my proof: https://keybase.io/andrewmbenton/sigs/m4O8mq4uxoPSm2XlB1RUT1XkH5v8KX7UR448y8T74mo ]