Search the Jargon File, a comprehensive compendium of hacker slang illuminating many aspects of hackish tradition, folklore, and humor.
Alternatively, browse terms starting with:
The Jargon File is great by itself, but it also has plenty of references to invaluable resources, born from the quintessence of the hacker community. For your convenience we have compiled the list of all books that have been mentioned throughout the Jargon File. Here's a random example:
Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides; Addison-Wesley 1995. ISBN 0-201-63361-2.
From the Preface -- This book isn't an introduction to object-oriented technology or design. Many books already do a good job of that...this isn't an advanced treatise either. It's a book of design patterns that describe simple and elegant solutions to specific problems in object-oriented software design... Once you understand the design patterns and have had an "Aha!" (and not just a "Huh?" experience with them, you won't ever think about object-oriented design in the same way. You'll have insights that can make your own designs more flexible, modular, reusable, and understandable, which is why you're interested in object-oriented technology in the first place, right?
This book has been mentioned in the following pages of the Jargon File: Gang of Four.
[from cyberpunk] Someone interested in the uses of encryption via electronic ciphers for enhancing personal privacy and guarding against tyranny by centralized, authoritarian power structures, especially government. There is an active cypherpunks mailing list at firstname.lastname@example.org coordinating work on public-key encryption freeware, privacy, and digital cash. See also tentacle.
Iron Age n.
In the history of computing, 1961-1971 — the formative era of commercial mainframe technology, when ferrite-core dinosaurs ruled the earth. The Iron Age began, ironically enough, with the delivery of the first minicomputer (the PDP-1) and ended with the introduction of the first commercial microprocessor (the Intel 4004) in 1971. See also Stone Age; compare elder days.
bottom-up implementation n.
Hackish opposite of the techspeak term top-down design. It has been received wisdom in most programming cultures that it is best to design from higher levels of abstraction down to lower, specifying sequences of action in increasing detail until you get to actual code. Hackers often find (especially in exploratory designs that cannot be closely specified in advance) that it works best to build things in the opposite order, by writing and testing a clean set of primitive operations and then knitting them together. Naively applied, this leads to hacked-together bottom-up implementations; a more sophisticated response is middle-out implementation, in which scratch code within primitives at the mid-level of the system is gradually replaced with a more polished version of the lowest level at the same time the structure above the midlevel is being built.