3 ms·

2x of silicon valley and then bonus on top, but that required moving into finance. It also helped that my previous employer was Apple, it opened many doors whe

2x of silicon valley and then bonus on top, but that required moving into finance. It also helped that my previous employer was Apple, it opened many doors when it came time to interview. The fact of the matter is that other industries are starved for talent. If you can keep up in silicon valley, where all anyone talks about is technology, you will be godly in a different marketplace with more capital flow. Finance in particular has way too many people who think things like this are a good idea and The Right Thing To Do: https://github.com/goldmansachs/gs-collections https://github.com/goldmansachs/gs-collections

sk5t 12y ago
Do you mean they're self-satisfied enough to write themselves a framework, but too myopic to see that writing it is a massively misguided waste of time?
- MichaelGG 12y ago
  Maybe it's because I don't know Java, but the complete separation of interface for "ImmutableBagFactory" and an implementation "ImmutableBagFactoryImpl", and the fact you need a factory for an "ImmutableBag" in the first place... seems like very poor design. Even if it is common in Java (?).
  - lmm 12y ago
    Given that constructors can't conform to interfaces, if you want to be able to pass a constructor around you pretty much have to do this. I agree it's probably overkill, but if you wanted really strong compatibility guarantees I can see how this would make sense.
nl 12y ago
Finance in particular has way too many people who think things like this are a good idea and The Right Thing To Do: https://github.com/goldmansachs/gs-collections https://github.com/goldmansachs/gs-collections . I think that's a pretty unfair criticism. Firstly, it isn't clear exactly what you don't like about it. That it is Java? That it exists? You need to put its existence into historical context. When it came out, it was before Google's Guava collections libraries were open source, so there were no decent collections libraries that did more than what the JDK libraries did. That's the context GS Collections were built for. (Disclaimer: I've never used them, but I do remember when they were released)
twic 12y ago
The last remark is baffling. There is no shortage of bad ideas in finance. GS collections isn't one of them.

sk5t 12y ago

Do you mean they're self-satisfied enough to write themselves a framework, but too myopic to see that writing it is a massively misguided waste of time?

MichaelGG 12y ago
Maybe it's because I don't know Java, but the complete separation of interface for "ImmutableBagFactory" and an implementation "ImmutableBagFactoryImpl", and the fact you need a factory for an "ImmutableBag" in the first place... seems like very poor design. Even if it is common in Java (?).
- lmm 12y ago
  Given that constructors can't conform to interfaces, if you want to be able to pass a constructor around you pretty much have to do this. I agree it's probably overkill, but if you wanted really strong compatibility guarantees I can see how this would make sense.

nl 12y ago

Finance in particular has way too many people who think things like this are a good idea and The Right Thing To Do: https://github.com/goldmansachs/gs-collections https://github.com/goldmansachs/gs-collections . I think that's a pretty unfair criticism. Firstly, it isn't clear exactly what you don't like about it. That it is Java? That it exists? You need to put its existence into historical context. When it came out, it was before Google's Guava collections libraries were open source, so there were no decent collections libraries that did more than what the JDK libraries did. That's the context GS Collections were built for. (Disclaimer: I've never used them, but I do remember when they were released)

twic 12y ago

The last remark is baffling. There is no shortage of bad ideas in finance. GS collections isn't one of them.