He provides a great explanation for the reader without familiarity with advanced physics, but at a level which is still interesting to the technical reader.
It doesn't make any sense to use floating point arithmetic in most financial calculations, anyway. Using integer arithmetic it's really easy to guarantee that money just doesn't disappear or appear due to rounding errors.
And if it has to handle amounts of money greater than $40 million (~2^32 cents) then you can just use 64-bit ints.
Exactly - except that the people who use linux all the time tend to abhor too much eye candy. A lot of *nix users think KDE or Gnome is too much already.
A lot of people who like fancy, useful 3d user interfaces have already got their macs too:)
code flow is just as important as code coverage. If code in section 1 is executed in unit test 1, and code in section 2 is executed in unit test 3, there needs to be a unit test which executes both. All combinations have to be handled, if sections of code have side effects on other sections.
If you have a nice gas cooktop and some cooking skills you can make a lot at home. Uni cafeteria can be a huge money drain if you're eating 3 meals a day.
For 4 people, you could probably save 50 pounds a month if everyone chips in and does some food work. Nothing fancy, but stay away from prepackaged food also, it's just as expensive and not healthy either.
Having a design is worthless unless you develop a series of tests against it. Even the best designs by the best software engineers have flaws, and if there aren't, some flaws will pop up in coding.
You can have a perfect design and crummy code, I've seen it over and over again.
Extreme programming is your friend on this one. Doesn't matter what language you use, test and retest at every change. Testing is the only, only, only way to get extremely stable software outside of formal verification methods.
Slashdot Mirror
Sean Carroll (and some other notable physicists) have a blog which covered this in more detail. See http://cosmicvariance.com/2006/11/16/dark-energy-h as-long-been-dark-energy-like/
He provides a great explanation for the reader without familiarity with advanced physics, but at a level which is still interesting to the technical reader.
It doesn't make any sense to use floating point arithmetic in most financial calculations, anyway. Using integer arithmetic it's really easy to guarantee that money just doesn't disappear or appear due to rounding errors.
And if it has to handle amounts of money greater than $40 million (~2^32 cents) then you can just use 64-bit ints.
Exactly - except that the people who use linux all the time tend to abhor too much eye candy. A lot of *nix users think KDE or Gnome is too much already. A lot of people who like fancy, useful 3d user interfaces have already got their macs too :)
code flow is just as important as code coverage. If code in section 1 is executed in unit test 1, and code in section 2 is executed in unit test 3, there needs to be a unit test which executes both. All combinations have to be handled, if sections of code have side effects on other sections.
If you have a nice gas cooktop and some cooking skills you can make a lot at home. Uni cafeteria can be a huge money drain if you're eating 3 meals a day. For 4 people, you could probably save 50 pounds a month if everyone chips in and does some food work. Nothing fancy, but stay away from prepackaged food also, it's just as expensive and not healthy either.
Having a design is worthless unless you develop a series of tests against it. Even the best designs by the best software engineers have flaws, and if there aren't, some flaws will pop up in coding. You can have a perfect design and crummy code, I've seen it over and over again.
Extreme programming is your friend on this one. Doesn't matter what language you use, test and retest at every change. Testing is the only, only, only way to get extremely stable software outside of formal verification methods.