Sometimes we're given advice, like an industry best practice or standard technique. And yet sometimes we might want to take it anyway because it's a best practice. We assume that because people have been doing a long time and it's recommended, it's probably a good idea. Other pieces of advice you really only want to do them if you kind of like deeply understand the reasoning behind them.
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