Abhay Raj Singh Yadav

Lots of posts on Zomato about new features on "re-ordering food from a cancelled order." Folks are discussing -- what are loopholes, how to enhance it, how to make it fullproof, and so on.   Have you given this much time and thoughts on the feature or product that you are working on ??   Many don't know why they're building a particular feature; they don't know what's in the business usecase or what value it adds. Many will just say -- the product team asked, so we are adding this feature. #thoughlessness #softwareengineer #product

13

A Day at the Apache Kafka 🚀 Today, I had the pleasure of attending an in-person Apache Kafka hosted by CRED in Bangalore. Here’s my feedback on this incredible event: 📍 Venue: Cred Aero, Bengaluru 🔹 Agenda Highlights: - @Vikas Sharma , CRED : Talk: Running Kafka Optimally in Production: Practical Usage Feedback: Vikas shared practical insights on optimizing Kafka in production environments, with valuable strategies for resource management. - Udayaram Kammara , Bazaarvoice : Talk: How Bazaarvoice Utilizes Kafka for Both Stream and Batch Processing Scenarios Feedback: Udayaram's session on Kafka's use at Bazaarvoice was enlightening, covering real-world use cases and challenges. - Diptiman Raichaudhuri , Confluent : Talk:Stream Processing for the Non-JVM World: pyflink and kafka-python Feedback: Diptiman's explanation of Apache Flink's architecture and the demonstration of kafka-python and pyflink were fascinating and beneficial for non-JVM users. What I Learned: - Effective strategies for running Kafka in production. - Real-world use cases and challenges in stream and batch processing. - Leveraging pyflink and kafka-python for stream processing. Overall, this meetup was a treasure trove of knowledge and inspiration. The sessions were well-organized, and the speakers were exceptionally knowledgeable. I’m excited to implement these learnings in my projects and continue exploring the potential of Apache Kafka and related technologies. 🙌 #ApacheKafka #KafkaMeetup #CRED #Bangalore #EventStreaming #StreamProcessing #TechCommunity #Networking #Python #Flink #DataPlatforms

24

2 Comments

Intuit leveraged K8sGPT and GenAI in their on-call process, resulting in improved issue detection, debugging, and resolution. 🚀 On-call engineers often face frequent alerts, tedious log scanning, and multiple team handoffs to resolve issues. Often, few teams have high operations load and engineers face fatigue resulting in low productivity. 😌 Intuit was facing similar issues with their complex Kubernetes deployment comprising 325+ clusters and 7000 services. They came up with a methodical approach to solve the problem through GenAI. What were the goals of the project ? 👉 Reduce the Mean Time To Detect (MTTD) an issue 👉 Reduce the Mean Time To Remediate (MTTR) an issue How did they solve the problem ? 1️⃣ Golden cluster signals - Single view of cluster's health and availability. It helped engineers to detect the bad clusters quickly reducing MTTD. 2️⃣ Debugging with K8s GPT - Adopted open-source K8s GPT to analyze root cause of failures. K8s GPT has integration with Open AI and other models. 3️⃣ Remediation with GenAI - Since public LLMs don't have Intuit specific data, they hosted local models and augmented them with Intuit specific data (RAG) that suggested remediation Intuit is planning to extend the tool and use it for other use cases, such as traffic and Java virtual machine debugging. They have published a detailed blog on how they adopted K8s GPT and the challenges they faced. You can find the link in the first comment. 👇 On-call weeks are challenging, but investing in GenAI can streamline the process and improve work-life balance. Share in the comments if you've used GenAI to improve your on-call process. Also, explore how K8sGPT could boost your team's operational efficiency. Also, folks who are interested to know more about K8s GPT can go to the github link, understand the code and start contributing. 🔥 #chatGPT #GenAI #softwareengineering

56

9 Comments

