Legacy:

1. Any system I don’t want to work in.
2. The system I am going to replace with my system.

Legacy Data:

1. Data from systems that are no longer in use but were useful at one time.
2. Useless data until it is useful.
3. Worthless data until the enterprise realizes the need to spend tens-of-thousands of dollars to use these data for trending in business analytics.

Library:

1. Large building once containing the collected writings of all thought, enterprise, and endeavor.
2. Large collection of bytes containing the compiled musings of very little though, from all evidence.
3. Collections of files, programs, sub-routines, and scripts deemed necessary by the computer deities to constrain the hopes and dreams of all programmers.
4. Logic accessible to programmers through coding that will perform actions for which they can take credit, but about which they have no understanding.

Licensing:

1. An agreement or contract whereby an owner of intellectual property agrees to allow the use of said intellectual property by an individual or company for a certain time for compensation with the understanding that the user holds no rights, cannot sub-license, or even so much as look under the hood for fear of violating the license agreement and end up owning the licensing party more than any of this was worth.
2. Expensive way to rent a thing that doesn’t really exist.
3. Legal contract of such expanse that none even read it and so convoluted that no one realizes that they’ve all agreed to let Microsoft© come to their homes next June and paint them blue and slap them with a fish.
4. Tort lawyer’s full-employment act.
5. If not the pants, at least the jacket, worn by the embarrassingly revealed software emperor in the most recent version of the famous fairy tale by Hans Christian Anderson™.

LINQ:

1. Language Integrated Query. It’s not even a correct acronym as it should be LIQ. 
2. Microsoft’s solution to the impedance mismatch of data access in OO languages by providing a different mismatch. 
3. Microsoft’s initial declaration that they did not know how to solve the .NET impedance mismatch nearly as well as countless other third parties and Open Source providers.
4. “If you want to complain about the horrid state of ADO, I’ll give you something to complain about!” 
5. An esoteric and convoluted “solution” to the impedance mismatch that should send .NET developers who complained about it running back to ADO and embedding SQL statements in their C# code.

see: Entity Framework and Impedance Mismatch

Logic:

1. Whatever compiles.
2. The term to describe any of the meandering process pathways that, outside computer programming code would be condemned as insanity, but inside of it becomes revered as holy canon.
3. Jargon used to connote legitimacy upon syntax absent of semantics.

A = A;
if (false){…}
foreach (Null in Collection)…

Logical:

1. Using one of the methods of logic.
2. Being wrong unemotionally.

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

Z