Give language examples a reason to pick them, and skip leaking questions

olli-agent commented

2026-10-16 12:15:59 +03:00

Collaborator

Two quiz fixes that came out of an example question with no reasonable answer: "A search API in ▁▁▁ takes a query, calls OpenSearch and returns ranked results", with Python, PHP, Node.js and Go as options.

Examples that say why the term was picked. The PHP, Node.js and Laravel examples described jobs any language or framework could do. Each now uses the trait that makes the term the pick: PHP's long-lived workers under FrankenPHP, Node.js holding thousands of open connections and sharing code with the browser, Laravel's Eloquent, queued jobs and scheduler. English and Finnish.
No question that shows its answer inside a word. Leaks let every name under four letters through, so PHP in "FrankenPHP" stayed visible after masking, in the new example and already in PHP's summary. A short name that looks like an abbreviation is now found as written inside other words. PHP is the only term this changes; it now appears in the quiz only as a wrong answer. README describes the rule.

Checked locally: check-glossary, gofmt, go vet, go test ./... (database tests skipped without PostgreSQL). The new tests fail without the fix.

Follow-up idea filed as #29.

Two quiz fixes that came out of an example question with no reasonable answer: "A search API in ▁▁▁ takes a query, calls OpenSearch and returns ranked results", with Python, PHP, Node.js and Go as options. - **Examples that say why the term was picked.** The PHP, Node.js and Laravel examples described jobs any language or framework could do. Each now uses the trait that makes the term the pick: PHP's long-lived workers under FrankenPHP, Node.js holding thousands of open connections and sharing code with the browser, Laravel's Eloquent, queued jobs and scheduler. English and Finnish. - **No question that shows its answer inside a word.** `Leaks` let every name under four letters through, so PHP in "FrankenPHP" stayed visible after masking, in the new example and already in PHP's summary. A short name that looks like an abbreviation is now found as written inside other words. PHP is the only term this changes; it now appears in the quiz only as a wrong answer. README describes the rule. Checked locally: `check-glossary`, `gofmt`, `go vet`, `go test ./...` (database tests skipped without PostgreSQL). The new tests fail without the fix. Follow-up idea filed as #29.

olli-agent added 2 commits

2026-10-16 12:20:47 +03:00

Give the PHP, Node.js and Laravel examples a reason to pick them c2bd9a04f8

The three examples described jobs any language or web framework could do,
so they taught nothing about the term and its quiz question had no right
answer the player could reason to: a search API in PHP read just as well
with Python, Node.js or Go in the blank. Each example now uses the trait
that makes the term the pick: PHP's long-lived workers under FrankenPHP,
Node.js holding thousands of open connections and sharing code with the
browser, and Laravel's own Eloquent models, queued jobs and scheduler.

Skip quiz questions whose text shows the answer inside a word

CI / lint (push) Successful in 2s

Details

CI / server (push) Successful in 22s

Details

CI / image (push) Successful in 4s

Details

CI / verify-staging (push) Successful in 51s

Details

3e86042483

Leaks let every name under four letters through, so that Git would not be
found in "digit". PHP is three letters, and its summary and example both
name FrankenPHP, which the blank leaves whole: the question showed its own
answer. A short name that looks like an abbreviation is now found as
written inside other words. PHP is the only term this changes, and it now
appears in the quiz only as a wrong answer.

olli merged commit 3e86042483 into dev

2026-10-16 12:30:20 +03:00

olli deleted branch fix/quiz-examples

2026-10-16 12:30:20 +03:00

Rows
Columns

Give language examples a reason to pick them, and skip leaking questions #30