Pakka Nimbu Podcast with Bhavin Doshi

Catch interesting conversation with Anuj Gupta and Bhavin Doshi about top misbeliefs about AI amongst leaders.

#hiring #startup #pakkanimbu Summary In this episode, Abha Bhakoo (https://www.linkedin.com/in/abhabhakoo/), VP Talent at Lightspeed India, discusses how developers, architects, and engineering managers can determine if they are a good fit for early-stage startups. She explains the different types of companies and personas that recruiters work with, such as builders, scalers, and leaders. Abha highlights the qualities that early-stage startups look for in candidates, including hands-on experience, resourcefulness, and the ability to work with ambiguity. She also emphasizes the importance of cultural fit, business acumen, and decision-making ability. Abha provides insights into the compensation structure of early-stage startups, including the significance of ESOPs. Lastly, she advises professionals to network, be open about their needs, and assess their strengths and areas for growth before considering a move to an early-stage startup. Keywords early-stage startups, fitment, builders, scalers, leaders, hands-on experience, resourcefulness, cultural fit, business acumen, decision-making, compensation, ESOPs, networking, #softwareengineer Chapters 00:00 Introduction and Background 05:58 Qualities Founders Look for in Early-Stage Startup Candidates 12:01 Navigating Compensation and ESOPs in Early-Stage Startups 23:13 The Value of Honesty, Transparency, and Open Communication 27:00 Committing to the Long-Term: Understanding the Vision and Motivation This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is 10xBluejay, Shift Left Incident Management Powered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Do check them out: http://10xbluejay.com/?utm_source=pakkanimbu&utm_medium=youtube&utm_campaign=engineeringUnplugged&utm_content=educate! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this conversation, Bhavin Doshi interviews Anuj Gupta (https://www.linkedin.com/in/anujgupta-82/) about career counseling for developers in the field of AI. They discuss whether developers should switch to an AI team, the importance of being AI aware, and how to make oneself more AI aware as a software developer. They also talk about the wrong steps to take in adding AI to one's resume, how to catch companies that glorify AI in job descriptions, and the critical questions to ask to understand the depth of AI work in a company. The conversation concludes with a discussion on the role of AI engineers and the future of AI. Keywords AI, career counseling, software development, AI team, AI awareness, resume, job descriptions, AI work, AI engineers, future of AI Takeaways - Developers should consider switching to an AI team based on their interest and passion for AI, rather than just following trends. - Being AI aware is important for all developers, even if they don't switch to an AI team, as AI is becoming more prevalent in various fields. - To make oneself more AI aware, developers can start with a project, learn the foundations of AI, and understand the limitations and nuances of AI. - When applying to positions with an AI component, it's important to ask critical questions about the depth of AI work in the company and not be swayed by glorified job descriptions. - AI engineers play a crucial role in optimizing AI systems and require a combination of software engineering and AI knowledge. - The future of AI will involve the evolution of roles and demands, and it's important to focus on what one is naturally good at and continue learning and adapting. Titles The Future of AI The Role of AI Engineers Sound Bites - "Should I switch to an AI team? Should I worry about leaving behind the regular software development and just switch to an AI team?" - "AI requires very specialized UX design because AI systems still make a lot of mistakes" - "It's more about being aware of AI and being aware of what AI's effects are on your craft." Chapters 00:00 Introduction and Switching to an AI Team 04:43 Specialized UX Design for AI Systems 09:24 Being AI Aware as a Software Developer 24:08 Becoming More AI Aware through Hobby Projects 29:36 The Role of AI Engineers 35:28 The Future of AI This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

