<?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 Manu Gupta on Medium]]></title>
        <description><![CDATA[Stories by Manu Gupta on Medium]]></description>
        <link>https://medium.com/@manugupt1?source=rss-3b9282d50923------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8iCYCy6ah7swjKj4.jpg</url>
            <title>Stories by Manu Gupta on Medium</title>
            <link>https://medium.com/@manugupt1?source=rss-3b9282d50923------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:00:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@manugupt1/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[Bits of tracing!!!]]></title>
            <link>https://medium.com/@manugupt1/bits-of-tracing-81697d7d2833?source=rss-3b9282d50923------2</link>
            <guid isPermaLink="false">https://medium.com/p/81697d7d2833</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Manu Gupta]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 19:08:26 GMT</pubDate>
            <atom:updated>2018-10-03T19:08:26.796Z</atom:updated>
            <content:encoded><![CDATA[<p>This week we were able to get tracing making our first steps towards observability in the <a href="https://github.com/gomods/athens">Athens Proxy server</a>. We intend to use tracing to:</p><p>A) Help new contributors understand critical code paths to get an idea of how proxy works.<br>B) Debug latency issues for production systems and fix performance bugs in our code.<br>C) See how the proxy interacts with user requests.</p><p>To try out tracing, we have a walk through that that you can use with a local development instance. The docs are at :</p><p><a href="https://docs.gomods.io/faq/">FAQ</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*tq9OTfsyOuQGLiEfA0P_Ng.png" /><figcaption>Let’s talk about observability in Athens!</figcaption></figure><p>Right now, the support for tracing is limited to the <a href="https://www.jaegertracing.io/">Jaeger exporter</a> and if you have a different exporter, feel free to <a href="https://github.com/gomods/athens/pulls">submit a PR</a> or <a href="https://github.com/gomods/issues">open an issue</a>. We use <a href="https://opencensus.io/">OpenCensus</a> as our library to collect metrics and tracing exports.</p><p>If you are looking forward to contribute to Athens and improve our observability (or anything else!), you can pick an issue from GitHub right <a href="https://github.com/gomods/athens/issues">over here</a>.</p><p>We hangout at in the #athens channel on the <a href="http://gophers.slack.com/">Gophers slack channel</a>. We look forward to waving us over here.</p><p>Our weekly development meetings are held at every Thursday @ 11am US Pacific Time. You can catch up with what we have been <a href="https://docs.google.com/document/d/1xpvgmR1Fq4iy1j975Tb4H_XjeXUQUOAvn0FximUzvIk/edit#heading=h.wq93w35iaia">doing in our meeting minutes here(psst! we have screencasts in the docs also)</a>. Join us at our next meeting by <a href="https://zoom.us/j/193797787">using this link</a>.</p><p>Until then!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81697d7d2833" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attending my first ProductCamp@Portland]]></title>
            <link>https://medium.com/@manugupt1/attending-my-first-productcamp-portland-194e5b604523?source=rss-3b9282d50923------2</link>
            <guid isPermaLink="false">https://medium.com/p/194e5b604523</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-camp]]></category>
            <dc:creator><![CDATA[Manu Gupta]]></dc:creator>
            <pubDate>Tue, 31 May 2016 20:46:11 GMT</pubDate>
            <atom:updated>2016-05-31T20:46:11.855Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>I attended my first Product Camp at Portland (an amazing town with great people, food and music). As someone who has not been (and is not) a product manager, my trip was very focused on what product managers do, how the role was defined and what their daily lives looked like. I have read a lot of books, articles etc, however, I had not met a lot of product people. So, on a whim (literally), I decided to visit the beautiful city of Portland, and attend my first ProductCamp.</p><p>Being at a ProductCamp was fun because it is the real deal. We have a lot of blogs are centered around great communication skills for product managers, and they are all fun to read. A lot of blog posts have been centered around great communication skills, and how as a product manager you won’t really build anything, tools for prioritizing your work flow, customer journey etc. and provide a lot of background information for product managers. But readings are one-way lane and we rarely get a chance to converse back, share our thoughts and enrich the communicators’ thought process. ProductCamps open the door for these conversations.</p><p>Being with the community made me realize that a product manager has to evolve continuously, and a product camp helps him / her to add new tool kits in arsenal. In many ways, ProductCamp Portland also served as a therapy session for product managers. Almost every product manager had a story to tell. These stories helped everyone to understand each other’s perspective. Off course, ProductCamp is not only for product managers but also others, and how they can work together with each other. Attendees with sales, ux or software experience were talking to other product people to figure out better ways of collaboration. This was single-handedly the most useful experience for me.</p><p>For me ProductCamp was all about learning, sharing, and an amazing way to build relationships that can go a long way in one’s professional career. Thanks to the amazing people ProductCamp organizers, I was able to give a talk at the ProductCamp. I was initially doubtful and was not even sure if my presentation will be useful or not. I sent a short bio to the organizers. They told me that I should just go ahead and submit it, as there was no harm in doing so, and I did exactly that. To my surprise, I was also accepted. What I realized was, that everyone in the room was willing to contribute and learn. There are really no presentations at ProductCamp, people attend to share experiences, and tools that will encourage them to become better product managers. I think it was Mike Lonergan posted a talk on the morning of ProductCamp, and he presented as well.</p><p>His topic was ‘Failure is an option’, but the interesting thing that it if everyone felt that this was a topic they can relate to, then it provided an open forum for the presenter and also the attendees to talk about it, discuss it, and build better ways of solving the problems they do. So, do not hesitate at all, just go ahead submit a proposal, and see if you can get a chance to talk about it. Even it was not accepted, there is always room for hallway conversations with product managers who are not necessarily in your work. I am really looking forward to my next ProductCamp (and if possible visit Portland again). I hope to meet some of you at some point at a ProductCamp somewhere, sharing your experiences.</p><p>Product Camp was one of the best experiences is my life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=194e5b604523" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying behaviors in constrained social systems]]></title>
            <link>https://medium.com/@manugupt1/identifying-behaviors-in-constrained-social-systems-bd25272f3334?source=rss-3b9282d50923------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd25272f3334</guid>
            <dc:creator><![CDATA[Manu Gupta]]></dc:creator>
            <pubDate>Mon, 07 Mar 2016 11:56:00 GMT</pubDate>
            <atom:updated>2016-03-07T11:56:00.912Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Identifying group behaviors is a challenge in social computing system. Unlike, individual systems, interactions in social systems create tribes. As tribes grow, they also take charge of social norms and evolve the foundations on which the system was built upon. For instance YikYak, an anonymous social platform defines itself as “ Yik Yak makes the world feel small again by giving you a feed of all the casual, relatable, heartfelt and silly things people are saying around you.” However, it is also clear distinct dynamics arise between different groups. Undergraduate students at the University of Michigan view it as a way to get support. On the other hand, older populations identify it as an obnoxious tool which can promote negative behavior. While these group dynamics are beyond a designer’s control, it is certainly possible to identify the constraints and how we can tune our systems around those constraints to define individual and group dynamics. Social systems can be designed by observing people’s daily habits and where they are constrained. Typically, people want to start a new habit, maintain a habit, stop a habit, increase activity of a habit, and decrease activity of a habit. To achieve any one of these, people will make trade off under certain constraints. Some of these constraints are time, money, physical effort, mental effort and how far is this particular behavior from social norms. Also, when someone follows a habit, he is usually motivated by the outcomes. Outcomes can be rewards, achievements, reducing guilt, reducing regret, reducing fear, charity, pleasure, fun and many others. As designers, I believe we have to build systems that map desires and outcomes that are satisfiable. These facilitators will form a foundation for our social systems and how they can work for certain tribes or groups.</p><p>I wanted to know as a designer what can facilitate habit formations for groups under constraints. User research tools like participatory design, critical thinking are excellent research tools for people to go back to an experience and describe it using artifacts. As such, these design methods are limited only by the expressive power of the participant and the designer’s choice of artifacts. They are successful in bringing out the emotions about previous experiences in ways that can be put back into the products that we build.</p><p>To understand these behaviors I designed my own UX research tool. When I was designing this tool, I had these questions in mind</p><ol><li>How do people make decisions when they are constrained by resources?</li><li>How do people make decisions when they are presented with limited choices and are constrained by resources?</li><li>What kind of information will invoke attention and motivation to change behavior?</li><li>How can we demonstrate people crowd source solutions work?(I was really curious to see how a platform like Fold.it can solve big science problems?)</li></ol><p>After the conducting the observations, several important observations were made.</p><ol><li>Given a range of choices, people do not make the most rational choice, but the best choice they felt. This implies as designers we should never design for the optimal or the most rational solution.</li><li>People do not feel comfortable in using other’s solutions until they were confident enough that other’s solution were right. Once they are confident, they might choose a solution that had taken a wrong turn.</li><li>People do not value facts, rather they value information that can potentially lead to a personal gain for them or avert a loss.</li></ol><p>In the next blog post, I will write in detail about the UX research tool, so that it is available for critique.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd25272f3334" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>