em7

joined 1 year ago
[–] [email protected] 9 points 1 year ago

Then I'm guilty of breaking the license. I have always been stealing code from Stack Overflow. Well, since I'm a senior dev right now I steal only from answers.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)
[–] [email protected] 3 points 1 year ago

Can you make it an Enterprise Bean?

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

Not sure what financing applications you develop. But what you suggest wouldn't pass a code review in any financial-related project I saw.

Using integers for currency-related calculations and formatting the output is no dirty hack, it's industry standard because floating-point arithmetic is, on contemporary hardware, never precise (can't be, see https://en.wikipedia.org/wiki/IEEE_754 ) whereas integer arithmetic (or integers used to represent fixed-point arithmetic) always has the same level of precision across all the range it can represent. You typically don't want to round the numbers you work with, you need to round the result ;-) .

[–] [email protected] 1 points 1 year ago (1 children)

If the language has really good type inference (Haskell comes to my mind though F# was quite nice as well) it's better. It really makes life much easier.

However when dealing with real-world problems (just moving data around which are changing constantly) the types don't really add that much, you need to test anyway. Test suites is what I need. Clojure and Common Lisp are OK.