#practo #seniorengineer #softwareengineers In this conversation, Bhavin Doshi and CTO of Practo Abhinav Lal (https://www.linkedin.com/in/abhinavlal/) discusses various aspects of tech debt and architectural decisions at Practo. Abhinav clarifies misconceptions around tech debt, emphasizing that tech debt is an intentional choice. He also shares insights into Practo's tech stack, including the use of SQL databases and Elasticsearch. He highlights the importance of addressing tech debt iteratively and the need to balance paying off the principal and interest. Abhinav concludes by discussing the challenges of throwing away code and the cultural mindset needed to tackle tech debt effectively. This conversation covers topics such as managing tech debt, engineering's value to the business, owning business outcomes, balancing short-term and long-term thinking, managing cloud costs, and Abhinav's journey from developer to CTO. Abhinav shares insights and experiences from his time at Practo, including the challenges and lessons learned along the way. Chapters in this video: 00:00 Introduction 09:00 Tech Stack and Evolution of Practos Products 23:44 Early Architectural Decisions 38:32 Tech Debt and Prioritization 51:02 Managing Tech Debt 54:23 Engineering's Value to the Business 56:46 Owning Business Outcomes 59:13 Balancing Short-term and Long-term Thinking 01:07:11 Managing Cloud Costs 01:16:37 Abhinav's Journey from Developer to CTO 01:33:46 Interesting Incidents from the Early Days This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this episode, Prajwal Kumar, AVP of Human Capital with Matrix Partners India, discusses the role of talent acquisition and its importance for businesses. He emphasizes the need for founders to have a clear understanding of their team-building requirements and aspirations. Prajwal also highlights the role of recruiters as candidates' advocates and the importance of building relationships with them. He provides insights into sourcing candidates and optimizing LinkedIn profiles, including the need to quantify impact in resumes. Prajwal also addresses common mistakes in resumes and the effectiveness of employee referrals in the hiring process. This conversation covers various aspects of the hiring process, including employee references, application response, filtering profiles, selecting the best offer, considerations beyond compensation, risk, and growth, the impact of layoffs, and the importance of networking. Chapters: 01:00 Introduction and Role of Talent Acquisition 02:03 Importance of Talent Acquisition for Businesses 03:35 Viewing Recruiters as Candidates' Advocates 06:31 Building a Relationship with Recruiters 15:59 Optimizing LinkedIn Profiles 19:20 Quantifying Impact in Resumes 22:29 Importance of metrics driven impact in resume 25:30 Common Mistakes in Resumes 28:30 Applying for Jobs and Employee Referrals 29:19 Employee Reference and Application Response 30:10 Filtering Profiles for Hiring Managers 32:50 Selecting the Best Offer 37:36 Considerations for Offer Selection 42:40 Factors Beyond Compensation, Risk, and Growth 46:25 Layoffs and Their Impact 55:19 The Importance of Networking This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

Hari talks about the journey of starting HackerRank, expanding the team, scaling the organization, the tech stack and infrastructure, monitoring and alerting, front-end development, and shares some scale experiences and mishaps. In this conversation, Hari Karunanidhi, the CTO of HackerRank, discusses various technical challenges and scaling issues faced by the company. He emphasizes the importance of end-to-end ownership and the need for developers to understand the whole context of their work. Hari also highlights the value of customer input and the role of technical practices in shaping the culture at HackerRank. He shares insights on remote work, conferences, and the importance of upskilling and learning opportunities for developers. The conversation concludes with a discussion on the potential of case studies, streaming coding sessions, and sharing experiences and learnings. Chapters in this video: 00:00 Starting HackerRank and the Early Challenges 08:23 Expanding the Team and Hiring Managers 16:22 Scaling the Team and Organizational Structure 29:18 Monitoring and Alerting 39:29 Front-End Development and Developer Experience 42:23 Scale Experiences and Mishaps 48:40 Technical Challenges and Scaling 51:01 Technical Practices and Culture 53:26 Learning from Customers 54:56 End-to-End Ownership 55:23 Identifying End-to-End Ownership in Hiring Process 58:41 Work from Office vs. Work from Home 59:10 Value of Conferences and Networking 59:37 Support and Recommendations for Developers 01:03:00 Early Days of HackerRank 01:03:28 Technical Practices and Culture at HackerRank 01:09:45 Managing Teams and Collaboration Across Time Zones 01:14:27 Value of Conferences in the Digital Age 01:17:42 Upskilling and Learning Opportunities for Developers 01:19:08 Breaking Down Silos and Fostering Collaboration 01:21:26 Learning from Open Source and Launching Projects 01:23:21 The Importance of Case Studies and Real-World Examples 01:25:14 Encouraging Innovation and Hackathons 01:27:11 The Potential of Streaming Coding Sessions 01:29:01 Sharing Experiences and Learnings This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠10xBluejay⁠⁠⁠, Shift Left Incident Management Powered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

