Thippana Vamsi Kalyan

𝙂𝘼𝙍𝘽𝘼𝙂𝙀 𝘾𝙊𝙇𝙇𝙀𝘾𝙏𝙄𝙊𝙉 - 𝙇𝙞𝙠𝙚 𝙩𝙝𝙚 𝙆𝙖𝙗𝙖𝙙𝙞𝙬𝙖𝙡𝙖! 🛢️ 🧠 𝐉𝐚𝐯𝐚 𝐁𝐮𝐟𝐟𝐞𝐭 : Day 1 of #30DaysOfJava Ever called the kabadiwala (scrap dealer) to clean out old newspapers and bottles piling up in your house? Every now and then, we need to get rid of things we don’t use anymore to free up space. In Java, this cleanup process is handled by something called Garbage Collection. Just like the kabadiwala goes around looking for items you don’t need, the Garbage Collector (GC) in Java hunts for objects in memory that aren’t being used by your program anymore. Once it finds them, it clears them out to free up memory, making sure your program runs smoothly without any memory clutter. Now, imagine calling the kabadiwala too frequently; he might start interrupting your routine. Similarly, if the Garbage Collector runs too often, it can slow down your application—a phenomenon called GC overhead. On the flip side, if he comes too late, your home will start overflowing with junk, just like memory issues in Java! 📌 Key Takeaway: Java’s Garbage Collector is like your friendly neighborhood kabadiwala, keeping your memory clean. But timing is everything—clean up too often, and you’ll slow down, wait too long, and you’ll run out of space! #java #oracle

21

5 Comments

I see signs of legacy teaching approach everywhere. Small details which are hiding the devil of an obsolete philosophy, supposed to leave years and years ago. Something that tells me, how deep the roots of frustration and low teaching efficiency. One of such details is the "course duration" notion. You don't need to be a prophet to say, that learning will take different time for different people. Some people like skipping sections they think they already know, some would carefully take notes and thoroughly refactor each piece to achieve their perfectionist goals. Some might argue that "course duration" is necessary to give learners a sense of how long an activity will take. And this is absolutely valid point. After all, we can measure the length of videos or the number of words to estimate this. But I see this as a paradox that needs resolution. On one hand, introducing "course duration" seems to focus on the learner's needs, yet it overlooks the subjective nature of learning - and the broader goals of the business. "Course duration" can become something, that is trying to tell you, how long you should learn. And nobody knows, what do they mean, if it will take more time for you. "Course duration" is also not something business really interested in, because the final goal in learning is not to spend exact time of hours there, but achieve some level of productivity. In this small detail I can see discrepancy with common sense. The great "five why's" technique would be probably useful there, and questions should have been asked, "Why do we want to have course duration?" It concerns me a lot, because nothing requires consistent and reasonable discourse as much as teaching and learning. Only being ordered in its reasoning, knowledge can be instilled. We need the practice of reasonable steps. #learning #courses #lms

3

2 Comments

Top learnings from my discussion with Kishore Gopalakrishna - Language choice for system development should balance team expertise, hiring potential, and ecosystem maturity. A well-implemented system in a familiar language often outperforms a poorly implemented one in a "faster" language. - Distributed systems are complex - they can fail in unexpected ways, making your own computer useless. This challenge is often underestimated. Understand the failure modes. - When building new systems, design for the long-term (10 years) but plan for the near-term (2-3 years). Implement for current needs while keeping the architecture flexible for future growth. Design for long term, plan for short-medium term. - Testing distributed systems requires going beyond known test cases. Develop test frameworks that generate new scenarios automatically to uncover unforeseen issues. - Cost optimization in data systems often involves trade-offs. Kafka, for example, sacrificed transactionality and exact-once delivery for higher throughput and lower cost per log. Its all about the Trade-offs. You get some, you lose some. - When approaching problems, start with first principles. Understand why something is expensive or inefficient before trying to optimize it. Don't jump on a solution. Understand the real problem first. - Open-source success relies heavily on community building. Foster respectful communication, clear processes for resolving conflicts, and a culture of helpfulness to grow a strong contributor base. There are many communities, but only the ones with good culture thrive. - Real-time analytics can significantly boost user engagement. Even small reductions in data latency can lead to measurable improvements in user experience and product value. - When considering real-time analytics, focus on how it can improve your users' lives rather than just technical capabilities. Many support issues can be eliminated by giving users direct access to real-time data. Product isn't useful if it making users' lives better. - Innovation in data products often comes from changing perspective - instead of asking "Do we need this?", ask "How can this improve our users' experience?" This shift can uncover valuable use cases for real-time analytics. Asking the right questions will help you reach the right answers. - When building data products, consider the long-term evolution of technology. Design choices should anticipate future developments, such as improvements in network speed or storage capabilities. Keep your design extensible. - As users become more data-savvy, there's increasing demand for self-serve analytics tools. Empowering users with direct access to data can reduce support overhead and enable more informed decision-making. Empower users to do more with data quickly. ———————————————————————— In case you haven't watched the episode yet, you can watch it here: youtu.be/SmLlJmU9Daw Also subscribe if you like such discussions.

