Would anyone out there like to explain their web based software design
process? I'm analyzing our current methods vs. other more productive
ways to handle project management, source code versioning, sftp, ssh,
debugging, testing, customer - programmer relationship (ex: new
features/requests), and development ide. I'm looking for more efficient
ways to produce reliable code, version it, test it, track bugs, and
implement. Things I'm looking for are the actual individual processes
it takes to get this job done.
Not looking for arguments on the best cvs or ide... just a good process
to follow in general. Something like.. should you test on an
independent development machine or your local workstation to combat
concurrent programming falacies? This isn't my first rodeo so I'm not
looking for simple answers unless they truly are simple...
-JI
process? I'm analyzing our current methods vs. other more productive
ways to handle project management, source code versioning, sftp, ssh,
debugging, testing, customer - programmer relationship (ex: new
features/requests), and development ide. I'm looking for more efficient
ways to produce reliable code, version it, test it, track bugs, and
implement. Things I'm looking for are the actual individual processes
it takes to get this job done.
Not looking for arguments on the best cvs or ide... just a good process
to follow in general. Something like.. should you test on an
independent development machine or your local workstation to combat
concurrent programming falacies? This isn't my first rodeo so I'm not
looking for simple answers unless they truly are simple...
-JI
Comment