<?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 Nikita Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Nikita Srivastava on Medium]]></description>
        <link>https://medium.com/@nikitaksrivastava?source=rss-01f390ca775f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*U4Z7Ck1g--_zIJ2uYjJhsQ.jpeg</url>
            <title>Stories by Nikita Srivastava on Medium</title>
            <link>https://medium.com/@nikitaksrivastava?source=rss-01f390ca775f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:05:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nikitaksrivastava/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[If I Knew Better, I Would Have Done Better]]></title>
            <link>https://medium.com/@nikitaksrivastava/if-i-knew-better-i-would-have-done-better-0904ae9e7c64?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0904ae9e7c64</guid>
            <category><![CDATA[pschology]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[trending]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 18:24:04 GMT</pubDate>
            <atom:updated>2026-11-14T07:36:55.943Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Of4EIvWkygcujNvw" /></figure><p>You know what’s strange? We spend so much time wishing we had done things differently.<br>I sometimes wonder how many times we’ve looked back at a situation and thought, <em>“God, why did I do that?”</em></p><p>Funny how some things seem so obvious now. You look back and wonder how you didn’t see it then.<br>Think about it. There are probably things you’ve done that you wouldn’t even consider doing today. People you would never trust so easily, situations you wouldn’t put yourself in, words you would choose differently.</p><p>But you weren’t the person you are today back then.<br>Maybe you trusted someone because you genuinely believed they wouldn’t let you down. Maybe you stayed because walking away felt harder than holding on. Maybe you kept trying because you couldn’t bring yourself to give up on something that meant so much to you.</p><p>And now, with the benefit of hindsight, you see it all differently.</p><p><em>But I wonder, why are we so hard on ourselves about it?</em></p><p>We make choices with the understanding we have at that point in life. Our judgement isn’t always right, our instincts aren’t always sharp, and our expectations don’t always match reality. That’s part of being human. We learn discernment through experience, and experience doesn’t always come gently.</p><p>Here’s what I find interesting, though. We are often able to extend grace to other people for the things they didn’t know, but struggle to offer ourselves the same consideration.<br>There’s a difference between accountability and self-punishment. You can acknowledge that you were naive without treating your younger self with contempt.</p><p>You have grown, your perspective has changed, and there are things you understand today that you simply couldn’t have understood back then.<br>So, the next time you look back and wish you’d done better, remember:</p><p><strong><em>If I knew better, I would have done better.</em></strong></p><p>And perhaps that’s enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0904ae9e7c64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kalpa: I Left a Little of My Heart Somewhere in the Mountains]]></title>
            <link>https://medium.com/@nikitaksrivastava/kalpa-i-left-a-little-of-my-heart-somewhere-in-the-mountains-13a8ecda5cf6?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/13a8ecda5cf6</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[mountains]]></category>
            <category><![CDATA[kalpa]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 12:14:12 GMT</pubDate>
            <atom:updated>2026-11-06T12:14:12.447Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hUpOwgtALIx-UkY9" /><figcaption>Kalpa, Himachal Pradesh.</figcaption></figure><p>There are places you visit, places you photograph, and then there are places you wish you could somehow keep with you. <strong>Kalpa</strong>, for me, was the third kind.</p><p>Tucked away in the beautiful <strong>Kinnaur district</strong> of Himachal Pradesh, Kalpa is one of those places that makes you wonder how something so beautiful can exist so quietly. It isn’t just about the mountains or the views. It’s about the feeling of being there. The kind of feeling that makes you put your phone down for a moment, look around and think, <em>How lucky am I to be witnessing this?</em></p><p>We visited Kalpa towards the end of May. Delhi was burning in the summer heat and honestly, the moment we entered Solan, I could feel the difference. The temperature, the wind, the quality of air, everything changed. The air became cooler, fresher and so much easier to breathe. I was actually shivering, but it was the happiest kind of shivering.</p><p>The journey itself was an experience. We started from Delhi in the evening and reached Kalpa the following afternoon, around 3–4 PM. More than 20 hours on the road, through winding mountain roads, valleys and landscapes that kept getting prettier. I am probably one of those people who behaves like a dog during road trips, with my face almost permanently outside the car window. I don’t want to miss a single thing happening outside.</p><p>There was also a beautiful morning stop near Shimla for some tea. Imagine being half asleep, stepping out into the chilly mountain air, and suddenly getting excited about taking photographs. That’s me. Sleep can wait when there’s a pretty view around.</p><p>But arriving in Kalpa was something else altogether.<br>Kalpa is a village, but it feels like a little world of its own. Narrow roads, beautiful traditional houses, distinctive wooden architecture and the prettiest doors. There are cafés, monasteries and temples tucked into the village, and somehow everything seems to belong exactly where it is. Sometimes, just walking through the lanes is enough.</p><p>And then we found this open ground.<br>There were children playing football, with the entire mountain range sitting right behind them. It was just an ordinary afternoon for the people playing there. But for someone who had travelled all the way to witness these mountains, it was extraordinary.</p><p><em>I sat there for more than an hour.</em><br>I remember looking at the mountains and getting goosebumps. My heart genuinely sank with the realisation that people like me are lucky enough to witness something like this with their own eyes. I wasn’t rushing to another viewpoint or looking for another photograph. I just wanted to sit there and take it all in.</p><p>And then came the sunset.<br>I don’t think I have ever seen mountains change colours quite like that. The golden light slowly turned orange, falling over the mountain peaks and making the entire landscape look unreal. While everyone was enjoying the evening, I wandered through the lanes and found a under-construction house with an outside staircase. I went up to the terrace, sat there and watched the sunset.<br><em>Just me, a terrace and that view.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*As23Fnr0_hvnd-7x" /></figure><p>The mountains kept changing colours, and I honestly didn’t feel like getting up. Sometimes, the best travel experiences aren’t the ones you plan. They are the little discoveries you make when you allow yourself to wander. Kalpa is also known for its magnificent views of <strong>Kinnaur Kailash</strong>, the sacred mountain associated with <strong>Lord Shiva</strong>, whose distinctive natural rock formation is revered as the <strong>Kinnaur Shivling</strong>.</p><p>Also, our hotel had its own charm. The room had a huge window overlooking the mountains and the little houses scattered across the landscape. But the night gave us another surprise.</p><p>As we opened the window and saw the moon rising between a few clouds. It wasn’t an ordinary moonlit night. The moon was incredibly bright, and the sky was filled with stars. We eventually stepped outside and simply sat there, looking up.</p><p>I don’t remember how long we sat, but I remember the feeling. The kind of silence where nobody really needs to say anything.</p><p>And of course, my mountain trip is incomplete without good food. We tried <em>Siddu</em>, with its delicious walnut filling, and <em>Thukpa, with </em>warm, hearty broth. And then there was Maggi. Maggi in the mountains hits different. Maybe it’s the cold, maybe it’s the view, or maybe it’s just comfort food. Well, guess we’ll never know.</p><p>We spent just two days and one night in Kalpa. And if there’s one thing I would tell someone planning a trip here, don’t make it a rushed stopover. Give this place time. Walk through its lanes, sit somewhere without checking the time, watch the mountains, eat something warm and let the place grow on you.</p><p>Because Kalpa isn’t just about ticking off viewpoints from a list.</p><p><strong>Leaving was probably the hardest part.</strong></p><p>I genuinely had tears in my eyes. I kept thinking about how rare an opportunity it is to travel somewhere like this, and <em>how uncertain it is when I’ll get to return.</em> There was so much more I wanted to see, so many more moments I wanted to experience.<br><em>I felt like I was leaving a little piece of my heart behind.</em></p><p>And perhaps that’s what travelling to the mountains does to you. You arrive with excitement, spend a few days surrounded by beauty, and leave carrying memories that are much bigger than the time you spent there.</p><p>I went to Kalpa with a heart full of curiosity. I left with a heart full of memories.<br><strong>If life gives you one chance, you better spend atleast two days in Kalpa.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13a8ecda5cf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Road We Never Took]]></title>
            <link>https://medium.com/@nikitaksrivastava/the-road-we-never-took-076c39e69a32?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/076c39e69a32</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Sat, 27 Jun 2026 13:26:41 GMT</pubDate>
            <atom:updated>2026-06-27T13:26:41.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGhiXmyZiPALWe8UlySPkA.jpeg" /></figure><p>A few days ago, I found myself doing something I’ve done more times than I’d like to admit.</p><p>No matter how content we are with our lives, our minds have an odd habit of wandering toward the road we never took.</p><p>The job we didn’t accept. The city we never moved to. The person we never told how we felt. The dream we quietly placed on hold because life happened.<br>It’s as if a part of us keeps visiting another version of reality, wondering whether that version of ourselves turned out happier.</p><p>The opportunities were endless. And then it hit me. <br>Of course it was perfect.<br>Reality never got the chance to touch it. I think that’s something we all do without realizing it.</p><p>Whenever life feels uncertain, our minds quietly wander toward the road we never took.</p><p>Sometimes I imagine what life would’ve looked like if I had said yes instead of no. If I had stayed instead of leaving. If I had been a little braver, a little earlier, or a little more certain.</p><p>And every single time, that imagined life somehow feels… better. Not because I know it would’ve been. Because I never had the chance to watch it fall apart.<br>That’s what fascinates me.<br>It’s almost as if another version of ourselves continues living somewhere inside our imagination, and every now and then we visit them just to ask,</p><p><em>“Would your life have been better than mine?”</em></p><p>But that’s an unfair comparison.</p><p><strong>We don’t compare reality with reality. We compare reality with imagination.</strong></p><p>The life we’re living has deadlines, disappointments, awkward conversations, unexpected bills, and ordinary Tuesday afternoons. The life we never chose has none of those.</p><p>It never had the opportunity to disappoint us. Instead, our minds quietly polish it. They remove the failures.<br>The wrong turns. The moments of self-doubt. What’s left behind is possibility.</p><p><strong>And possibility is beautiful because it has never been tested.</strong></p><p>Maybe that’s why <em>The Road Not Taken</em> continues to resonate with so many people. Not because it tells us which road was right.<br>But because it reminds us that every meaningful choice quietly closes the door on another version of ourselves.</p><p>I don’t think growing up is about learning how to make perfect decisions. I think it’s about making peace with the lives we’ll never get to live.<br>Because we’ll never know whether the other career would’ve made us happier.</p><p>Whether the other city would’ve felt more like home.<br>Whether the relationship we never started would’ve lasted forever or ended just the same. We’ll never know.<br>And perhaps that’s exactly why those lives continue to feel so perfect.</p><p><strong>Reality is allowed to be imperfect. Imagination never is.</strong></p><p>Maybe peace doesn’t come from proving we chose the right road.<br>Maybe it comes from accepting that every road eventually becomes ordinary once you start walking on it.</p><p><strong>The road we never took only looks extraordinary because we never stayed on it long enough to discover its own disappointments.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=076c39e69a32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Smart People Make Bad Decisions]]></title>
            <link>https://medium.com/@nikitaksrivastava/why-smart-people-make-bad-decisions-5e80b7c7508c?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e80b7c7508c</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Sun, 21 Jun 2026 08:20:56 GMT</pubDate>
            <atom:updated>2026-06-21T08:20:56.383Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most dangerous things about the human mind is how quickly it wants certainty.<br>The moment something feels wrong, we start looking for an explanation. And once we find one, we rarely stop to ask whether it’s the right one.</p><p>That’s why solving the wrong problem is so common.</p><p>Not because people lack intelligence, but because intelligence combined with urgency can be surprisingly deceptive. Once we become attached to an explanation, every new observation starts reinforcing it. Momentum builds around the diagnosis long before the diagnosis itself has been questioned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aTz_aePetNmu7siDzsz9uw.jpeg" /></figure><p>And that is where mistakes become expensive.</p><p><strong>Because effort applied in the wrong direction doesn’t fail immediately.</strong></p><p>It scales.<br>At first, it even looks impressive. Discussions happen. Strategies are created. Systems are optimized. Everyone feels productive because something is moving.</p><p><strong>But movement and progress are not the same thing.</strong></p><p>Many systems become addicted to movement because movement is visible. It creates the comforting feeling that a problem is being addressed, even when nobody has paused to ask whether they are addressing the right problem in the first place.<br>I think this pattern becomes visible everywhere once you start noticing it.</p><p>Take productivity.</p><p>Someone feels constantly overwhelmed and assumes productivity is the issue. They build better routines, organize their calendar, download new apps, and optimize every hour of the day.</p><p>And for a while, it works.<br>Their life becomes more structured. More organized. More efficient. <br>Yet the exhaustion remains.<br>Because productivity was never the real problem.</p><p>The real problem was living in a state where rest itself felt uncomfortable. No planner or scheduling system can solve a nervous system that no longer knows how to switch off.</p><p>The same thing happens in technical systems.</p><p>An analyst notices inconsistent reporting numbers and immediately starts investigating dashboards, queries, and calculations. Hours are spent improving reports and validating logic.<br>But the inconsistency survives.</p><p>Eventually, the issue turns out to be duplicate records entering the system upstream. The reporting layer was never the problem. It was simply where the problem became visible.<br>And that’s what makes smart people especially vulnerable to bad decisions.</p><p>Symptoms are often easier to see than causes.<br>Over time, organizations and individuals start building layers around those symptoms. More reviews. More approvals. More processes. More controls.<br>Not because people are incompetent.</p><p>Because they are intelligently solving the wrong thing.<br>The best problem solvers I’ve met are not the people who find answers the fastest. They’re the people who stay uncertain a little longer.<br>The people willing to challenge the framing of the problem before investing energy into the solution.</p><p><strong>Because once certainty enters the room, curiosity usually leaves.<br></strong>And curiosity is often the only thing standing between a symptom and its source.</p><p>The most expensive mistakes are rarely caused by a lack of intelligence. They happen when intelligence becomes attached to the wrong answer.<br>The real cost isn’t wasted effort.<br><strong>It’s wasted direction.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e80b7c7508c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How One Wrong Merge in Pandas Quietly Corrupts Your Entire Dataset]]></title>
            <link>https://medium.com/@nikitaksrivastava/how-one-wrong-merge-in-pandas-quietly-corrupts-your-entire-dataset-c2df3a4d3317?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2df3a4d3317</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 13:15:54 GMT</pubDate>
            <atom:updated>2026-04-29T13:15:54.451Z</atom:updated>
            <content:encoded><![CDATA[<p>I was recently working on a small dataset in Pandas, trying to combine user and order information for a simple analysis.<br>Nothing particularly complex. Just two clean tables, a merge operation, and a few calculations on top.</p><p>For anyone unfamiliar, <strong>Pandas </strong>is a Python library widely used for data manipulation and analysis. It makes working with structured data significantly easier through operations like filtering, grouping, aggregation, and merging datasets.<br>One of the most common operations in Pandas is <strong><em>merge()</em></strong>.</p><p>At a high level, it does exactly what it sounds like. It combines two datasets based on a common key, similar to joins in SQL.<br>Simple enough. Or at least, that’s what I thought.</p><p>Everything in my workflow looked normal. The code ran successfully. The output was structured. No exceptions, no warnings, no obvious red flags.<br>And yet, one metric felt slightly off.</p><p>That moment is interesting because this is how many real data issues begin. Not with a crash. Not with a visible error. <br>But with results that look reasonable enough to trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1AIrAuOvsQk9PXMNQWOsg.png" /></figure><p><strong>A lot of data issues are easy to catch:</strong></p><ul><li>Missing column raises an error.</li><li>A syntax issue breaks execution.</li><li>A typo forces you to debug.</li></ul><p>Those failures are visible. A bad merge is different. A bad merge succeeds. That is what makes it dangerous for huge data points.</p><p>Imagine you are working with two datasets.</p><p>A users table:</p><pre>import pandas as pd<br><br>users = pd.DataFrame({<br>    &quot;user_id&quot;: [1, 2, 3],<br>    &quot;name&quot;: [&quot;Nikita&quot;, &quot;Vansh&quot;, &quot;Rohit&quot;]<br>})</pre><p>And an orders table:</p><pre>orders = pd.DataFrame({<br>    &quot;order_id&quot;: [101, 102, 103, 104],<br>    &quot;user_id&quot;: [1, 1, 2, 2],<br>    &quot;amount&quot;: [250, 300, 150, 200]<br>})</pre><p>The objective is straightforward.<br>You want to combine user details with order information.</p><p>So you write:</p><pre>merged = users.merge(orders, on=&quot;user_id&quot;)</pre><p>It runs instantly.<br>No warnings, no issues, no reason to question anything.</p><p>The output looks completely fine.<br>You print the merged dataset:</p><pre>print(merged)</pre><pre>   user_id   name   order_id  amount<br>0        1  Nikita       101     250<br>1        1  Nikita       102     300<br>2        2   Vansh       103     150<br>3        2   Vansh       104     200</pre><p>At first glance, this looks correct.<br>And technically, it is.</p><h3>What actually happened?</h3><p>Before the merge, your users table had one row per user. After the merge, Nikita appears twice. Vansh appears twice.<br>Why?</p><p>Because one user can have multiple orders. This is a one-to-many relationship. Pandas did exactly what you asked it to do. It expanded each user row to match every related order row.<br>The merge did not corrupt your dataset because Pandas failed. It corrupted your dataset because your mental model was incomplete.</p><h3>Where analysis quietly starts going wrong?</h3><p>The real damage happens after the merge.<br>Not during it.<br>Suppose you calculate:</p><pre>total_users = merged[&quot;user_id&quot;].count()<br>print(total_users)</pre><p>Output:</p><pre>4</pre><p>But how many users actually exist?<br><strong>Three.<br><em>Nikita. Vansh. Rohit.</em></strong></p><p>The number <strong>four </strong>is not random. It is inflated. Your merge multiplied rows.</p><p>Now imagine using this data in reporting. <br>Or calculating conversion metrics. <br>Or feeding it into dashboards.<br>The analysis is no longer answering your intended question. But because the output looks clean, the mistake often survives.</p><h3>Why this happens so often?</h3><p>Because data analysis is not only about code. It is about understanding how data connects. And that is where many issues begin.<br>A merge feels simple. Take two tables. Join them.<br>But underneath that single line of code is an assumption:</p><p><strong>How does one dataset relate to another?</strong></p><p>Is it:</p><ul><li>one-to-one</li><li>one-to-many</li><li>many-to-many</li></ul><p>That distinction is easy to ignore when the code runs successfully. But it matters far more than most people realize. A merge is not just combining tables. It is defining relationships between rows.<br>And when that relationship is misunderstood, the output may still look correct while quietly changing the structure of your data.<br>That is where analysis begins to drift.</p><h3>The correct way to think about it</h3><p>The goal is usually not “<em>merge everything</em>.” The goal is preserving analytical intent.<br>If your analysis requires one row per user, then your orders dataset must first be reshaped.<br>Aggregate before merging:</p><pre>orders_agg = (<br>    orders<br>    .groupby(&quot;user_id&quot;)[&quot;amount&quot;]<br>    .sum()<br>    .reset_index()<br>)</pre><p>Now merge:</p><pre>merged = users.merge(orders_agg, on=&quot;user_id&quot;, how=&quot;left&quot;)</pre><p>Result:</p><pre>   user_id   name   amount<br>0        1  Nikita     550<br>1        2   Vansh     350<br>2        3   Rohit      NaN</pre><p>Now the structure aligns with the original goal.<br>One row per user. Stable metrics.</p><h3>A safeguard most analysts ignore</h3><pre>users.merge(orders, on=&quot;user_id&quot;, validate=&quot;one_to_many&quot;)</pre><p>The <strong><em>validate </em></strong>parameter forces you to explicitly define the expected relationship. It is less about code safety and more about analytical discipline. It asks an important question before your merge runs:</p><p>Do you actually understand the shape of your data? That is a far more valuable check than most people realize.</p><h3>Final thought</h3><p>In data analysis, silence can be deceptive.</p><p>A query that runs is not necessarily correct. A dataset that looks structured is not necessarily reliable. An output that feels reasonable is not necessarily true.</p><p>Hope you found this helpful. Let’s connect on LinkedIn:<strong> </strong><a href="https://www.linkedin.com/in/nikitasrivastava06">nikitasrivastava06</a>.<br>Happy Learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2df3a4d3317" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Most Documentation Isn’t as Good as You Think]]></title>
            <link>https://medium.com/@nikitaksrivastava/most-documentation-isnt-as-good-as-you-think-974b71915a30?source=rss-01f390ca775f------2</link>
            <guid isPermaLink="false">https://medium.com/p/974b71915a30</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[documentation]]></category>
            <dc:creator><![CDATA[Nikita Srivastava]]></dc:creator>
            <pubDate>Sun, 26 Apr 2026 04:22:41 GMT</pubDate>
            <atom:updated>2026-04-26T04:23:04.208Z</atom:updated>
            <content:encoded><![CDATA[<p>Most documentation feels complete when it’s written.</p><p>It covers the feature. It explains the flow. It answers questions the writer can anticipate.<br>And yet, the moment someone tries to use it, it slows them down.<br>They slow down. They reread. They get stuck. Or worse, they stop reading and just ask someone else.<br>That gap is the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*flnlrYH3Xd58AgL8_ow8-Q.png" /></figure><h3><strong>Common issue:</strong></h3><h3><strong>1. Structure</strong></h3><p>In many cases, documentation mixes everything together. Setup instructions, background information, warnings, and edge cases all sit in the same flow.<br>From a technical writing perspective, this breaks usability.</p><p>A more effective structure separates content into clear sections such as:<br>- Prerequisites<br>- Step-by-step actions<br>- Expected output<br>- Error handling</p><p>For Example:<br>Before:</p><pre>To configure settings, ensure dependencies are installed and then proceed to update values carefully...</pre><p>After:</p><pre>Prerequisites: Dependencies installed  <br>Steps: Open settings → Update values → Save  <br>Expected: Configuration applied</pre><p>When these are clearly defined, users can navigate faster and focus only on what they need.</p><h3><strong>2. Assumptions</strong></h3><p>Documentation is often written by someone who already understands the system. As a result, key details are skipped.</p><p>For example, a step might say:</p><blockquote>“Run the script and verify the output.”</blockquote><p>But this assumes the user knows:</p><ul><li>where the script is located?</li><li>what environment it should run in?</li><li>what “correct output” looks like?</li></ul><p>Without that clarity, even a simple step becomes a blocker. A clearer version would be:</p><blockquote>Open the file config.yaml located in /etc/app/.<br> Update the timeout value from 30 to 60.<br> Save the file and restart the service using restart app-service.<br> You should see a confirmation message in the logs indicating the service restarted successfully.</blockquote><p>The difference is not technical complexity. It is clarity and completeness in execution.</p><h3>3. Scannability</h3><p>Most users do not read documentation line by line. They scan for commands, file names, and key actions. This is where formatting choices matter.<br>Using short paragraphs, consistent terminology, and clearly separated steps makes a big difference in how quickly someone can act on the information.</p><p><strong>Feel free to connect on LinkedIn: </strong><a href="https://www.linkedin.com/in/nikitasrivastava06">nikitasrivastava06</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=974b71915a30" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>