Harshad Saykhedkar shares his background and past experiences in the AI/ML field, including working at Slack and Astro. He discusses the challenges of transitioning from hardware to software engineering and the importance of effective communication in remote work settings. Harshad also talks about the acquisition of Astro by Slack and the learnings he gained from working in a US-based company. He then dives into the early days of building xAmbit AI, the decision to quit his full-time job, and the iterative process of finding the right product-market fit. Harshad explains the architectural decisions made for Xambit AI and the roadmap for the company's future. In this conversation, Harshad discusses the work being done at xAmbit AI and their focus on building AI applications in-house. He also mentions his passion for teaching AI and mathematics to others. The conversation then shifts to the target market of xAmbit AI and their plans for expansion. Finally, the conversation concludes with closing remarks and appreciation for the podcast. Takeaways Effective communication is crucial in remote work settings, especially when working with cross-cultural teams. Working in a US-based company can provide valuable experience and exposure to different perspectives and feedback. Building a startup requires taking a leap of faith and being open to iterating on ideas and pivoting when necessary. Architectural decisions should prioritize security, scalability, and the ability to understand and control the technology stack. xAmbit AI aims to automate and improve workflows in finance and legal industries using AI, with a focus on building real solutions for real problems. xAmbit AI focuses on building AI applications in-house and welcomes those interested in working with Rust and PyTorch to reach out to them. Harshad has a passion for teaching AI and mathematics and has conducted workshops on these topics. xAmbit AI currently targets the Indian market and plans to achieve product-market fit in India before expanding globally. Chapters 00:00 Introduction and Background 01:21 Past Experiences 05:04 Learnings from Previous Jobs 09:11 Working in a Remote Setting 12:32 Acquisition of Astro by Slack 19:12 Starting Exambit AI 20:26 Considerations in quitting to do your own startup full-time 25:11 Building Xambit AI 30:32 Architectural Decisions 39:24 Product and Technical Roadmap 41:35 Building In-House and Teaching AI 42:47 Target Market and Expansion Plans 43:48 Closing Remarks This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠10xBluejay⁠⁠, Shift Left Incident Management Powered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this conversation, Sahil Ahuja and Bhavin discuss the challenges and strategies of managing library dependencies in software development. They explore the differences between patch, minor, and major versions and the impact of each on code stability. They also delve into the complexities of major version upgrades and the need for careful planning and testing. The conversation highlights the importance of maintaining a layered repo structure to facilitate easier bug fixing and code changes. Sahil shares his experience with upgrading from React VR to React XR and the significant performance improvements it brought. They also discuss the role of automated testing in VR environments and the benefits of manual testing in certain scenarios. Chapters 00:00 Introduction and Context 00:58 Understanding Patch, Minor, and Major Versions 02:24 The Challenges of Major Version Upgrades 04:17 Managing Dependencies in a Layered Repo Structure 07:36 Delaying Major Version Upgrades 09:33 Dealing with Minor Version Changes 12:27 Upgrading Libraries and Mitigating Risks 15:51 Backend Repo Dependencies 18:14 Upgrading Backend Libraries 21:32 The Story of React VR and React XR 23:54 Challenges with React XR and the Decision to Switch 26:49 Rewriting GMetri with React 3 Fiber 30:55 Lessons Learned and What Could Have Been Done Differently 35:37 Automating Tests in VR Environments 37:59 Closing Remarks This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠10xBluejay⁠, Shift Left Incident Management Powered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

