Humor
Humor
Assume everything is implicit unless you are told otherwise.
I generally consider it bad practice to have encoded fields in tables and implicit rules in objects. You should generally make your rules explicit by creating calculated columns, views, & etc for databases and creating properties for classes that encode the rules.
Example:
public bool IsBest { get { return rating >= 3; } }
Meticulity: The capacity for or degree of meticulousness. One's ability to be detail oriented. One's meticulity quotient is a large factor in one's success as a software developer.
Usage: Sam does not demonstrate a high degree of meticulity in his code.
I've just been through another review where we wanted to use Meat Cooking terminology for an artifact. I had looked this up before, but had neglected to blog on it so I didn't have the "Doneness" lost handy. This link at AskTheMeatMan.com clears it up. The Doneness levels are:
|
Doneness |
Tempurature |
|
Very Rare |
130º F |
|
Rare |
140 º F |
|
Medium Rare |
145 º F |
|
Medium |
160 º F |
|
Well Done |
170 º F |
|
Very Well Done |
180 º F |
Term: Brownian Architect
Related Terms: Brownian Architecture
Noun:
Application architect that makes snap decisions for various design problems by using the first design pattern that comes to mind without regard to long term effects or maintaining an overall architectural plan. Applications managed by Browning Architects are characterized by Brownian Architecture.
Strategy for Avoiding Brownian Architecture:
The primary way to produce a coherent architecture when dealing with a Brownian Architect is to employ a Brownian Motor. The concept is to ignore architectural decisions and continue to discuss the design problem until the Brownian Architect randomly lands on the correct decision. Note that great deal of energy must be spent to produce a coherent architecture in this way.
Term: Brownian Architecture
Related Terms: Brownian Architect
Noun:
Software architecture designed by a Brownian Architect. Marked by a random juxtaposition of conflicting software design patterns and procedures.
You know your too busy when...
- When you work up a sweat working at your desk
- When you have to talk to yourself or you won't listen
- When everyone you run into you have an issue to discuss with them
- When a trip to the bathroom becomes a scheduled meeting time
In case someone hasn't seen this, here is some holiday satire from Don Box and Chris Anderson.
The associated MSDN TV video shows how to do your own layout panel. Interestingly, Chris introduces the two pass Measure/Arrange layout model in Avalon as a new concept that allows “content negotiation, sized-content ...” Later, he explains that page layout may call Measure multiple times before calling Arrange to discover the optimal layout.
Shows Panel, Measure, MeasureOverride, Arrange, ArrangeOverride, DesiredSize (Can't seem to find proper documentation for ...Override in the beta documentation)
I couldn't contain myself on this one. Aliso Viejo, Calif. was about to ban Styrofoam cups because Dihydrogen Monoxide was used in their production. Via Instapundint.
The PC Police are careful to ensure that everyone uses inclusive language, however we must all draw the line somewhere. I draw mine at the Phylum Chordata. I address all my co-workers Gentlechorates, for example. It seems to me the spinal chord is what separates us humans, sharks and hagfish from the ganglion driven world of worms. I call making things second nature, “Putting it in the spinal chord.” Like any good reflex, that is where our quickest surest actions take place. To whit: we're really not that much different from chickens!