The language of silicon dreams and stack overflows.
The process of reviewing, refining, and preparing technical tasks before development begins—not to be confused with the other kind of grooming your HR department warns about. It's like mise en place for coding.
An operation that completes entirely or not at all, with no in-between states visible to other processes. Like Schrödinger's database transaction—it's either done or not done, never halfway.
A way for an application to send real-time data to other applications via HTTP callbacks. It's the polite way for services to say 'hey, something happened' instead of you constantly asking 'did something happen yet?'
The practice of intentionally breaking things in production to make sure your systems can handle failure gracefully. It's like testing your smoke detector by setting small fires, except your boss approves.
A design pattern that prevents cascading failures by automatically stopping calls to a failing service, like an electrical circuit breaker but for API calls. When things go wrong, it fails fast instead of timing out slowly and taking everything down with it.
Five object-oriented design principles that form a convenient acronym: Single responsibility, Open-closed, Liskov substitution, Interface segregation, and Dependency inversion. Developers memorize them for interviews then promptly violate them all in production.
Reusable chunks of code that perform specific tasks and can be summoned by the main program whenever needed, like having a personal assistant for your algorithm. Also known as functions or procedures, these are the building blocks that let programmers avoid copy-pasting the same code a hundred times. They take inputs, do their thing, and return outputs—ideally without causing your entire program to crash.
A self-contained, interchangeable component of a larger system designed with well-defined interfaces, making it the LEGO brick of engineering and software design. Modules allow developers and engineers to break complex systems into manageable chunks that can be developed, tested, and replaced independently. This modular approach prevents one broken piece from taking down the entire operation—unless someone forgot to document the interfaces properly.
A duplicate copy of data, files, or systems stored separately from the original to prevent catastrophic loss when (not if) disaster strikes. This insurance policy for your digital life ranges from simple file copies to elaborate redundant systems, and it's the difference between a minor inconvenience and a career-ending catastrophe. The most important backup is always the one you forgot to make yesterday.
In the startup world, the speed at which your development team can actually ship features, measured in story points or whatever agile metric your project manager is obsessed with this quarter. Unlike regular speed, velocity has direction—ideally forward, though some teams seem to excel at moving sideways. It's the number that determines whether you'll make your demo day deadline or spend the weekend surviving on Red Bull and regret.
The gradual loss of signal strength, wave amplitude, or general oomph as something travels through space or time. In tech, it's why your Wi-Fi sucks in the bathroom; in biology, it's why scientists deliberately weaken pathogens to make vaccines. Think of it as nature's (or physics') way of enforcing the "things get worse over distance" rule.
The supposedly clear specifications of what a system, project, or product must do, which somehow always turn out to be neither clear nor complete when development begins. In tech, they're the sacred documents that stakeholders change weekly while insisting nothing has changed. The gap between what's written and what's actually wanted could swallow entire development teams.
The passive-aggressive chat status acronym meaning "be back when I damn well feel like it"—a digital middle finger to the expectation of immediate availability. It's the ultimate power move for asserting boundaries in an always-online world. Basically, it translates to "stop expecting me to respond immediately, I have a life."
Pre-designed patterns or frameworks that save you from reinventing the wheel every single time you need to create something. In tech, it's the skeleton code that keeps developers from crying into their keyboards at 2 AM. Whether you're building websites, writing emails, or designing presentations, templates are the reason you can pretend to be productive without starting from scratch.
To diagnose and solve a problem through systematic investigation, usually while silently cursing whoever created the mess in the first place. In tech, it's the art of Googling error messages and pretending you knew the solution all along. The process typically involves turning it off and on again, checking if it's plugged in, and eventually admitting you need to call someone smarter.
The structured arrangement of elements within a design, document, or physical space—basically how you organize stuff so it doesn't look like a toddler's collage. In design and tech, it's the blueprint that determines where everything goes before the client inevitably asks you to move it all around. A good layout is invisible; a bad one makes people's eyes bleed.
The science and technology of generating, controlling, and detecting photons—basically light particles—especially in visible and near-infrared spectrums. It's like electronics, but with light instead of electrons, powering everything from fiber optics to laser surgery. Think of it as the reason your internet is fast and your eye surgery doesn't require a medieval torture device.
The act of replacing humans with machines, usually sold as 'efficiency gains' while simultaneously creating an entire industry of people who maintain the machines that replaced people. Originally meant to free humans from tedious tasks, it now mostly means replacing checkout clerks with self-service kiosks that require three employees to supervise. The ultimate corporate dream: a workforce that doesn't need bathroom breaks or complain about the office temperature.
The modern internet equivalent of a rickroll, where you click on a promising tutorial or explainer video only to discover it's entirely in Hindi. This phenomenon is especially common with programming tutorials and STEM content, where the English thumbnail and title cruelly mask the linguistic surprise awaiting you. It's the educational version of expecting one thing and getting something completely different.
The scientific measurement of a fluid's resistance to flow, or as regular humans call it, "thickness." This friction coefficient determines whether your substance pours like water or oozes like honey. Engineers obsess over this because apparently knowing the exact internal friction of liquids is how bridges get built and engines don't explode.
Structured Query Language, the bread and butter of database management that lets you talk to relational databases without needing a doctorate in computer science. Pronounced either "sequel" or "S-Q-L" depending on which tech bro you want to annoy at the office.
Wanna Be Mod—a gaming term for overzealous players who act like they have moderator powers they definitely don't possess. These self-appointed hall monitors patrol forums and chat rooms, reporting violations and lecturing others, desperately hoping the actual admins will notice their free labor.
The electronic equivalent of turning it up to eleven—the process of boosting voltage, power, or current to make weak signals actually worth listening to. Whether you're talking guitar pedals or telecommunications, it's all about making the small stuff big without completely destroying the integrity of the original signal. Engineers love it, audiophiles obsess over it, and marketing teams dramatically overstate its importance.
The increasingly rare state of not being connected to the internet or larger network—either by technical failure or deliberate choice, neither of which your boss will find acceptable as an excuse. In IT, it means a system that's been disconnected; in real life, it's the mythical state of actually being present in the physical world. Some say people used to live offline full-time; anthropologists are still studying these ancient cultures.