Edwin K

+1 for "context engineering" over "prompt engineering". People associate prompts with short task descriptions you'd give an LLM in your day-to-day use. When in every industrial-strength LLM app, context engineering is the delicate art and science of filling the context window with just the right information for the next step. Science because doing this right involves task descriptions and explanations, few shot examples, RAG, related (possibly multimodal) data, tools, state and history, compacting... Too little or of the wrong form and the LLM doesn't have the right context for optimal performance. Too much or too irrelevant and the LLM costs might go up and performance might come down. Doing this well is highly non-trivial. And art because of the guiding intuition around LLM psychology of people spirits. On top of context engineering itself, an LLM app has to: - break up problems just right into control flows - pack the context windows just right - dispatch calls to LLMs of the right kind and capability - handle generation-verification UIUX flows - a lot more - guardrails, security, evals, parallelism, prefetching, ... So context engineering is just one small piece of an emerging thick layer of non-trivial software that coordinates individual LLM calls (and a lot more) into full LLM apps. The term "ChatGPT wrapper" is tired and really, really wrong.

The deal is now confirmed. $32B in CASH. Biggest deal in Google/Alphabet history.

After advising 50+ consumer companies over the last year, the one thing that separates those who can execute and those who can't: Having a full-time designer in the room at all times I've met with countless companies that have raised millions—and even one that has raised billions—that do not even have a designer on payroll. This makes product development broken: 1/ You simply cannot have constructive conversations about ideas without visualizing them in real-time 2/ Your experiments will frequently have inconclusive results because users cannot discover features or they misunderstand how they work 3/ There is no one who can galvanize the team with a vision of what the product could look and feel like And to be abundantly clear: I'm not referring to visual UI or graphics. I'm talking about someone who can think through the fundamental building blocks of product comprehension—like navigation, interaction and copywriting—and is technically savvy enough to visualize those components in high resolution. There can certainly be exceptions to not having a designer, like where the CEO is an exceptional visual thinker, but that does not scale beyond a small team. At the end of day, products live and die in the pixels: it's what the users see and tap. And without someone shepherding that process, you are effectively wandering the desert blind.