“You are neither right nor wrong because the crowd disagrees with you. You are right because the data and reasoning are right.”
As a quick note, I was just reminded that you can populate a Scala
List using a
Range, like this:
scala> (1 to 5).toList res0: List[Int] = List(1, 2, 3, 4, 5) scala> (1 to 10 by 2).toList res1: List[Int] = List(1, 3, 5, 7, 9) scala> (5 to 11).toList res2: List[Int] = List(5, 6, 7, 8, 9, 10, 11) scala> ('d' to 'h').toList res3: List[Char] = List(d, e, f, g, h)
Those are just a few examples. For many more ways to populate Scala lists with sample data, see How to populate Scala collections with a Range, How to generate random numbers, characters, and sequences in Scala, and Different ways to create and populate Lists in Scala.
My new favorite website (ITHare.com) has this terrific infographic that demonstrates that all CPU operations are not equal.
architecht.io has this interesting interview with Bradford Cross on AI and startup businesses. I don’t know much about AI, but from my experience with it, I’m sure that you want to “own” the data.
“The plural of anecdote is not data.”
“To me, the most important part of a program is laying out the data structure.”
I’ve seen several articles about major software bugs (and a lack of testing) recently, and one of them is related to MRI/fMRI image processing. From this article at theregister.co.uk:
When you see a claim that “scientists know when you're about to move an arm: these images prove it”, they're interpreting what they're told by the statistical software.
A whole pile of “this is how your brain looks like” fMRI-based science has been potentially invalidated because someone finally got around to checking the data.
I’m sure there must be other ways to mathematically see these differences, but I agree with the general concept that it can be easy to be misled by data. (Image from this Twitter page.)
How big is your data? This slide comes from this Twitter page.
If you need to have multiple types extend a base type in Haskell, while using the
data keyword, and while using Haskell’s record syntax, this approach seems to work: