JevMade Sign in
← Back to guides

JevMade field notes / Game-building article

Make Jev’s speed and cost visible in a word game

Pochang Lab turns Jev’s judgments into a Japanese technology-term game, showing response times and estimated costs while explaining the failed questions that moved repeat checks back into code.

Original by Pochang LabEvaluation

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“Making Jev’s Speed and Cost Playable Two Hours of Conversation, Zero Handwritten Lines” by Pochang Lab. Read the original source.

This expanded guide is an AI-narrated adaptation prepared by JevMade. It expands the source’s essential ideas, examples and caveats in JevMade’s own words and is not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

Our summary

Pochang Lab built a Japanese word game to experience Jev’s speed and cost, rather than just read a price list. Players enter technology terms to fill five category meters. Jev answers set questions without writing replies, while the screen shows the requests, response times and estimated running cost.

Five questions about each term travel together in one request. Jev judges its category, characteristics and which prepared trivia entry fits. Ordinary code extracts words, keeps score, checks repeats and selects the displayed lines. Failed questions about repeated text and related technology names helped the maker redraw that boundary.

The article’s demo reports a 407-millisecond average and about 0.15 yen in usage. Its 14 judgments include two local checks and twelve calls to Jev. These are maker measurements, not guarantees. The cost uses a fixed exchange rate; typed text goes to TypeSafe and is also logged locally.

Key takeaways

  1. Use Jev for fuzzy judgments, but keep exact repeat checks, point calculations and prepared replies in code.
  2. Send independent questions about the same term together, and distinguish naming a technology from naming something related to it.
  3. Count actual service calls separately from local checks; reported speed and estimated usage cost do not establish accuracy or total development cost.

The article and linked game are one guide. The README’s roughly 0.14-yen example differs from the article’s roughly 0.15-yen clip. Demo mode makes paid calls; the maker’s figures exclude Claude Code and human time.

Pochang Lab · Original published

Read the original guide Opens the author’s site in a new tab.

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.