Advice for Writing Shrinkwrapped Software

Chris Mullins, Chief Software Architect for Coversant in Sacramento, presented this slide deck on Writing Shrinkwrapped Software to the Sacramento .NET User Group in August.

It’s filled with tips, advice and knowledge on writing shrinkwrapped software. Although it contains some .NET-specific content, the bulk of the message is language agnostic.

Start Small, Get Big
Growth Secrets for Self-Funded Startups. It'll Change Your Life.
What you get for signing up:
  • A 170-page ebook collecting my best startup articles from the past 5 years
  • Previously unpublished startup-related screencasts
  • Exclusive revenue-growing techniques I don't publish on this blog
"The ideas and information Rob provides should be required reading for anyone that wants to create a successful business on the web." ~ Jeff Lewis
Startups for the Rest of Us...
If you're trying to grow your startup you've come to the right place. I'm a serial web entrepreneur here to share what I've learned in my 11 years as a self-funded startup founder. Luckily several thousand people have decided to stick around and join the conversation.

For more on why you should read this blog, go here.

5 comments ↓

#1 Chris Mullins on 12.02.06 at 8:50 pm

What a great slide deck! Whoever put that one together sure knew his stuff! Why all the focus on orginization though? All we need to do is write the code, put up the download link, and we’re done. Right?

#2 admin on 12.03.06 at 1:39 am

🙂

#3 http:// on 12.03.06 at 8:14 am

“Don’t use Source Safe”. I love it! I’ve been saying the same thing for 10 years. Excellent presentation, even with only seeing the slides. -mattyj

#4 http:// on 12.03.06 at 3:53 pm

My favorite: Bug and features tracking, “Don’t write your own! No! No! No! No! (NO!)”.

#5 Chris Mullins on 12.04.06 at 6:06 pm

It’s amazing to me how many people start off on new projects that are just doomed to fail before the first line of code is done. Not using the right tools, failing to do due diligance where required, and steering clear of the areas they don’t like (Product Installation, ugrade scripts, EULA’s, etc) all doom a project to failure, even with the best engineering talent.