One of a new wave of buzzwords that have been made popular by the emerging breed of Ruby/Scala developers, low ceremony is usually used to describe web frameworks – if a framework is “low ceremony” then the amount of setup/configuration it requires is minimal and the central idea is that it will stay out of your work and lets you focus on your code.
CTP stands for Community Technology Preview, another fancy term for a ‘beta’ or ‘prototype’.
RTM stands for Release To Manufacturing or Release To Market.
Software release life cycle
Yet another recurring phrase on DotNetRocks’s podcasts, and a catchy one at that! The term ‘technical debt’ was coined by Ward Cunningham to describe the eventual consequences a software development organization incurs when it chooses to do things the quick and dirty way, which benefits the short-term but increases complexity and ultimately is more costly in the long term.
Technical debt incurs interest payments in the shape of extra effort required for future development, but can be paid down by refactoring the quick and dirty design into better designs. It costs to pay down technical debt, but you gain by reducing future interest payments.
Technical debt is almost unavoidable in any real-world development project, and sometimes it may be sensible to incur some technical debt in order to meet an important deadline just as businesses incur some debt to take advantage of a market opportunity.
Steve McConnell’s in-depth look on technical debt
Coding Horror’s article on paying down your technical debt
AMFVO is short for Action Message Format (AMF) Value Object (VO).
AMF is a binary format used to serialize ActionScript objects, primarily used to exchange data between a Flash application and a remote service; a VO is also known as a Data Transfer Object (DTO), it is used to transfer data between application subsystems.
An AMFVO is simply a value object used to transfer ActionScript objects between a Flash application and a remote service.
The most widely used AMF encoding framework for .Net is FlourineFX.
The term ‘duck typing’ is often used to describe a type of dynamic typing in programming languages where the object’s current set of methods and properties determines the valid semantics.
duck test — If it looks like a duck, swims like a duck and quacks like a duck, then it probably is a duck