NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Understanding the problem (Score:1)
The bigger the project, the more important to have someone breaking the big problem into logical smaller problems. Even then, I think everyone needs to understand the larger problem.
This is where I might find some fault with Microsoft as an example of getting things done. When I look at their products, I too often have images of a software department and marketing department fighting with each other. In these cases it seems like the original problem and solution get polluted with a sales/marketing/world domination angle. They do get stuff done, I'm just not always sure what they got done.
Reply to This
Re:Understanding the problem (Score:1)
This is exactly how I feel.
Code is always a trade-off. It always caters to some cases better than to others, because there is never any single way to do things that would always be best. Of course, I'm not saying anything new this is why Extreme Programming proposes what it proposes, and why it embraces constant refactoring as a way of life for a project.
What is important, is to be aware of the trade-offs. That requires a solid understanding of the problem first; it's okay to parse HTML with sim