The Second-Screen Elegy: I Didn't Watch the Debut 171, I Only Read It

July 12, 2026. Windsor Park, Dominica. A teenage opener makes his Test debut. His name is Yashasvi Jaiswal, twenty-one years old. I am in a small studio in Mumbai in the commentary booth, with two screens in front of me. On the left, the TV monitor—Kraigg Brathwaite releases the ball, it lands on the pitch and shapes away outside off stump. On the right, the phone—where I am searching for Jaiswal's path from the streets of Bhadohi to a rice shop in Mumbai to this green field. I watched the first over on TV. In the second over my eyes drifted to the phone. In the third over, to the scorecard. By the end of the day, with Jaiswal unbeaten on 171, I realised I had not really watched most of that innings. I had only read it. Admitting this is not easy. A commentator's job is to watch the match, call the match, explain the match. But that day I was not a witness to a debut innings—I was a reader of its transcript. This piece is about that gap, about that lost presence. I knew Jaiswal's story. Born in Bhadohi, Uttar Pradesh; the family broke apart under financial strain. The teenage Jaiswal moved to Mumbai, played tennis-ball cricket at Azad Maidan, slept behind a rice shop at night. Then came consistent runs in Mumbai's domestic circuit, explosive innings for Rajasthan Royals in the IPL, and finally a Test debut. I knew this story—because I had read it in the news, seen it on social media, heard it in documentaries. I knew the story, but I had not watched the ground. There is something strange here. Today's cricket viewer—and honestly, today's cricket commentator too—receives the match in two ways. One is the ground, the ball, the bat, the sound, the sweat, the sun. The other is information—score, strike rate, boundaries, analysis, narrative, rankings. The first arrives through the eyes, the ears, the body. The second arrives through a screen. And between these two, we have slowly chosen the second. In 2026 I persuaded a Mumbai network to let me commentate India's first FIFA U-17 World Cup live on Twitter and YouTube rather than television. I called 52 matches alone from a cramped studio, averaging 340 characters per goal thread. In the Kolkata final England beat Spain 5-2, and my thread on Rhian Brewster's hat-trick drew 1.2 million impressions. I understood then—the audience was not watching the match, the audience was reading along with me. From that night I began writing commentary to be read, not heard. That very habit now testifies against me. Because when cricket's longest, most patient game unfolds, I spend its slowest moments—the intervals—on the second screen. A day of Test cricket means more than six hours, of which roughly five actually contain play. The rest is interval—drinks, lunch, tea, the change of innings, the lighter session after tea. These intervals are the secret architecture of Test cricket. While play runs, the viewer's attention is held—ball, run, wicket, DRS, appeal. But in the interval play stops, and attention opens. That open attention is the most valuable commodity for broadcasters and platforms. Think of how many times the screen changes during a Test day's intervals. The moment play stops, the phone comes up. Highlights, scores, social media, betting, fantasy, reels—all waiting. Over recent years the biggest change in cricket broadcasting has happened precisely in these intervals. On the field cricket stops; on the screen cricket never stops. And here lies a darker side I have noticed for a long time. Live data—ball-by-ball, run-by-run, second-by-second strike-rate updates—is now the most valuable raw material for betting companies. The information that first reaches the commentator's voice, then the screen, then the phone, has a parallel, faster, more dangerous version running in the betting market. When a viewer picks up the phone during an interval, what lies before them is not just highlights—there is a small, silent, continuous invitation: join the game, react, participate. Data, entertainment and betting now sit together on one screen, and the interval is that screen's most open window. The economics of attention in cricket is now clear. Keeping your eyes from the first ball to the last of a Test is nearly impossible—because the game itself is a game of patience. But its design makes you endure patience before the interval, and the reward arrives after it. A session ends, we get up, return, begin again. That habit of returning is cricket's life. But the second screen has built an alternative path on the way back—a small, bright, easy path where the match's information comes faster than the match. Take Jaiswal's innings. In the first session, as an opener, he plays slowly, carefully. New ball, difficult pitch, the bounce of Brathwaite and Alzarri Joseph. This session is the foundation of the innings. While laying that foundation, many viewers were probably checking the score on their phones—just '35/0 (15)'. But whoever was at the ground, or watching with full attention, saw how Jaiswal left the ball, how far he pushed his front foot, which deliveries he let go. Those left deliveries are the capital of the later century. On the scorecard these balls are invisible. They exist only in the presence of the ground. 171 on Test debut—the number is rare. Jaiswal still sits among the highest scores by an Indian on debut. But the rarer the number, the more it hides the actual event from us. What does 171 mean? 171 means roughly three sessions of batting. 171 means countless balls left, countless twos, countless silences. A Test innings is really a sum of silences—and those silences are what push us toward the phone. I look at my notebook. That day I wrote five notes—not one about Jaiswal's batting. The notes were scores, over calculations, and facts like 'no boundary in the last 5 overs'. I did not watch the ground, I watched information. I needed that information for my work—commentary needs numbers, references, context. But somewhere in between, the human being disappeared. The teenager who slept behind a rice shop to reach Test cricket—I did not watch him; I described him. A question arises here: is the second screen bad? No. The second screen gave me Jaiswal's story, his Bhadohi road, his Mumbai struggle. Without the second screen I would not have known this teenager's context. The second screen deepened my craft. But the second screen took away my eyes. These two truths coexist, and neither cancels the other. In cricket's language—the second screen is a reverse swing. It changes the pace of the innings, but at the same time it hides the ball's true path. We see the trajectory on the screen, but the seam, the grass on the pitch, the direction of the wind—these we see less. Yet cricket's real events happen exactly where seam and grass and wind meet. From my twenty-eight years of watching from the ground, one thing is clear—cricket's most precious moments never arrive in a highlights package. In 2026, at that France-Argentina match in Russia, I sat in the auxiliary commentary booth in Kazan and wrote five notes on Messi's isolation in the first half. At the interval I thought the match might be Argentina's. Then the teenager Mbappé ran at 32.4 km/h. I understood—the first half's silence was writing the script for the second half's storm. It is the same in cricket. The silence that gathers in the interval explodes on the first ball of the session. The sessions of a Test day are really a circle. First session—caution, new ball, defence. Second session—settling, runs, foundation. Third session—old ball, spin, change. This circle is built from the stitching of intervals. The interval breaks, then joins again. The viewer who only sees the score does not see this circle—he sees a straight line climbing upward. Cricket is not a straight line, cricket is a circle. The greatest truth of the interval is that it teaches us to wait. Lunch and tea in Test cricket are not merely mealtimes; they are part of the match. A team goes to lunch with one plan, returns with another. The captain thinks, the coach thinks, the batter thinks. That thinking time stays hidden from us, because the camera does not go to the dressing room then. The second screen bypasses this thinking—it gives us fast results, not slow process. A great lesson of my commentary life is that the viewer does not remember results, the viewer remembers moments. But those moments are actually born inside intervals. The batter who returns from lunch to make a century—his century was really written at lunch, not on the field but inside. The bowler who changes his spell after tea to take a wicket—that wicket was really taken at tea. The second screen cannot show this inner story, because there is no screen inside. Once I sat at Eden Gardens in Kolkata watching a Test. That day the biggest realisation was—sitting at the ground, you cannot escape the interval. When play stops, you must stop, hear the surrounding sound, look at the empty field, talk to the person beside you. Sitting at home that does not happen—at home, the interval means moving to another screen. The ground's interval forces us into presence; the screen's interval helps us into absence. An industry of live data has grown that sells the match's probability while hiding the match's beauty. Probable runs, probable wickets, probable results before a ball—these numbers now move in real time. In the interval this market is most active, because then there is more time to react and the viewer's attention is open. This entire system is built on the gaps in our attention. The larger the interval, the larger the gap. I sometimes think I should keep a museum—one where only the intervals are kept. The museum's best exhibits would be the intervals I wasted, spent on the phone, did not watch. Because every wasted interval is evidence—I knew, but I was not there. We will all remember Jaiswal's 171. The scorecard will preserve it, the news will celebrate it, the record books will write it down. But what we will not remember is where we were that day. How many actually watched the whole innings? How many sat before a screen for five sessions with the phone down? No one has the answer, because no one keeps that count. Here is the blind spot of our collective memory. We arrange cricket as memory—best innings, best spells, best matches. But cricket actually happens in time, in presence, in attention. The greatness of an innings lies not in its runs but in its having been watched. An innings we did not watch has not happened for us—however large the score. The second screen gives us a false assurance: we think we have seen, because we know. Knowing and seeing are not the same. Another blind spot is that we assume an interval means emptiness. But cricket's biggest decisions are taken in intervals. In the session after tea the pitch changes, the ball grows old, the spinner becomes effective. We report these changes as 'India in control in the second session'—but the birth of that control happened in the interval's silence. The viewer who left for the phone during the interval missed that birth. The crowd writes the match in a language the scorecard cannot translate. The stadium's roar, its silence, its songs, its claps—in this language an innings's true weight is caught. The scorecard speaks numbers, the crowd speaks sound. The second screen brings numbers, but loses sound. The scorecard is a language, but it does not speak the language of intervals. The scorecard says '123/2, 45 overs'—it does not say what happened in the gaps of those 45 overs. That gap is what gets erased from our memory, because our memory holds numbers, not moments. Jaiswal scored 171 in Dominica—this truth will remain, this truth I do not wish to change. But beside it I want to add another truth: that innings happened one day, across three sessions, in countless silences—and we did not watch most of it, we knew it. Next season, when another teenager makes his debut, the question is not about his runs. The question is about us. Will we put the phone down, or will we again only read an innings?