Geeks With Blogs
Amusingly MOSS ...It's funny how difficult some stuff is when it really shouldn't be February 2009 Entries
When not to use exception handling, or, "Don't try too hard"
Okay, people. I officially deem it OK to remove someone's geek cred if they put a try block around the entire of a method body. Furthermore, you get to remove even more geek cred if they just re-throw the error that was caused in the try block. Here's an example of what I'm talking about: private void foo() { try { // do the foo. // do more foo. // do the rest of the foo. } catch (Exception ex) { throw ex; } } Contrary to popular perception, try/catch blocks are not for preventing errors - they are ......

Posted On Friday, February 27, 2009 2:17 PM

97 Things Every Software Architect Should Know
A co-worker shared this gem with me, and every bit of it is true. This is a must-read for aspiring architects. http://97-things.near-time.... One thing that I really appreciate about the articles on this site is that they draw a clear distinction between an architect and a senior developer who calls himself an architect. While many people feel that a certain number of years of programming experience entitle you to architect status, programmers ......

Posted On Thursday, February 26, 2009 6:05 PM

Workflow SPListItem modified by SHAREPOINT\system
I came across this last week. It took me entirely too long to get it fixed, considering how simple the resolution was. It turns out that my understanding of how Workflow operates wasn't up to snuff. Scenario I have a workflow attached to a forms library, activating when a list item is modified. The intent of the workflow is to modify one or more fields on a particular list item in this list, after it is edited by another process. Each of these fields are modified in different methods, which are tied ......

Posted On Monday, February 23, 2009 11:36 AM

Backwards Engineering

I heard someone say, "backwards-engineer a solution" on a conference call today.  I think he meant, "reverse-engineer," but it got me thinking about when we pass "backwards-engieneering" off as "forward-thinking."

Just food for thought.  I may write about this more as my fancy is struck.

Posted On Thursday, February 12, 2009 12:41 PM

Systems Design and Poker Odds
Deciding whether to implement a new, unproven widget to save in development costs is a lot like deciding whether to call a player who goes all-in on the first hand of a poker game. You may land your cards, but is it really worth it? The way to determine whether or not to take the risk with an unproven widget is a lot like how a professional would assess the scenario I just described. An accomplished poker player knows what each hand is worth, not only in terms of the potential winnings, but in terms ......

Posted On Saturday, February 7, 2009 9:15 PM

Copyright © Adam McKee | Powered by: