R "Ray" Wang writing for the Forbes CIO Network this week postulates some impressive psychological and business next steps for cloud computing in 2011. Saying we are “past the tipping point” already on all 4 major layers in 2010, Wang writes as follows about what 2011 holds in store:
You are here
Though it is certainly not a good coding practice, no error handling is far better than half-baked error handling. Without any sort of error handling in your code, any time the user performs an action that defies reason or your sysadmin throws the server out the window, you'll likely get some ugly exception splashed across the user's screen. However, no matter how distasteful project managers often find them, these error messages usually contain helpful information that gives some poor codemonkey a hint as to what the problem might be.
The work breakdown structure is not a "to do" list. Rather, it is a hierarchy of deliverables with major deliverables developed during a scope definition process which we then decompose into smaller and smaller deliverables.
I've been doing quite a bit of work lately with the Microsoft CRM SDK and taking advantage of the Advanced Developer Extensions. Here's a quick introduction to what they are and what you can do. It definitely makes building applications against MS CRM easier. I had a situation recently where I was inserting and account and a contact associated with that account.
I have found XQuery to be of good use when persisting serialized objects to Sql Server. Using XQuery we can pass an xml string to a stored procedure and derive the expected results with fairly simple code. We start with an XML string, which may contain multiple nodes and values. [code language="sql"] DECLARE @testXmlString XML SET @testXmlString = ' <Root> <employee> <name>Tim</name> <age>27</age> <company>ToplineStrategies</company> <title>Developer</title> <Education>B.S.
While this item is way below the clouds, every so often a piece of the programmer's art comes along that just takes your breath away.
A few weeks ago our company decided to buy some tools for our department. I’m obviously not talking about hammers or screwdrivers here, but computer work tools. Even though I am sometimes tempted to use a real hammer on my computer, especially when it takes a long time to compile 200 lines of code! Anyways, without getting too sidetracked, most of my co-workers decided to go for ReSharper which I personally think is a great option.
Timing the performance of a particular piece of code is a task that I find myself doing frequently and I suspect most developers do as well. Perhaps it's the load time for a web page, the execution of a stored procedure, calling a web service, or any number of other timings. In .NET I've often used the DateTime class to calculate the elapsed time with code similar to this.
Here at Topline, I personally tend to spend most of my time writing C# code and T-SQL. In the last year or two, however, in a game of tag that I didn't realize I was playing, I have become "it" when it comes to UI design. As a result, I have spent a lot of evenings learning CSS, and, contrary to what I supposed at the outset, I have grown to enjoy quite a bit. That being said, I am still learning and from time to time I encounter new and earth-shattering principles off CSS design that I have somehow missed before.