Continuous Deployment
This morning Steve gave a presentation on context automation and Kynetx at the Utah Technology Council's CTO P2P forum. The presentation was great and the audience asked a lot of good questions. One thing that came up (I don't even remember why) was the subject of continuous deployment. I decided I'd pull a few URLs out of my head and put them in a blog post for people to mull over. The first URL I think of when I consider continuous deployment is code.flickr.com. If you've never been there, the bottom of the page lists when the last deployment
Continue reading {Continuous Deployment}
SaaS Lessons Learned
I'm at the Enterprise Software Summit in Sundance this afternoon (I'm speaking tomorrow). Greg Gianforte, from Right Now, is speaking about things they've learned about supporting software as a service (SaaS). Deployment choice - on premise and hosted. Large enterprises, particularly financial and government, need an on premise solution. You need a software architecture that supports both. Installations often go to a hosted solution, hosted solutions rarely move to on premise installations. Software has to be architected from the start with multi-tenancy in mind. "On demand" does not equal "pay as you go" Separate the way to pay from
Continue reading {SaaS Lessons Learned}
Cut the Vision in Half and Ship It
How many of us can relate to this? Moral: If you find yourself talking more than walking, shut up, cut the vision in half, and launch it. You can always fill in the gaps later. In fact, you'll know more about what gaps need to be filled after you've launched "half a feature" than if you tried to fill them in before launching anything. From Simple means launching something - Signal vs. Noise (by 37signals)Referenced Tue Dec 13 2005 09:52:40 GMT-0700 (MST)
Continue reading {Cut the Vision in Half and Ship It}





