JevMade

Sign in
← Back to guides

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
Bookmark: Ask one question of every function Keep this in your collection.
Leave a noteWhat would you try with this? : Ask one question of every function

Only you can see your notes.

Listen to this guide

JevMade’s plain-English explanation

0:00 /

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

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

The small self-test and performance figures are source-reported.

GitHub README

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

Your note

Only you can see this. Clear the text and save to remove it.

Keep what you save

Sign in to keep bookmarks and private notes on every device. We email you a link; there is no password, and the same link creates your account.