Small Method Size Good for Debugging

Also bear in mind that the less code in each method the easier it will be to pin-point the location of the error.

Also you should bear in mind that throwing an exception is a big overhead and should only be used when a real exception has occurred...something you really did not expect and cannot recover from.

http://web.archive.org/web/20100402092458/http://blog.thekid.me.uk/archive/2007/07/25/debugging-tips-for-sharepoint-and-wss-exceptions.aspx

Web Services vs. Native Invocation

The performance overhead of invoking web service operations is several orders of magnitude larger than that of invoking native Java classes. That's because marshaling and un-marshaling XML, processing SOAP envelopes, etc. are expensive operations.

 http://www.oracle.com/technetwork/articles/soa/data-tier-caching-for-soa-101753.html

Do Input Normalization Server Side

"I could either handle it on the client or more likely handle it [upper case conversion of input search value] at the [WCF] service ... that way I don't need the client developer to have to worry about it."

Robert Green - WPF Using Visual C# 2010

C# 'using' = syntatic sugar

As you know, the using statement is syntactic sugar for a try/finally that disposes of the IDisposable object. 

Michael Burr
 - http://stackoverflow.com/questions/248961/c-sharp-using-statement-catch-error 

Perlis Epigrams

e.g. "It is easier to change the specification to fit the program than vice versa

We will never run out of things to program as long as there is a single program around.

http://web.archive.org/web/19990117034445/http://www-pu.informatik.uni-tuebingen.de/users/klaeren/epigrams.html

ECM Strategy

Technology can enable streamlined management of content, but the underlying strategy must come first.

http://www.aiim.org/What-is-ECM-Enterprise-Content-Management