My Learning moments

In the past 8 years Skill is a blend of product + domain + data + AI lens. Learning is more from a customer point of view vs a technology point of view. How well you build your MVP depends on product and domain clarity. With a frugal setup often it means you end up playing product, domain, data, and AI roles. Many projects have to pick up and answer the below questions as part of successful strategy and MVP.

→ How you've adapted to industry shifts, GenAI's meaningful adoption 

→ How you've overcome engineering challenges balancing business goals

→ How your skills align with the company's vision, Learning to predict the future

→ How you bridge the gap between tech and business, Fast yet impactful use cases, Get the basics right

Keep Exploring!!!

Ideas - Solutions - New Perspectives

• Some knowledge is from what we worked
• Some knowledge is from what we read
• Some knowledge is from what we were referred
• The solution is always evolving

Ideas may not always have past references :)

Something Trendy <> Good

Donald Knuth advice to young engineers -
- Follow your own instincts.
- Prestige comes from doing good science, not just popular science.
- Deep knowledge builds confidence.
- A liberal education involves learning everything about something and something about everything. pic.twitter.com/LAqvitXvxq

— Vipul Vaibhaw (@vaibhaw_vipul) November 24, 2023

War <> Advanced Soceity

Kindness, Empathy Creativity is more important than Grudge, Crooked, Wicked intentions

Keep Exploring!!!

Experience vs Algorithms vs Design vs Polyglot expertise

1. If I solve all algos and core data structures - Does it make it a good programmer - Yea Possibly he can solve build solutions
2. What do I do in my work ? - Understanding data, domain, customer problems, applying the lens of data + ML + BI finding potential solutions 
3. Where does this experience come from? - Similar domains, problems, building products 
4. What does experience mean ? - Collection of different roles / functions / projects / products 
5. Did I do only development or support or testing or performance? - When you build solutions you have to wear multiple hats to build them. There is no hard boundary for each role. To think from a customer perspective and building solutions is different from building solutions and how customers will use it
6. Do I remember all algos, code now ? - Now, Some I remember, Some I learn as I apply
7. Do I need to learn to practice every day? - There is no boolean way of answering for knowledge to say you know or don't know. As long as you can build solutions and code up you are good enough to solve customer solutions.

There is no one definition of skills. Do not go by what is being dictated. Building solutions takes as much time as you learn core cs basics. Expertise comes with time and experiments, not just coding standard problems.

Keep Thinking!!!