theburningmonk.com

One of a new wave of buzz­words that have been made pop­u­lar by the emerg­ing breed of Ruby/Scala devel­op­ers, low cer­e­mony is usu­ally used to describe web frame­works – if a frame­work is “low cer­e­mony” then the amount of setup/configuration it requires is min­i­mal and the cen­tral idea is that it will stay out of your work and lets you focus on your code.

Def­i­n­i­tion:

CTP stands for Commu­nity Tech­nol­ogy Preview, another fancy term for a ‘beta’ or ‘prototype’.

RTM stands for Release To Manu­fac­tur­ing or Release To Market.

Ref­er­ences:

Soft­ware release life cycle

Yet another recur­ring phrase on DotNetRocks’s pod­casts, and a catchy one at that! The term ‘tech­ni­cal debt’ was coined by Ward Cun­ning­ham to describe the even­tual con­se­quences a soft­ware devel­op­ment orga­ni­za­tion incurs when it chooses to do things the quick and dirty way, which ben­e­fits the short-term but increases com­plex­ity and ulti­mately is more costly in the long term.

Tech­ni­cal debt incurs inter­est pay­ments in the shape of extra effort required for future devel­op­ment, but can be paid down by refac­tor­ing the quick and dirty design into bet­ter designs. It costs to pay down tech­ni­cal debt, but you gain by reduc­ing future inter­est payments.

Tech­ni­cal debt is almost unavoid­able in any real-world devel­op­ment project, and some­times it may be sen­si­ble to incur some tech­ni­cal debt in order to meet an impor­tant dead­line just as busi­nesses incur some debt to take advan­tage of a mar­ket opportunity.

Ref­er­ences:

Steve McConnell’s in-depth look on tech­ni­cal debt

Cod­ing Horror’s arti­cle on pay­ing down your tech­ni­cal debt

The term ‘duck typ­ing’ is often used to describe a type of dynamic typ­ing in pro­gram­ming lan­guages where the object’s cur­rent set of meth­ods and prop­er­ties deter­mines the valid semantics.

Why?

duck test — If it looks like a duck, swims like a duck and quacks like a duck, then it prob­a­bly is a duck