Another evening, another round of Chai and Fries at pathan's hotel, and my friend and I were back at it. This time, diving deeper into the nuts and bolts of architecture for his e-commerce company. As we discussed the data model, it became clear that every layer of this system would be shaped by how we organize and structure data. The big question was: - How many APIs do we need? - What should the API responses look like? - And, of course, what data types should we use to ensure efficiency and compatibility? During this discussion, chai walay bhai came and said "Abhi 2 baja hai, 3 bajay hum kursi lailaiga, apna ghar jao" 😢 We looked at him innocently and came back to our topic, and started mapping out some key areas. - Catalog APIs for fetching product details and categories. - User APIs for authentication, profile management, and order history. - Cart and Checkout APIs to ensure seamless transactions. From there, the conversation shifted to API communication protocols. Should we stick with the tried-and-tested or lean into modern innovations? Here’s how we broke it down. GraphQL: A modern, flexible API that pulls only the data you need. Perfect for dynamic stores, although latency and connection timeouts could pose challenges. WebSockets: Ideal for bidirectional communication, like real-time notifications or stock updates. But harder to scale and load balance effectively. REST APIs: Reliable and straightforward in our case. Each option came with its pros and cons, and we had to balance scalability, performance, and simplicity. It’s fascinating how these decisions are never just technical, they’re about anticipating the needs of users and the business. It's almost 3:15 AM, and we saw Pathan bhai marching toward us, and my friend suddenly asked pathan bhai, "1 chai or miljaigi?" and he replied "makhol na karo, apna ghar me ja ke peo" 😥 We realized we already drink 4 cups each and were just scratching the surface of the technicalities. We realized would need a better place to sit next time where we could spend more time. What’s your go-to API protocol, and why? I Would love to hear your take in the comments. Stay tuned for the next part of this evolving e-commerce journey! #APIs #Architecture #GraphQL #Websockets #Ecommerce #Chai #Fries #Pathanbhai #Architecture #ReactJS #TechLeadership #FrontendEngineering #StaffFrontendEngineer #TechHiring #WebApplication #TeamBuilding #FutureOfWork #TechCareers #RESTAPI #WebDevelopment #SoftwareArchitecture #DigitalTransformation #CareerGrowth #KnowledgeSharing #TechJourney

15

8 Comments

🚨 Beware of Online Stock Trading Scams🚨 In a shocking turn of events, three individuals in Bengaluru have lost a total of ₹9.54 crore to online stock trading scams within just one week. The victims, including two businessmen and an engineer, were deceived by promises of high returns and early access to IPOs. The scammers added the victims to WhatsApp groups where they shared investment tips. The victims were then persuaded to download trading apps and transfer large sums of money, believing they were making substantial profits. Initially, they received a small profit to keep them engaged, but the others saw no returns. Stay vigilant and always verify the authenticity of investment opportunities. Let’s work together to prevent such scams and protect our community. #CyberSecurity #OnlineScams #InvestmentFraud #StaySafe Source: https://lnkd.in/gEhbZtP5

3

Senior developers can stay connected to the codebase, provide productive hands-on experience, maintain updated technical skills, and remain highly productive even without coding regularly. However, over time, not writing code or delivering key features can lead to a sense of moral high ground because they are not involved in meeting strict customer deadlines. On a personal note, I get little to no time to write code, but I ensure to contribute to at least one project per quarter, just for the love of it. It is one of the few job profiles that allows individual contributors to operate at such top levels. Making the most of it. Regardless, interesting read.

12

Apple iPhone sales in India cross $10 billion by value in 2024; Samsung second best . Research firm IDC estimates Samsung Electronics's smartphone shipments at $5.23 billion between January and September, trailing Apple's $7.96 billion. This has widened the gap between the two in value market share with Apple at a record 27% and Samsung at 17.7%. https://lnkd.in/gJ-xUADr

1

