http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/ The Cigital Software Security and Quality Blog Fri, 16 May 2008 03:52:22 +0000 http://wordpress.org/?v=2.0.11 http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-5180 Fri, 28 Dec 2007 16:44:07 +0000 http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-5180 What a great article! I'm glad to know the details of this example (which I mentioned in our own blog above) and also the fact that sometimes simpler is better than fancy for writing codes. A good example to pass along to my own undergraduate math majors.... What a great article! I’m glad to know the details of this example (which I mentioned in our own blog above) and also the fact that sometimes simpler is better than fancy for writing codes. A good example to pass along to my own undergraduate math majors….

]]> http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-5179 Fri, 28 Dec 2007 16:30:10 +0000 http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-5179 [...] Or at least, there used to be. In the article “A Tale of Two Banks,” Craig Miller explains how in the 1970s compounding wasn’t done as frequently as today, both because of the market and because of technological limits. At one point, though, two banks began to use the frequency of compounding as a way to compete with each other: one advertised weekly, the next daily, and then the first announced that it would compound continuously. The second bank followed, and Miller was hired to write the appropriate code. (The article itself contains many more details of the scenario, and is certainly worth a read!) [...] […] Or at least, there used to be. In the article “A Tale of Two Banks,” Craig Miller explains how in the 1970s compounding wasn’t done as frequently as today, both because of the market and because of technological limits. At one point, though, two banks began to use the frequency of compounding as a way to compete with each other: one advertised weekly, the next daily, and then the first announced that it would compound continuously. The second bank followed, and Miller was hired to write the appropriate code. (The article itself contains many more details of the scenario, and is certainly worth a read!) […]

]]> http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-2538 Tue, 18 Sep 2007 15:22:43 +0000 http://www.cigital.com/justiceleague/2007/09/18/a-tale-of-two-banks/#comment-2538 Excellent story! I actually guessed Fortran by the end of your 2nd paragraph. It's what we used in 1997 to write the image processing software for an industrial grade CT Scanner. Image acquisition was done with more modern languages with built-in drivers for the CCD and locomotion (4 axes), but once all the images were acquired, we then ran Fortran routines to produce the 3D image constructions. I tried porting the Fortran to C, for better supportability, but it ended up being a wasted effort as the C never could run as efficiently. Fortran was designed for computationally complex functions like these. :) Excellent story! I actually guessed Fortran by the end of your 2nd paragraph. It’s what we used in 1997 to write the image processing software for an industrial grade CT Scanner. Image acquisition was done with more modern languages with built-in drivers for the CCD and locomotion (4 axes), but once all the images were acquired, we then ran Fortran routines to produce the 3D image constructions. I tried porting the Fortran to C, for better supportability, but it ended up being a wasted effort as the C never could run as efficiently. Fortran was designed for computationally complex functions like these. :)

]]>