Keep It Simple, Stupid | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I see your point. Overview to specifics and if the specifics can be broken into teams the better.
I am coming from a little smaller company (9 employees) that are struggling to fill the niche of customers that have around 10-15k to spend instead of the 800k or more for the big boys. I have often wondered whether it is better to built something form scratch or to look for something that has already been done and modify it. The first way takes more time, but gives you exactly what you want. The other takes less time, but often does not give you what you want. Programming always seems to be a trade off between time, money,and functionality (maybe we should add reliability?). In reply to Re: Re: Planning your software before writing
by belize
|
|