I recently attended an enlightening session on Large Language Models (LLMs) by Arko C and Rohit Agarwal, and I wanted to share some key takeaways: 1. Deployment: Private deployments are often impractical, but leveraging LLMs in applications shows great promise. 2. Security: Ensuring the protection of sensitive data is a major concern when deploying LLMs in public environments. 3. IP Ownership: Retaining control over intellectual property is crucial, especially when building core functionalities around LLMs. 4. Accuracy: LLMs often face issues with accuracy, which can impact the reliability of applications. 5. Latency: High latency is a significant problem, leading to inefficiencies and increased costs, sometimes up to 50x more. 6. Cost Management: Managing costs is vital due to the high expenses associated with deploying and maintaining LLMs. 7. Continuous Improvement: It's vital to keep measuring, experimenting, and improving LLMs for optimal results. 8. LLM Integration: Simply adding LLMs to chatbots isn't enough; understanding customer needs and data, followed by meticulous fine-tuning, is key. 9. Generative AI: Many are just beginning to explore its potential; iterative development is crucial. 10. AI POC: Fine-tuning open-source models often proves more advantageous than relying on external models due to IP, latency concerns, cost-effectiveness, and the ability to customize to specific business needs. Bryckel AI Vinish Makkar Sienam Ahuja Vik Lulla MRICS / MCR #AI #LLM #GenerativeAI #Chatbots #MachineLearning #Innovation

35

3 Comments

Cofounder Conflicts 😞 ! Everyone owns everything, no one owns anything! I agree so much, Aman! Many teams suffer because everyone is doing everything and unfortunately even when everyone on the team wants to take ownership and be accountable, by design they are unable to. Clear divisions from Day 0 aren’t just a good practice—they're essential. I would go ahead and even say that don't even wait for traction. Do it early, align responsibilities, and set clear metrics for each function. Not only does this create accountability, but it also prevents the extended teams from feeling confused about who to take directions from. Sure, co-founders can contribute across the board (they should!), but there must always be a primary owner for every key function and metric. It keeps the vision sharp and execution smoother. If you are a founder or someone who worked in an early stage startup, do share if you witnessed this? How did you tackle it? Let’s discuss! 👇 #Startups #CoFounders #Accountability #Growth #Leadership #Entrepreneurship #India

20

2 Comments

🔍 Ruchir Sharma Decodes Trump's Election Victory and Its Impact on the Global Economy In his latest analysis from #BreakoutNations, renowned economist Ruchir Sharma explores the implications of Trump's recent election win. Out of 70 polls, only 20% of incumbents have secured victory, signaling a significant protest vote from the electorate. 📊 Key Insights The low incumbent win rate suggests widespread voter dissatisfaction and a desire for change. 📈 Tariffs and Executive Authority Tariffs can now be implemented via executive orders, bypassing the need for Congressional approval. This allows for quicker economic adjustments in response to global trade dynamics. 🏛️ Areas Requiring Congressional Action 💰 Fiscal Stimulus: Essential for driving economic recovery and supporting growth initiatives. ✂️ Tax Cuts: Crucial for increasing disposable income and encouraging investment. 🛂 Immigration Reform: Vital for addressing labor market needs and enhancing national security. 🌐 Geopolitical Implications If #Trump perceives a strategic advantage in negotiating a deal with China, he is likely to pursue it aggressively. This move could lead to a transactional relationship between the U.S. and China, where economic gains are prioritized over longstanding alliances. Consequently, allies may reconsider their strategic partnerships, evaluating the benefits and risks of aligning closely with the U.S. in a shifting geopolitical landscape.

2

LLVM Social Bangalore is back with an online meet. And this time, we’ll be hosting Prof. Manas Thakur from Indian Institute of Technology, Bombay on a very interesting topic about #JIT #Compilers! Title: Fixing the see-saw: Enabling precise optimizations in JIT compilers, efficiently Date: 18th May 2024 (Saturday) Time: 3:00 PM onwards Venue: Online (Google Meet) RSVP: https://lnkd.in/gJeMR_2V Note : You must RSVP to get the meeting link! Please do this ahead of time. Abstract (In the Professors own words): Just-in-time (JIT) compilers offer novel ways to optimize programs based on their execution profile and have found significant usage in languages with managed runtimes. However, as the JIT-compilation time directly affects the execution time of a program, precision-enhancement techniques from the static-analysis world seldom find way into these otherwise powerful systems. In this talk, I would first illustrate the above challenge using examples of program analysis aimed at enabling stack allocation of heap objects in Java. We would see how we have developed techniques to not only allocate a large number of objects on stack (leading to reduced garbage collection and improved performance), but to also handle challenges posed by possible dynamism in Java Virtual Machines. We would also understand how we facilitate code specialization in even newer dimensions by reusing compiled code for the lazy dynamic language R. All parts of the story would be bound by our encompassing goal: efficiency during program execution. Website: https://lnkd.in/g664qcVy Research Group: https://lnkd.in/gSHMyV8R Google Scholar: https://lnkd.in/gxZNaDni #JustInTime #CompilerDevelopment #IITB #stackallocation #heap #staticanalysis #pl #research #performance #java

