Загрузка видео...

Не удалось загрузить видео

На главную

New chapter! Context problems. Who can solve these by hand ✍️? Download PDF: The first five: 1. Mark the context: the window as cells you can count 2. What fills the window: the system prompt, the user, the model's reply 3. Turn by turn: every turn is the same...

11,641 просмотров • 18 дней назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Naval Ravikant on the importance of hiring high-agency people Naval defines agency as: “People who just solve problems without even being asked to solve the problem—they identify the problem, they go solve it, they don’t even necessarily have to update you every step of the way, they’re not asking silly questions, and they’re just coming up with solutions.” He believes this is important because “building a startup is an infinite set of problems that are being thrown at you.” And there comes a day where you can’t even look at every problem your company is facing—let alone solve every one of them. He cites the Vinod Khosla aphorism: "The team you build is the company you build, not the plan you make.” And your ability to solve problems is based entirely on how many problem-solvers you have at your company. As Naval puts it: “If you have somebody who takes 10% of your time and management to solve problems, you can only have 10 of those people working with you. But if somebody takes 5%, you can have 20 of those people.” When building Airchat and AngelList, he thought of each team as a Navy Seal team: “Everyone is just really good at what they do. They know their job. They do it. They don’t complain. They’re not egotistical about it. And if they have to constantly be corrected, led around by the nose, you have to clean up after them, or you question their judgement, it’s not going to work out.”

Startup Archive

552,837 просмотров • 2 лет назад

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 просмотров • 1 месяц назад

How Jason Calacanis Got Claw-Pilled: An AI Agent Prompted Itself to Build Him a CRM in Seconds “ The moment I became Claw-pilled, I was like, ‘Hey, I want to build my network, I know these 20 people in Japan, I had dinner with them during my recent trip, I want to know who they know, so check out LinkedIn and other things, and who they're associated with, and make me a mind map of it, and then the next trip I want to meet with the next circle of those connections.’” “It's like, ‘Okay, I got the results,’ and it said, ‘Where do you want me to put them?’” “I was like, ‘Well, where can you put them?’” “And it said, ‘I can put it in a Google sheet, I can put it in a Notion table, I can put it here, I could give you a PDF, I could give you a CSV file, or I could write you a CRM.’ And I was like, ‘Yeah, sure, make me a CRM system…’ and it made a CRM system.” “I think maybe 1/1000 people working with AI have had that experience. Maybe it's 1/10,000, where your agent says, ‘I'll make you bespoke software.’ The context is so good because the memory's getting better. When did that happen?” Perplexity CEO Aravind Srinivas: “I think it happened with Opus 4.5. That was the inflection point when models started being amazingly good at orchestration, and reasoning, and tool calls.” “The models started becoming very good at handling the context, so the context window no longer became a problem, and that made it suddenly so good at doing very long orchestration tasks.” —------------------------------------------ Our episode is sponsored by the New York Stock Exchange - a modern marketplace and exchange for building the future. It all happens at the NYSE 🏛 -

The All-In Podcast

170,961 просмотров • 5 месяцев назад

Linus Torvalds, creator of Linux, on why AI is both a bubble and a revolution at the same time: His answer refuses the binary, laying out why both things can be true at once: "I mean, clearly, it's clearly both, right? It's clearly a bubble and at the same time, it's very interesting and I think it will change society and I think it will change how most skilled jobs get done." But he pushes back on the maximalist framing: "At the same time, I don't think it's as revolutionary as people make it out to be." When asked about artists being angry that AI models were trained on their work without consent, Linus is blunt: "That's reality. Deal with it. That genie is out of the bottle. You're not getting it back. And you're not getting it back whether you are a photographer who's out of work… or you're a programmer that has to learn to deal with a new reality." On programming specifically, he's more optimistic, though he has a sharp caveat about vibe coding: "I really think that AI will be a tool and it will make people more productive. I think that vibe coding is great for getting into programming. I think it's going to be a horrible thing to maintain." His conclusion is that programmers aren't going anywhere: "You still want to have the people who know how to maintain the end result." Linus separates the technology from the noise around it: "I'm a huge believer in AI. I'm not a huge believer in the whole things going on around AI. I find the marketing and the market to be sick and twisted and there is going to be a crash and it's not… it's going to be ugly."

Big Brain AI

52,726 просмотров • 3 месяцев назад