In this podcast, Krish explores the process of digital analysis and how to take the analysis forward. He discusses different approaches to analyzing product usage, including general product usage analysis, client-specific product usage analysis, feature-specific product usage analysis, ad hoc analysis, and usage pattern analysis. Krish emphasizes the importance of communicating the analysis to the product team and translating it into meaningful requirements for the engineering team.
Takeaways
Chapters
00:00 Introduction and Recap
03:58 Communicating Analysis to Product Team
04:59 General Product Usage Analysis
09:34 Client Specific Product Usage Analysis
14:51 Feature Specific Product Usage Analysis
20:39 Ad Hoc Analysis
25:25 Usage Pattern Analysis
31:03 Translating Analysis into Requirements
Snowpal Products
Building a Mobile App - Part I (Starting to build a native mobile app, and wondering which way to go?)
Building a Mobile App - Part II (React Native, Flutter, and some others)
Aggregations in Mongo - Much faster and the best (and maybe only?) alternative in many cases
Make your Git commits frequent so you run into fewer merge conflicts
Heroku Cloud Application Platform - why it will help your TTM (Time to Market)
Building a Brand New Application? Looking for a way to reduce your ramp up time?
Development Efficiency - Are you bouncing your servers too often?
Code Quality - How can you assess the quality of a codebase before reviewing a single line of code?
Backwards Compatibility Issues - a few ways to ensure that you do not run into them
Native Mobile App - Design Patterns & Separation of concerns (Part 1)
Native Mobile App - Design Patterns & Separation of concerns (Part 2)
Databases & Denormalization - Faster queries for faster retrieval
Reusable UI components (React and beyond) - both presentational & functional
Caching - What to Cache, and When to Cache (Part 3)
Caching - Are you optimizing before identifying the problem? (Part 2)
When looking to make performance improvements, it is natural to look for that ”single” big problem. But, that’s hardly ever the case.
Keep your code DRY. As in, super DRY! Code duplication is a maintenance nightmare.
Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?
Should you implement that next requirement now, later or never?
[Paid Course] Snowpal Education: Writing scripts to understand REST APIs
Join Podbean Ads Marketplace and connect with engaged listeners.
Advertise Today
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast