Self-Liquidating Premium:

A manufacturer's premium in which the product's cost is recovered through a retail sale of the product.

Properties of Good Tests:

Independent - No test should affect the outcome of any other test. Put another way, you should be able to run your tests in any order and always have the same outcome. A corollary of this is that setup/teardown methods are evil (both because they increase dependence and they decrease readability)
Readable - The intent of each test should be immediately obvious (both by its name and by its code).
Fast - Each test should run as quickly as possible, so the entire suite is also fast. The faster the suite, the more you'll run the tests, and the greater benefit you'll get (because you'll catch regressions quickly)
Precise - Each test should focus on testing one thing (and only one thing) well. Ideally, if a test fails, you should know exactly what part of your production code broke by just glancing at the name of the test. Also, if your tests are precise, it's less likely that a change in your code will require you to change many different tests. In practice, precise tests are short and only have one assertion or expectation per test.

Refresh Rate of a Monitor:

This is the speed at which the monitor's picture is redrawn or flashed in front of your eyes. Slower refresh rates provide a noticeable flicker. Higher refresh rates create a steady picture (and is easier on your eyes). The refresh rate is determined by the video card, but also must be supported by the monitor. The maximum refresh rate will be different for different resolutions. A minimum of 75 Hertz is recommended (TV refresh rates are 30 Hz, which is why there is a noticeable flicker).

Quickly Manage your Incoming mail:

QuickRule is a Lotus Notes feature, which allows you easily create mail rules, helping you manage the burden of email overload.
Select a message in your mail file, and click "Tools- Create QuickRule..."
The will bring up the Create QuickRule dialog box, and the values from the selected message will be filled in for you automatically.
In section #1, you select the condition(s) you want the rule to match: Sender, Domain, or Subject, the values (pre-filled in for you so no typing errors!) and how they should be evaluated: Contains, Does not contain, Is, or Is not.
In section #2, you decide if the rule must match any one of the conditions or all of the conditions.
In section #3, you define the action to take, such as which folder to move the message into.

Seiban:

This is the name of a Japanese management practice taken from the words sei, which means manufacturing, and ban, which means number. A seiban number is assigned to all parts, materials and purchase orders associated with a particular customer job, project or anything else. This enables a manufacturer to track everything related to a particular product, project or customer, and facilitates setting aside inventory for specific projects or priorities. That makes it an effective practice for project and build to- order manufacturing.

Sum the numbers in the filtered list:

After filtering the rows in a list, you can use the SUBTOTAL function, instead of the Excel SUM function, to sum the numbers in the visible rows.
A SUBTOTAL formula will be automatically inserted, while clicking the AutoSum button to total the visible cells in the column or manually keying the formula =SUBTOTAL(109,B2:B9)
The first argument in the SUBTOTAL function is a function number that specifies how the numbers should be calculated. There is a 9 in this example, which tells Excel to SUM the numbers.
Other function numbers can be used, such as 1 for AVERAGE, and 3 for COUNTA. Look in Excel's Help for a complete list.

Pair Programming:

Pair programming is a software development technique in which two programmers work together at one work station. One types in code while the other reviews each line of code as it is typed in. The person typing is called the driver. The person reviewing the code is called the observer or navigator. The two programmers switch roles frequently (possibly every 30 minutes or less).
While reviewing, the observer also considers the strategic direction of the work, coming up with ideas for improvements and likely future problems to address. This frees the driver to focus all of his or her attention on the "tactical" aspects of completing the current task, using the observer as a safety net and guide.
Benefits:
· Design quality: Shorter programs, better designs, fewer bugs
· Reduced cost of development: With bugs being a particularly expensive part of software development, especially if they're caught late in the development process, the large reduction in defect rate due to pair programming can significantly reduce software development costs
· Learning and training: Knowledge passes easily between pair programmers: they share knowledge of the specifics of the system, and they pick up programming techniques from each other as they work
· Overcoming difficult problems: Pairs often find that seemingly "impossible" problems become easy or even quick, or at least possible, to solve when they work together
· Improved morale: Programmers report greater joy in their work and greater confidence that their work is correct
· Decreased management risk: Since knowledge of the system is shared among programmers, there is less risk to management if one programmer leaves the team
· Increased discipline and better time management: Programmers are less likely to skip writing unit tests, spend time web-surfing or on personal email, or other violations of discipline, when they are working with a pair partner. The pair partner "keeps them honest"
· Fewer interruptions: People are more reluctant to interrupt a pair than they are to interrupt someone working alone