Comments on: Deploying Desktop-based Software Continuously

By: Ash Maurya

Ash Maurya — Wed, 24 Feb 2010 12:52:56 +0000

Ruang – What do you mean by debugging? Troubleshooting problems in production?

By: Ruang

Ruang — Mon, 25 Jan 2010 16:07:15 +0000

Ok, I got Continuous Deployment working now. I update after every new feature now. Plus I’m using some new software.

By: Ruang

Ruang — Mon, 25 Jan 2010 16:07:00 +0000

Ok, I got Continuous Deployment working now. I update after every new feature now. Plus I’m using some new software.

By: Ruang

Ruang — Tue, 19 Jan 2010 13:46:35 +0000

Even when my application is working in development, a lot of times bugs show up when I deploy to production. A lot of null reference exceptions. It may have to do with permissions on production – I’m not really sure.

By: Ruang

Ruang — Tue, 19 Jan 2010 13:46:00 +0000

By: Ash Maurya

Ash Maurya — Tue, 19 Jan 2010 02:50:01 +0000

Yes, there is an important distinction to be made between a software release and a marketing release. Continuous deployment addresses the former and doesn’t dictate what is delivered and to whom. Patches and updates to live software are certainly fine as is delivering the next “marketing release” continuously to an internal audience till public launch.

That said, other forces like the need for quick learning/feedback loops can override the potential impact of “launch hype” especially in a startup where a lot is unknown. I am not saying a marketing launch is not a powerful tool, but it’s power is usually overstated. Personally I’d take a soft-launch is it lets me build the “right” product, than a big marketing launch that has low or no traction.

By: Ash Maurya

Ash Maurya — Tue, 19 Jan 2010 02:50:00 +0000

By: Schwabe

Schwabe — Mon, 18 Jan 2010 23:07:21 +0000

Why kill the hype?
Sure, continuous deployment is an effective development strategy – but it kills the impact of ‘launch hype’.

Building momentum towards the next big software release generates hype – and hype is a powerful dynamic that can multiply marketing performance.

Sure, if your pricing model is subscription based then continuous deployment is natural. But for every other desktop app that is not, you’re going to want to leverage launch hype to help drive new sales.

To solve the challenge (of implementing continuous development for an ‘off the shelf’ software product) we would need to achieve a certain harmony with the overall scope of the business model. And I think you can do that by implementing Continuous Development principals primarily for patches & updates.

By: Schwabe

Schwabe — Mon, 18 Jan 2010 23:07:00 +0000

Why kill the hype?
Sure, continuous deployment is an effective development strategy – but it kills the impact of ‘launch hype’.

Building momentum towards the next big software release generates hype – and hype is a powerful dynamic that can multiply marketing performance.

By: uberVU - social comments

uberVU - social comments — Mon, 18 Jan 2010 22:53:52 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by justinpirie: RT @tweetmeme Deploying Desktop-based Software Continuously http://tinyurl.com/ybkr298...