Why is boredom important for software engineers? What is the power of jargons to allow you to think about very complex things in a simple manner? Which of the generalist vs specialist hiring should you prefer as a candidate? Find out about all of this, and more, in this episode of Pakka Nimbu Podcast with Manu Manjunath, Senior Principal Engineer at Atlassian, who shares unique insights from his long journey through various startups! This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is 10xBluejay, Shift Left Incident Management Powered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 Introduction 01:05 One early ingredient in Manu's growth journey 4:50 Changing tech domains while switching jobs 8:33 Specialist vs Generalist hiring 11:00 Professional upskilling routines 20:00 Technical conferences for networking and growth 22:21 Are we over-entertained today? 30:44 Reading books and scatter focus 34:16 Power of technical jargons 39:08 Outro Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this episode, Swanand Pagnis discusses the importance of deep work and how it can lead to career growth and mastery. He shares his experiences in building the Ruby community and highlights the challenges he faced in finding meaningful work. Swannand emphasizes the need for clear boundaries between deep work and shallow work, and suggests strategies for reducing the number of meetings. He also discusses the value of pairing-free time and the importance of thinking time. Overall, Swanand encourages listeners to prioritize deep work and develop an X factor in their careers. In this conversation, Bhavin Doshi discusses the principles and strategies of deep work. He emphasizes the importance of planning for uncertainty and having a clear focus. He suggests using weekly themes to prioritize tasks and manage multiple streams of work. Bhavin also highlights the need for a productive work environment and the value of leisure time. He cautions against going too far down the rabbit hole and overestimating deep workability. Finally, he warns of the pitfalls of losing the big picture, ineffective collaboration, and missing out on leadership opportunities. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters: 00:00 Introduction and Building the Ruby Community 03:00 The Challenge of Deep Work 08:09 The Caliber vs Ambition Problem 10:56 The Value of Deep Work 18:40 Narrative Structure of the Talk 21:07 Setting Boundaries Between Deep Work and Shallow Work 23:34 Reducing the Number of Meetings 30:39 Meeting-Free Days and Weeks 37:24 Segmenting Shallow Work 39:49 The Importance of Pairing-Free Time 41:46 The Importance of Thinking Time 49:32 Navigating Uncertainty for Focus 53:00 Planning for Uncertainty 56:17 The Power of Weekly Themes 58:40 Leadership and Deep Work 59:11 The Importance of Leisure Time 01:01:08 Creating a Productive Work Environment 01:06:01 Embracing Boredom 01:13:30 Working at the Edge of Your Ability 01:25:36 Pitfalls of Deep Work Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this conversation, Anand Bagmar shares his journey in the software space and the defining experiences that shaped his beliefs. He discusses the transition from testing to quality and the importance of understanding agile and influencing quality throughout the software development lifecycle. Anand emphasizes the need to focus on practices rather than best practices, as what works in one context may not work in another. He also explores the challenges of managing empowerment and risk, and the importance of understanding the impact of testing on the end user. The conversation concludes with a discussion on shift left and the need for developers to take responsibility for testing. The conversation explores the concepts of shift left and shift right in software development. Shift left refers to moving testing earlier in the development cycle, while shift right focuses on automating deployments, configurations, and feedback loops. Both shifts are essential for ensuring quality and involve all roles in the development process. The conversation also highlights the importance of developers asking questions about requirements, understanding test cases, and writing tests for their code. Mistakes that developers often make include not prioritizing testability and measurability, and not performing a thorough sanity check before handing over their work. Chapters 00:00 Introduction and Background 03:49 Defining Experiences and Transformation 09:24 Transition from Testing to Quality 12:05 Changing Testing Approach 17:21 Understanding Agile and Influencing Quality 20:17 Practices and Best Practices 25:05 Starting Point and Context 28:22 Managing Empowerment and Risk 31:46 Handling OTP Validation 36:45 Connecting to Databases and Test Data Management 45:21 Testing Scenarios in Production 51:33 Understanding Impact and Shift Left 53:11 Shift Left and Shift Right 59:09 Mistakes Developers Make This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find Bhavin Doshi on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

