CAH-Woke Culture in IT.json

{
  "black": [
    "Our new diversity initiative mandates that all code reviews must now include ____.",
    "The CEO announced that the company's biggest innovation this year was not a new product, but ____.",
    "After the re-branding, our mission statement became 'Empowering ____ through ____ technology'.",
    "The most controversial item on the quarterly all-hands agenda was ____.",
    "We had to re-architect the entire system to ensure ____.",
    "My performance review noted I needed to improve my ____.",
    "The mandatory sensitivity training revealed that ____ is a microaggression.",
    "To foster a more inclusive environment, we replaced 'master' branch with ____.",
    "The ethical AI committee determined that our algorithm was biased because of ____.",
    "Our latest HR policy now requires all engineers to declare their ____ before committing code.",
    "We fired the lead developer for ____.",
    "The company's new 'woke' marketing campaign featured ____.",
    "During the retrospective, the biggest blocker identified was ____.",
    "Our tech lead was accused of ____ during the stand-up.",
    "The company's new policy on remote work emphasizes ____.",
    "To avoid perpetuating harmful stereotypes, we now refer to 'debugging' as ____.",
    "The intern got fired for asking about ____.",
    "We achieved peak wokeness when the engineering team started debating the ethics of ____.",
    "The most unexpected outcome of our DEI initiative was ____.",
    "My boss said I needed to be more ____."
  ],
  "white": [
    "Performative allyship.",
    "An un-gendered avatar.",
    "Mandatory unconscious bias training.",
    "The emotional labor of maintaining open source.",
    "Using 'folks' instead of 'guys'.",
    "A blockchain-enabled safe space.",
    "Decolonizing the codebase.",
    "A non-binary API endpoint.",
    "The privilege of being an early adopter.",
    "Critiquing 'disruptive innovation' as inherently colonial.",
    "A LinkedIn post about intersectional algorithms.",
    "Pronoun stickers on every monitor.",
    "Hiring exclusively based on 'culture add' rather than 'culture fit'.",
    "Replacing 'stand-up' with 'gentle stretching huddle'.",
    "The ethical implications of dark mode.",
    "A Slack channel dedicated to discussing power dynamics.",
    "Retiring problematic memes from the internal wiki.",
    "The white male gaze in UX design.",
    "Canceling the company mascot for problematic historical ties.",
    "A 'caste-safe' programming language.",
    "Micro-aggressions detected by AI.",
    "Explaining Rust ownership to a boomer.",
    "That one guy who only talks about Web3.",
    "Toxic positivity in agile sprints.",
    "Re-evaluating the 'push to production' pipeline for consent.",
    "Tokenizing diversity quotas.",
    "The performative outrage over a missing 'accessibility' tab.",
    "Changing 'whitelist/blacklist' to 'allowlist/denylist' but keeping 'master/slave' for legacy reasons.",
    "A 'safe space' for tech bros to vent about reverse discrimination.",
    "The CEO's apology tour after a bad tweet.",
    "Demanding reparations for technical debt.",
    "Pronouns in email signatures.",
    "A DEI consultant's six-figure invoice.",
    "The woke-washing of SaaS products.",
    "Using only 'they/them' for all generic user accounts.",
    "The forced celebration of National Pickle Day.",
    "Getting 'called out' on Twitter for a commit message from 2008.",
    "A gender-neutral bathroom in the server room.",
    "The unexamined privilege of using camelCase.",
    "An entire sprint dedicated to refactoring offensive variable names."
  ]
}