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.

Subscribe to this blog via RSS.

If you'd like to receive a very occasional email when I publish a major new article, enter your email below. Cancel anytime.

Launch Your Product. Build Your Future.
If you want to launch your product (or website) and build your future, you've come to the right place.

I'm a full-time Micropreneur based in Fresno, California and I run the Micropreneur Academy, an online learning environment designed to get one-person web startups from zero to launch in four months.

I use the term Micropreneur to describe an entrepreneur who creates the lifestyle of their choice through a portfolio of one-person technology businesses (MicroISVs, SaaS websites, e-commerce sites, etc...).

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.