The conversation explores the concept of the pirate mindset in the world of software development. The spirit of the pirate is about being rebellious, breaking rules, and embracing a sense of adventure and exploration. It is a reminder to not lose sight of the DNA of the rebel and renegade that drives innovation. The conversation also delves into the importance of craftsmanship and engineering in software development, emphasizing the need to be both a good craftsman and a good engineer. Pirate stories from the speaker's career highlight the value of taking risks, trusting one's judgment, and being responsible while challenging the status quo. The conversation concludes by discussing the relevance of the pirate mindset in today's rapidly evolving tech landscape, emphasizing the need for continuous learning, adaptation, and collaboration. In this conversation, Bhavin Doshi discusses the importance of collaboration and teamwork in software development. He emphasizes the need for all team members, including product managers, project managers, and DevOps professionals, to adopt a pirate mindset and work together towards a common goal. Bhavin also highlights the value of a strong team in building successful software products. He mentions the book 'The Mythical Man-Month' and its relevance even today. Finally, Bhavin shares his new venture as a YouTube and Twitch streamer, where he focuses on programming and building a generative AI startup called Vivary. Chapters 00:00 The Spirit of the Pirate 14:07 Craftsmanship and Engineering 19:55 Pirate Stories: SAP and Scaling IT Infrastructure 30:27 Taking Risks and Trusting Your Judgment 33:45 The Pirate Philosophy and Hacker Culture 39:57 Continuous Learning and Adapting 43:49 Building Empathy and Collaboration 47:36 Relevance of the Pirate Mindset 50:03 The Importance of Collaboration and Teamwork 52:08 The Value of a Strong Team 52:39 The Timelessness of Advice 53:07 Bhavin's YouTube and Twitch Streaming This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is 10xBluejay, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! You can find Vagmi here: Twitch: https://www.twitch.tv/hackwithvagmi X: https://x.com/vagmi Youtube: https://www.youtube.com/@vagmi LinkedIn: https://www.linkedin.com/in/vagmi/ Find me on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In this conversation, Bhavin Doshi and Senthil discuss the growth of software engineering and the importance of aligning architecture with business goals. They explore the concept of industrial engineering and the need for on-the-job learning. The conversation also delves into the balance between technical depth and managerial skills, emphasizing the importance of understanding the business impact of software solutions. They discuss the challenges of articulation and the role of emotion in software engineering. Finally, they explore the benefits of leveraging the team for clarity and the importance of balancing introversion with team interaction. This conversation explores the balance between good tech and good business solutions, emphasizing the importance of avoiding extremes. The concept of tech debt is discussed, with an emphasis on quantifying and prioritizing debt based on its impact. The conversation also delves into measuring interest payments and considering the probability and business impact of tech debt. The importance of identifying slow poison and avoiding costly mistakes is highlighted. The conversation concludes with three top suggestions for personal growth: expanding abstraction, learning new skills, and considering the growth environment. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 Introduction and Background 02:15 Software Engineering Growth 03:41 Industrial Engineering and Learning on the Job 07:05 Fundamental Principles of Software Engineering 08:33 Aligning Architecture with Business 09:32 Common Practices in Good Engineering 11:29 Technical Depth and Managerial Skills 17:43 Balancing Technical and Business Considerations 20:00 The Role of Emotion in Software Engineering 23:47 Developing the Skill of Articulation 26:11 Being Part of a Team and Leveraging the Team 32:12 Balancing Objectivity and Emotional Attachment 38:24 Overcoming Challenges in Articulation 42:38 Leveraging the Team for Clarity 45:03 Balancing Introversion and Team Interaction 49:50 Balancing Tech and Business Solutions 51:05 Quantifying Tech Debt 52:29 Measuring the Impact of Tech Debt 53:54 Quantifying Debt and Prioritizing 56:18 Measuring Interest Payments 58:16 Considering Probability and Business Impact 01:00:06 Identifying Slow Poison 01:02:05 Avoiding Costly Mistakes 01:05:15 Expanding Abstraction and Learning New Skills 01:07:11 Growth in the Right Environment Find me on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠⁠https://youtube.com/@pakkanimbu⁠⁠

