Comments on: Building A Software Toolbox http://www.3000k.com/blog/archives/86 Just another WordPress weblog Sat, 26 Jul 2008 02:58:59 +0000 http://wordpress.org/?v=2.0.2 by: Eric http://www.3000k.com/blog/archives/86#comment-2801 Sat, 21 Apr 2007 03:24:10 +0000 http://www.3000k.com/blog/archives/86#comment-2801 Ha! HyperCard used to be my toolbox. But after it hadn't been updated in 12 years I finally put the 'ol HyperCard down for some ClarisWorks love. Now where's my Commodore 64 tape drive...? Ha!

HyperCard used to be my toolbox. But after it hadn’t been updated in 12 years I finally put the ‘ol HyperCard down for some ClarisWorks love.

Now where’s my Commodore 64 tape drive…?

]]> by: Jim Faris http://www.3000k.com/blog/archives/86#comment-1658 Fri, 23 Mar 2007 21:22:31 +0000 http://www.3000k.com/blog/archives/86#comment-1658 I've seen Eric's tool box, it's all HyperCard!!! I’ve seen Eric’s tool box, it’s all HyperCard!!!

]]> by: Chris Bloom http://www.3000k.com/blog/archives/86#comment-1477 Sat, 17 Mar 2007 22:30:52 +0000 http://www.3000k.com/blog/archives/86#comment-1477 Good points. As far back as my first Powerbuilder and Visual Basic class, it was always stressed that you shouldn't try to rebuild the wheel. Re-using existing code not only saves time, but avoids erroneous errors from miskeying if you're in a rush. In addition to using a few open source solutions for various solutions (database abstraction, for example) I also keep my own custom library of functions that I tend to use in all of my projects, plus a set of starter template pages (html, css and js files along with some php include files) that allow me to start plugging in content right away. In the case of my own common files, I've found that it's a good idea to synchronize the files <em>back</em> into my common source folder at the end of every project. This way, any changes that I made to the common files (new functions, better documentation or just bug fixes) will be available the next time I start a project using them. If the changes are significant enough, I'll also synchronize the changed files to any old projects that used them (with a fair amount of regression testing of course). Good points. As far back as my first Powerbuilder and Visual Basic class, it was always stressed that you shouldn’t try to rebuild the wheel. Re-using existing code not only saves time, but avoids erroneous errors from miskeying if you’re in a rush. In addition to using a few open source solutions for various solutions (database abstraction, for example) I also keep my own custom library of functions that I tend to use in all of my projects, plus a set of starter template pages (html, css and js files along with some php include files) that allow me to start plugging in content right away. In the case of my own common files, I’ve found that it’s a good idea to synchronize the files back into my common source folder at the end of every project. This way, any changes that I made to the common files (new functions, better documentation or just bug fixes) will be available the next time I start a project using them. If the changes are significant enough, I’ll also synchronize the changed files to any old projects that used them (with a fair amount of regression testing of course).

]]>