On 8/28/2012 5:24 PM, John Kasunich wrote: > That means > any user space program that exports hal objects would need to be > tested against all other such programs. Or am I missing something > about how these tools work? Ha ha ha. This brings to mind a blog entry I stumbled across just the other day thanks to Hacker News, http://henrikwarne.com/2012/08/22/top-5-surprises-when-starting-out-as-a-software-developer/
The number 1 surprise for Warne was "1. Complexity from Aggregation So, given that there were no clever algorithms in use, and that the whole application was only using pretty basic data structures, it seemed at first that there wouldn’t be many challenges working on the system. Wrong! I quickly realized that the system is hugely complicated, not with complicated features, but in having lots and lots of simple features aggregated together. This is something I have seen in all systems I have worked with. Most features are dead simple, but because there are so many of them, you get subtle (or not so subtle) interactions between them causing bugs. The complexity of the system comes from the aggregation of many simple parts, not from any complex parts." It may not be exactly the same circumstance you are describing but the consequences are the same. So it would seem Seb's approach is necessary but not sufficient. That means it is still necessary. As my grandmother used to tell us kids, "half a loaf is better than none." Regards, Kent ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
