The four groups

  • Bug categories you'd file in a tracker

    NULL POINTER · OFF-BY-ONE · RACE CONDITION · MEMORY LEAK

    The four canonical 'classes of bug' every onboarding doc lists.

  • Things printed in a Java stack trace

    CAUSED BY · AT · FRAME · THREAD

    Caused by, at com.example…, the stack frame, the thread name — the four anatomy parts of a JVM exception dump.

  • GitHub pull-request review states

    NIT · LGTM · APPROVE · REQUEST CHANGES

    Nit: and LGTM are convention; Approve and Request changes are the literal GitHub review verdicts.

  • Words that pair with ROOT

    CAUSE · DIRECTORY · PRIVILEGE · KIT

    Root cause, root directory, root privilege, rootkit. The wordplay group — every tile is incomplete without ROOT in front.

Why this puzzle works

The trap here is CAUSED BY vs CAUSE. Both are about reasons, but only one is a stack-trace line — the other is half of *root cause*. Same with THREAD (the JVM concept) vs anything else thread-y. If you find yourself with three tiles in a group and a confident fourth that doesn't quite fit, you're probably looking at a wordplay tile in disguise. Connectle's purple group is always wordplay — the tile is a *word*, not a *concept*.

How to read a Connectle without solving it

A code-themed grouping puzzle rewards counting as much as recognition. Start by listing every plausible group, then notice which tiles appear in two lists. Whichever group has exactly four unambiguous members is your anchor — solve it first and the rest of the board collapses by elimination. The hardest tier (purple) is almost always wordplay: tiles that share a prefix or suffix, not a concept. If a tile feels orphaned, ask whether the same word could follow or precede a common engineering word like root, stack, cache, or queue.