<?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 Bibek Kc on Medium]]></title>
        <description><![CDATA[Stories by Bibek Kc on Medium]]></description>
        <link>https://medium.com/@bibekkc125?source=rss-97a1f2791493------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*30rX-57H-etV-TUFDjlNGg.jpeg</url>
            <title>Stories by Bibek Kc on Medium</title>
            <link>https://medium.com/@bibekkc125?source=rss-97a1f2791493------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:17:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bibekkc125/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[Case study: My experience in designing a photography service and camera renting mobile platform]]></title>
            <link>https://medium.com/design-bootcamp/my-experience-on-designing-a-photography-service-and-camera-renting-mobile-platform-b9d13e7d6c4d?source=rss-97a1f2791493------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9d13e7d6c4d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Bibek Kc]]></dc:creator>
            <pubDate>Thu, 29 Apr 2021 06:53:33 GMT</pubDate>
            <atom:updated>2021-04-30T02:52:36.875Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photography service and camera renting mobile app screens" src="https://cdn-images-1.medium.com/max/1024/1*qmXBYD1Rc5FIVkXPkpELGQ.png" /><figcaption>DSLR Sewa (Photography service and camera renting platform)</figcaption></figure><p>Recently, I posted a UX design case study on camera renting and photography service platform on <a href="https://www.behance.net/gallery/115200625/DSLR-Sewa-Case-Study">Behance</a>.</p><p>I wanted to share my experience and lessons that I learned during each phases of the design process. Before I jump off to the design process itself, let’s first talk about the elephant in the room, which happens to be client requirements for most client based projects.</p><h3><strong>Client’s Requirements</strong></h3><p>The client wanted to develop a mobile app where users could book for photography services, rent photography as well as videography equipments and studios could hire photographers/videographers based on their project needs.</p><p>Basically, the client wanted to digitize the conventional process of renting equipments and booking photography services.</p><p><strong>What I did: </strong>I conducted a meeting with a client where I discussed about the requirements and tasks needed to be done from my side.</p><p><strong>What I expected: </strong>A list of clear requirements indicating the things that needs to be done from my side.</p><p><strong>What happened:</strong> First of all the client had a lot of ideas which were not achievable in the current timeline. So I discussed with the client to breakdown project requirements into <a href="https://www.indeed.com/career-advice/career-development/smart-goals">SMART goals</a>. Then, I assigned higher priority to the goals that had most impact and least to the ones having lesser impact on the business.</p><p><strong>What I learned:</strong> Not all requirements are specified at the beginning of the project, so you need to adopt a flexible process that welcomes requirements during any phase of design.</p><p>Now let’s jump to the design process itself. As with most of the UX based projects, I followed the same <a href="https://mitsloan.mit.edu/ideas-made-to-matter/design-thinking-explained">design thinking</a> process of solving problem.</p><figure><img alt="Design thinking process" src="https://cdn-images-1.medium.com/max/1024/1*33khN9zpFCMWnF8pLqeVTQ.png" /><figcaption>Design thinking process</figcaption></figure><h3><strong>Empathize</strong></h3><p>The main idea is to understand user’s pain points and frustrations to create better solution of the problem.</p><p><strong>What I did:</strong> Due to COVID-19, I wasn’t able to adopt contextual inquiry or ethnographic observations(which I believe are much more accurate in identifying user’s pain points), so I created a survey and sent it out to the users which I thought could be the target audience for this platform. Also, I conducted 1 on 1 interviews with the users to have a better insight of the problems that they were facing.</p><p><strong>What I learned: </strong>Surveys are used to collect large number of data and they give us quick insight about user needs and opinions whereas interviews are much more detailed and provide much more context about users pain points if right target audience are involved.</p><p>Bear in mind that, there is a difference in what people actually feel and what people say about the product. So, user interviews sometimes tend to be biased. In that case, ethnographic observations and contextual inquiries can prove to be useful in identifying audience needs and pain points.</p><h3><strong>Define</strong></h3><p>The main goal is to map the data from user research into presentable personas, journey maps, empathy maps and storyboards, so that it helps in better communication with the team, stakeholders and project managers.</p><figure><img alt="User persona created during design thinking process" src="https://cdn-images-1.medium.com/max/1024/1*w3dDdYFh0zJ81bR7ROprTg.png" /><figcaption>User persona</figcaption></figure><p><strong>What I did:</strong> I translated the results from user interviews into user personas. User journey maps were not created due to lack of active users using competitor products.</p><p><strong>What I learned: </strong>Creation of personas, journey maps, empathy maps and story boards all depends upon your project scope, timeline and budget. Each of these deliverables serve a different purpose and it’s up to you to choose the right ones that help define user’s pain points.</p><p>Some people prefer user interviews and map the results into personas. While some prefer mapping results from contextual inquiry or ethnographic observations into empathy maps because they might find the data to be accurate.</p><h3><strong>Ideate</strong></h3><p>In this phase, all the possible solutions are listed down and later narrowed down to fit the project scope.</p><p><strong>What I did:</strong> I started by brainstorming all the possible ideas and wrote them down. Then I created a sitemap to better understand the overall project structure. Slowly I started connecting all the bits and pieces by creating a user flow while aligning my ideas to the project scope.</p><p><strong>What happened:</strong> While creating user flow and sitemaps, at some point I didn’t have enough information to connect the missing pieces. Also, I missed out on testing my sitemap and user flow with appropriate audience.</p><p><strong>What I learned:</strong> It’s totally fine if you don’t have enough information while creating sitemaps or user flows. The missing information gaps could be filled by discussing with the team, project manager and the stakeholders. Even then, some information still remains to be explored for most cases.</p><p>Remember earlier I mentioned about adopting a flexible design process, well if you have enough information to step forward, you could move on towards testing your sitemaps and user flow using techniques such as: tree testing or task based approach and then return back to update your existing user flow or a sitemap.</p><h3>Prototype</h3><p>In this phase, wireframes and mockups are created with continuous iteration to adapt to project needs.</p><figure><img alt="Low fidelity wireframes of camera renting mobile app" src="https://cdn-images-1.medium.com/max/1024/1*MEcvdDPFs5hB9DyqsWNVeg.png" /><figcaption>Wireframes</figcaption></figure><p><strong>What I did:</strong> At first, I created low fidelity wireframes using pencil and paper to portray the main ideas of the product. Then I moved on to high-fidelity prototype to better represent the wireframes and present it to the client. While I didn’t create any mid-fidelity prototype due to the project timeline, I was continuously creating components and styles for typography, colors, grids in parallel with high-fidelity prototype.</p><p><strong>What happened:</strong> When I presented high-fidelity prototype to the client, the client asked for a bunch of new features to be incorporated within the existing project.</p><p><strong>What I learned:</strong> The wireframes should be tested with the client as well as target audience to minimize re-iteration of high-fidelity prototype which is costly in terms of effort and time. Mid-fidelity prototype must be created to make the functionality of product clear between designer, stakeholder/client and the team.</p><p>Don’t rush towards creating a final high-fidelity prototype. Instead focus on solving problems and minimizing design iterations while the prototype translates from low, mid to high fidelity. Also, try to create components and styles in parallel with the UI. This will save you a lot of time while creating style guide, pattern library or a design system.</p><h3>Test</h3><p>In this phase, complete product is tested with target users and adjustments are made based on the user feedback.</p><p><strong>What I did:</strong> I wasn’t able to test the product with users because of the project timeline and budget.</p><p><strong>What I learned:</strong> Testing the product with target users gives valuable insights which helps to enhance the usability of the product. Continuous testing and iteration helps to build a product that’s best for both the users and business.</p><h3><strong>Key Takeaways</strong></h3><p>Here are some of the things that I’ve learned from this project:</p><ul><li>Adopt a flexible and iterative design process that welcomes change in every phase.</li><li>Address most of the design decisions during wire-framing phase(less cost) to minimize re-iteration during mid and high fidelity prototyping phase(more cost).</li><li>Creation of components, styles must be in parallel with the UI to reduce work, develop design system and create consistency across the design.</li><li>Continuous testing and iteration based on user feedback helps develop a product that satisfies both the user needs and business.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9d13e7d6c4d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/my-experience-on-designing-a-photography-service-and-camera-renting-mobile-platform-b9d13e7d6c4d">Case study: My experience in designing a photography service and camera renting mobile platform</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating through commits in Git]]></title>
            <link>https://bibekkc125.medium.com/navigating-through-commits-in-git-a613d533ffe?source=rss-97a1f2791493------2</link>
            <guid isPermaLink="false">https://medium.com/p/a613d533ffe</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[git-commit]]></category>
            <category><![CDATA[gitflow]]></category>
            <dc:creator><![CDATA[Bibek Kc]]></dc:creator>
            <pubDate>Thu, 07 May 2020 10:42:37 GMT</pubDate>
            <atom:updated>2020-05-07T10:42:37.000Z</atom:updated>
            <content:encoded><![CDATA[<p>As a front-end developer, I’ve found myself quite difficult to navigate between commits while working in projects. So, I’m going to discuss 3 different ways to navigate to a particular commit in Git.</p><ol><li>Using (~) tilde operator</li><li>Using (^) operator</li><li>Using &lt;commit&gt;</li></ol><p>Let’s consider a scenario where we have 3 different branches each pointing to different commits as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/1*uwgjSdzyKDQG9gd9DdZh3Q.png" /><figcaption>Git commit history</figcaption></figure><p>Say for example, we are working on a new feature, so we have created a feature branch. In this case, <strong>HEAD</strong> currently points to feature branch.</p><p><strong>You might be wondering what HEAD is?</strong></p><p><strong>HEAD</strong> is simply a pointer that points to local branch that you are working on.</p><p>Now let us assume that, we made some experimental changes in commits <strong>‘g’ </strong>and <strong>‘h’. </strong>So, we want to get to commit <strong>f</strong> to see the state before we have made experimental changes so that the commit history looks somewhat like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*T13E5Gbq8G4pmjrbsGurng.png" /><figcaption>HEAD pointing to commit ‘f’</figcaption></figure><h3>Using (~) tilde operator</h3><pre>git checkout HEAD~2   </pre><p>The number 2 after (~) operator means 2 steps backward from current <strong>HEAD</strong> position. If we do not provide number after (~) operator then git will navigate to previous commit.</p><h3>Using (^) operator</h3><pre>git checkout HEAD^^</pre><p>The operator (^) helps to navigate to previous commit one at a time. In this case, 2 (^) operators after <strong>HEAD</strong> means two commits backwards from current <strong>HEAD</strong> position.</p><p><strong><em>Note:</em></strong><em> Unlike (~) tilde operator, (^) operator does not have number as an argument.</em></p><h3>Using &lt;commit&gt;</h3><pre>git checkout f</pre><p>The above command would simply put the <strong>HEAD</strong> pointer to point commit <strong>‘f’</strong>.</p><p>After checking out on a commit you may see a message somewhat like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10bt_3mhc_KxX8G-poH4RQ.png" /><figcaption>Detached HEAD state</figcaption></figure><p>Detached HEAD means HEAD now points to commit rather than local branch.</p><p>Now, you can move around commits easily using these techniques.</p><h3><strong>Bonus Tip</strong></h3><p><strong>What if you have a merge commit (commit with more than one parent commits)?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*Afz9AWv-ofqGjSmqQM-wjQ.png" /></figure><p>Since our HEAD points to commit <strong>‘i’ </strong>or develop branch,</p><pre>git checkout HEAD^<br>------- or --------<br>git checkout HEAD~</pre><p>This command would point to the previous commit (i.e commit <strong>‘e’</strong>). We can navigate to commit <strong>‘h’</strong> using,</p><pre>git checkout HEAD^2</pre><blockquote>In case of commits with multiple parent commits, we can navigate between parent commits using <strong>^</strong> followed by number.</blockquote><p>Now you can combine these techniques to navigate back and forth between commits.</p><pre>git checkout HEAD^2~2^^</pre><p>The above code shifts HEAD to commit <strong>‘a’</strong>, which is equivalent to:</p><pre>git checkout HEAD^2<br>git checkout HEAD~2<br>git checkout HEAD^^</pre><pre>-------- or --------</pre><pre>git checkout a</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a613d533ffe" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>