There are definitely cases where forward chaining is better than backward chaining. I would say that my example of coming up with risk-driven development of taking a data engineering project and identifying that the most likely risk was actually the libraries and not the user interface,I would say that's forward chaining. So maybe you could talk us through like how do you do forward chaining or what's kind of a good procedure for doing forward chaining? Like maybe you walked it, walked us through the process.
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