To generate value, one needs to solve real problems, to solve problems needs to know business execution at ground level, this just translates to people, data, information, and touchpoints. Taking some info from ground level, Adding the pieces with your ideas, and Building a working idea is the balance of feasibility vs solution analysis. We may not know everything 100% but learning things on the go/need basis and learning to make progress in the interest of time is key. The feeling of once you do two or three examples, This is all it is all about that becomes paramount :)
The ability to learn / self-manage / progress with directions / see the big picture is more important than remembering code syntax. I believe it's a balance of all, not just algos. How you know where to apply, and when to apply is much beyond kaggle and competitive tests :)
- Learning business
- Knowing Touchpoints
- Data Exchange patterns - Methods of information exchange (Batched / Real-time)
- Tech tools landscape
- Prototype code up
- 30% business, 30% data, 30% code to get perspective
- Hire someone who knows what business problem they solve
- How they design based on time constraints
- Tradeoff on Tech vs Time vs Design
- Thinking for scale/performance
- Need not be full stack but knows how to communicate and get things done
- Customer is more important than individuals EGO's
Keep Exploring!!
No comments:
Post a Comment