Commit to a data-shape sketch before coding
Draft a data-shape sketch that names ADT, operations, and access pattern before implementation.
Write a data-shape sketch for the next feature that stores or transforms a collection Use this before coding a feature with saved views, imports, permissions, categories, recommendations, queues, or relationship data. Data-shape sketch Feature: [feature name] Collection or relationship: [what is being stored] ADT shape: [array/list, set, dictionary, stack, queue, priority queue, tree, graph] Dominant operation: [index access, membership, key lookup, oldest-first, latest-first, highest-priority, traversal] Invariant: [unique key, no cycles, FIFO order, sorted order, parent rule, collision-safe lookup] Implementation candidate: [specific language/library structure] Test that protects the shape: [one behavior test] Did you attach a data-shape sketch to a ticket,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in