Disclosure: I was a founding member of the Python in Excel team and am looking for new problems that Python in Excel could solve.
2,512 karma · joined April 30, 2011
My alias is jflam (at the company I work for).
Disclosure: I was a founding member of the Python in Excel team and am looking for new problems that Python in Excel could solve.
You'll notice in their video [1] that they never show the prompts running interactively. This is for a roughly 800K context. They claim that "the model took around 60s to respond to each of these prompts".
This is not really usable as an interactive experience. I don't want to wait 1 minute for an answer each time I have a question.
I think about the cue as kind of being like "Hey Siri/Alexa/Cortana" but in reverse.
When I'm listening to someone else talk, I'm already formulating responses or at least an outline of responses in my head. If the LLM could do a progressive summarization of the conversation in real-time as part of its context this would be super cool as well. It could also interrupt you if the LLM self-reflects on the summary and realizes that now would be a good time to interrupt.
1. Interruption - I need to be able to say "hang on" and have the LLM pause. 2. Wait for a specific cue before responding. I like "What do you think?"
That + low latency are crucial. It needs to feel like talking to another person.
Some feedback:
Who is the customer for this? Can you describe what their day looks like and how Nino helps them get their work done better/faster/cheaper? What are the top 5 problems that they face that Nino is clearly better than the competition? Be specific and show the workflows.
Where do they work? Who do they collaborate with? What are they collaborating on? Do the same exercise - SxS comparison with how they do things in existing tools and show how Nino is clearly better than their existing solution.
Finally, don't ever underestimate how difficult it is to get people to change from whatever they are doing today. Today is not 1990 - people have been using solutions to the general information worker problem for decades now. Why will they switch?
$ ollama run mixtral
> So it really brings together many of the things that Intel is doing as an IDM, now bringing it together in a heterogeneous environment where we’re taking TSMC dies. We’re going to be using other foundries in the industry, we’re standardizing that with UCIe. So I really see ourself as the front end of this multi-chip chiplet world doing so in the Intel way, standardizing it for the industry’s participation with UCIE, and then just winning a better technology.
Edit: I see that it was shut down too.
The core functions of the device form factor formerly known as the cellphone, whatever we want to call it — the pocket device — what would you say the core functions are five years out?
at the centerpiece of Ben's argument is lovely.
I don’t know.
The reason I don’t know is because I wouldn’t have thought that there would have been maps on it five years ago. But something comes along, gets really popular, people love it, get used to it, you want it on there. People are inventing things constantly and I think the art of it is balancing what’s on there and what’s not — it’s the editing function.
Contrast it with Bill Gates' answer to the same question:
How quickly all these things that have been somewhat specialized — the navigation device, the digital wallet, the phone, the camera, the video camera — how quickly those all come together, that’s hard to chart out, but eventually you’ll be able to make something that has the capability to do every one of those things. And yet given the small size, you still won’t want to edit your homework or edit a movie on a screen of that size, and so you’ll have something else that lets you do the reading and editing and those things. Now if we could ever get a screen that would just roll out like a scroll, then you might be able to have the device that did everything.
It makes me reflect on how important it is to remain humble about the possibilities of AI and what developers can create using it (and the tools that they will use to create it). "And we are just getting started".
Today's LLMs are kind of like Dory from Finding Nemo - you have to recreate the context every time you do a slightly different task, or when the context window for the LLM is no longer sufficient to remember previous turns in a conversation.
An agent can sit on the other side of a piece of collaborative software that was designed for human collaboration. This is why chatbots are the current "killer app" for AI, we already understand how to collaborate with other people via chat.
Now imagine what we can do with more sophisticated pieces of software like Figma or Excel. Disclosure: I work on the Python in Excel feature and we just announced Copilot for Excel a couple of days ago. [2] Other modalities that excite me are tools like Vision Pro which will be an interesting test bed for multi-modal generative agents.
The next day there was an engineer sitting in the back of my car with a bunch of test devices capturing traces of the BT comms with the head unit. Apparently Subaru didn't sell enough units to warrant its own certification process for BT so this was the first time engineers had looked at it. IIRC it did get better a few updates later; it was maddeningly unusable out of the box.
Disclosure: I work on the design of the integration.
On versioning: we freeze the container image that your Workbook was authored against. You need to manually accept (and validate things continue to work) updates to that container image as we roll forward.
That only works if there is a forever fixed version of Python embedded in your game. The value of Python in this context is its ecosystem and folks will need to install additional packages and libraries into the execution environment. Now you're managing a local distribution of Python.
- We can guarantee a consistent experience for all users. Imagine having to maintain your own local distribution of Python and guaranteeing that it works with Excel as versions diverge over time? Yikes.
- We make it possible to share your Excel workbook with other users and have the calculation just work. That wouldn't work with random local installs of Python and users would be super frustrated by this.
- Security. Imagine opening an Excel workbook that can execute Python code running locally as you.
Also, I totally agree with your second point. Trying to write an internal app in Python that integrates with all of your existing IT infrastructure is an exercise in frustration at best. Excel is already part of the IT infrastructure virtually everywhere and is a programmable reactive canvas.
Disclosure: I work on the design team for the feature.