What your really looking at is some kind of Heirarchical Storage Solution. What happens is that once you have predetermined how much data will be saved from the camera each night. You can get some kind of disk array to store it on. That disk array will also be attached to some kind of HSM solutions such as what is provided by StorageTek's SAMFs. That solution will automatically backup the data that is stored on your disk and remove it from your disk so new data can be stored on the costly disks. From now on your OS and applications think that the data is on disk but in reality its on tape. When the data is requested the software will automatically get it from tape and place it back on the disk. This can be rather costly however.
From what I have found every project is different and different styles of attacking those projects are good. However I think that XP makes some very scary assumptions.
First of all do customers ever even know what they want. Their assumptions may be very different that was is realistic which leads to very odd demands for features.
Second, I am sure that programmers can program given just one feature but from my experience I think that its important to get a good look at the forest over the trees. At least sometimes. Programs can often be streamlined and optimized only when the full problem is understood.
I do agree that managers should make the business decisions but they also need to be involved in the schedule estimates. Programmers are programmers for a reason. Many good programmers are not good at evaluating their own work. Sometimes they are but there are tools that managers can use to evaluate the time it will take to program something given past work as a basis. I guess programmers could do this as well but like the artical says, "Programmers should program".
Anyway just my thoughts
I am wondering if they are going to use the gnu compilers or are they just going to use their own prepriatory compilors. It seems to me that businesses haven't figured out yet that if you contribute to one of the many projects as opposed to doing your own then you don't have to reinvent the wheel. You benefit from other ideas. And everyone benefits overall. What happens when every company out there is vying for their own status as the standard. It seems to me then there won't be any standards...
Slashdot Mirror
What your really looking at is some kind of Heirarchical Storage Solution. What happens is that once you have predetermined how much data will be saved from the camera each night. You can get some kind of disk array to store it on. That disk array will also be attached to some kind of HSM solutions such as what is provided by StorageTek's SAMFs. That solution will automatically backup the data that is stored on your disk and remove it from your disk so new data can be stored on the costly disks. From now on your OS and applications think that the data is on disk but in reality its on tape. When the data is requested the software will automatically get it from tape and place it back on the disk. This can be rather costly however.
From what I have found every project is different and different styles of attacking those projects are good. However I think that XP makes some very scary assumptions. First of all do customers ever even know what they want. Their assumptions may be very different that was is realistic which leads to very odd demands for features. Second, I am sure that programmers can program given just one feature but from my experience I think that its important to get a good look at the forest over the trees. At least sometimes. Programs can often be streamlined and optimized only when the full problem is understood. I do agree that managers should make the business decisions but they also need to be involved in the schedule estimates. Programmers are programmers for a reason. Many good programmers are not good at evaluating their own work. Sometimes they are but there are tools that managers can use to evaluate the time it will take to program something given past work as a basis. I guess programmers could do this as well but like the artical says, "Programmers should program". Anyway just my thoughts
I am wondering if they are going to use the gnu compilers or are they just going to use their own prepriatory compilors. It seems to me that businesses haven't figured out yet that if you contribute to one of the many projects as opposed to doing your own then you don't have to reinvent the wheel. You benefit from other ideas. And everyone benefits overall. What happens when every company out there is vying for their own status as the standard. It seems to me then there won't be any standards...