Skip to content

Latest commit

 

History

History
36 lines (21 loc) · 1.7 KB

File metadata and controls

36 lines (21 loc) · 1.7 KB

Contributing

This is the repo I most want help with. There are thousands more stories out there and I have seen a fraction of them. No One Is as Dumb as All of Us, which is exactly why more eyes on this makes it better.

Useful

  • New collections, and missed episodes or scenes in existing ones.
  • Better mappings. You read a lesson and thought "that is not what that story is about," tell me.
  • Corrections to the real-incident collections, with a source.
  • Rewrites that land the same lesson in fewer words. Especially these.

The One Rule

The story has to stand alone. If you have to summarize the plot before the lesson lands, it is the wrong story. The whole trick is that the audience already knows it.

Not Useful

  • Anything client-identifiable. No company names, no anonymized-but-obvious details, nothing lifted from a real engagement.
  • Vendor promotion. Tool mentions are fine when they earn their place. Marketing isn't.
  • Obscure stories that need a fandom to decode. The warehouse manager has to know it too.

Format

Match the columns in an existing collection: source, lesson, category, NIST function, ISO controls. CSV or a markdown table both work. Mark the collection fiction or real. Do not worry about matching the tone, I will edit.

How

Open an issue first for a new collection so we agree on the shape before you spend time on it. Missed episodes and corrections can go straight to a PR.

Style

Plain English. One line per lesson, the story then the point, separated by a colon. If a sentence needs a second read, rewrite it. Short. Length isn't thoroughness.

License

Contributions come in under CC BY 4.0, same as everything else here.