41

3 Comments

The Power of Knowing What You Don't Know Was talking to a person who constantly failing in system design round. After every failure, he is gaining more knowledge around design pattern, distributed system, cloud etc, still no luck. After a deep discussion I realized he is unable to understand the gaps he has. He is focusing on what he knows, this pattern, this framework, SQL/NOSql etc but he least bothered to identify what he “Does Not Know”. His confidence on his technical skill was making him blind fold to identify his own gaps. The book titled; “Think Again by Adam G” talks this phenomenon in detail. When someone think he/she knows everything, this the biggest mistake they make. Knowing what you don’t know allows you to keep an open mind. It puts you in a better position to adapt when you find practical knowledge. In above use case, my colleague failed to focus on scalability, cost, possible failure points etc. he could not “read between the lines” when interviewer was giving hints. He could only connect to this blind spot when I identified them. This concept works everywhere, retrospection in agile methodology serves this purpose only where you identify the unknow in a particular sprint. It could be a developer strength/weakness, infra issues, cross vertical integration etc. While developing a feature/project, we always think about happy path (known info) but if we focus more to identify the unknowns then we will have more reliable systems. Unknows like, what are the scenarios where my code will fail, gaps in upstream and downstream system etc. Top sports person excels in this ability, they never focused on known strength of opponent players, rather they work on unknowns like, shots the player is not comfortable with, mistakes he does while playing a specific shot, going way ahead from the crease while playing the shots etc. The ability to recognize what you don’t know is a skill that can be developed. It starts with knowing the right questions to ask. As Socrates said, "If knowledge is power, knowing what you don’t know is wisdom. Use your ignorance to your advantage." A gap in knowledge shouldn’t be seen negatively but as an opportunity to seek wisdom and ensure a better future. Thanks for reading. 

12

Why closures are able to hold the values even after getting returned? A good article I found from Amandeep Singh explains this in detail. It's pretty crisp and clear! Especially check example 2 and it's explanation. https://lnkd.in/ggcsPH8i #frontend #JS #closures #languageinternals

5

GenZ won't accept "orders" without a clear "why". They want to make decisions by themselves and have a sense of achievement. Leading by frameworks is the way! Here are the 5 essential components every framework should have: 1. Clear "Why" Every decision has an objective to achieve. If the decision isn’t aiming in that direction, it is probably the wrong call. 2. Constraints Encourage out-of-the-box thinking while providing necessary limits to guide your team. 3. Accessible Data Sources Docs, metrics, spreadsheets, anything that can help them finding information. 4. Examples Share past decisions that followed the framework to help your team navigate new situations 5. Feedback Channel No framework is perfect! Everything requires refinement. Provide a way for feedback. #DecisionMaking #Empowerment #LeadershipSkills #LeadingGenZ

7

My team and I were brainstorming the backend architecture of one of our core systems at Zomato. While creating the HLD diagram, we kept adding the most intuitive microservices and their interactions within the mesh. At this stage, we were only thinking in terms of abstract functionalities that these services would offer. Meanwhile, one of the team members proposed why we couldn't combine three (out of N 😛) services and just create one for now. From a bird's-eye view, it felt not so convincing. He explained the rationale by justifying the similarity in functionalities, flows, and data modeling. Trust me, that was not so intuitive when we were putting those three white boxes in the HLD diagram. I still had concerns about the independent scalability of those three pieces and possible challenges due to noisy neighbor issues. We asked ourselves a question: "What business outcomes do we expect from this system?" Ultimately, we got convinced with the suggestion of a merger. Learnings: 1) Technical experience in a business domain matters. Identifying similarity would have been a non-trivial job for someone who had not worked with those systems in the past. 2) Engineering efforts should (also) be traded off against the business outcomes. Engineers working in silos without a business goal generally end up overengineering the system. 3) For leads, leverage the technical expertise of your team members. Avoid being an expert in every aspect. #engineering #architecture #business #datamodeling #backend

