12 Lessons from 12 Months of 2025

When I look back at 2025, it does not feel like a year of big announcements or dramatic changes. It feels more like a year where a lot of small things quietly shifted direction. At the time, most of these changes did not feel important. Only later, when I slowed down and looked back, did I realize how much they shaped the way I think and work today.

This is not a highlight reel. It is simply what stayed with me after the year ended.

Doing the work mattered more than talking about it

For a long time, I believed effort needed to be visible to matter. I thought if people did not see me working, then somehow the work itself counted less. In 2025, that belief softened. I contributed to open-source projects like Selenium and Aluminium without making noise about every commit or pull request. I just did the work. Somewhere along the way, recognition came on its own. I got featured in the Selenium Conference spotlight, which was unexpected but reassuring. It reminded me that consistent work has a way of surfacing, even when you are not trying to push it forward or broadcast every step.

Writing publicly changed how carefully I think

Writing in public forced me to be more honest with my own thoughts. I started publishing articles on Ministry of Testing and Sparks, and once something is out there, you cannot rely on intention alone. The words need to make sense on their own, without you standing beside them explaining what you really meant. This pushed me to slow down and ask myself whether I really understood what I was trying to say. Over time, that habit spilled into my everyday thinking. I started noticing vague thoughts earlier and questioning them before they turned into half-baked opinions I might regret later.

Testing became harder and more interesting once systems grew

Moving from monolithic systems to microservice-based architectures changed how I see testing. Problems were no longer neat or isolated. Failures rarely had one clear reason you could point to and fix. At first, this felt frustrating. I wanted things to be simple again. Later, it became interesting. I stopped chasing completeness and started focusing more on understanding risk. Testing began to feel less like a checklist you work through mechanically and more like a way to explore how things actually behave when you put them under pressure.

Switching tools did not change problems, but it changed how I see them

I moved my automation stack from Selenium with Python to Playwright with JavaScript. Changing tools felt exciting at the beginning, but the excitement settled quickly. The same kinds of problems showed up again, just wearing different clothes. What really changed was my awareness. Some habits became harder to justify when the new tool exposed them clearly. Others became more visible in ways I could not ignore anymore. I realized tools do not solve problems for you, but they do expose how you think about them. They hold up a mirror to your process, whether you are ready to look or not.

More people reading does not automatically mean more impact

My writing reached readers across more than forty countries and six continents. Seeing those numbers felt nice, but it also taught me something important. Numbers are easy to notice and hard to interpret. They feel good in the moment but tell you almost nothing about whether anything you said actually mattered. Real impact is quieter. It shows up when someone reaches out with a thoughtful response or says that something helped them think differently about a problem they were stuck on. I learned to care less about reach and more about whether what I wrote felt honest and clear.

I stopped being a passive observer and chose deeper conversations instead

I became more actively involved in online testing communities like Ministry of Testing, The Test Chat, Test Tribe, and BrowserStack communities. At some point, just watching from the sidelines started to feel safe but limiting. I found myself listening politely instead of engaging actively. So I stepped in. I spent more time in spaces where conversations continue past the first exchange, evolve over days or weeks, and sometimes disagree in ways that make you reconsider what you thought you knew. That depth suited me better. It helped me learn slowly but more meaningfully.

Building something under pressure taught me more than preparation

I participated in the BrowserStack Automation Hackathon with Gaurav Khurana and ended up winning for the Delhi NCR region. Working under time pressure changes how you think. There is less room to over-plan and more need to decide quickly with whatever information you have. That experience taught me where I tend to overthink and where I actually rely on instinct without realizing it. It reminded me that learning often accelerates when you are forced to act, not when you are sitting around feeling perfectly prepared. Sometimes the best teacher is just not having enough time to second-guess yourself.

Getting rejected still helped me understand what needs work

I submitted multiple call for proposals to different conferences. Some cleared the initial review rounds, which felt encouraging. But none made it to the final selection. That was disappointing at first. I wanted everything to land perfectly. Later, it became useful. Those moments showed me that direction matters, but clarity matters more. Even without detailed feedback from organizers, rejection helped me see what needed refinement. It pointed to the gaps I had been ignoring or glossing over in how I structured my ideas.

Exploring new areas without clear outcomes was still worth it

I began exploring AI agents and Model Context Protocol concepts in the context of testing. That uncertainty felt uncomfortable at times. There was no clear goal, no obvious payoff waiting at the end. But it also stretched my thinking in ways I did not expect. It taught me to sit with incomplete understanding and resist the urge to rush toward conclusions just to feel like I was making progress. Not every effort needs a clear result to be valuable. Sometimes just wandering around in a new space teaches you things you would never learn by staying on the well-worn path.

Learning improved when I slowed down instead of consuming more

For a long time, I thought learning meant reading more. The more I took in, the more I would know, right? In 2025, I started reading more consistently, including topics beyond testing. But I also realized the problem was not lack of information, but lack of processing. Reading widely helped widen my perspective, but journaling regularly made the real difference. Writing things down helped me pause, reflect, and connect ideas that otherwise would have just floated past. Learning became deeper once I stopped treating it like something to get through quickly and started treating it like something to actually digest.

I started paying more attention to how I think, not just what I learn

Chess entered my routine quietly. I did not take it up seriously or competitively. It simply gave me a space to notice how I make decisions under constraints. It taught me patience and the real cost of rushing into moves without thinking them through. Over time, those lessons showed up in my work as well. I became more comfortable slowing down and thinking a few steps ahead instead of just reacting to whatever was right in front of me. Around the same time, I also attended structured learning cohorts like HOTS Smart QA and SmarQA Transformation program, which helped me see patterns in my thinking I had missed before.

I realized some ideas work better when spoken than written

Toward the end of the year, I experimented with creating videos. It was awkward and far from polished, but it revealed something important. Some ideas feel more natural when spoken. They carry pauses, tone, and context that writing sometimes loses or flattens out. This realization shaped how I think about the coming year. I identified video as a focus area for 2026, not to create content for the sake of it, but to understand my own thinking better and see which medium serves different kinds of ideas.

Looking ahead

2025 did not change everything at once. It changed small things, quietly and consistently. How I learn. How I choose depth over noise. How I think before acting. Looking back, it feels less like a year of achievements you can list on a resume and more like a year of alignment with what actually matters to me. That feels like a good place to move forward from.