In the episode 05 of Pakka Nimbu podcast, we have Sahil Ahuja, CTO of GMetri. GMetriXR is a no-code editor to build your own metaverse. Sahil talks about the architecture of metaverse system, moving away from cloud and self-hosting the infrastructure, creating a virtual file system and solving latency problems for global metaverse. He also talks about importance of IAC (infrastructure as code) to do sustainable infra, importance of incremental solutions (and avoiding big bang solutions), and insights into build vs buy decisions in startups. Sahil graduated from NIT Trichy, and did his finance masters from IIM Calcutta. He worked at Goldman Sachs and Bank of America Merryl Lynch, before discovering his love for hacking and building systems. He has been building GMetri since 2016. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 Introduction and Background 01:00 Introduction to Gmetri 03:19 Metaverse Experiences and Self-Exploration 04:17 Architecture and Infrastructure Challenges 06:09 Building a Virtual File System 07:35 Unconventional Decisions and Solutions 10:02 Robustness and Edge Cases 11:28 Latency and Global Platform Challenges 13:50 Solving Latency Issues 18:02 Challenges of Replicating Data 20:27 Addressing Latency with Caching 22:23 Making Cost-Effective Decisions 23:20 Transitioning to Self-Hosting 26:40 Setting Up a Personal Data Center 28:35 Managing Hardware Failures 30:29 Software Upgrades and Management 32:24 Data Center Hosting and Cost Savings 38:12 Build vs Buy Decision 41:34 Scaling and Hiring Sysadmins 42:52 Transitioning to Self-Hosting 43:18 Managing Connectivity during COVID-19 Links from this podcast: https://doku.dev/post/2020/gmetri-built-its-own-data-center-and-cut-cloud-costs/ https://www.youtube.com/@gmetrixr/videos https://docs.gmetri.com Find me on other platforms: LinkedIn: ⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠⁠⁠ Youtube: ⁠⁠⁠https://youtube.com/@pakkanimbu⁠

This conversation discusses the challenges of dealing with flaky tests and the impact they have on the development process. The speaker shares their experience of struggling with identifying and fixing flaky situations, as well as the psychological and operational impact it had on them. They explain how they decentralized the problem by defining test health and flakiness, building a service catalog, and routing alerts to the appropriate teams. The speaker also discusses the importance of approaching engineering problems with calmness and the need to improve code organization. They highlight the efforts made to speed up the CI suite and reduce test coupling. The conversation concludes with a discussion on introducing static analysis tools and the cultural change and adoption process. In this conversation, Puneet shares his experience of implementing changes to improve the CI/CD process. The transfer of ownership from the central team to developers was facilitated by minimizing additional work through documentation and providing examples. Quantifying the impact and value of the changes helped in gaining developer buy-in. Enforcing ownership and responsibility was driven top-down by management, with metrics and performance indicators supporting the shift. The differentiation between critical and non-critical tests allowed for targeted alert routing and escalation. The involvement of managers and automation helped create urgency and behavior change. Puneet advises focusing on solving patterns rather than instances and investing time in learning from others' experiences. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 Introduction 00:59 Challenges with Flaky Tests 02:23 Decentralizing the Problem 04:17 Defining Test Health and Flakiness 05:16 Building a Service Catalog 06:16 Approaching Engineering Problems with Calmness 07:44 Routing Alerts and Ownership 08:39 The Impact of Routed Alerts 09:09 The Challenges of Alert Routing 10:34 Improving Code Organization 11:33 Identifying and Fixing Flaky Situations 16:19 Predicting Test Failures 17:18 Debugging Flaky Tests 18:16 Struggling with Building a Complete Process 19:44 Escalating the Problem to Developers 21:09 The Impact of Flaky Tests on Production 23:36 The Inconvenience of Flaky Tests 25:02 The Cycle Times of CI Runs 26:27 Speeding Up the CI Suite 28:21 Improving MongoDB Performance 30:40 Reducing Test Execution Time 32:08 Reducing Test Coupling 35:30 Introducing Static Analysis Tools 39:19 Adopting Linters and Formatters 41:42 Cultural Change and Adoption 46:29 Improving Pre-Commit Checks 47:57 Transfer of Ownership 48:26 Minimizing Additional Work for Developers 49:26 Documenting for Easy Learning 50:50 Quantifying the Impact and Value 51:48 Enforcing Ownership and Responsibility 52:43 Metrics and Management Support 53:13 Measuring Flakiness and Ownership 54:09 Creating Urgency and Behavior Change 55:07 Differentiating Critical and Non-Critical Tests 56:06 Failure Scenarios and Ownership 57:36 Escalation and Manager Involvement 59:01 Democratizing Alerts and Involvement 59:56 Differentiating Infrastructure and Application Failures 01:03:20 Solving Patterns, Not Instances 01:05:46 Learning from Others' Experiences 01:06:15 Investing Time in RCA and Learning 01:07:34 Avoiding Overcommitment and Seeking Feedback Find me on other platforms: LinkedIn: ⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠ Twitter: ⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠ Telegram: ⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠ Youtube: https://youtube.com/@pakkanimbu

