JevMade field notes / Technical guide

Ask one question of every function

every asks a focused question about each function, a named block of code. It ranks likely matches and explains when a small code excerpt cannot answer a whole-program question.

Original by sufianetaouilEvaluation

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“every” by sufianetaouil. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 soufiane

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

A function is a named block of code that performs a task. every asks whether each function shows a described behaviour, such as hiding an error. It ranks likely matches so a reviewer knows where to start, rather than claiming every high score proves a defect.

Some questions fit one function; others need nearby code or a view of the whole program. The tool labels that distinction, saves reusable answers, and repeats borderline checks. Its reports include what source was shared, the cost, and the limits of what was examined.

The supplied evaluation uses only twenty hand-written functions. Question wording can change scores, and broad questions may return too many matches. Every scanned function goes to TypeSafe. Decide whether confidential code may be shared, and read the surrounding source before drawing a conclusion.

Key takeaways

Ask a question the available code can actually answer.
Read likely matches before calling them bugs.
State missing context rather than implying the whole program was checked.

More guides →See the experiments →