Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • October 25, 2016, 09:00:55 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: how i work on programs  (Read 5248 times)


  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,333
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
how i work on programs
« on: June 17, 2005, 06:12:05 PM »
i just wanted to write a note to people who make suggestions or bug reports..
hopefully its clear over time from watching the forum, but basically i try to address serious bugs right away, and other features for my programs tend to get added in batches.  so just because i don't act on a suggestion right away doesn't mean that i'm ignoring it.  it's just with a large group of programs i'm usually only working on one or two at a atime, and suggestions for the others get recorded and will wait until i shift back into doing major work on that program.


  • Columnist
  • Joined in 2005
  • ***
  • Posts: 136
    • View Profile
    • Boredom Solutions
    • Donate to Member
Re: how i work on programs
« Reply #1 on: June 17, 2005, 06:27:12 PM »
Makes sense to me.  There's not much point in adding extra features to a program that has a crashing problem or what-have-you until the problem is fixed.  Then you can introduce new problems with new features and the cycle repeats. :mrgreen: