๐๐ ๐๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ถ๐ป๐ด ๐๐ต๐ฎ๐ฝ๐๐ฒ๐ฟ ๐ฏ: ๐ช๐ต๐ ๐๐๐ฎ๐น๐๐ฎ๐๐ถ๐ป๐ด ๐๐ ๐๐ ๐๐ฎ๐ฟ๐ฑ๐ฒ๐ฟ ๐ง๐ต๐ฎ๐ป ๐๐ ๐๐ผ๐ผ๐ธ๐
One of the biggest takeaways from Chapter 3 of AI Engineering was realizing that building an AI model is only part of the challenge. Figuring out ๐ต๐ผ๐ ๐๐ผ ๐ฒ๐๐ฎ๐น๐๐ฎ๐๐ฒ ๐ถ๐ ๐ณ๐ฎ๐ถ๐ฟ๐น๐ ๐ฎ๐ป๐ฑ ๐ฎ๐ฐ๐ฐ๐๐ฟ๐ฎ๐๐ฒ๐น๐ can be just as difficult.
With traditional software, it's usually easy to tell whether something works. If a calculation is wrong or a test fails, you know there's a bug. But AI doesn't always work that way. A model can generate multiple reasonable answers to the same question, making it much harder to determine which one is actually better.
That made me think:
๐๐ผ๐ ๐ฑ๐ผ ๐๐ฒ ๐ธ๐ป๐ผ๐ ๐ถ๐ณ ๐ฎ๐ป ๐๐ ๐บ๐ผ๐ฑ๐ฒ๐น ๐ถ๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ถ๐บ๐ฝ๐ฟ๐ผ๐๐ถ๐ป๐ด?
๐๐ฒ๐ป๐ฐ๐ต๐บ๐ฎ๐ฟ๐ธ๐ ๐ก๐ฒ๐ฒ๐ฑ ๐๐ผ ๐๐ฒ๐ฒ๐ฝ ๐๐๐ผ๐น๐๐ถ๐ป๐ด
Reading this section made me realize how difficult it is for evaluation benchmarks to keep up with the pace of AI development.
The chapter explains that GLUE (General Language Understanding Evaluation) was introduced in 2018 to measure how well language models performed on common natural language tasks. But within about a year, models had already become so good at it that researchers introduced SuperGLUE in 2019 as a more difficult benchmark.
GLUE evaluates tasks such as:
Question answering
Sentiment analysis
Sentence similarity
Text classification
The chapter also mentions newer benchmarks like:
SuperGLUE
MMLU (Massive Multitask Language Understanding)
MMLU-Pro
Each one was introduced because the previous benchmark was no longer challenging enough.
What I found interesting is that a model getting a higher benchmark score doesn't always mean it understands language better. Sometimes it simply means the model has become very good at solving that particular benchmark.
๐จ๐ป๐ฑ๐ฒ๐ฟ๐๐๐ฎ๐ป๐ฑ๐ถ๐ป๐ด ๐๐ป๐๐ฟ๐ผ๐ฝ๐ ๐ฎ๐ป๐ฑ ๐ฃ๐ฒ๐ฟ๐ฝ๐น๐ฒ๐ ๐ถ๐๐
Another section I really enjoyed was the explanation of entropy and perplexity.
The chapter explains entropy as a measure of how much information a token carries and how difficult it is to predict the next token in a sequence.
Perplexity measures uncertainty. If a model is very uncertain about what comes next, its perplexity will be higher. If it predicts confidently and accurately, the perplexity becomes lower.
I also liked learning that cross entropy, perplexity, bits-per-character (BPC), and bits-per-byte (BPB) are all different ways of measuring how well a language model predicts text. The better a model predicts text, the lower these metrics become.
Another point that stood out was that there isn't a single "good" perplexity score. The value depends on:
the dataset being evaluated
the tokenizer being used
how perplexity is calculated
how much context the model has access to
That was a helpful reminder that metrics should always be interpreted in context instead of being compared blindly.
I also found it fascinating that these metrics connect directly to text compression. If a model predicts text efficiently, it can represent that information using fewer bits. I had never thought about language models and data compression being so closely related before reading this chapter.
๐๐ ๐ฎ๐ฐ๐ ๐๐๐ฎ๐น๐๐ฎ๐๐ถ๐ผ๐ป ๐๐. ๐ฆ๐๐ฏ๐ท๐ฒ๐ฐ๐๐ถ๐๐ฒ ๐๐๐ฎ๐น๐๐ฎ๐๐ถ๐ผ๐ป
Another concept that made a lot of sense was the difference between exact and subjective evaluation.
Some tasks have one correct answer.
For example:
Solving a math problem
Passing a unit test
Answering a multiple-choice question
Those are easy to evaluate because the answer is either correct or incorrect.
But many AI applications don't work that way.
How do you measure whether one response is more helpful, more creative, or better written than another?
That's where evaluation becomes much more subjective.
๐๐ ๐๐๐ฑ๐ด๐ถ๐ป๐ด ๐๐
This was probably my favorite section of the chapter.
Instead of relying only on humans, researchers are now using one AI model to evaluate another.
An AI judge can answer questions like:
Is this response relevant?
Does it contain hallucinations?
Which response is better?
Which answer would users probably prefer?
The chapter even discusses research showing that some AI judges can agree with human evaluators surprisingly often.
But it also explains why we shouldn't blindly trust these judges.
They can be influenced by:
the prompt
the order responses are presented
the model itself
different scoring methods
One sentence from the chapter really stuck with me:
"Do not trust any AI judge if you can't see the model and the prompt used for the judge."
That feels like a good reminder as more AI tools become black boxes.
๐๐ผ๐ผ๐ธ๐ถ๐ป๐ด ๐๐ฒ๐๐ผ๐ป๐ฑ ๐๐ต๐ฒ ๐ช๐ผ๐ฟ๐ฑ๐
Another idea I found interesting was the difference between lexical similarity and semantic similarity.
Two sentences can use completely different words while meaning almost the same thing.
For example:
"What's up?"
"How are you?"
On the other hand, two sentences can look almost identical while meaning something completely different.
The classic example from the chapter was:
"Let's eat grandma."
"Let's eat, grandma."
A single comma changes everything.
This is where embeddings become so important. Instead of comparing words directly, embeddings represent meaning as vectors, allowing models to compare ideas rather than just matching text.
That's what powers many modern AI applications like semantic search, recommendation systems, retrieval, clustering, and RAG.
๐๐ผ๐บ๐ฝ๐ฎ๐ฟ๐ถ๐ป๐ด ๐๐ป๐๐๐ฒ๐ฎ๐ฑ ๐ผ๐ณ ๐ฆ๐ฐ๐ผ๐ฟ๐ถ๐ป๐ด
The chapter also discusses comparative evaluation, an approach that compares responses instead of scoring them individually.
It's often easier to compare two responses than to assign one response an absolute score.
It's much easier to say:
"Response A is better than Response B."
than to confidently say:
"This response deserves exactly 8 out of 10."
That idea is now used heavily in preference training and ranking AI models.
This chapter gave me a new appreciation for AI evaluation.
Before reading it, I mostly thought about model architectures, prompting, fine-tuning, and inference. Now I realize that evaluation is just as important.
A powerful model isn't necessarily a useful model. If we can't measure reliability, usefulness, safety, or alignment, it's difficult to know whether a model is actually improving.
One of my biggest takeaways from this chapter is that evaluation isn't just about assigning a score to a model. It's about understanding what those scores actually mean, choosing the right evaluation method for the task, and recognizing the limitations of each approach.
As AI continues to evolve, I think building better evaluation methods will become just as important as building better models.
United States
NORTH AMERICA
Related News
Secret Claude Tracker Shocks Users After Anthropic's Anti-Surveillance Stance
12h ago
EV Batteries Defy Expectations, Last Hundreds of Thousands of Miles
1d ago
GBase 8a Performance Anomaly Case Study: How a Single Parameter Change Sparked a Chain Reaction
1d ago
Who Else Has Inherited a Codebase With Zero Comments and a Prayer?
1d ago
ๅฎ็พ็ๅนณๅบธ
3h ago