Restructure data into an index when it needs to be accessed quickly. A list of hashmaps is about as deep as it should get. Deeply nested data creates tight bindings to structure where they shouldn't exist. Separate concerns when using structured data: Data in storage/transport should be as flat as possible.Neither of these was a mistake.ĭuring my first 2 years at Salesforce, I came to these conclusions: and choosing to work with the guy I actually sat next to most of the previous couple years. Attempts at using concurrency were pretty frustrating and complicated.Īround 2 years ago, I made my new team decision primarily based on 2 opportunities: the opportunity for learning functional programming practices and Clojure. Using Ruby meant that you were choosing ease over performance. My first couple years were heavy in Ruby using object-oriented paradigms and though I really enjoyed using Ruby and the many creature comforts that came with it, it also had a lot of drawbacks as a language. So pretty soon I've spent about even time on two different teams over 4 years.
I started at working Salesforce in around this time 2014.
