A student asked me about his old company's wiki, one page holding every feature and all the technical debt, updated again and again under the same name with only the version number changing. How do you keep that from poisoning the agent?
I do not know his company, so I could only give him the approach. You cannot fix anything that you don't understand.
Put a PhD in quantum physics in front of a symphony orchestra and hand him the conductor's stick. What is he going to do? He does not understand music, and his PhD is irrelevant there. Only the people who understand the context can do context engineering.
That is where the value has moved. Java is still the foundation, but knowing Java no longer impresses anyone on its own, because AI knows Java too. What impresses is understanding the business, how it works and what the strategy is, because that subject matter expertise gives you the intuition for what the agent needs to read.
If I go to Florida, I do not pack ski boards and a winter jacket. Hot climate, nice weather: linen clothes, sunscreen. I reverse-engineer the luggage from the destination.
You have to write the context for an agent that will test the checkout of a grocery app. The company wiki is two hundred pages. Where do you start?
Not on page one of the wiki. With an agent, the destination is the goal. Start at the destination, the checkout today and what it must do, and only then go to the wiki and take the pages that job needs, in their current version. That is the answer to the student too. Somebody who knows the product decides which version of that page is true today, and the agent gets that version and nothing else. The agent cannot make that call. Someone who understands the business can.