<?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 Shishir Paudyal on Medium]]></title>
        <description><![CDATA[Stories by Shishir Paudyal on Medium]]></description>
        <link>https://medium.com/@ritushishir?source=rss-7fdb6eb24ee4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0I00UZluwbqy-_HZ.jpg</url>
            <title>Stories by Shishir Paudyal on Medium</title>
            <link>https://medium.com/@ritushishir?source=rss-7fdb6eb24ee4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:10:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritushishir/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[नरिसाउनु न बाबा!]]></title>
            <link>https://medium.com/@ritushishir/%E0%A4%A8%E0%A4%B0%E0%A4%BF%E0%A4%B8%E0%A4%BE%E0%A4%89%E0%A4%A8%E0%A5%81-%E0%A4%A8-%E0%A4%AC%E0%A4%BE%E0%A4%AC%E0%A4%BE-c003594ff372?source=rss-7fdb6eb24ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c003594ff372</guid>
            <category><![CDATA[बच्चा]]></category>
            <dc:creator><![CDATA[Shishir Paudyal]]></dc:creator>
            <pubDate>Sun, 20 May 2018 06:24:27 GMT</pubDate>
            <atom:updated>2021-12-09T03:43:38.752Z</atom:updated>
            <content:encoded><![CDATA[<p>छोरीका लागि राति उठेर रुनु नौलो हैन, हिजो पनि उठेर रोइन्।रातको ३ बजेको हुदो हो, ममीले भुलाउन खोजिन्, सकिनन्। नानीले नै बाबासगँ जाने भनेपछि सजिलो भो - नानी अर्को खाटमा अाइन्।भुल्न त भुलिइन् छोरी तर केको सुत्नु! ममीले सुतौ भन्दा ‘बुबु खाम न’ भन्ने शैलीमा बिस्तारै फकाउने स्वरमा भनिन्- ‘बाबा, बिस्कुट खाम न’! मैले पनि उस्तै स्वरमा भने — अहिले सुतौ नानी, भोली बिहानै उठेर दिन्छु है।बिस्कुट नदिने कुरा त छदै थियो,अझै मेरो आफ्नै अल्छि र सुत्न झनै ढिलो हुने सम्भावना मैले टार्न खोज्दैथिएँ तर छोरीको अगाडि केहि जोर चलेन। भान्सामा गएर बिस्कुटको एउटा पिस ल्याएर छोरीलाइ दिए। बाटो र घरछेउ मन्दिरको बत्तिको प्रकाशको कारण कोठामा बत्ति नबाले पनि मधुरो-मधुरो उज्यालो हुन्छ। त्यहि उज्यालोमा मैले छोरीलाइ हेरेँ-खुशि देखिइन छोरी। हातमा बिस्कुट थमाइदिए र पल्टदै भनेँ — ‘लौ खाऊ अब’।छोरीले बिस्कुट समाइन् तर खाइहालिनन् बरु भनिन्- नरिसाउनु न बाबा, है?!</p><p>अरे! म झसङ्ग भएँ। किन त्यस्तो भनिन् छोरीले भनेर म सोच्दै थिएँ, उनले फेरी थपिन्- ‘बाबा नरिसाउनु न, मुसुक्क हास्नुसन है!’ यस्तो समेत भन्ने भइसकिन् छोरी, अचम्म लाग्यो र अाफैसित नमज्जा लाग्यो। अघि बिस्कुट दिदा मेरो स्वर अलि झर्केको जस्तो मानिन् छोरीले शायद! मैले अहिले चाहि सानो स्वरमा भनें- बाबा रिसाउनु भा’छैन छोरी। छोरीले ‘हस’ भन्दै बिस्कुट खान थालिन्।मलाइ लाग्यो-यति साना बच्चाले पनि कस्तो बुझ्न सक्छन् है माया गरेको, अनि कतिखेर रिसाएको भनेर।यिनीहरुलाइ अरु सबै कुरा जस्तै माया, हेला, हासो र रिस पनि हामि आफै सिकाइरहेकै हुदारहेछौ! हुन पनि हो आखिर — जुनसुकै ठाउ, धर्म, भाषाको भएपनि सबैले सजिलै बुझ्ने पहिलो कुरा भनेको प्रेम र घृृणा नै हो!</p><p>नानीलाइ अघिको कुरालाइ मेटाएर अरू आश्वस्त पार्ने प्रयासमा होला शायद मैले हास्दै भनें- छोरी, म रिसाएको छैन, बाबा तिमिसगँ कहिले पनि रिसाउनुहुन्न है ! छोरीले फेरी ‘हस’ भन्दै बायाँ हात मेरो गाला तिर ल्याइन र सोधिन् — बाबाको गाला हो यो? मैले हास्दै ‘हो’ भनें ।अनि छोरी अलि तन्किएर बाबाको गालामा ‘माया’ गरिन्।मलाइ पनि छोरीले माफ गरे जस्तो लाग्यो र हलुका र निकै खुशिको अनुभव भो।मनमनै फेरी नरिसाउने प्रण गरेँ, र मधुरो प्रकाशमा छोरीलाइ हेरेँ — छोरी बिस्कुट खान थालेकि थिइन्।</p><p>अलि दिनपछि एकपटक एउटा कोठाबाट अलि चर्को स्वरमा उनकी ममीलाई बोलाएको मात्र थिए ममी भन्दा पहिले छोरी आपुगिन र भनिन — बाबा, ममीलाइ किन गाली गर्नुभको ! फेरि अचम्म परें, अस्ति छोेरिले मलाइ नरिसाउन गरेको आग्रह सम्झें अनि मुसुक्क हासेर भनें — गाली गरेको हैन छोरी बोलाको मात्र हो!</p><p>छोरीको डर या छोरीले नराम्रो सिक्लिन भन्ने डरले मात्र पनि रिसाउन र अलिकति चर्को समेत बोल्न नहुने भो अब! छोरीले हरेक पटक हामीलाइ सम्झाउदा मैले भनिरहेको हुन्छु — रिसले कहिल्यै राम्रो गर्दैन, तिमी पनि नरिसाउ है छोरी!</p><p>२०७४ पुष १०,कुमारी क्लब, बल्खु</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c003594ff372" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Emojis in Rocket Chat, different perspective!]]></title>
            <link>https://medium.com/@ritushishir/emojis-in-rocket-chat-different-perspective-e99e509c54c5?source=rss-7fdb6eb24ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e99e509c54c5</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[rocket-chat]]></category>
            <category><![CDATA[emoji]]></category>
            <dc:creator><![CDATA[Shishir Paudyal]]></dc:creator>
            <pubDate>Sat, 07 Oct 2017 04:16:44 GMT</pubDate>
            <atom:updated>2017-10-07T04:16:44.431Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently we started using RocketChat for our team communication. I find this tool very cool! Like in other chat platforms, one can use various emojis here too. There is no doubt emojis make online conversations more lively and sometimes people’s choice of different emojis is really fascinating.</p><p>Sometimes the emojis can completely substitute for your expression and you don’t need to write any new message. Here is an idea how they can be used creatively to deliver the message ‘silently’ in group chat rooms.</p><p>One ideal situation could be when you have not much to say but you still want to acknowledge to some message. You could get some request which takes some time and you can simply put :loading: to tell it’s underway. Later it can be replaced with ✅ once job is complete. And sometimes it’s perfectly fine to tell that you are 🤔 rather than remain silent when a friend asks to fix a 🐛. You should be 🆗 if you receive 🙇 from your friend when you do something for her/him or 👍 when someone simply agrees with your idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdX-vitFNluovvb6A7U_oA.png" /></figure><p>Obviously these emojis can be used as a reply on the conversation but keeping them only as emojis allows the conversation to be short and you won’t be distracting others by posting less-important responses like okay, thanks, done. Sometimes you can simply count ❌ or ✔️ instead of ‘yes’ and ‘No’ replies to know how many votes your idea got in your team. Or you can simply choose 🍕or 🍝 or simply ☕️ to tell what you want to order for your team lunch. That makes your team’s fun-manager’s job easy.</p><p>Comments are welcome : Please add on your ideas on making Rocket Chat conversation more meaningful using emojis. Anyways you can simply 👏 using ⤵️ if you ❤️ this story!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e99e509c54c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical writing without technical writer]]></title>
            <link>https://medium.com/@ritushishir/technical-writing-without-technical-writer-8bf3664496cc?source=rss-7fdb6eb24ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bf3664496cc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technical-writing]]></category>
            <dc:creator><![CDATA[Shishir Paudyal]]></dc:creator>
            <pubDate>Sat, 01 Apr 2017 09:29:59 GMT</pubDate>
            <atom:updated>2017-04-01T09:29:59.449Z</atom:updated>
            <content:encoded><![CDATA[<p>The fact that most of the software development companies do not have dedicated technical writers doesn’t understate the importance of writing on WHY, WHAT and HOW part of any product development. There should be someone to document all these things.</p><p>And almost all software engineers are same, they don’t want to write anything(technical) unless the output is visible immediately. They all discuss, decide and develop a solution but don’t bother to document. So how to get someone to write technical stuffs?</p><p>The first thing would be highlighting the importance of technical writing and talking about its basic form. Many people are confused about what the technical writing is and yes, that is a separate topic to talk. As the people are overthinking about the standards and practices to be followed in technical writing, giving a basic training could also help.</p><p>You can start the practice of writing in your team with a member who is good at writing. Don’t assign him/her any other tasks than writing so that s/he gets enough time to organize the thoughts, ideas and the content before actually writing. Writing about the product whole team is working on is not an easy task and it needs collaboration from all the team members. No need to think about much details or formats and list of basic things that need to be covered is enough for initial stage of writing.</p><p>Encourage or enforce everyone in the team to communicate the problems and solutions in written form rather than through verbal communication. That change makes everyone comfortable in writing technical stuffs. And next time give that honor of writing to another member. After couple of months, there will be enough people ready to write and explain what they do and how they do.</p><p><strong>Kickstarter</strong></p><p>In my opinion, incident of some bug fixing could be the candidate topic to give it a go. The next important task after fixing the bug could be writing its details which can be helpful in case of similar issues. Couple of questions to be answered are,</p><ul><li>What was the actual problem, was it happening for all users only some user specific? How big was the impact?</li><li>Was it only about some features breaking or something unintended was happening?</li><li>How did it get missed while testing?</li><li>What was the fix for it? Was it proper fix or hack? Does it need any further work?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bf3664496cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s the problem you want to solve?!]]></title>
            <link>https://medium.com/@ritushishir/whats-the-problem-you-want-to-solve-43f3c2072681?source=rss-7fdb6eb24ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/43f3c2072681</guid>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Shishir Paudyal]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 16:40:27 GMT</pubDate>
            <atom:updated>2017-02-27T16:40:27.249Z</atom:updated>
            <content:encoded><![CDATA[<p>How often are you able to state the exact problem you are trying to solve by building a product or adding a feature?</p><p>‘Do you guys know the problem you guys are trying to solve?’ when someone asked to my team, we didn’t know how to answer that question. Of course, the simple answer at that time was ‘of course, we do’ but later I realized something different. Though we were fully aware of the value added by the work we were doing it was little difficult to describe the problem we are trying to solve.</p><p>Then I started seeing the point of asking one simple question every time we talk about building a new feature — what problem is it going to solve?</p><p>Like in some other fields, the software development can also be explained in terms of the problem we are trying to solve. Every products or every features in a product are intended to solve some specific problem and defining them is the best way of marketing of that product.</p><p>Defining the problem helps us prioritize different tasks we do. The thing that solves the biggest problem tops the list of things that need to be done. Other things with lesser problems can wait for some time.</p><p>While thinking in terms of problem at hand encourages you to think of many alternative solutions rather than focusing on the idea/feature at hand. Defining the problem can be used iteratively as a means of collecting requirements more clearly and validating the solution you are trying to implement. Be sure that you are not trying to solve the problem that doesn’t even exist.</p><p>When features get directly associated with the problems it becomes apparent that how successful the feature is. As a developer when I see the features I worked on are in action and making things easier for other people then I can feel a sense of accomplishments. And that keeps me motivated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43f3c2072681" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>