Posts

Issue faced at workplace 1

  Problem Database returns: InternalCalls: "61;34;35" Need: 3 separate columns with values 61 , 34 , 35 Solution Summary What We Did Added helper methods to identify and split semicolon columns Modified header generation to output 3 column names instead of 1 Modified data processing to split values on ; and output separately Added "Teams To Teams Calls" heading when these columns appear Where We Changed Code Async CSV ( GenerateCSVContentAsync ): Modified AddCsvHeaders and ProcessRowsWithFilteringAsync Sync CSV ( GetCSV ): Modified the dsGlobalKPI processing section Excel (pending): Will need DataTable restructuring Core Logic If column is "InternalCalls" or "ExternalCalls": Headers: Output 3 names instead of 1 Data: Split "61;34;35" → output "61,34,35" Else: Output normally Key Learnings Same logic, different contexts - Had to implement splitting in 3 places (async CSV, sync CSV, Exce...

9-15-2025

 Visited Bundling again. https://www.debugbear.com/blog/make-fewer-http-requests https://www.debugbear.com/blog/render-blocking-resources https://stackoverflow.com/questions/36517829/what-does-multiplexing-mean-in-http-2 unicode CssRewriteUrlTransform TYpe of content that can be preloaded https://gemini.google.com/app/74af011b549ef661 https://claude.ai/chat/c5690923-6693-413a-a9e8-3e05e4ddb206 ========= Here is a summary of our entire conversation, formatted for your daily learning log: Summary of Web Performance Optimization in ASP.NET MVC This log details a step-by-step process of diagnosing and fixing web performance issues in an ASP.NET MVC 5 application, focusing on client-side optimizations. 1. Initial Diagnosis: The Problem with Load Time Symptom: A high load time (24.14 seconds) and a high number of HTTP requests (75). Key Insight: The huge gap between DOMContentLoaded (2.77 s) and load (24.14 s) points to a significant delay in downloading and processing client-side ...

Coffee With QA Guy

 Do more unit testing. Have Confident answers. Think of all the cases before starting.

Group deletion

  Daily Learning Log Entry Date: July 10, 2025 Developer: Abdul Rahman Kidwai Project: Group Deletion Performance Optimization 🎯 Problem Statement Group deletion operations were taking 10+ minutes for 376 filter deletions, causing poor user experience and potential timeout issues. 🔍 Learning & Discovery Process Initial Investigation Assumption : Blob storage was the bottleneck Reality Check : Database operations were the real performance killer (80-200 seconds per operation) Key Insight : Always profile before optimizing - assumptions can be wrong Root Cause Analysis Database Issues : 376 individual SQL operations instead of bulk operations Azure Storage Throttling : Unlimited concurrent requests triggering rate limits Thread Pool Concerns : Risk of exhausting web server resources with long-running operations 🔧 Technical Solutions Implemented 1. Database Bulk Operations (Primary Solution) Before : 376 individual DELETE statements After : 3 bulk SQ...