Skip to content

Latest commit

 

History

History
39 lines (28 loc) · 1.54 KB

File metadata and controls

39 lines (28 loc) · 1.54 KB

Contributing Snippets

Got a snippet idea? Add it to the right file and open a PR.

How to add a snippet

  1. Pick the file that matches the wall zone your snippet fits:

    • snippets/vibecode.js — AI, vibe coding, modern dev life
    • snippets/hackathon.js — hackathon chaos, building fast, shipping
    • snippets/community.js — collaboration, community, showing up for each other
    • snippets/experts.js — asking questions, learning from experts, impostor syndrome
    • snippets/coffee.js — coffee-fuelled ideas, hallway conversations, the magic of a break
  2. Add your snippet at the bottom of the file with the next sequential number:

    // --- #12 ---
    yourSnippetHere();
  3. Optionally, credit yourself by adding your name to the comment:

    // --- #12 --- by Your Name
    yourSnippetHere();

Cross-zone snippets

A snippet might feel at home in more than one zone — that's fine. If it fits multiple walls, add it to each relevant file with its own number in each. Just make sure it genuinely fits the tone of each zone rather than adding it everywhere by default.

What makes a good snippet

  • Reads like real(-ish) code but the joke lands without explanation
  • Relatable to ServiceNow developers, hackathon participants, or the broader dev community
  • Short — ideally fits in 5–10 lines
  • No product-specific references, no real APIs or internal details

Tone

Playful. Builder energy. The kind of thing you'd put on a coffee mug or a hoodie. Not a tutorial, not documentation — just vibes.