938

24 Comments

𝐃𝐄𝐀𝐃𝐋𝐎𝐂𝐊 - 𝙒𝙝𝙚𝙣 𝙏𝙬𝙤 𝘾𝙤𝙤𝙠𝙨 𝘼𝙧𝙚 𝙎𝙩𝙪𝙘𝙠 𝙒𝙖𝙞𝙩𝙞𝙣𝙜 𝙛𝙤𝙧 𝙀𝙖𝙘𝙝 𝙊𝙩𝙝𝙚𝙧 🍳🍲 🧠 𝐉𝐚𝐯𝐚 𝐁𝐮𝐟𝐟𝐞𝐭 : Day 4 of #30DaysOfJava (Extending analogy of Post 3 : https://lnkd.in/gE9mb6dJ) Imagine two cooks in a kitchen. One has a frying pan and needs the spoon to finish their dish, while the other has the spoon but needs the pan. Each cook is waiting for the other to release the tool they need, but neither will budge. As a result, nothing gets done, and both dishes remain uncooked! This is what deadlock in Java looks like. In Java, deadlock occurs when two or more threads are stuck waiting for each other to release resources. Each thread holds a resource and refuses to give it up until it gets another resource from the other thread. Since neither can proceed, the program grinds to a halt—much like our cooks staring at each other in frustration, unable to finish their dishes. 📌 Key Takeaway: Deadlock in Java is like two cooks waiting for each other to give up a tool they need. Both end up stuck, and nothing gets done! Thoughts on the analogy ? If you are looking for referrals and other tech job related stuff, check out Ramit Kundu 's discord community : https://lnkd.in/g9Mupq_3 #java #Oracle #jobs #referral

21

8 Comments

I am not someone who usually gets so many views on my blog posts. Thank you for this. And I know that most the views are because of the big names (Atlassian, Stripe). My other blogs are from my practical knowledge that got me here. Please go through them also 😋. Adding some links in comments This week, I'll be sharing more interview experiences and how I prepared in past 6 months. That will not be the "best resource" to follow, but atleast what worked for me :) #interview_experiences #tech #hiring

41

1 Comment

