Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Revenue from commercial modules?Revenue from commercial modules?
Previous
 
Next
New Post
12/10/2009 12:22 PM
 

Rodney Joyce wrote

 Tony Hussein wrote

Developers who spend too much time in support are developers who develop poor software.  

 

I beg to differ. I write good software (it is my passion) - I spent WAY too much time on support. Obviously quality of software has an affect on support time - but the primary reason is that most users expect support for free and have way too high expectations. The amount of time I spent on support ultimately killed my business (Smart-Thinker commercial module development) - if I could do it again I would change my licensing module and charge people for support (of course, where the support has occured because of a bug (my fault) it's free - but a lot of issues are configuration or integration issues. If I had a penny for each customer who said "Here's my Host details - just log in and fix it please" I would be a lot richer than I am now...

You have to plan out your support and build it into your licensing/budget. It will be the biggest part of your committment if your module has more than 100 lines of code...

 

Why didn't you continue the business and change the license.. even retoactively? If you had two options, whether to kill the business or start charging for support even for people who already purchased a license, I would think people would choose the latter. But you probably had other reasons.

 
New Post
12/10/2009 12:41 PM
 

Jon Seeley wrote

 Tony Hussein wrote

Developers who spend too much time in support are developers who develop poor software. When I develop software, I make it easy to use, has good user usability, extensive help and so on.  Even my error messages are verbose.

 

 

Wow... are you God?  Seriously dood get off your high horse and come down to the real world.  The other posts here are accurate -- development is really only a small percentage of coding and the rest is maintenance (of which support plays a huge part).  I make my software "easy to use" with "good usability" and "extensive help", etc., but I still spend at least half my time in my day job performing support.  Why?  Because people are generally inept when it comes to software. 

I think what you're really trying to say is that developers who spend a lot of time resolving BUGS as their support are the ones who develop poor software.  Yes, a program chock full of bugs can be considered poor software but a piece of software that has a lot of support calls does not necessarily make it bad.

 

Your mileage may vary. Your productivity vs mine may vary. Like I said.. I empower the user to help themselves. I create good help screens, tool tips, video tutorials, step by step turorials, getting started tutorials, install forums so users help each other.. etc. Hire minions to do trivial support issues. Do whatever you can so that support issues trickle down to very little. Don't be surprised that most developers just code and expect everyone to be able to use their software.

I downloaded thousands of software, most of them sucked in terms straight of out useful help. Make the thing easy to use. For example, if an option is disabled, put a tootip and explain why it's disabled. NOBODY is this world does this yet it's a very useful usability issue. In my emails, my sig has links to resources. I can go on and on giving tips on how to create great sofwtare. Most developers just want to code and ignore proper documentation because it's boring and time consuming. Most developers suck in designing good screen layouts, user interfaces. They need to be reading non programmiung books to expand their skills.

I don't create software used by millions of users and I don't have to deal with many support issues. If you work in a big company, let IT people take care of mundane support issues. I am also a fast typist and read qucikly. I can reply to tens of emails in a very short time. YMMV.

That's why Joel Spolsky hires developers who are 10 times as productive as the average developer but can to pay them 1.5 as much. Learn about time management skills. GTD skills. How can people like Scott Guthrie and Scott Hanselman have time to be sooo productive and peolpe wonder if they ever sleep. Enough said.

Maybe one day I will have my own horse!

 

 
New Post
12/11/2009 12:26 PM
 

I type slowly because some of my users can't read fast...

But seriously - it sounds as though you have the support side of things sorted - as long as you have that considered then the dev side of things (of which you appear to be a self-confessed uber-coder-guru) should be a piece of cake... just get your licensing/pricing right and choose a simple module in an untapped niche...

 


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
12/11/2009 6:24 PM
 

I am not an uber coder but thrive to become close. I believe in good testing and act on feedback.

 
New Post
12/11/2009 7:25 PM
 

Tony,

The other part to consider (Chime in everyone) is that nobody has the ability to test on all of the 10,000 hosts and configurations and their permutations.

You may build and test the software to work 100% of the time for your known configurations, but there is always another user with another configuration that you haven't seen yet. The time it takes to figure out that it is setting X that is killing you can be considerable. For each customer that calls up, you may have to spend a fair amount of time narrowing it down to setting X. Hiring minions is OK if you can identify the issue from the symptoms, but what if you cannot? What if a bunch of issues all look the same?  What if a user tells you something that isn't true ("I didn't change setting X - It's the default"), etc. Some things are not in your control.

I haven't seen any module sales figures here; I didn't expect to see any, to be honest. If they are really high, it invites people to compete and undercut your price. If they are low, it might get depressing - at the least it doesn't look good for the DNN community.

Disclaimer: I don't develop DNN modules, but I do develop software professionally.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Revenue from commercial modules?Revenue from commercial modules?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out