惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
博客园 - 司徒正美
Last Week in AI
Last Week in AI
博客园 - 聂微东
Jina AI
Jina AI
月光博客
月光博客
爱范儿
爱范儿
美团技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Hugging Face - Blog
Hugging Face - Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 叶小钗
T
Tailwind CSS Blog
博客园 - 【当耐特】
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Apple Machine Learning Research
Apple Machine Learning Research
有赞技术团队
有赞技术团队
罗磊的独立博客
小众软件
小众软件
雷峰网
雷峰网
IT之家
IT之家
大猫的无限游戏
大猫的无限游戏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
V
Visual Studio Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Don't worry, you are not in danger
Dominik Seifert, Ph.D. · 2026-06-15 · via DEV Community

Dominik Seifert, Ph.D.

We went from "prompt engineering" to "context engineering" to "let 'er rip" in less than 2 years.

"Prompt engineering" always sounded cheesy to us "converted engineers": that's not real engineering. It's "fiddling" at best. But is it all that trivial? Probably.

Soon after came "Context engineering": The idea that working with an LLM is not about one message, a "prompt" that we send out as the singular input of our request. Rather, we should manage and "engineer" the entire bulk of the "conversation", build up a cohesive structure, compress and filter out the noise while avoiding falling into the deep pits of the "telephone game" as we take many turns to solve a complex problem.

Just a few short months later, and Ralph is taking the wheel. "Harness engineering" entered the realm. Just let the LLM do it all: let it bang its proverbial head against the wall again and again, keep track of its own outcomes and let it learn as it goes. With the added twist that the learning gains are not that of Lisa Simpsons but rather that of Ralph Wiggum. RL but it escaped the labs, and instead of steroids we put it on Xanax.

This is how we can solve all problems now. Nothing to worry about here.

"But wait there is more." Let's not call it Ralph, because that would literally sound stupid. Instead, let's rebrand it as "loop"ing. And instead of building the loop ourselves, let the LLM write the loop, build the harness, and figure out all the difficulties there.

Even more complex. Even more layers of abstraction and momentum build-up, an even longer horizon whose trajectory absolutely no one can predict anymore, all the while adding variables to account for and even more cognitive holes for the LLM to fall into.

According to Boris Cherny: That's it. Coding is solved. Uninstall your IDE now (and not at a later point when this is proven to work) because the AI is taking care of everything now.

Don't worry, even though it has all your API keys, partial access to prod and full access to your CI via pipeline files, I'm sure it won't abuse any of that.

Let the LLM do it all while you get your beauty sleep. Sweet dreams.

Original published at: https://www.linkedin.com/posts/dominik-seifert-phd-8b663b54_we-went-from-prompt-engineering-to-context-share-7472275432722169856-x8R_/