In this episode, Bhavin Doshi interviews Alagu Muthuraman, co-founder at Peoplebox, about a production issue they faced with collaborative editing. They discuss the challenges of debugging an issue that is hard to reproduce and the stress management required during such incidents. Alagu shares his experiences and strategies for staying calm and strategic in high-pressure situations. He emphasizes the importance of creating a safe space for the team, buying time to fix the issue, and normalizing the situation by sharing stories of similar incidents. He also advises young engineers to be prepared for stressful situations and to focus on learning and growth. In this conversation, Bhavin Doshi shares insights on handling stress and improving performance in high-pressure situations. He discusses different approaches in crisis situations and emphasizes the importance of reflecting on incidents and learning from them. Bhavin also highlights the need for creating playbooks to handle incidents effectively and taking responsibility for mistakes. He suggests participating in SOS calls to gain wisdom and emphasizes the importance of mutual empathy and transparency. Bhavin concludes by stating that early career experiences in managing incidents can be valuable for personal growth. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 Introduction and Background 05:17 The Issue with Collaborative Editing 08:34 Identifying the Root Cause 16:11 Debugging the Issue 25:17 The Impact and Panic 30:36 Managing Panic and Staying Strategic 41:52 Advice for Young Engineers 50:28 Handling Stress and Improving Performance 51:43 Different Approaches in Crisis Situations 52:38 Reflecting on Incidents and Learning from Them 54:08 Creating Playbooks for Handling Incidents 57:03 Taking Responsibility and Apologizing 58:27 Participating in SOS to Gain Wisdom 59:25 Mutual Empathy and Transparency 01:02:16 Responsibility at Different Levels 01:03:11 Early Career Experiences as a Gift Find me on other platforms: LinkedIn: ⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠ Youtube: ⁠https://youtube.com/@pakkanimbu⁠

