jellybean
of an electronic component, or software algorithm: generic, standard, vanilla, easy to find
jellybean: a generic, off-the-shelf electronic part
In electronics and software engineering, jellybean refers to any component, integrated circuit, or algorithm that is common, interchangeable, and widely available from multiple suppliers. A jellybean part is the opposite of custom or specialty: it performs a straightforward function, costs very little, and you can source it from any decent distributor without negotiation or long lead times. The term carries a mild dismissal, the implication being that such parts are as plain and uniform as jellybeans in a jar.
Jellybean components include standard logic gates, common operational amplifiers like the 741 or TL072, basic voltage regulators, and any resistor or capacitor in standard values. In software, a jellybean algorithm is one that follows textbook approaches: a generic sorting routine, a standard finite state machine, or a basic PID controller. These are not wrong; they are proven, documented, and teach-able. But they are not optimized for your specific problem, and they do not confer competitive advantage.
Why designers avoid and embrace them both
Manufacturers dislike jellybeans when cost, size, or power efficiency matters critically. If you are designing a hearing aid or a space-qualified instrument, you will often specify a non-standard part with better performance in your narrow use case, even if it costs more and has a six-month lead time. Conversely, in consumer electronics and rapid prototyping, jellybeans are gold. They let you get to market fast, they are cheap, and they fail in ways every engineer already understands.
The term shows up most in design reviews and procurement meetings. A designer might say, "Use a jellybean opamp for the front end, it is good enough." This signals confidence and economy, not laziness. In many applications, a jellybean choice is the right one because the real engineering challenge lies elsewhere: in the firmware, the signal path, the mechanical design, or the power budget.
The metaphor is American, probably dating to the 1990s as surface-mount standardization made component reuse more obvious. Like jellybeans themselves, generic ICs and algorithms are mass-produced, come in standard packages, and cost pennies in volume. The word is slang, not official, but it is precise and widely understood across hardware design, embedded systems, and legacy software shops.