jdsullivan

3 ms·

1. 1.▲
   by jdsullivan 3y ago

   The more important and general wisdom: know your audience. You will sometimes have clients with deep technical backgrounds that expect a sufficient level of detail to have any faith or trust in your solutions. You need to be able to tailor
2. 2.▲
   by jdsullivan 11y ago

   The iBot was able to "walk" up and down stairs: http://www.dekaresearch.com/ibot.shtml In retrospect, it's a bit surprising they never enhanced it to operate hands free like this - it was made by the same fol
3. 3.▲
   by jdsullivan 12y ago

   This is a durability metric, not an availability one. This typically tells you the likelihood of losing a given object in a year. (5 9's would be quite poor for this, implying a loss of 1 object out of 100,000 every year)
4. 4.▲
   by jdsullivan 14y ago

   Not quite: "On strings, numbers and collection classes, hashCode() always returns a consistent value, apparently even across different JVM vendors. It’s like that despite the documentation for hashCode() explicitly not guaranteeing consiste
5. 5.▲
   by jdsullivan 14y ago

   Please see javadoc for String.hashCode: http://docs.oracle.com/javase/6/docs/api/java/lang/String.ht... It's true that relying on hashCode to remain stable across arbitrary objects is brittle, but this is not the case for String.