<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thuve R on Medium]]></title>
        <description><![CDATA[Stories by Thuve R on Medium]]></description>
        <link>https://medium.com/@thuve104r?source=rss-7fda53674985------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4G3w5f8PJAuuHdPcVnBD4w.jpeg</url>
            <title>Stories by Thuve R on Medium</title>
            <link>https://medium.com/@thuve104r?source=rss-7fda53674985------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:21:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thuve104r/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[THE END OF AN ERA, BUT NEVER THE END OF A LEGACY]]></title>
            <link>https://medium.com/@thuve104r/the-end-of-an-era-but-never-the-end-of-a-legacy-52181096391b?source=rss-7fda53674985------2</link>
            <guid isPermaLink="false">https://medium.com/p/52181096391b</guid>
            <category><![CDATA[chennai-super-kings]]></category>
            <category><![CDATA[cricket]]></category>
            <category><![CDATA[ms-dhoni]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ipl]]></category>
            <dc:creator><![CDATA[Thuve R]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 19:18:10 GMT</pubDate>
            <atom:updated>2026-11-17T23:46:22.826Z</atom:updated>
            <content:encoded><![CDATA[<p>MS Dhoni — The Man Who Taught Me How to Stay Calm When Life Gets Difficult</p><p><strong>17 November 2026 | A personal tribute to Mahendra Singh Dhoni</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*dj7xs6kOKB3a0HNJmSrd7A.jpeg" /></figure><p>There are certain moments in life when words are simply not enough.</p><p>Today is one of those days.</p><p>For millions of cricket fans, 17 November 2026 will be remembered as the day an extraordinary chapter in the Indian Premier League came to an end. For me, it is something much more personal. It is the day I realised that the man I had grown up watching, admiring and learning from would no longer walk onto an IPL field as a player.</p><p>Mahendra Singh Dhoni.</p><p>My Captain Cool. My Thala. My favourite cricketer. And, without even knowing it, one of the biggest influences on how I look at life.</p><p>Today, MS Dhoni officially brought his IPL playing career to an end. He will continue his journey with Chennai Super Kings as a mentor, but the thought of watching an IPL season without seeing him behind the stumps, wearing that yellow jersey and walking towards the crease is difficult to accept.</p><p>Some goodbyes are difficult even when you know they are coming.</p><p>And this one hurts.</p><p>From 2015: A Childhood That Grew Up Watching a Legend</p><p>My connection with MS Dhoni goes back to 2015.</p><p>I was just a young cricket fan when I started following him closely. At that time, I didn&#39;t understand every tactical decision, captaincy move or cricketing strategy. I simply enjoyed watching him play.</p><p>The way he walked onto the field. The way he stood behind the wickets. The way he finished matches. The way he remained calm when an entire stadium was holding its breath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*JM2WaBewFBE1xwTow61uvw.jpeg" /></figure><p>Something about him was different.</p><p>As the years passed, my admiration became something deeper. I started paying attention not only to his performances but also to his decisions, his attitude, his leadership and, most importantly, the way he handled difficult situations.</p><p>From 2015 to 2026, almost eleven years of watching, learning, celebrating, worrying and believing.</p><p>I have watched him win matches, lift trophies, face criticism, experience disappointing seasons and return with the same determination.</p><p>I didn&#39;t just watch a cricketer.</p><p>I watched someone whose journey taught me lessons that I could carry far beyond cricket.</p><p>The 2016 Chapter: When Things Didn&#39;t Go as Planned</p><p>Not every chapter of a legend&#39;s career is filled with trophies.</p><p>In 2016, Chennai Super Kings and Rajasthan Royals were suspended from the IPL, and Dhoni became the captain of Rising Pune Supergiants.</p><p>It was a completely different chapter for him.</p><p>The team struggled throughout the season. Expectations were high, but results were disappointing. Rising Pune Supergiants finished seventh in the eight-team competition, winning only five of their fourteen matches.</p><p>For someone who had become synonymous with success, this was a challenging period.</p><p>But what stayed with me was not simply the position on the points table.</p><p>It was the experience of watching a successful leader face a difficult season.</p><p>There were no guarantees of victory. There were no easy answers. There were matches where things did not work, decisions that did not produce the expected results and moments when the pressure was enormous.</p><p>Yet, the journey continued.</p><p>That taught me something important:</p><p>Your identity should never depend entirely on your latest success or failure.</p><p>A bad season does not erase your achievements. A difficult chapter does not define your entire story.</p><p>Sometimes, the most valuable lessons come from the seasons you would rather forget.</p><p>2017: The Response to a Difficult Chapter</p><p>The following season, Rising Pune Supergiant reached the IPL final.</p><p>Although they narrowly lost to Mumbai Indians, that journey demonstrated the importance of persistence and adaptation.</p><p>It reminded me that difficult periods are not necessarily the end of something.</p><p>You can experience disappointment, lose confidence, face criticism and still find a way forward.</p><p>Dhoni&#39;s journey made me appreciate the importance of continuing to work even when the results are not immediately visible.</p><p>Not every comeback needs to be dramatic.</p><p>Sometimes, simply refusing to give up is already a victory.</p><p>What I Learned From Captain Cool</p><p>People call him Captain Cool because of his ability to remain composed under pressure.</p><p>But I believe there is much more to his personality than simply staying calm.</p><p>Over the years, I have admired several characteristics that I genuinely want to carry into my own life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*GyBrY327dXXyvboNCTzfcw.jpeg" /></figure><p>1. Staying Calm When Everything Goes Wrong</p><p>One of the biggest lessons I learned from Dhoni is emotional control.</p><p>When a match becomes difficult, when the required run rate increases or when wickets fall, panic can make everything worse.</p><p>Dhoni showed that a calm mind can make better decisions.</p><p>I started relating this to everyday life.</p><p>Not every problem needs an immediate emotional reaction. Not every difficult situation deserves panic. Sometimes, stepping back, thinking clearly and making the next decision is the best thing you can do.</p><p>Being calm does not mean you do not feel pressure.</p><p>It means pressure does not control you.</p><p>2. Never Let Failure Become Your Identity</p><p>His difficult seasons taught me that failure is part of every meaningful journey.</p><p>There will be moments when your hard work does not produce the expected outcome. There will be people who question your abilities. There will be situations where you begin questioning yourself.</p><p>But one unsuccessful attempt should never become the definition of your potential.</p><p>I learned to accept setbacks, understand mistakes and move forward.</p><p>3. Leadership Is About Responsibility</p><p>Dhoni&#39;s leadership was never only about holding the captaincy title.</p><p>He trusted his players, backed people during difficult periods and understood that a captain must take responsibility when things go wrong.</p><p>One of the most powerful leadership lessons is that you cannot take all the credit when things go right and disappear when things go wrong.</p><p>Leadership means standing with your team in both situations.</p><p>4. Trust People and Give Them Opportunities</p><p>He was known for backing players and giving them confidence.</p><p>Not every player performs perfectly from the beginning. Sometimes, people need someone who believes in them before they believe in themselves.</p><p>That is a quality I admire deeply.</p><p>Whether in a workplace, a team or any personal journey, believing in people can make a difference.</p><p>5. Let Your Work Speak</p><p>Dhoni was never someone who needed to explain every decision publicly.</p><p>He often allowed his performances and actions to communicate for him.</p><p>In a world where people sometimes spend more time talking about their ambitions than working towards them, this lesson feels especially relevant.</p><p>Work consistently. Improve quietly. Let the results speak.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*zBLfQp1fM7gOHvoKRoEOWA.jpeg" /></figure><p>6. Accept Change and Keep Moving Forward</p><p>His journey included changes in teams, captaincy responsibilities, roles and expectations.</p><p>He adapted.</p><p>That taught me that life does not always follow the path we originally planned.</p><p>Sometimes, we need to accept a new role, adjust our expectations and continue moving forward without losing our identity.</p><p>7. Respect the Game and Respect People</p><p>His humility, professionalism and respect for teammates and opponents are among the qualities that made him special.</p><p>Success should never make someone forget where they started.</p><p>That is another lesson I want to remember.</p><p>The International Goodbye: 10 July 2019</p><p>There is one cricketing memory that will always remain emotional for me.</p><p>The 2019 Cricket World Cup semi-final between India and New Zealand.</p><p>India were chasing 240. The team had lost important wickets, and the situation was becoming increasingly difficult.</p><p>Then came Dhoni.</p><p>He and Ravindra Jadeja brought India back into the contest with an extraordinary partnership.</p><p>Jadeja played a magnificent innings of 77. Dhoni remained at the other end, doing what he had done so many times throughout his career: keeping hope alive.</p><p>The target was getting closer.</p><p>For a moment, it felt possible.</p><p>Then came the run.</p><p>Martin Guptill&#39;s direct hit.</p><p>Dhoni was short of his crease.</p><p>Out.</p><p>50 runs from 72 balls.</p><p>I still find that moment difficult to describe.</p><p>For a player who had been involved in so many successful run chases, whose running between the wickets was among his greatest strengths, to be dismissed through a run-out at such a crucial moment was heartbreaking.</p><p>India eventually lost the match.</p><p>And that was his final international appearance.</p><p>He announced his retirement from international cricket on 15 August 2020.</p><p>I didn&#39;t know then that the memory of that run-out would become one of the most emotional moments in my journey as a Dhoni fan.</p><p>Sometimes, a single frame stays in your memory longer than an entire match.</p><p>The Yellow Jersey: More Than a Team</p><p>Chennai Super Kings became more than just a cricket franchise to me because of Dhoni.</p><p>The yellow jersey, the number seven, the gloves, the helmet and that familiar walk towards the middle.</p><p>They became part of the IPL experience.</p><p>Five IPL championships as captain. Two Champions League T20 titles. Countless memorable finishes. Generations of supporters who connected with the franchise through him.</p><p>But his legacy cannot be measured only through trophies.</p><p>It is also in the confidence he gave young players, the belief he created among supporters and the countless people who learned something about leadership simply by watching him.</p><p>For me, the yellow jersey represents consistency, loyalty, belief and an entire childhood of memories.</p><p>20 May 2025: The Rajasthan Royals Match I Will Never Forget</p><p>There is one match I want to mention separately.</p><p>20 May 2025.</p><p>Chennai Super Kings versus Rajasthan Royals at the Arun Jaitley Stadium in Delhi.</p><p>That evening, Dhoni came in to bat and scored 16 runs from 17 deliveries, including a six.</p><p>It was not a match-winning innings. CSK scored 187/8, and Rajasthan Royals chased the target, winning by six wickets.</p><p>But I didn&#39;t know that I was watching his final IPL batting innings.</p><p>That six.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-enhTxXYl5PZCAi8uFcxzg.jpeg" /></figure><p>That familiar sight of Dhoni connecting with the ball.</p><p>That moment when the ball travelled beyond the boundary.</p><p>I didn&#39;t know it would become such a precious memory.</p><p>He was dismissed in the final over, caught by Tushar Deshpande off Akash Madhwal.</p><p>At the time, it was simply another disappointing CSK result.</p><p>Today, looking back, that innings feels different.</p><p>It is strange how an ordinary cricketing moment can become extraordinary with the passage of time.</p><p>I wish I had known that I was watching one of his final moments with the bat.</p><p>I would have watched every delivery a little more carefully.</p><p>I would have appreciated every second a little more.</p><p>And perhaps I would have understood how quickly these moments become memories.</p><p>His final IPL playing appearance came five days later, on 25 May 2025, against Gujarat Titans. He did not bat in that match.</p><p>In 2025, CSK finished at the bottom of the table.</p><p>Even then, I never measured my admiration for Dhoni by the team&#39;s position.</p><p>Because supporting someone only when they win is easy.</p><p>The real connection is built over the difficult seasons too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*TdhQXyL8orDT3j_dXe7wRg.jpeg" /></figure><p>2026: The Season Without Him</p><p>The 2026 IPL season was already different.</p><p>Dhoni did not play a single match because of a calf injury.</p><p>For someone who had become such a familiar presence in the tournament, not seeing him on the field felt unusual.</p><p>There was no opportunity to watch him walk out to bat. No familiar finish. No gloves behind the stumps.</p><p>And now, on 17 November 2026, the final announcement has arrived.</p><p>He has retired from IPL playing duties and will take up the role of mentor with Chennai Super Kings.</p><p>The player chapter is closed.</p><p>But the story continues.</p><p>17 November 2026: A Date I Will Remember</p><p>Today, when the IPL 2027 retention news started coming out, I knew it could be an important day.</p><p>But knowing something might happen and actually seeing it happen are two different feelings.</p><p>MS Dhoni will no longer be part of the playing squad as a player.</p><p>For the first time in the franchise&#39;s history, the IPL will move forward without him as an active player for Chennai.</p><p>I know that cricket must move forward.</p><p>New players will arrive. New captains will lead. New records will be created. New champions will lift trophies.</p><p>But there is something that cannot be replaced.</p><p>The feeling of watching your childhood hero walk onto the field.</p><p>The excitement of waiting for him to come out to bat.</p><p>The hope that somehow, even when everything seems lost, he will find a way.</p><p>That feeling belongs to a different time now.</p><p>And I think that is what makes today so emotional.</p><p>What Dhoni Taught Me Beyond Cricket</p><p>I want to make one thing clear.</p><p>My admiration for Dhoni is not only because he won trophies or finished matches.</p><p>It is because his journey helped shape the way I think about my own journey.</p><p>There are times in life when things do not go according to plan.</p><p>You work hard, but the result is disappointing.</p><p>You make decisions, but they do not always work.</p><p>You trust people, but sometimes they let you down.</p><p>You have ambitions, but the road towards them becomes difficult.</p><p>In those moments, I often think about the lessons I have learned from watching him.</p><p>Stay calm.</p><p>Take responsibility.</p><p>Trust the process.</p><p>Learn from failure.</p><p>Respect the people around you.</p><p>Never allow temporary setbacks to destroy your confidence.</p><p>And above all, keep moving forward.</p><p>I am still learning. I still have many challenges ahead. I have personal ambitions, professional goals and dreams that I want to achieve.</p><p>But the qualities I admired in him are qualities I want to develop in myself.</p><p>Perhaps that is the greatest influence a sportsperson can have on someone.</p><p>They may never meet you.</p><p>They may never know your name.</p><p>But their journey can still change the way you approach your own life.</p><p>To My Captain Cool: Thank You.</p><p>Thank you for the memories.</p><p>Thank you for the unforgettable finishes.</p><p>Thank you for the trophies, the celebrations and the moments that made millions of people believe until the very last ball.</p><p>Thank you for showing us that leadership is not about being the loudest person in the room.</p><p>Thank you for showing us that silence can be powerful, patience can be a strength and confidence does not need constant explanation.</p><p>Thank you for teaching us that failure is not the opposite of success. It is part of the journey.</p><p>Thank you for giving me almost eleven years of memories that I will carry for the rest of my life.</p><p>I started watching you as a young cricket fan in 2015.</p><p>Today, in 2026, I am no longer that same person.</p><p>I have grown. My perspective has changed. My ambitions have evolved.</p><p>But one thing has remained constant.</p><p>My respect for you.</p><p>I don&#39;t know whether I will ever experience the same feeling watching another cricketer.</p><p>Maybe I won&#39;t.</p><p>Because some connections are not about statistics, trophies or records.</p><p>They are about memories, emotions and the years of your life that become connected to a person.</p><p>And you will always be part of mine.</p><p>The number 7 will always mean something special.</p><p>The yellow jersey will always bring back memories.</p><p>And Captain Cool will always remain Captain Cool.</p><p>You may have retired from playing, but you have not retired from our memories.</p><p>The end of an era is not the end of a legacy.</p><p>It is simply the beginning of remembering it differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*8ShQTXUM-2H-uRdvzxzLQA.jpeg" /></figure><p>ONE LAST THOUGHT</p><p>Somewhere, a young cricket fan who started watching you in 2015 is sitting today, looking back at almost eleven years of memories.</p><p>I watched you win. I watched you lose. I watched you struggle. I watched you rise again.</p><p>And without realising it, I learned how to face some of my own struggles.</p><p>Thank you, Mahi.</p><p>Forever a Dhoni fan. Forever a Thala supporter. 💛</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*u4VtDZNVhAkAK8EDuOP8LQ.jpeg" /></figure><p>#MSDhoni #ThankYouDhoni #CaptainCool #Thala #WhistlePodu #CSK #IPL2027 #LegacyNeverEnds</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52181096391b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Code: 14 Lessons from Building 24hours.lk and the 24 Eco System]]></title>
            <link>https://medium.com/@thuve104r/beyond-the-code-14-lessons-from-building-24hours-lk-and-the-24-eco-system-42348cad2694?source=rss-7fda53674985------2</link>
            <guid isPermaLink="false">https://medium.com/p/42348cad2694</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Thuve R]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 19:03:34 GMT</pubDate>
            <atom:updated>2026-11-17T19:03:34.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*BxnQxDGAscdLOJ7q9b8vwg.jpeg" /></figure><p>What building real-world web and mobile applications taught me about architecture, APIs, databases, scalability, security, and production engineering.</p><p>Building an application is easy when everything goes as expected. Building one that continues to work when things go wrong is a completely different engineering challenge.</p><p>When I started working on 24hours.lk and its companion mobile applications, the 24 Eco System, I initially approached development from a feature-oriented perspective. Build the interface, connect the API, integrate the database, implement authentication, and make everything work.</p><p>But real-world software development quickly teaches you that making an application work is only the beginning.</p><p>What happens when multiple users perform the same operation simultaneously? What happens when a database query becomes unexpectedly slow? What happens when a mobile application communicates with an outdated API? What happens when a deployment introduces an issue into a live environment?</p><p>These are not just hypothetical engineering questions. They are the kinds of challenges that make enterprise application development fundamentally different from building a simple application.</p><p>Throughout my experience working on 24hours.lk and the 24 Eco System, I began to understand that software engineering is not simply about writing code. It is about designing, connecting, maintaining, and improving systems that must operate reliably under unpredictable conditions.</p><p>Here are 14 important lessons that changed the way I think about software engineering.</p><p>---</p><p>1. Architecture Matters More Than Individual Features</p><p>One of the biggest mindset changes I experienced was understanding that a feature is rarely isolated.</p><p>A seemingly simple feature might involve multiple layers:</p><p>- Frontend and mobile interfaces<br>- API communication<br>- Authentication and authorization<br>- Business logic<br>- Database operations<br>- File storage<br>- Notifications<br>- Infrastructure and deployment</p><p>A small change in one layer can create unexpected consequences elsewhere.</p><p>This made me think more carefully about separation of concerns, service boundaries, reusable business logic, API contracts, database relationships, and deployment strategies.</p><p>My question gradually changed from:</p><p>&quot;How can I build this feature?&quot;</p><p>To:</p><p>&quot;Where should this feature belong in the overall architecture, and how will it affect the rest of the system?&quot;</p><p>That is when I started thinking beyond individual components and focusing on the system as a whole.</p><p>2. APIs Are the Contracts Between Applications</p><p>When multiple applications communicate with the same backend, APIs become one of the most important parts of the architecture.</p><p>For example, 24hours.lk has a web experience alongside its companion mobile applications. Both environments need to communicate with backend services consistently.</p><p>A simplified architecture looks like this:</p><p>24hours.lk Web<br> |<br> v<br> Shared API Layer<br> |<br> v<br> Business Logic<br> |<br> v<br> Database<br> ^<br> |<br> Shared API Layer<br> ^<br> |<br> 24 Eco System Mobile</p><p>The API is not simply an endpoint that returns data. It is a contract between different applications.</p><p>That contract needs to account for:</p><p>- Request validation<br>- Consistent response structures<br>- Authentication and authorization<br>- Pagination and filtering<br>- Error handling<br>- API versioning<br>- Backward compatibility<br>- Performance and reliability</p><p>A backend designed around the convenience of one frontend can quickly become difficult to maintain when additional clients are introduced.</p><p>A good API should serve the ecosystem, not just a single screen.</p><p>3. Database Design Is a Performance Decision</p><p>During early development, database design can feel straightforward. Create collections or tables, define relationships, store information, and retrieve it when needed.</p><p>However, real application data changes everything.</p><p>As the amount of data increases, queries that performed perfectly during development can become expensive. Relationships become more complex, and retrieving unnecessary information can affect the overall application experience.</p><p>I started paying much closer attention to:</p><p>- Database indexing<br>- Query optimization<br>- Data normalization and denormalization<br>- Pagination strategies<br>- Transactions<br>- Connection pooling<br>- Data consistency<br>- Migration strategies<br>- Read and write patterns</p><p>The important realization was that database design is not only about how information is stored.</p><p>It directly influences application scalability, responsiveness, and reliability.</p><p>A database is not just a storage layer. It is part of the performance architecture.</p><p>4. Concurrency Introduces Problems That Local Development Cannot Reveal</p><p>When developing locally, it is easy to test an operation with one user and assume everything works correctly.</p><p>Production environments are different.</p><p>Multiple users can interact with the same resources simultaneously. Two requests might attempt to update the same record within milliseconds.</p><p>Without proper handling, this can introduce race conditions and inconsistent data.</p><p>This is where concepts such as atomic operations, database transactions, isolation levels, idempotency, and optimistic or pessimistic locking become important.</p><p>For example, imagine two users attempting to reserve the same available resource at almost exactly the same time.</p><p>Both requests might initially see the resource as available.</p><p>Without appropriate concurrency control, both operations could succeed when only one should.</p><p>This taught me an important lesson:</p><p>Correctness is not just about whether an operation works individually. It is about whether it remains correct when multiple operations happen together.</p><p>5. Authentication Is More Than Implementing a Login Page</p><p>Authentication is often one of the first features developers implement. However, login is only the visible part of a much larger security process.</p><p>A production application needs to answer several questions:</p><p>- Who is making this request?<br>- Is their session still valid?<br>- What happens when a token expires?<br>- What permissions do they have?<br>- Can they access the requested resource?<br>- How should sessions and credentials be protected?</p><p>This introduces access tokens, refresh tokens, session management, OAuth, role-based access control, permission systems, and secure credential handling.</p><p>One distinction became particularly important to me:</p><p>Authentication answers: Who are you?</p><p>Authorization answers: What are you allowed to do?</p><p>Both are essential. Successfully logging into an application should never automatically grant access to every resource.</p><p>6. Mobile Development Introduces an Entirely Different Set of Challenges</p><p>Building companion mobile applications introduced challenges that are not always visible during web development.</p><p>Mobile applications operate in unpredictable environments.</p><p>Users may experience:</p><p>- Unstable internet connections<br>- Temporary network disconnections<br>- Interrupted API requests<br>- Background execution restrictions<br>- Limited device resources<br>- Different screen sizes<br>- Different operating system versions<br>- Outdated application versions</p><p>A backend can be functioning perfectly while a mobile user still experiences a failed operation.</p><p>This means mobile applications need carefully designed loading states, error handling, caching, retry mechanisms, synchronization strategies, and network-aware behavior.</p><p>It also highlights the importance of designing APIs that can handle unreliable network conditions.</p><p>A reliable mobile experience depends on more than a responsive interface. It depends on how gracefully the application handles failure.</p><p>7. Performance Optimization Is a Full-Stack Responsibility</p><p>When an application feels slow, the frontend is not necessarily the problem.</p><p>Performance issues can originate from multiple layers:</p><p>- Frontend rendering<br>- Network latency<br>- API processing<br>- Database queries<br>- External service integrations<br>- Server resource limitations</p><p>Consider this hypothetical request breakdown:</p><p>Client rendering 150 ms<br>Network 250 ms<br>API processing 100 ms<br>Database query 1,200 ms<br>Response processing 300 ms<br>--------------------------------<br>Total 2,000 ms</p><p>The database alone accounts for most of the response time.</p><p>Optimizing frontend components would not solve the actual bottleneck.</p><p>This changed how I approach performance issues. Instead of making assumptions, I focus on identifying where the time is actually being spent.</p><p>Tools such as application monitoring, structured logging, database profiling, and distributed tracing can help identify the underlying cause.</p><p>Performance optimization starts with measurement, not assumptions.</p><p>8. Production Errors Are Different From Development Errors</p><p>Local development provides a relatively controlled environment.</p><p>Production does not.</p><p>Real-world deployments introduce challenges involving:</p><p>- Environment configuration<br>- Incorrect or missing secrets<br>- Database permissions<br>- Network connectivity<br>- DNS configuration<br>- SSL/TLS certificates<br>- Server resource limitations<br>- Third-party service failures<br>- Unexpected user behavior</p><p>Sometimes, the most frustrating issue is an error message that simply says:</p><p>&quot;Something went wrong.&quot;</p><p>At that point, identifying the actual cause becomes difficult without proper observability.</p><p>This is where structured logging, monitoring, error tracking, and distributed tracing become essential.</p><p>You need to understand what happened, where it happened, which request triggered it, and how the system behaved at that moment.</p><p>A production application should not only report that something failed. It should provide enough information to investigate why it failed.</p><p>9. Deployment Is Part of Software Engineering</p><p>There is a significant difference between:</p><p>&quot;It works on my machine.&quot;</p><p>And:</p><p>&quot;It works reliably in production.&quot;</p><p>Deploying an application involves much more than transferring source code to a server.</p><p>It requires understanding:</p><p>- Production build processes<br>- Environment variables and secrets<br>- Database migrations<br>- Domain and DNS configuration<br>- SSL/TLS<br>- CI/CD pipelines<br>- Server resource management<br>- Backups and recovery<br>- Monitoring<br>- Rollback strategies</p><p>A deployment changes a live environment that real users depend on.</p><p>That means deployment decisions need to be treated as engineering decisions, not simply administrative tasks.</p><p>Writing the code is one responsibility. Delivering it safely is another.</p><p>10. Backward Compatibility Is a Long-Term Responsibility</p><p>One interesting challenge of developing both web and mobile applications is that users do not always run the latest version.</p><p>Imagine the backend changes its response structure today.</p><p>The web application might receive an update immediately, but mobile users could continue using older versions for weeks or months.</p><p>Suddenly, the backend needs to support different generations of clients.</p><p>This is where API versioning, backward-compatible changes, deprecation policies, feature flags, and migration strategies become important.</p><p>A change that works perfectly for the latest application version might break an older client.</p><p>This made me realize that software development is not only about supporting today&#39;s users.</p><p>You also need to protect the experience of users who are still running yesterday&#39;s software.</p><p>11. Security Must Exist at Every Layer</p><p>Security cannot be treated as a feature that is implemented once and forgotten.</p><p>It needs to be considered throughout the entire application architecture.</p><p>Client Application<br> |<br> v<br>Authentication<br> |<br> v<br>API / Server<br> |<br> v<br>Authorization<br> |<br> v<br>Business Logic<br> |<br> v<br>Database<br> |<br> v<br>Infrastructure</p><p>Each layer introduces potential security risks.</p><p>A secure frontend cannot compensate for an insecure API. Authentication cannot compensate for missing authorization checks. A properly secured API cannot compensate for exposed database credentials.</p><p>Important areas include input validation, access control, secure session management, secret management, rate limiting, encryption, and dependency security.</p><p>The most important realization is that security is not the responsibility of one component.</p><p>Security is a responsibility shared across the entire system.</p><p>12. The Hardest Bugs Are Rarely Syntax Errors</p><p>Syntax errors are usually straightforward to identify and resolve.</p><p>The more challenging problems are those caused by interactions between different parts of the system.</p><p>For example:</p><p>- An API request succeeds, but the interface does not update.<br>- Two operations modify the same record simultaneously.<br>- A mobile application sends an outdated request payload.<br>- A database query becomes slow only when the dataset grows.<br>- A token expires during an operation.<br>- A deployment succeeds but the application fails at runtime.<br>- An external service responds before another dependent operation finishes.</p><p>These issues require a different debugging mindset.</p><p>Instead of focusing on a single file or function, you need to understand how information moves through the system.</p><p>That leads to another important lesson: understanding system behavior is often more valuable than simply understanding individual lines of code.</p><p>13. Debugging Requires Understanding the Entire Request Lifecycle</p><p>My approach to debugging gradually changed.</p><p>Previously, I would often start by looking for the error in the relevant component or function.</p><p>Now, I try to understand the complete request lifecycle.</p><p>User Action<br> |<br> v<br>Frontend / Mobile App<br> |<br> v<br>Network Request<br> |<br> v<br>Authentication<br> |<br> v<br>API Layer<br> |<br> v<br>Business Logic<br> |<br> v<br>Database / External Services<br> |<br> v<br>API Response<br> |<br> v<br>Frontend State Update</p><p>An error that appears in the frontend might originate from the backend. A backend failure might actually be caused by a database query or an external dependency.</p><p>Understanding this complete flow makes debugging more systematic.</p><p>It also reinforces the importance of correlation IDs, meaningful logs, request tracing, and consistent error handling.</p><p>Don&#39;t just ask where the error appeared. Ask where the problem actually started.</p><p>14. The Technology Stack Is Only Half the Story</p><p>Working on 24hours.lk and the 24 Eco System reinforced something I believe every software developer should understand.</p><p>Knowing a framework does not automatically mean knowing software engineering.</p><p>You can become comfortable with React, Next.js, Flutter, Node.js, Python, or any other technology. But building reliable applications requires knowledge that extends beyond individual frameworks.</p><p>It involves understanding:</p><p>- Software architecture<br>- Distributed systems<br>- Database engineering<br>- Networking<br>- Security<br>- Concurrency<br>- Caching<br>- Scalability<br>- Observability<br>- Infrastructure<br>- Deployment and reliability</p><p>Frameworks and libraries help us implement solutions.</p><p>Engineering knowledge helps us understand which solutions are appropriate, why they work, and how they behave under real-world conditions.</p><p>The deeper you go into production systems, the less the challenge is about syntax and the more it becomes about systems engineering.</p><p>---</p><p>What Building 24hours.lk Taught Me About Software Engineering</p><p>Looking back, the most valuable part of working on 24hours.lk and its companion mobile applications was not simply learning new technologies or implementing individual features.</p><p>It was developing a different way of thinking.</p><p>I started seeing applications as interconnected systems rather than collections of screens and components.</p><p>A user generates a request. The frontend communicates with an API. Authentication verifies identity. Business logic makes decisions. Databases maintain state. External services provide additional capabilities. Infrastructure keeps everything running. Monitoring helps us understand what happens when something fails.</p><p>Every component has a responsibility, and every connection between those components matters.</p><p>There is still much more to learn, experiment with, and improve. Enterprise software engineering is an ongoing learning process because real-world systems continuously introduce new challenges.</p><p>But one lesson stands out above everything else:</p><p>Building an application that works is software development. Building an application that remains reliable, secure, scalable, and maintainable under real-world conditions is software engineering.</p><p>And that is the difference I have come to appreciate through this journey.</p><p>---</p><p>About the Author</p><p>I&#39;m a software engineer and technology enthusiast interested in building scalable applications, exploring system architecture, and solving real-world engineering problems.</p><p>Currently, I&#39;m involved in building 24hours.lk and the 24 Eco System at HABB Global, exploring how technology can connect services and create more accessible digital experiences.</p><p>I enjoy learning by building, experimenting with new technologies, and understanding what happens beyond the code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42348cad2694" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Redis Is Essential in Enterprise Applications]]></title>
            <link>https://medium.com/@thuve104r/why-redis-is-essential-in-enterprise-applications-37985df10db3?source=rss-7fda53674985------2</link>
            <guid isPermaLink="false">https://medium.com/p/37985df10db3</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Thuve R]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 18:56:39 GMT</pubDate>
            <atom:updated>2026-11-17T18:56:39.824Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*TLyDcVUJw-BdTKFps9LEsQ.jpeg" /></figure><p>In today&#39;s enterprise world, users expect applications to be fast, reliable, and always available. As businesses grow, traditional databases alone often struggle to handle increasing traffic and real-time demands. This is where Redis becomes a game changer.</p><p>**What is Redis?**</p><p>Redis (Remote Dictionary Server) is an open-source, in-memory data store that can be used as a cache, database, message broker, and streaming engine. Because it stores data in memory instead of on disk, Redis delivers responses in milliseconds.</p><p>**Why Enterprise Applications Need Redis**</p><p>1. Lightning-Fast Performance</p><p>Redis dramatically reduces response times by storing frequently accessed data in memory. Instead of querying the primary database for every request, applications can retrieve cached data almost instantly.</p><p>Example: User profiles, product catalogs, and application settings can be served from Redis rather than repeatedly querying the database.</p><p>2. Reduces Database Load</p><p>Enterprise systems often experience thousands or even millions of requests per day. Redis acts as a buffer between the application and the database, significantly reducing database queries and improving overall system stability.</p><p>3. Better Scalability</p><p>As your business grows, traffic increases. Redis helps applications scale horizontally by handling repeated read operations efficiently, allowing backend databases to focus on critical transactions.</p><p>4. Session Management</p><p>Managing user sessions across multiple servers can be challenging. Redis provides centralized session storage, making it ideal for load-balanced and distributed applications.</p><p>5. Real-Time Applications</p><p>Redis is widely used for:</p><p>- Live notifications<br>- Chat applications<br>- Gaming leaderboards<br>- Live analytics dashboards<br>- Real-time tracking systems</p><p>Its publish/subscribe (Pub/Sub) capabilities make instant communication possible.</p><p>6. Background Job Processing</p><p>Enterprise applications often need to process emails, reports, image uploads, and notifications asynchronously. Redis works seamlessly with job queues, allowing background tasks to run without slowing down the user experience.</p><p>7. High Availability</p><p>Redis supports replication, clustering, and automatic failover, ensuring applications remain available even if a server fails.</p><p>Common Enterprise Use Cases</p><p>- API response caching<br>- Authentication and user sessions<br>- Rate limiting APIs<br>- Shopping cart storage<br>- Real-time notifications<br>- Leaderboards<br>- Background job queues<br>- Distributed locking<br>- Analytics and counters</p><p>Benefits at a Glance</p><p>- Millisecond response times<br>- Reduced database workload<br>- Improved application scalability<br>- Better user experience<br>- Lower infrastructure costs<br>- High availability and reliability<br>- Excellent support for real-time features</p><p>Best Practices</p><p>- Cache only frequently accessed data.<br>- Set expiration (TTL) for cached items.<br>- Monitor memory usage regularly.<br>- Use Redis clustering for high-traffic systems.<br>- Never use Redis as the only permanent storage for critical business data unless your architecture is specifically designed for it.</p><p>Final Thoughts</p><p>Redis is more than just a caching tool—it&#39;s a core technology that enables modern enterprise applications to deliver exceptional performance, scalability, and reliability. Whether you&#39;re building an e-commerce platform, SaaS application, banking system, ERP, or social platform, integrating Redis can significantly improve user experience while reducing backend workload.</p><p>As enterprise applications continue to grow in complexity and scale, Redis remains one of the most valuable technologies for building high-performance systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37985df10db3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Internship Journey: Learning Beyond the Classroom]]></title>
            <link>https://medium.com/@thuve104r/my-internship-journey-learning-beyond-the-classroom-6920ff889637?source=rss-7fda53674985------2</link>
            <guid isPermaLink="false">https://medium.com/p/6920ff889637</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Thuve R]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 18:52:42 GMT</pubDate>
            <atom:updated>2026-11-17T18:52:42.274Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*PMxN_oeIa_vXcxDDuZSUvA.jpeg" /></figure><p>Internships are one of the most valuable experiences for any undergraduate, and I am grateful to have completed mine. This journey allowed me to bridge the gap between academic knowledge and real-world software development while improving both my technical and professional skills.</p><p>From my very first day, I was introduced to a collaborative development environment where teamwork, communication, and problem-solving played a major role. I had the opportunity to work on real projects, understand industry workflows, and learn how professional software products are built and maintained.</p><p>Throughout my internship, I gained hands-on experience with modern web technologies, version control using Git, API integration, debugging, and deploying applications. I also learned the importance of writing clean, maintainable code and following industry best practices. Working alongside experienced developers helped me improve my coding standards and exposed me to new tools and frameworks.</p><p>One of the biggest lessons I learned was that software development is not only about writing code. It involves understanding user requirements, collaborating with team members, managing deadlines, and continuously learning new technologies. Every challenge I encountered became an opportunity to grow and improve my skills.</p><p>Beyond technical knowledge, this internship strengthened my confidence, communication, time management, and ability to work effectively in a professional team. The guidance and support from my mentors played a significant role in my growth throughout this journey.<br>Looking back, this internship has been a milestone in my career. It has given me practical experience, valuable industry exposure, and a clearer vision of the software engineering field. I am excited to apply these lessons in my future projects and continue growing as a developer.<br>I would like to express my sincere gratitude to my mentors, teammates, and the organization for providing me with this incredible opportunity. This experience will always remain an important part of my professional journey, and I look forward to embracing new challenges in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6920ff889637" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>