Backward-chaining is the idea of starting with something concrete that's not quite what you want and then taking a step back. In software, one thing I was trying to do at one point was see if essentially I could take a Python script and run a slightly modified version of it on hundreds of different machines. And so I googled around a bit and found a product Amazon Web Services batch which offered to do this for me. So now my previous approach of just forward chaining all the time would have been to try and really study exactly how batch worked. Instead I took a specific batch project, made sure it worked, and then deleted all of the stuff that was specific to
Read the full transcript here.
What is risk-driven development? How should we weigh advice, best practices, and common sense in a domain? What makes some feedback loops better than others? What's the best way to take System 2 knowledge and convert it to System 1 intuition? What are forward-chaining and backward-chaining? When is it best to use one over the other? What are the advantages and disadvantages of centralization and decentralization?
Satvik Beri is a cofounder and head of Data Science at Temple Capital, a quantitative hedge fund specializing in cryptocurrency. He is a big believer in the theory of constraints, and he has a background helping companies find and eliminate major development bottlenecks. Some of his interests include machine learning, functional programming, and mentorship. You can reach him at satvik.beri@gmail.com.
Staff
Music
Affiliates