Koo failed, Ola succeeds. Why? ---------------------------------- The founder says Koo failed because it's a copy of other social networking platforms. There are some raving allegations about what Ola is all about. Isn't it a copy? That is the question being asked. Let's let the experts decide on that. In my view, there is no such thing as pure innovation, or it's very rare to find. Anything that humans invent (or maybe discover) is mostly an improvisation or inspiration from nature. By that definition, everything is a copy or improvisation (if you don't like the word "everything," then use "most of it" 😃) What is my take on why Koo failed? If everything is a copycat and some copycats are successful while others fail, what makes the difference? I believe copycats are successful because they still differ from the original, and that difference adds value. Let's explore this further with an example. The difference could be cultural, regulatory adoption/restrictions, emotion, etc. Usually, it's very difficult to rely solely on these differences to create a successful copycat product. Software products are easy to modify. Interestingly, when product adoption increases, the software cost decreases. So, it's easy for the early entrant to outcompete others. Now, let's not debate why so many successful products exist. They all differentiate in some form or tap into the weaknesses of the competition. So the takeaway should be: how do you differentiate or tap into the weaknesses of the competition? PS: If anyone wonder what is Koo then thats also one of the reason for the failure 😋 searching wont cost you.. at least for the money burnt to build the product please give a check www.krkaleraj.com #productengineering #innovation # leadership #entreprenuership #koo #twitter #X #threads #Truthsocial

22

4 Comments

One of the most common mistakes engineers make while writing multi-threaded programs is assuming common operations are thread-safe ⚡ I went through the assembly code to understand why exactly "count++" is not thread-safe and compiled my learnings into a super interesting and highly practical video that covers - how threads compete for the shared resource - how to disassemble code to instructions - how code actually gets executed on the CPU give it a watch: youtu.be/kBHd7kn_1EU ⚡ Admissions for my System Design August 2024 cohort are open, if you are SDE-2, SDE-3, and above and looking to build a rock-solid intuition to design any and every system, check out arpitbhayani.me/course #AsliEngineering #ConcurrencyInDepth

238

5 Comments

Understanding how the CPU works and how to write thread-efficient programs is very important. Thread Context Switching - When a program is executed in a single-core CPU, the CPU can work with and execute only one thread at any given time. Each thread gets its share of CPU time. For example, when a thread is writing something to the disk, and if it's consuming time, the CPU switches to another thread while the earlier thread is waiting. Threads are context-switched, and it looks like it is multitasking, and things are going on in parallel, which is not. Processing : Sequential processing is where programs are executed in a sequence, one by one, getting allocated with the CPU Concurrency: Parts of the program can be run independently and combined for the result and to speed up the execution on a single CPU Parallel: Each program can be run on each CPU independently and combined for the final results to speed up the execution Single Vs. Multi-thread - By running multiple threads vs. single threads to execute a program, the overall execution time can be reduced, and efficiency can be improved. Process Vs. Threads: A process uses CPU, memory, disk, and other resources to execute a program. A process can spin up one or multiple threads to complete the job. Sync Vs Asyn: Sync is executed in a sequence and cannot be skipped, but Asyn can run its block of the program separately from the main program and doesn't have to wait for completion to move on Thread Deadlock: When the resources required by a thread are being blocked by another one, and each one is waiting on another one, it leads to a deadlock state #cpu #development #technology #softwaredesign

456

35 Comments

What happens under the hood when you turn on your Android mobile phone When you power on your mobile phone, a meticulous self-test is conducted on all the hardware components. This comprehensive check ensures that every part of your device is functioning flawlessly. Once this rigorous hardware test is successfully completed, the Boot ROM, stored on the CPU, initiates the loading process. The bootloader loads Android OS, validating certain aspects of the initial loading. The kernel loads device drivers and background processes and manages the system resources. The init process loads and mounts directories and files and starts various processes. The Android runtime is initialized and is mainly used by the Android operating system. As the runtime, ART executes the Dalvik executable (DEX) format and DEX bytecode specification. After these system services are started, the activity manager kicks in to bring the user the initial screen to start interacting. Power-On Self-Test (POST): When you press the power button, the phone undergoes a quick self-check process known as POST. This test ensures that essential hardware components like the processor, memory, and battery function correctly. Bootloader: After the POST is successfully completed, the bootloader, a small yet crucial program stored in the phone's read-only memory (ROM), takes charge. It not only initializes the hardware but also orchestrates the booting process, including selecting the operating system to load. Loading the Kernel: The bootloader loads the Android kernel into the device's RAM (Random Access Memory). The kernel is the core of the Android operating system. It manages the device's resources, such as the CPU, memory, and input/output operations. Init Process: Once the kernel is loaded, the init process (short for initialization) is started. This process is responsible for initializing the Android system and launching essential system services and daemons. Android Runtime (ART) Initialization. This is a critical step as ART is the runtime environment where Android applications come to life. It's responsible for a significant task and compiles the application code into machine code, ensuring efficient execution on the device's hardware. This makes ART a crucial part of the booting process. Starting System Services: After the initialization of ART, various system services are started. These services include the Android System Server, which manages core system components like the package manager, activity manager, and window manager. Launcher and User Interface: Once the system services are up and running, the launcher (the user interface that displays your home screen, app icons, and widgets) is started. This allows you to interact with your device and access your installed applications. Loading Applications: Any pre-installed applications and services configured to start automatically are loaded. These may include system apps like the dialer, messaging app.

203

21 Comments

What happens under the hood when you turn on your Android mobile phone When you power on your mobile phone, a meticulous self-test is conducted on all the hardware components. This comprehensive check ensures that every part of your device is functioning flawlessly. Once this rigorous hardware test is successfully completed, the Boot ROM, stored on the CPU, initiates the loading process. The bootloader loads Android OS, validating certain aspects of the initial loading. The kernel loads device drivers and background processes and manages the system resources. The init process loads and mounts directories and files and starts various processes. The Android runtime is initialized and is mainly used by the Android operating system. As the runtime, ART executes the Dalvik executable (DEX) format and DEX bytecode specification. After these system services are started, the activity manager kicks in to bring the user the initial screen to start interacting. Power-On Self-Test (POST): When you press the power button, the phone undergoes a quick self-check process known as POST. This test ensures that essential hardware components like the processor, memory, and battery function correctly. Bootloader: After the POST is successfully completed, the bootloader, a small yet crucial program stored in the phone's read-only memory (ROM), takes charge. It not only initializes the hardware but also orchestrates the booting process, including selecting the operating system to load. Loading the Kernel: The bootloader loads the Android kernel into the device's RAM (Random Access Memory). The kernel is the core of the Android operating system. It manages the device's resources, such as the CPU, memory, and input/output operations. Init Process: Once the kernel is loaded, the init process (short for initialization) is started. This process is responsible for initializing the Android system and launching essential system services and daemons. Android Runtime (ART) Initialization. This is a critical step as ART is the runtime environment where Android applications come to life. It's responsible for a significant task and compiles the application code into machine code, ensuring efficient execution on the device's hardware. This makes ART a crucial part of the booting process. Starting System Services: After the initialization of ART, various system services are started. These services include the Android System Server, which manages core system components like the package manager, activity manager, and window manager. Launcher and User Interface: Once the system services are up and running, the launcher (the user interface that displays your home screen, app icons, and widgets) is started. This allows you to interact with your device and access your installed applications. Loading Applications: Any pre-installed applications and services configured to start automatically are loaded. These may include system apps like the dialer, messaging app.

247

27 Comments

Hiring Tip! Hire less domain specific unless strategy etc, in this age of LLMs. All Public LLMs are domain agnostic. Domain specific LLMs are also being made by domain heavy orgs. Domain knowledge should not be a mandatory skillset in hiring In Indian context hire if possible multidimensional like Hardik Pandyas , Surya Kumars, Sanju Samsons, Shivam Dubes!! as client requirements are also boomeranging! #LLMs,#Domains

11

1 Comment

In the previous class of my HLD cohort, we continued with understanding how to scale the stateful components of the system, and one very important topic that came up was: How do you decide on the right partition key? The 3 important points to consider: - The cardinality of the set represented by the key you are choosing. - It should have a uniform distribution of load across the values. - Check your usage patterns and understand how your application is going to be used. At times, you cannot satisfy all 3 above in which case your problem-solving comes into the picture. You have to implement some custom solution using the same building blocks of system design. If you also want to understand systems in detail, join below: Learn HLD in-depth and from scratch: https://lnkd.in/g-VVEmSU LLD Cohort: https://lnkd.in/ga5nvShy Multi-threading Cohort: https://lnkd.in/gDdwUY6w Free system design videos covering a lot of topics: https://lnkd.in/dyVEPVqf Connect 1:1 with me on @engineBogie: https://lnkd.in/dTqdUjwd

7

🚀 Exciting News! 🚀 My friend Durgaprasad Budhwani has developed and launched his tool, SmartEReply! 🎉 It’s designed to transform the way we communicate across platforms like LinkedIn™, Twitter™, Reddit™, Telegram™, WhatsApp™, Slack™, Microsoft Teams™, Gmail™, and Outlook™. Key Features: - 🤖 AI-Powered Responses: Instantly generate replies for emails, social media messages, and DMs with just one click. - ⚡ One-Click Replies Across Multiple Platforms: Maintain high-quality communication effortlessly. - 📱 Social Media Engagement: Connect with your audience and boost your online presence. - 💬 Messaging Assistant: Simplify messaging on various platforms. - 📧 Email Assistant: Manage emails efficiently with AI-crafted drafts. - 🔍 Summary Feature: Summarize lengthy content and web pages instantly. - ✍️ Writing Enhancement: Improve your writing with AI suggestions. As a Product Hunt community member, you can use SmartEReply for free during its beta phase! 🆓 👉 Check out all the details and support the launch here: https://lnkd.in/gwE6kSYE #AI #SmartEReply #ProductHunt #DigitalCommunication #ProductLaunch #Innovation

20

1 Comment

Had a great time at the Uber Gen AI Meetup in Bangalore! As I'm starting my Gen AI learning journey, it was amazing to see how experts are using AI to solve real problems. Following are some of the highlights from the event: - Jayaram Valliyur set the stage with their welcome and keynote on Uber's advancements in GenAI - Vivasvat Keswani introduced Uber's Michelangelo: Platform to build, deploy, and operate machine learning/ GenAI solutions at Uber’s scale - Sameera Poduri showed us how Uber is using Generative AI to make customer service better. - Varsha Mahadevan from Coinbase discussed the importance of keeping AI safe and secure in applications, focusing on prompt injection and implementing guardrails to prevent misuse. - Lokesh Agarwal from Kognitos discussed how AI could change our future - Pratyush Kumar from Sarvam AI emphasized the importance of using Indian languages in AI, making it more inclusive and also discussed building a full stack GenAI platform - Rush Tehrani from Uber focused on scaling ML infrastructure, deployment and serving of LLMs at Scale - Manyata Goyal and Geeti Oberoi introduced us to Uber’s tool, uLabel, which is Uber's labeling framework / data annotation solution that helps with organising data. - Ayush Garg, Chanakya Malireddy, Radhesh Sarma, and Georgy Mathew brought to light various advanced techniques like RAG-based chatbots, dynamic few-shot prompting, auto evaluation framework, showcasing Uber's leadership in applying AI to solve complex problems. - Smit Shah spoke on extracting actionable insights from LLMs, another testament to the practical uses of AI in business operations. - Ajeet Ganga explained how they're leveraging Gen AI to help manage Uber's workforce better - Panel discussion on "Unlocking the Value of Gen AI" moderated by Sameera Poduri featured Rohit Chatter from Walmart, @Vivasvat Keswani from Uber and Saurabh Dash from Cohere, along with Pratyush Kumar from Sarvam AI, offering diverse perspectives on the integration and impact of AI technologies across various sectors. Grateful to have been part of an event that showcased groundbreaking discussions on Gen AI. Big Shoutout to all the hosts at Uber for organising such a well-coordinated event. Looking forward to more such events! #UberGenAIMeetup #AI #Learning

68

2 Comments

Here's another successful framework they have applied. Suppose, you are against the surrender of the villages or against government actions. If you raise the voice, then you could be considered as a supporter of northern corporate and you are automatically triggered by other citizens as "not worthy to listen to" - Nir Eyal describes this as an internal trigger. Moreover, the framework has developed a manual, that was evolved and played out exceptionally well by the northern corporate and the government authorities. This is a plan prepared over the years, developed and infused into society. This framework is not new, but as Social Media was emerging, so-called analysts, political figures, YouTubers, military and other telegram authors, bunch of commentators were grown for a sole purpose - to develop a "Habit forming behaviours in citizens". These people are players. As data manipulation became easier, the developed behaviours started to ensure that regardless of the actions taken, majority of the society will not act against in order to avoid being triggered by the players and less knowledgable supporters of the actions. On the other hand, some other simple citizens don't think about the depth of messages and actions and most of them lack critical thinking, they do not try and look other ways, they are looking into the "manual", which leads to the most simple interpretation - "what is good or bad for me ?" or "whatever manual insists is the right thing to do for me". The choice is simple, it's based on the manual. Others who act or raise the voice, become internally triggered by the supporters of the actions and either getting muzzled or silenced or becoming obsolete (these people usually won't come back to make another try). The framework develops a vicious circle, that can not be broken, unless a better "reward" (I am not gonna talk about this though) is proposed to the citizens and sometimes players in order to develop a switch of the vector. The book here describes an ability of brain manipulation for creating good, habit forming products that actually hook people to improve their lives. However, Nir mentions an important aspect of building habit forming products. That is if they are not done for the good they become evil. With AI emerging and content creation/curation becomes easier, this framework will emerge too and will most probably create other, more complex instances, which can self-educate, those can potentially erase the line of morality and truth, deceiving the reality in unprecedented level. We'll be facing superpowers, that can be used for evil. Here and now or tomorrow in the future, it's up to the people to decide how we will progress, because as it is said - "The only thing necessary for the triumph of evil is for good people to do nothing." Now it can be misattribution, but in a way it's true. P.S. There is no evidence that Edmund Burke said the last quote in my text, so no reference to him.

10