122

5 Comments

A Billion Dollar B2C startup founder asking others to not hang out with people 🤷‍♂️. Other instances: 1. Tech Founder telling you writing code is unimportant. 2. VCs telling tech founders that they don't differentiate companies based on tech. Things you see only in Indian startup ecosystem.

19

2 Comments

Spent some time today going through Meesho's blog on how they reduced 90% of their Redis infra cost and it is filled with interesting details ⚡ The blog covers their design, key decisions, and nuances around picking the right data structure and tuning Redis the right way. Give it a read, it is pretty informative. The high-level overview of it 1. key-value based initial design leading to bloated memory 2. moving to Redis Hash 3. it still bloats memory, but beyond a threshold 4. internals details on how Redis uses ziplist to implement hash 5. tuning `hash-max-ziplist-entries` configuration 6. minimizing calls to Redis using Lua script I have seen many people adopting KV based approach and then throwing money on infra to handle scale. But Meesho's blog highlighted how knowing database tunables can help you significantly reduce your infra costs. give it a read - https://lnkd.in/gp9N3JMh To be honest, this is a pretty interesting blog for anyone using Redis in production. I made a similar blunder back in 2020 and then spent 2 weeks optimizing it, so a hard relate :) #AsliEngineering #SystemDesign

663

16 Comments

📢 This week I have gone through the research paper "Scaling Memcache at Facebook". 💠 🔍 Problem statement: 🔸 In early days Facebook needed a near real-time system to handle billions of read requests due to a high read-to-write ratio. 🔸 This is where Memcache—a distributed memory caching system that significantly reduces database load by caching data in RAM—comes into the picture. 📗 In this article, I learned how Facebook improved performance for billions of users. Below is a short summary of the paper: 🚀 Leases to Reduce Cache Miss Overload:   🔸 When a cache miss occurs, Facebook uses leases —only one request updates the cache, while others wait, avoiding DB overload. 💡 Custom Memcached Pools:   🔸 Data is stored in different pools (wildcard, replicated, etc.) to ensure frequent data access is quick, and less-used data doesn’t clog up resources. ⚡ UDP Protocol for Faster Reads:   🔸 To speed up responses, Facebook switched to UDP for read requests, cutting latency by 20%. 🔄 Replication & Consistency:   🔸 Memcache data is replicated across servers and regions with *eventual consistency*, ensuring up-to-date data without heavy database hits. 💥 Handling Failures with Gutters:   🔸 When a Memcached server crashes, Gutters (backup servers) take over, preventing traffic surges from overwhelming the DB. ✨ Facebook’s enhancements to Memcache are a powerful example of how engineering ingenuity can handle the demands of billions of users and real-time performance. #blogpost #facebook #paper #article #blogpost #cached #content #writing #react #dev #nextjs #postgres #redis #python #javascript #nodejs #monorepo #learninpublic #LearnInPublic #BuildInPublic #buildinpublic #tech Official Link -

3

Software is "soft", & Hardware is fcuk*** "hard." 𝗙𝗼𝗿 𝗜𝗻𝗱𝗶𝗮 🇮🇳, It becomes even harder in the domain of hardware Hardware <>deep tech/hard tech/more I would not have said this but This is something new for me So why is Hardware hard? → 5% of startups in India are deep tech startups, → While 95% are related to software → Software businesses can be easily scaled → Getting funds for software is way easier than hardware (Black pill) → VC for Software>> VC for Hardware → Few investors understand this and are ready to support the long journey. → Raising money is a significant challenge considering there is no hardware ecosystem and a high dependency on European countries 🇪🇺 and China 🇨🇳 Still, we were able to have Ather Energy, Ola Electric, Skyroot Aerospace and more Thriving in the ecosystem, which reminds me of a quote by Shri. Arun Jaitley  “𝗔𝗻 𝗲𝗹𝗲𝗽𝗵𝗮𝗻𝘁 🇮🇳, 𝗠𝗮𝗱𝗮𝗺 𝗦𝗽𝗲𝗮𝗸𝗲𝗿, 𝗺𝗼𝘃𝗲𝘀 𝘀𝗹𝗼𝘄𝗹𝘆 𝗯𝘂𝘁 𝘀𝘂𝗿𝗲𝗹𝘆.” <1/n>.... To be continued Some data points Sources: White paper: Telecom Standards Development Society of India *Software is Hard too.*

