🧠 IT Idioms & Slang

IT idioms are figurative expressions used specifically in tech workplaces that don't exist in standard English dictionaries or carry different meanings. Examples: 'boiling the ocean' (attempting too much at once), 'bike-shedding' (arguing over minor details), 'rubber duck debugging' (explaining code to an object to find the bug). They reflect developer culture, startup mindset, and engineering values.

Must-know IT idioms include: move the needle (make a measurable impact), boil the ocean (attempt an impossibly large task), yak shaving (doing increasingly indirect tasks before reaching the real goal), bike-shedding (debating trivial issues), drinking the Kool-Aid (blindly following company ideology), hockey stick growth (slow then exponential growth), and eating your own dog food (using your own product).

Idioms are figurative expressions with meanings understood by most professionals — 'move the needle', 'push the envelope'. Slang is more informal, sub-community-specific, and evolves faster — 'LGTM', 'nit', 'bike-shed', 'yak shave'. Both appear in Slack, code reviews, and team discussions, but idioms are generally safe in formal writing while slang should be reserved for casual team communication.

Bike-shedding (also called Parkinson's Law of Triviality) describes the tendency to spend disproportionate time on trivial details while neglecting complex important issues. In tech teams, it appears when discussions about button colours overshadow architecture decisions. The term comes from a story about a committee approving a nuclear plant but spending most time debating a bike shed's paint colour.

Yak shaving describes a chain of tasks where each step requires fixing something else before you can proceed — until you find yourself doing something seemingly unrelated to your original goal. Example: "I needed to deploy the fix, but first had to update Docker, which required updating the OS, which meant updating the SSH config..." It's a humorous way to explain why simple tasks take hours.

Key startup idioms: product-market fit (product meets a strong market demand), hockey stick growth (exponential growth curve), land and expand (win small, grow the account), run out of runway (deplete funding), pivot (change business direction), blitzscaling (prioritise growth speed over efficiency), escape velocity (self-sustaining growth).

Common GitHub culture idioms: LGTM (Looks Good To Me — PR approval), ship it (deploy now), rubber duck review (superficial approval), bikeshedding (debating PR details instead of logic), bus factor (how many people can leave before a project fails), scratch your own itch (build what you personally need), eating your own dog food (using your own software).

Generally no — formal technical writing (RFCs, ADRs, API documentation, post-mortems) should use precise, literal language. Idioms are best reserved for Slack, standups, retrospectives, and informal team communication. In international teams with non-native speakers, overusing idioms can cause miscommunication. The exercises on this page help you understand idioms you'll encounter, not necessarily use them.

'Boiling the ocean' means attempting a task that is too large, complex, or impractical to complete — trying to solve everything at once. Use it when scoping work: "Let's not boil the ocean — we should focus on the core use case first." It's appropriate in planning meetings, sprint planning, and product discussions when pushing back against scope creep.

The Slang-to-Formal sub-section teaches how to translate informal IT communication into professional language — converting Slack messages to emails, transforming casual standup language into formal status reports, and rewriting GitHub comments into Jira descriptions. Ideal for professionals moving into client-facing or management roles.