On InformIT.com, I have published a selection of jargon terms from my book. Some of the terms many consultants will be very familar with, some perhaps not so.
I am also taking this opportunity to announce that the next article series on InformIT will be diving into the topic of “The Economics of Technical Debt”. As an officially certified armchair economist*, it is my duty to offer up my own analogies between bad code and bad economics in this series that (3 articles in, soon to be published in short intervals) skewers the notion that you can write bad code and simply leave the consequences for someone else. Especially in consulting, where presumably you are trying to gain clients for the long term (i.e. long enough such that you can’t just walk after leaving them with a mess).