12

2 Comments

Leetcode was launched in 2015.   People still cleared interviews before that. The competition was still tough then. There were no: - Leetcode playlists - doubt support or influencers. Yet, engineers learned, solved problems, and built tech that drives our world today.  Today, students are suffering and struggling because: - there is so much competition - they have too many resources - they have no patience & short attention spans. Here’s a reality check:  – Stop Pitying Yourself.  – Stop Playing the Victim.   – Stop saying you have no guidance. You don’t need ten resources to crack a job, you just need one roadmap and one simple plan. You need focus and consistency to make it work and get results. If 500 people are applying to the same job as you, then: - 300 are irrelevant or spam and get filtered out.   - 200 are left, but only 40+ have solid resumes.   - Fewer than 10 pass assessments due to weak problem-solving skills.   -1 gets the job, the one with real skills, projects, and the right mindset.  Most fail because:   1. No relevant projects or skills   2. Weak problem-solving ability   3. Poor communication or the “chill job” mindset  That’s the reality of too much competition. You can aim for your desired job and start working on it now! 1. Pick a role you want to aim for.   2. Understand the required skills in the industry.   3. List what you lack and work on it step-by-step.   4. Learn by doing: Build projects, practice system design, and solve problems.  Don’t hoard resources. Stick to one.  Dive deep. Learn thoroughly. Test yourself consistently.  The real competition isn’t those 100s of applicants. It’s you versus the few prepared candidates. Be skilled. Be focused. Be ready. That’s how you win.  

328

8 Comments

A prominent Indian builder bought land in Ayodhya before the Ram Mandir announcement, hired Bollywood stars, and ran full-page ads, raising property prices by 900%. Now, buyers can't sell. This tarnishes India's real estate reputation, as people are often tricked into bad investments. However, real estate can be a good investment if you understand these points: 1. **Builder Control**: Builders sell high and buy low. Avoid buying overinflated properties for good returns. 2. **Clueless Buyers**: Ensure rental yield is above 4%. On a 1Cr property, rent should be at least 4 Lakhs annually. Overpaying leads to poor returns. 3. **Inflated Prices**: Selling an overinflated property is difficult. Buyers will investigate rental yields. Builders create FOMO to sell. You need experience and good judgment. Buy real estate only when it mathematically makes sense. CREDIT: Akshat Shrivastava #RealEstate #Investment #Property #India #RealEstateTips #BuyerBeware #PropertyMarket #InvestmentStrategy #Ayodhya #FOMO Rishiyank Sharma

7

2 Comments

Flipkart came 13 years after Amazon's founding. India never had its own major search engine or smartphone manufacturer. Consumers and businesses readily adopted western products. Meanwhile, the AI wave is unfolding quite differently. Local companies are taking a leading role, and that is probably the strongest foundation the local tech ecosystem could have. Few notable moves: • In March, Yotta Data Center Services became the first hyperscale provider in India to offer Nvidia’s cutting-edge AI training chips locally. • Tata Consultancy Services (TCS) reports a $1.5 billion order book for Generative AI-based consulting. • Local startup Sarvam AI raised $41 million, and has launched a general-purpose model rivaling some of the world's best. • Reliance and the Adani Group have earmarked billions for their own AI ventures. • Ola’s AI division, Krutrim, has made headlines by achieving a valuation of over $1 billion. Globally, the monetization of AI remains elusive, and India will face its own set of challenges. But with each paradigm-shifting technology, the gap in the speed of innovation is closing rapidly. Source: https://lnkd.in/e3_YjCad #AI #India #Tech

37

2 Comments