Founders read a lot; books, articles, etc. Because how we
think about what we build important for what we build.
Tech leadership owns the need to looking onto the future and find the hidden corners. How do we plan the the unknown corners?
How do we think around a problem? What patterns work and what are just defaults that do not yield the results we want.
The cost of code has dropped. What happens to all the decisions based on the old cost models?
We hunt the non-obvious move—radical at first glance, simple in hindsight—by questioning the rules everyone follows.