2 ms·
Nah ! I am not convinced that context engineering is better (in the long trem) than prompt engineering. Context engineering is still complex and needs maintaina
by truth_seeker 1y ago
Nah ! I am not convinced that context engineering is better (in the long trem) than prompt engineering. Context engineering is still complex and needs maintainance. Its much lower level than human level language.
Given that domain expertise of the problem statment, we can apply the same tactics in context engineering on higher level in prompt engineering.
- hnlmorg 1y agoThis whole industry is complex and needs constant maintenance. APIs break all the time -- and that's assuming they were even correct to begin with. New models are constantly released, each with their own new quirks. People are still figuring out how to build this tech -- and as quickly as they figure one thing out, the goal posts move again. This entire field is basically being built on quicksand. And it will stay like this until the bubble bursts.
- truth_seeker 1y agoAgreed. but making ENGLISH or any human speakable language as main interface shoul be given highest priority IMHO !
- CharlieDigital 1y agoGoing to disagree here. Early in the game when context windows were very small (8k, 16k, and then 32k), the team I was working with achieved fantastic results with very low incidence of hallucinations through deep "context engineering" (we didn't call it that but rather "indexing and retrieval"). We did a project for Alibaba and generated tens of thousands of pieces of output . They actually had human analysts reviews and grade each one for the first thousand. The errors they found? Always in the source material.
- truth_seeker 1y agoAre we on the same page ? Whats really stopping you to parse and prioritise CUSTOM CONTEXT if given as text instruction in prompt engineering.
- CharlieDigital 1y agoThat's why indexing and retrieval is perhaps the better term. Custom context doesn't exist unless a team makes it so.