eob

11 ms·

61.
by eob 4y ago
Thanks for the feedback!
62.
by eob 4y ago
Working on it! 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 AP
63.
by eob 4y ago
That "Ask the Bible" service that went viral the other day on Twitter had me thinking the same thing. Especially for the set of problems with "Step 1: Hosting embeddings for some large corpus", it feels like there's
64.
by eob 4y ago
Re: earning -- 100%. We'd love to talk to you if you've got thoughts / requests (crew@steamship.com). Re: DSLs -- what's the famous saying? "All services that survive eventually grow large enough to re-implement ema
65.
by eob 4y ago
Steamshipper here -- 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?
66.
Show HN: Deploy Button for GPT-3 API Back Ends(steamship.com)
75 points by eob 4y ago|23 comments
67.
by eob 4y ago
Steamship is Heroku for LLM apps. 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 simpl
68.
by eob 4y ago
Hey jcq3 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
69.
Show HN: Insults as a Service(steamship.com)
14 points by eob 4y ago|0 comments
70.
Shipped with AI – Weekly, focused AI commentary for builders and investors(shippedwithai.substack.com)
3 points by eob 4y ago|1 comments
71.
by eob 4y ago
Hey folks! 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 tha
72.
Show HN: An adaptive Chinese reader. Only helps where you need it(mandopando.com)
2 points by eob 4y ago|1 comments
73.
by eob 4y ago
We (steamship.com) use Swift on the server to power our Heroku-style AI apps platform. 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 som
74.
by eob 4y ago
If you can afford it, giving yourself a sabbatical is an incredible way to recharge. Everyone's financial / family / etc situation is different, so do what works for you, but I think there's actually a pretty broad range
75.
by eob 4y ago
I wrote a few scripts that power automatingpaperwork.com entirely from a set of Notion pages and it was the best “procrastinate writing by coding” project I’ve ever done. If anyone wants a copy of the code, feel free to reach out (contact d
76.
We stay productive as a remote-first startup(medium.com)
3 points by eob 4y ago|0 comments
77.
by eob 4y ago
We've built a hybrid database that federates workloads & queries atop both a relational & vector component. Right now we've got fairly limited interaction between those two halves of the brain, but it's one of the thi
78.
by eob 4y ago
We will! Part of what we're doing is building a platform that captures the broader lifecycle of tasks beyond "inference alone" -- things like data import, index building & maintenance, drift detection, corpus query.
79.
by eob 4y ago
Plug here from Steamship: if you're working on a project with audio/video and wanting some form of search, analysis, or triggering, we would really love to hear how you're thinking about it.
80.
by eob 4y ago
Steamship works a bit like the the heyday of jQuery plugins: File.import(url).transcribe('service').tag('service').query('..') Except instead of manipulating a web page like jQuery, it orchestrates remote NLP w
81.
by eob 4y ago
[Steamshipper here] We debated this a lot internally -- specifically whether we should pick a less charged initial dataset to experiment with. In the end, one of the reasons we decided to run with it was because we felt the controversy time
82.
by eob 4y ago
[Disclosure: I'm a Steamshipper] The similar thing this project has got me really wanting is the ability to find snippets of a topic across all the podcast archives I like. Sort of the podcast equivalent of falling into a Wikipedia hol
83.
by eob 4y ago
Thanks, Michael! I can't wait for Lumina Desk to come out :)
84.
by eob 4y ago
Thanks! And yes, the spaghetti code is a huge issue behind the scenes of production NLP deployments. We really hope this can make a huge dent in the problem. Right now we're aiming for self-service signups in October and then the first
85.
by eob 4y ago
It's been fantastic working with you all as well :-) We're huge fans!
86.
by eob 4y ago
Thanks! We're built atop AWS at the moment, but we're designed in a way that's friendly to cloud-agnostic / private-VPC usage down the road if that becomes critical. For now, we're focused on public API endpoints in
87.
by eob 4y ago
Hi folks! OP here. We're really excited about what we've been building and eager to get your feedback. We think developer usability is one of the biggest bottlenecks in AI today. It's easy to make an AI demo, but 100x harder
88.
Steamship: Heroku for Language AI(medium.com)
24 points by eob 4y ago|10 comments
89.
by eob 4y ago
Where are you seeing your UK claim in the first link? Those look like US - not UK - graphs, showing the trends in the opposite direction.
90.
by eob 4y ago
Oh interesting -- I didn't know any of the above Raymond controversy (or even really who he was; the name just is etched in my brain from that book) As a guy who found the Jargon File via that book, I'm grateful he did it. But I c

More ›