Atlas48/JargonFile
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Original files version 4.4.7

Browse Source
This commit is contained in:
Bob Mottram
2014-03-27 18:54:56 +00:00
parent c632ed8d67
commit cb847ea893
2578 changed files with 26300 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
original/html/B/bottom-up-implementation.html Normal file
View File

@@ -0,0 +1,13 @@
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>bottom-up implementation</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../B.html" title="B"/><link rel="previous" href="bottom-post.html" title="bottom-post"/><link rel="next" href="bounce.html" title="bounce"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">bottom-up implementation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bottom-post.html">Prev</a><EFBFBD></td><th width="60%" align="center">B</th><td width="20%" align="right"><EFBFBD><a accesskey="n" href="bounce.html">Next</a></td></tr></table><hr/></div><dt><a id="bottom-up-implementation"/><dt xmlns="" id="bottom-up-implementation"><b>bottom-up implementation</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> Hackish opposite of the techspeak term <span class="firstterm">top-down design</span>. 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 <span class="emphasis"><em>build</em></span> 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 <span class="firstterm">middle-out implementation</span>, 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. </p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bottom-post.html">Prev</a><EFBFBD></td><td width="20%" align="center"><a accesskey="u" href="../B.html">Up</a></td><td width="40%" align="right"><EFBFBD><a accesskey="n" href="bounce.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">bottom-post<73></td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"><EFBFBD>bounce</td></tr></table></div></body></html>