Many electrons have been consumed talking about the business and technical benefits of moving to the cloud. At Spanning, we try to apply those same lessons to our daily work in order to produce products at a pace that was not even feasible back in the packaged apps days. This post discusses how we can quickly make imperfect decisions now, that allow us to move forward, learn a little more, then re-evaluate the next set of issues with more context. This is the same model that companies use when they move to the cloud... only pay for the services that you need now.
If you’re writing a serious application, on the web or otherwise, you’ve got to have good logging. In the context of application development, reading logs is my personal favorite method for tracking bugs and rooting them out. A service like Loggly is perfect for programmers like me. It provides an easy to use web interface with searching capabilities that allows you to see what your application is logging at any time that you’d like to check in. Debugging with Loggly is nice, but it’s just the tip of the iceberg, thanks in part to its Loggly API.