I think the building blocks of the most impressive experiences will come from choosing the exact right point to involve an LLM, the orchestration of the component pieces, and the user experience.
That's certainly what I found in games. The games which felt magic to play were never the ones with the best hand rolled engine.
The tools aren't there yet to ignore prompts, and you'll always need to drop down to raw prompting sometimes. I'm looking forward to a future where wrangling prompts is only needed for 1% of my system.
It's always true that you need to drop down a level of abstraction in order to extract the ultimate performance. (eg I wrote a decent-sized game + engine entirely in C about 10 years ago and played with SIMD vectors to optimise the render loop)
However, I think the vast majority of use cases will not require this level of control, and we will abandon prompts once the tools improve.
Langchain and DSPY are also not there for me either - I think the whole idea of prompting + evals needs a rethink.
(full disclaimer: I'm working on such a tool right now!)
For UK people there's Lollipop: https://lollipopai.com (full disclaimer: I'm a co-founder :)
It's integrated with Sainsbury's with one-click basket transfer, an option to remove items you already have, and a recipe uploader for your favourites. Early days so feedback really welcome.
Lollipop is making the mundane magical. We are cooking up the fastest and most enjoyable online grocery shopping and cooking experience in the world, helping busy families and those overwhelmed by the pressures of daily life.
We building a product that doesn't just look after everyone but our planet too. Helping to reduce the £10 billion of food waste thrown away every year is a huge priority for us.
Our diverse founding team of 17 have built businesses such as Monzo, Amazon, Curve and our backers have scaled companies like Ocado, Innocent, Babylon and Deliveroo. We know what it takes to build products enjoyed by millions of people across the world.
You'll work in a small tight-knit semi-autonomous cross-functional product squad, iterating useful, usable, and delightful experiences on web and mobile.
Our tech:
* Hotwire (Stimulus/Turbo), Rails, PostgreSQL, Flutter for mobile
Postscript: The idea was to put to bed some of the endless Scrum vs Kanban debate. Processes have to be adapted for use: hardly anyone says this, because people get paid to say the opposite.
Gower Street | REMOTE (UK-based) | Full-time | Developers/Data Scientists
Gower Street Analytics is a startup in the movie business, using Clojure to do data science.
We mostly code in Clojure, ClojureScript and Python. We use Postgres and CSVs in S3 for persistence, and host services with Docker, Terraform and AWS.
We’re growing the team carefully and interested in meeting developers and data scientists at all levels of experience. We’re committed to being an equal opportunities employer and are actively looking to increase diversity.
Yeah, thanks for linking to this: the reason I didn't use it was mostly because it was longer than 18 lines :) Nice not to have to track and maintain a version of other people's code when you don't have to.
> The final puzzle piece
...to what? That's what I'm worried about!