context clarity as bottleneck

3 articles · 10 co-occurring · 0 contradictions · 0 briefs

Booch's observation that 'the No Engineer is explaining why something can't be done while the Yes Engineer has shipped' is a concrete example of clarity (having a clear problem + authority to solve it

Related concepts

workflow automation 2 prompt engineering vs context engineering 1 prompt engineering 1 organizational context management 1 organizational ai adoption curves 1 llm evaluation 1 knowledge distribution in teams 1 cost structures and ai workflows 1 cognitive load in ai workflows 1 code generation 1

Evidence chain (3 articles, showing 3)

@Grady_Booch: Having been part of the industry for 50 years, I can confidently report that ... example_of

@bcherny: I talk to engineers at other companies every day and hear the same thing: one... example_of

The 10x/non-10x disparity with identical tools suggests clarity and context management are the differentiators, not model capability.

@potetm: the real reason you feel so exhausted after coding with LLMs. example_of

Author's observation that 'decisions are harder than tasks' is a practical manifestation of the thesis that clarity (not model capability) is the bottleneck. Unclear context forces more decisions.

query this concept

$ db.articles("context-clarity-as-bottleneck")

$ db.cooccurrence("context-clarity-as-bottleneck")

$ db.contradictions("context-clarity-as-bottleneck")