Skip to content

Commit d8eae85

Browse files
Boris Devclaude
andcommitted
Add Language AI Evaluation 101 post
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 63dc30a commit d8eae85

4 files changed

Lines changed: 43 additions & 3 deletions

File tree

docs/boris_dev_resume.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ Urban Mapping provided geospatial analytics to Tableau.
127127
| **Papers & code** | **Non-tech fun** |
128128
|---|---|
129129
| LLM-based taxonomy (topic modeling): [bertopic-easy](https://github.com/borisdev/bertopic-easy) | Climbed Cotopaxi (21,000 ft) |
130-
| [Language AI Evaluation 101: Know your user](https://medium.com/@boris.dev/why-did-your-language-ai-feature-fail-66a280954287) | Bodyboarded Mexpipe |
130+
| [Language AI Evaluation 101: Know your user](language-ai-evaluation-101.md) | Bodyboarded Mexpipe |
131131
| [Langchain PR: Causal Program-aided Language (CPAL)](https://github.com/hwchase17/langchain/pull/6255) — see Harrison Chase's [tweet](https://twitter.com/LangChainAI/status/1678797225013440514) | Taught with students in Medellín, Colombia to make ClusterPy (open-source geo clustering library) |
132132
| [Work papers](https://docs.google.com/document/d/1pMID97O4hHkK8ok7cwLH4Y4KpsgQSPUAXtYrscwcyb4/edit) | Taught kids snowboarding as an instructor |
133133
| [Academic papers](https://scholar.google.com/citations?hl=en&user=Nk4jOl0AAAAJ&view_op=list_works&gmla=AKKJWFcXmp1czN7ENwhvDx7hvgEHHD9lR1FLROPUvMco2ptysbNAe0Cdya8R9DZUmePAtMN53t2N97S_t5xA4NF-) | Counseled severely emotionally disturbed children |

docs/index.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,6 @@
66
| 2 | [What Is Knowledge Engineering, Really?](knowledge-engineering.md) | A working definition built around elicitation, evaluation, and 0→1 modeling in messy domains |
77
| 3 | [Fine-Tuning LLMs Will Restructure Your Data Science Team](fine-tuning-restructures-data-science.md) | How fine-tuning replaces annotation pipelines and the NN-optimization role; the new "fine-tuning analyst" |
88
| 4 | [Why Domain-Specific Language AI Features Fail](domain-specific-language-ai.md) | The customer-discovery process for niche language AI, and why a Lean Startup approach is required |
9-
| 5 | [Hyper-Local Community Funding: A DAO Alternative to CDFIs](hyperlocal-community-funding.md) | Local digital tokens and DAOs as a delivery mechanism for under-served-neighborhood capital |
10-
| 6 | [CV: Knowledge Engineering in Messy Domains](boris_dev_resume.md) | The IR-compile pattern across clinical trials, legal billing, maritime construction, narrative gaming, and geographic inequality |
9+
| 5 | [Language AI Evaluation 101: Know Your User](language-ai-evaluation-101.md) | Why simplistic Ground Truth produces misleading accuracy metrics; cognitive empathy as the iteration loop |
10+
| 6 | [Hyper-Local Community Funding: A DAO Alternative to CDFIs](hyperlocal-community-funding.md) | Local digital tokens and DAOs as a delivery mechanism for under-served-neighborhood capital |
11+
| 7 | [CV: Knowledge Engineering in Messy Domains](boris_dev_resume.md) | The IR-compile pattern across clinical trials, legal billing, maritime construction, narrative gaming, and geographic inequality |

docs/language-ai-evaluation-101.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Language AI Evaluation 101: Know Your User
2+
3+
*Originally published on [Medium](https://medium.com/@boris.dev/why-did-your-language-ai-feature-fail-66a280954287), Mar 20, 2023. Co-authors: Robert McKee and Shawn Larson.*
4+
5+
## Background
6+
7+
A language AI application can be a liability to your customer if it makes just a few terrible judgements on high-risk matters.
8+
9+
## The evaluation problem
10+
11+
"Most AI applications launch with bad predictions." Why? The cause is an overly simplistic evaluation test dataset that leads to exaggeratedly positive evaluation metrics. By "overly simplistic" we mean that the evaluation dataset, or Ground Truth, does not contain examples that robustly represent high-stakes, nuanced customer semantic judgements. Why is this Ground Truth so challenging to build? Because it requires both customer feedback and data science.
12+
13+
## Illustration
14+
15+
Imagine a Mom whose children text her hundreds of questions every day. Your job is to build her a language AI app that reduces her toil. You start by building a Ground Truth dataset of example correct responses. This Ground Truth is key to evaluating your future AI's prediction performance.
16+
17+
**Iteration 1's Ground Truth.** The problem with this initial set of examples is that all of them depend on rationales that are overly simplistic. After training the model on these examples, evaluation against a test set drawn from the same simplistic distribution yields a 100% accuracy metric. That metric is misleading.
18+
19+
To make a more rigorous evaluation, we need to discover more nuanced examples — questions whose correct response depends on context, priority, or risk that the simplistic rationales don't capture.
20+
21+
**Iteration 2's Ground Truth.** Adding nuanced examples depends on *cognitive empathy* — sitting with the customer and discovering the implicit principles she actually uses. When we re-evaluate the same model against this richer test set, the accuracy drops to 0%.
22+
23+
The lesson is twofold:
24+
25+
1. **Your quantitative evaluation will be misleading when your Ground Truth is overly simplistic.** Same model, two test sets, two opposite verdicts.
26+
2. **Building Ground Truth is iterative, not a checkoff.** It is a continuous-improvement process driven by customer dialog, not a one-time annotation pass.
27+
28+
In summary: *without cognitive empathy for your customer, your language AI performance metrics are meaningless.*
29+
30+
## Connection to the IR-compile pattern
31+
32+
This is step 1 of [the pattern](boris_dev_resume.md#common-pattern) — decomposing human expertise into an IR — applied specifically to evaluation. The "nuanced rationales" you discover through cognitive empathy *are* the primitive concepts of the domain IR. Without that decomposition, the eval dataset is just surface-text matching, and the metric measures nothing real.
33+
34+
## References
35+
36+
1. *Human-in-the-Loop Machine Learning* by Robert Munro, O'Reilly Media, 2021.
37+
2. *The One Practice That Is Separating The AI Successes From The Failures.* Forbes, Aug 14, 2022.
38+
3. *Evaluation.* LangChain Blog, March 14, 2023.

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,5 +42,6 @@ nav:
4242
- "What Is Knowledge Engineering, Really?": knowledge-engineering.md
4343
- "Fine-Tuning LLMs Will Restructure Your Data Science Team": fine-tuning-restructures-data-science.md
4444
- "Why Domain-Specific Language AI Features Fail": domain-specific-language-ai.md
45+
- "Language AI Evaluation 101: Know Your User": language-ai-evaluation-101.md
4546
- "Hyper-Local Community Funding: A DAO Alternative to CDFIs": hyperlocal-community-funding.md
4647
- "CV: Knowledge Engineering in Messy Domains": boris_dev_resume.md

0 commit comments

Comments
 (0)