Cloud coding pitfalls: Tips for avoiding big, bad bugs

According to this ACM article, the seven coding constructs that have been the most frequent source of bugs are function calls, assignments, conditions, pointers, uses of NULL, variable declarations, function declarations, and return statements. There are dozens of other conference presentations, books, and taxonomies that provide statistically valid guidance — or at least opinions — on coding practices to avoid.

But so far, I haven’t found anything like that for coding in the cloud.

And make no mistake about it, the distributed, multi-language environment inherent in the cloud presents some real coding challenges. But before we nerd out entirely, let’s do a bit of bug triage. There are three interesting categories of bugs:

To read this article in full or to leave a comment, please click here


RSS-1

Check Yourself Before You Wreck Yourself. Avoiding Self-Sabotage At Work

I was standing in the security line at an airport when a TSA worker came walking alongside the line yelling out in an animated way, “No liquids, no aerosols, no gels or creams on the airplane…You better check yourself before you wreck yourself!” I couldn’t stop myself from laughing out loud. As the CEO of over a thousand employees at the time, I couldn’t help but imagine what it would be like if every CEO walked through the halls of their company yelling out something similar…”No negativity, no dishonesty, no disrespect in the workplace…You better check yourself before you wreck yourself!” Frankly, it might actually be a good idea. After all, that TSA worker certainly got every one of us standing in the line that day to think twice about what we had in our carry-ons.


Cloud Computing