Loading video...

Video Failed to Load

Go Home

196,431 views • 1 year ago •via X (Twitter)

10 Comments

HyenaKripto's profile picture
HyenaKripto1 year ago

Grt > google

Alpha-Infinity's profile picture
Alpha-Infinity1 year ago

$GRT IS BARELY MID-CAP #CRYPTO: TIME 2 BUY. GRT GETS HOT DEC-FEB HISTORICALLY="#AMAZON OF QUERYING" & "#GOOGLE OF #BLOCKCHAIN" #WEB3+HUGELY UNDERVALUED #NVIDIA #Election2024 #HBAR #XRP #TREND #FOMO #TRADERS #FUTURE #VALUE #cryptocurrency #cryptos #hodl

Bao Anh's profile picture
Bao Anh1 year ago

to the moon

Dennoxxxx's profile picture
Dennoxxxx1 year ago

Very Good Explantation!

supriyadi Kaisar ꧁IP꧂ ✸,✸'s profile picture
supriyadi Kaisar ꧁IP꧂ ✸,✸1 year ago

to the sky..

YJ168's profile picture
YJ1681 year ago

GRT = GTR

TaparooSwap's profile picture
TaparooSwap1 year ago

Hey team! Our ETH <> BTC Bridge is live, and you’ve been selected to be onboard! Welcome to Bitcoin @graphprotocol 🧡

aysima 🍬's profile picture
aysima 🍬1 year ago

🚀🚀🚀🚀🚀

GRT-Bull's profile picture
GRT-Bull1 year ago

we need commercials on TV bro

Glen2Moon's profile picture
Glen2Moon1 year ago

Is GRT like a Web3 data highway toll?

Related Videos

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,089 views • 13 days ago