The language of silicon dreams and stack overflows.
A tool that analyzes code for potential errors, style violations, and suspicious constructs without executing it. Named after the tiny annoying bits of fluff on clothing, because code issues are equally annoying and everywhere.
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.
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.
The complete set of technologies, languages, and tools used to build an application. Essentially your project's ingredient list, often inflated with trendy items you don't need but added anyway for your resume.
The shortened form of rubber duck debugging, now a verb. The act of solving your own problem by explaining it out loud, ideally to a bath toy but technically anything inanimate works.
An attack where someone steals an active session token to impersonate a logged-in user, like grabbing someone's coat check ticket and claiming their jacket. Except the jacket is their bank account.
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.
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 application that performs most processing locally rather than relying on a server—the opposite of a thin client. Like someone who brings their own everything to a potluck instead of contributing to a shared meal.
The art of instructing computers to do your bidding through carefully crafted code, which they will interpret exactly as written rather than as intended. It's equal parts problem-solving, debugging your own mistakes, and Googling "why doesn't this work" at 2 AM. The profession where you spend 10% of your time writing code and 90% figuring out why that code hates you.
Read The Manual (the F is flexible based on frustration level). The universal response to questions answered in the documentation that nobody reads. Often delivered with varying degrees of professional courtesy.
The observation that organizations design systems that mirror their communication structure. If your company has four teams, you'll build four subsystems—whether that makes sense or not.
The practice of advocating passionately for specific technologies or platforms, often involving conference talks, blog posts, and Twitter arguments. It's like regular evangelism but the deity is a JavaScript framework.
Technology systems and solutions built and used inside organizations without IT department approval or knowledge. Usually created by frustrated employees who got tired of waiting for the official three-year approval process to get Slack.
The process of replacing something with a newer, theoretically better version—emphasis on "theoretically" because upgrades have a 50/50 chance of improving things or breaking everything. It's when you install the latest version of software hoping for new features but secretly dreading the bugs that come with them. The IT equivalent of "if it ain't broke, we'll fix that."
The twisting force that makes things rotate, measured in Newton-meters and responsible for everything from opening jar lids to powering engines. Physics' way of explaining why longer wrenches work better and why your car's specs include numbers you pretend to understand. Essential for engineers and mechanics; confusing for everyone else who just wants their wheels to turn.
A background process that runs continuously on Unix-like systems, handling tasks without any user interaction—like a helpful ghost in your machine. Despite the demonic name, it's usually benign, managing things like printing, networking, or scheduled tasks while you're blissfully unaware. When something goes wrong with a daemon, you'll spend hours hunting through log files to exorcise it.
A group of similar things collected or occurring closely together, whether they're galaxies in space, servers in a data center, or problems in your project timeline. In military terms, it's also shorthand for cluster munitions or the chaotic situations they often describe with additional colorful language. The technical term for 'bunch of stuff grouped together,' now scientifically validated.
The actual act of building or putting something into action, as opposed to just talking about it in endless meetings. It's where rubber meets road, theory becomes reality, and developers discover that the "simple" feature actually requires rewriting half the codebase. Also a corporate buzzword for "we finally did the thing we said we'd do six months ago."
A coil of wire that becomes magnetic when electricity flows through it, basically the electromagnetic equivalent of Dr. Jekyll and Mr. Hyde. Engineers love these because they turn electrical signals into physical movement, making them perfect for everything from car starters to doorbell mechanisms. The unsung hero of electromechanical switches everywhere.
Advanced Encryption Standard, the government-approved way to scramble your data so thoroughly that even the NSA needs a warrant (theoretically). It's the cryptographic algorithm that protects everything from your credit card transactions to your embarrassing Google searches. Built to replace DES when computers got too fast, it comes in flavors of 128, 192, and 256-bit keys for varying levels of paranoia.
A magical piece of software or hardware that compresses video files so they don't take up your entire hard drive, then decompresses them so you can actually watch the cat videos you hoarded. Short for 'coder-decoder,' it's why your 4K movie doesn't require a forklift to transport. The reason video conferences are possible and also the reason they look terrible when your internet hiccups.
In tech, it's the code you embed to monitor, measure, and log what your application is actually doing behind the scenes, because trust but verify. Think of it as installing security cameras in your software to catch bugs in the act. In music, it's arranging notes for different instruments, but let's be honest, you're here for the tech definition.
An imaginary line connecting points on Earth where your compass points at the exact same wonky angle away from true north. Geographers and navigators love these lines because magnetic declination is messy, and apparently someone needed to map out all the places where compasses are equally confused. It's like a contour map for magnetic chaos.