In this conversation, Bhavin Doshi and Rajneesh Prakash discuss the importance of digging deeper to overcome challenges and stagnancy in one's career. They highlight the need for knowledge sharing and the consequences of not sharing knowledge, particularly in the context of on-call responsibilities. The conversation also delves into the challenges of alerting and monitoring operational, system, and domain issues, and the importance of proper alerting and response to reduce time wasted in solving production incidents. In this conversation, Bhavin Doshi and Rajneesh Prakash discuss the challenges and importance of alerting and monitoring in software development. They explore the reasons why teams often struggle to set up effective alerts and the impact it has on system health. The conversation highlights the lack of awareness, time constraints, and the complexity of monitoring ecosystems as major obstacles. They also discuss the need for default alerts and centralized alert management to streamline the process. Overall, the conversation emphasizes the importance of proactive measures to prevent production issues and the need for continuous improvement in alerting practices. This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, they are building a very promising product "Bluejay" that makes it easier for developers to create and manage alerts. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Chapters in this video: 00:00 The Importance of Digging Deeper 11:38 Feeling Not Good Enough and Overcoming Stagnancy 20:40 The Lack of Knowledge Sharing and Its Consequences 34:31 The Challenges of On-Call and Time Wasted 41:37 The Nature of Operational, System, and Domain Issues 45:00 The Difficulty of Alerting Operational Issues 49:23 The Importance of Proper Alerting and Response 52:40 Importance of Alerting and Monitoring 55:09 Challenges in Setting Up Alerts 57:32 Lack of Awareness and Time 58:30 Complexity of Monitoring Ecosystem 59:20 Breadth of Components and Evolving Ecosystem 01:01:17 Need for Default Alerts and Centralized Alert Management 01:03:28 Summary and Closing Remarks Find me on other platforms: LinkedIn: ⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠ Youtube: ⁠https://youtube.com/@pakkanimbu⁠

In this conversation, Amit Chhajer⁠, the CTO of Trudoc, discusses the challenges of alerting and monitoring in production back-end systems. He shares his experience of dealing with excessive alerts and the impact of noise in the alerting process. Amit explains the process of reducing the number of alerts and the importance of ownership and teamwork in maintaining system uptime. He also highlights the significance of tracking metrics and reporting, as well as the need for continuous alert optimization. Amit emphasizes the concept of everyone as a 10x engineer and the value of laziness and smart work. He concludes by discussing the Indian context of hard work and the importance of having a good peer set. Takeaways - Excessive alerts can lead to noise and impact system uptime. - Reducing the number of alerts requires a systematic approach and teamwork. - Tracking metrics and reporting are essential for monitoring system performance. - Alert optimization is an ongoing process that requires continuous evaluation and improvement. - Everyone has the potential to be a 10x engineer, and laziness can drive smart work. - The Indian context of hard work should be balanced with the importance of efficiency and effectiveness. Chapters 00:00 The Problem of Excessive Alerts 02:14 Challenges Faced as an Engineering Leader 03:05 The Impact of Noise in Alerts 04:33 Reducing the Number of Alerts 05:52 The Process of Alert Reduction 06:22 The Importance of Ownership and Teamwork 08:09 Tracking Metrics and Reporting 10:23 The Challenge of Alert Optimization 11:22 Fixing Specific Alerts 13:08 Monitoring Database Queries 16:01 The Concept of Everyone as a 10x Engineer 17:28 The Culture of Continuous Hygiene 19:21 Handling Dependent Microservices 23:32 The Importance of Well-Set Alerts 30:34 The Value of Laziness and Smart Work 32:00 The Indian Context of Hard Work 35:09 The Importance of a Good Peer Set 35:57 Closing Remarks This episode is also available as podcast on all major platforms, including Spotify, Apple Podcasts, and Amazon Music. This episode's sponsor is ⁠⁠⁠BlueJay by 10xEngg⁠⁠⁠, Shift Left Incident ManagementPowered by AI. If you aren't using them, you are missing out!! It automatically handles the creation of alerts and adds a ton of intelligence to them going forward! Request a demo from them TODAY! Find me on other platforms: LinkedIn: ⁠⁠⁠⁠https://www.linkedin.com/in/bkdonline/⁠⁠⁠⁠ Twitter: ⁠⁠⁠⁠https://twitter.com/PakkaNimbu⁠⁠⁠⁠ Telegram: ⁠⁠⁠⁠https://t.me/pakkanimbu⁠⁠⁠⁠ Youtube: ⁠https://youtube.com/@pakkanimbu⁠