<?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 Balaji Prasad on Medium]]></title>
        <description><![CDATA[Stories by Balaji Prasad on Medium]]></description>
        <link>https://medium.com/@balajiprasad?source=rss-3018fccf28b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4mE521DQ-nqroju-9DO2BQ@2x.jpeg</url>
            <title>Stories by Balaji Prasad on Medium</title>
            <link>https://medium.com/@balajiprasad?source=rss-3018fccf28b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:38:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@balajiprasad/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[How to be a Top-Ranked Event on Townscript?]]></title>
            <link>https://medium.com/townscript-product/how-to-be-a-top-ranked-event-on-townscript-29d2792d1ff7?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/29d2792d1ff7</guid>
            <category><![CDATA[events]]></category>
            <category><![CDATA[event-organizer]]></category>
            <category><![CDATA[event-planning]]></category>
            <category><![CDATA[event-marketing]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Mon, 23 Dec 2019 12:16:19 GMT</pubDate>
            <atom:updated>2019-12-23T12:25:00.705Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Why is my event not visible at the top?”</h4><p>tl;dr: “If your event looks good and is doing well, it will automatically come out at the top!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iu6-cGb4KpEzyd7djVI3lw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@austris_a?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Austris Augusts</a> on <a href="https://unsplash.com/s/photos/numbers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It’s totally in your hands to be a top-ranked event on the listing and home pages. Here’s the high-level gist of the algorithm we use to compute your event’s rank score.</p><p>We compute scores of all live events on our platform once in every 24 hours. The better the rank of an event, the better it’s position will be on listings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*Zu3MJgoNsh8C9aCAgHzzfQ.jpeg" /></figure><ol><li><strong>Good Content:</strong> Some of the organizers do not fill out all the information fields. It is crucial to have good images, name and description filled out. Events that do not have images or descriptions will not be shown at the top.</li><li><strong>Pageviews:</strong> The more page views your event has, the better it gets. There might be different sources of page views — social media sharing, organic clicks, clicks from listing pages, from emails etc. You need to do all the things possible to make your event go wide.</li><li><strong>Tickets Sold:</strong> Number of tickets also sold matters. If people are buying your event, that means it deserves to be in a better position.</li><li><strong>Rate of Tickets Sold:</strong> There might be events which have a massive number of tickets and others comparatively small. Therefore, relying only on the tickets sold parameter will not be fair. Here’s where the rate of tickets sold will come into the picture — the average number of tickets sold in the last seven days.</li><li><strong>Event Proximity:</strong> The closer your event end date, the more we push your event :)</li></ol><p>This is just a sneak-peak of our approach. It has more stuff going on under the hood, and it will get better and smarter with more data and will include parameters like content quality, organizer score (history) etc. in the near future.</p><p>We aim to help organizers (who want to sell tickets) and users (who want to find better events) as well in the best possible way to reach their goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29d2792d1ff7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/townscript-product/how-to-be-a-top-ranked-event-on-townscript-29d2792d1ff7">How to be a Top-Ranked Event on Townscript?</a> was originally published in <a href="https://medium.com/townscript-product">Townscript Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Realization of a Wrong-doing After Becoming Product Manager]]></title>
            <link>https://medium.com/townscript-product/realization-of-a-wrong-doing-after-becoming-product-manager-650fc8ff5ea2?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/650fc8ff5ea2</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Wed, 09 Oct 2019 08:31:51 GMT</pubDate>
            <atom:updated>2019-10-09T08:31:51.632Z</atom:updated>
            <content:encoded><![CDATA[<h3>Realization of a Wrong-Doing After Becoming Product Manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoEr7Pn4_WP_i6Sw7WcYsg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@fodelwdc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Fares Hamouche</a> on <a href="https://unsplash.com/s/photos/mirror?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>To tell you an interesting anecdote of mine, you need to know a little bit of me. I was a developer for four years before turning into PM around one and half month ago. As a developer, I used to think more about the “solution” instead of thinking about the “problem”. I do not intend or imply to say that all developers are the same, maybe it’s just me. After becoming PM, I have started to look at things from a different perspective.</p><blockquote>“It isn’t that they cannot find the solution. It is that they cannot see the problem.” — G.K Chesterton</blockquote><p>Recently I was researching a feature in my PM track. Interestingly two years ago in 2017, I worked on this same feature as a developer. The solution implemented back then was also brainstormed by me.</p><p>About the feature — We, at Townscript, have a web module for check-in and print badge .i.e a software for “on event day” execution. A lot of organizers from different verticals use this software — Marathons, conferences, workshops etc. UI/UX of this application is pretty simple and has limited features so that the module is straightforward to be used for.</p><p>Organizers of marathons requested a feature using which they can collect the information of the person who is collecting goodies on behalf of someone else. For example, let’s say Romeo and Juliet are going to run for Satara Hill Marathon. Both of them need to go to Bib expo before the event and collect their bibs and goodies. Juliet is unavailable on the day of bib expo, and she has asked Romeo to do it on behalf of her. Now, when Romeo goes and collects goodies and bib of Juliet, the system needs to record that Romeo has collected Juliet’s things. We need a way to do this.</p><p>About the solution implemented — Three actions can be performed on every attendee using our check-in application: i) Check-in the attendee, ii) edit the details of the attendee and iii) print badge for the attendee.</p><p>We have built a new feature called “form questions for on-ground” to solve the problem. Organizers will create form questions say “Bib collector’s name”, “Collector’s phone” etc. from their event dashboard. These questions will not be shown in online booking flow form but only in check-in module’s edit details flow.</p><p>So the implemented flow in this scenario would be — the person sitting at the check-in desk would click on edit attendee first, enter the collector’s details and save. Then he would click on the check-in attendee action and check-in the attendee.</p><p>Do you notice any problem here?</p><p>This problem can be solved in a much simpler way without the need of on-ground question feature. What could have been done is — add “check-in remarks” text area field in check-in attendee action. This field will be optional and will be shown for all events of all organizers. No need for organizers to create any new questions. Also, now person sitting at the check-in desk needs to click on one action -&gt; check-in the attendee -&gt; enter check-in remarks if required (collector’s name/phone etc.) and check-in the attendee. That’s it!! It’s that simple :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*XNVDkRwQ56027bTZ2uypBQ.jpeg" /><figcaption>Solutions comparison</figcaption></figure><p>Even some of you might have stories similar to this where a problem can be solved in a much simpler way but ended up in creating unnecessary complex features like the above “form questions for on-ground”. Do share about them with me in the comments section :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=650fc8ff5ea2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/townscript-product/realization-of-a-wrong-doing-after-becoming-product-manager-650fc8ff5ea2">Realization of a Wrong-doing After Becoming Product Manager</a> was originally published in <a href="https://medium.com/townscript-product">Townscript Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveraging Customer Messaging Platform to Understand Product Pain-points]]></title>
            <link>https://medium.com/townscript-product/leveraging-customer-messaging-platform-to-understand-product-pain-points-f8396b604359?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8396b604359</guid>
            <category><![CDATA[user-behavior]]></category>
            <category><![CDATA[user-study]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 07:10:10 GMT</pubDate>
            <atom:updated>2019-08-21T09:51:27.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dc4MttY-d9z1JrllzpefEw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@simplicity?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marija Zaric</a> on <a href="https://unsplash.com/search/photos/customer-text?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>All of us are continually striving to understand user behavior and solve their pain-points. While there are many ways to do this — user studies, interviews, design sprints etc. — The messaging platform which our support teams use to talk to customers can also be a great tool to analyze user behavior. It just requires some patience initially to go through all the conversations and a need for a standard process to make it sorted for future (Hint — automation) :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*aIa-VcHM8U0pQbHBrjupFw.png" /><figcaption>Example chat application</figcaption></figure><p>We, at Townscript, use <a href="https://www.google.com/aclk?sa=l&amp;ai=DChcSEwir5Y7W6YHkAhXYhHAKHf9ICaAYABAAGgJzYg&amp;sig=AOD64_0ylGcibWxyQ0wtqH7-d7HncUlhQg&amp;q=&amp;ved=2ahUKEwiAlojW6YHkAhUShuYKHbFPCtMQ0Qx6BAgQEAE&amp;adurl=">Intercom </a>for customer messaging. It has been embedded in our user Dashboard .i.e. logged-in users can talk to our support team round the clock using Intercom.</p><p>To start off, I have read all the conversations in our Intercom of the past three months (1000+ conversations). As all the conversations will not be useful in the product perspective, I have documented all the pain-points/queries related to product told by users in Excel sheet.</p><p>After gathering more than a sufficient number of data points in the sheet, I have tried to categorize the messages in broad buckets. What I understood is generally when a high priority bug creeps into the system, there is a low probability that customers intimate team on Messaging platform. She/He will immediately escalate the situation on call/email or the worst-case social media :D</p><p>Coming back to broad buckets, here are three major categories which I figured out:</p><p><strong>Bug:</strong> As pointed above, there are not many data points present in this bucket.</p><p><strong>Feature Unclear:</strong> Customer conversations can be a gold mine to analyze if users are really understanding and using the features we build as they are supposed to be. Interestingly, there are a lot of questions and doubts raised by customers, which lead to considerable time waste of support team.</p><p>Example: At Townscript, we have built a robust KYC system for Organizers to ensure no fraudulent Events are happening on the platform. A new organizer who has filled her KYC details will naturally be eager to know when will the KYC status change to “VERIFIED”.<br> <br>Almost 95% per cent of new organizers after filling KYC details would immediately message support team on Intercom asking when will the status change. The standard response of the team would be “Please wait for 24–48 hours for the status to change”.</p><p>A simple way to avoid all these conversations and anxiety of organizers is to communicate the above message as part of the KYC flow itself. We could simply show the, “please wait for 24–48 hours” message after users submit their KYC details.</p><p><strong>New feature request:</strong> Some times, our customers come up with genuine pain from their side, which can lead to a useful feature building.</p><p>Example: At Townscript, we want organizers to create events in a hassle-free manner without any confusion at all. This is one of the most critical funnels for us. To make this experience easier for organizers, we have deliberately let go off some features as part of Event Creation. Though these features are present once the event is created.<br> <br>One such feature which we did not include in Event Creation is “Edit Ticket” .i.e. Organizer will not be able to edit the details of the ticket(s) she has created during event creation. Sometimes, organizers make mistakes (After all, they are humans just like us) and would want to modify ticket details. Since new organizers do not know that they can do these modifications after event creation, they panic and immediately message support on Intercom asking what to do now :) The organizer is now stuck and that too in the most crucial funnel — Event Creation!</p><p>We are launching Edit Ticket in Event Creation very soon.</p><p>Here is the summary pie-chart of the gathered data points :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kFnep0iKGZ5VXYH6DTXPcg.png" /></figure><p>Some bonus tips for Intercom users : <br>1. <strong>Automation -&gt; Tag messages: </strong>Intercom has a feature of tagging messages. We have created the above categories as tags, additionally support team is free to use feature tags too (For example — event creation, KYC flow etc.) Intercom has API’s which can be used to fetch tagged conversations and all the details associated with it. <br>We are building a feature for our internal team purpose, where we can view all the tagged conversations with the date and feature filters.</p><p>Exclusive sneak peek:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXF0PBzk0LQ33eiCWQYoLg.png" /><figcaption>Viewing organizers who have tagged conversations</figcaption></figure><p><strong>2. Reducing pricing: </strong>Intercom has a feature called — “Archive user”. When a user is archived, he will not count towards billing of that month. Intercom charges are based on the average number of users (.i.e. organizers in our case). <br>When an organizer signs up on Townscript, his object is created on Intercom also (with bare minimum details — no privacy compromise here). But not all these users message on Intercom, also some of them do not log in more than twice too. So based on the number of their “sessions”, these inactive number of users can be archived (Intercom has API to do this) regularly. This can help in reducing the billing amount.</p><h4>What Next</h4><p>We are going to monitor intercom tagged conversations regularly, which will be useful for a better understanding of our product and organizers too. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8396b604359" width="1" height="1" alt=""><hr><p><a href="https://medium.com/townscript-product/leveraging-customer-messaging-platform-to-understand-product-pain-points-f8396b604359">Leveraging Customer Messaging Platform to Understand Product Pain-points</a> was originally published in <a href="https://medium.com/townscript-product">Townscript Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SEO Basics for Developers]]></title>
            <link>https://medium.com/@balajiprasad/seo-basics-for-developers-48870c982248?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/48870c982248</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[search-engine-optimizati]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Sun, 13 Aug 2017 08:21:01 GMT</pubDate>
            <atom:updated>2017-08-13T08:58:44.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Building web applications without being aware of SEO is like making a movie and releasing it without any marketing &amp; publicity. You might be a brilliant filmmaker but your effort will go in vain unless and until you are Christopher Nolan who doesn’t need to reach out to people. Similarly, your website will not have the right platform to project itself if the SEO part is not done right. Here is my 2 cents on the basics of SEO.</p><ol><li><strong>Sitemap &amp; Robots txt</strong></li></ol><p>Sitemap is like the routemap of your website. There are two kinds of sitemaps :</p><p>i) Sitemap XML : This is for search engine crawlers like Google and contains list of web pages of your website. Sitemap XML is where you can communicate with crawlers to tell them where all the links of your website are and what are their priority and change frequency. Example of a tag in sitemap -&gt;</p><pre>&lt;url&gt;<br>&lt;loc&gt;https://www.website.com/about-us&lt;/loc&gt;           &lt;changefreq&gt;weekly&lt;/changefreq&gt;<br>&lt;priority&gt;0.6&lt;/priority&gt;<br>&lt;/url&gt;</pre><p><a href="https://www.sitemaps.org/protocol.html">https://www.sitemaps.org/protocol.html</a> can be a good guide to follow while making a sitemap.</p><p>ii) Sitemap HTML : This is primarily for users who visit your website. Sometimes it can get confusing to find a specific page on your website and this is where Sitemap HTML can help your site visitors. You can list all the links which you think are important and can be helpful for your users in this page.</p><p><strong>Robots txt: </strong>This is a text file to instruct web robots typically search engine robots how to crawl pages on your website. You can mention directories/links of your website which you don’t to be crawled. You can also disallow certain bots from crawling your website.</p><pre>User-agent: [user-agent name]<br>Disallow: [URL string not to be crawled]</pre><p>2. <strong>Canonical Tag</strong></p><p>When you add parameters like utm to a link, it becomes a new URL which is crawlable. In this case, you might not want crawlers to crawl the link which has utm parameters. Also, it is certainly possible to have multiple URL’s which have same content and you want only one among those to be crawled by crawlers. There are two ways to do this -</p><ol><li>Add the links which should not be crawled to robots.txt file</li><li>Add canonical tag to the unwanted links and redirect crawlers to the link you want to be crawled</li></ol><p>The correct solution is to add canonical tag instead of adding URL’s to robots.txt. All the SEO juice your unwanted links are generating will be redirected to the link you want to be crawled. Here is how you add canonical tag -&gt;</p><pre>&lt;link rel=&quot;canonical&quot; href=&quot;http://example.com/wordpress/seo-plugin/&quot;&gt;</pre><p><strong>3. AMP</strong></p><p>AMP stands for Accelerated Mobile Pages. AMP is a way to build web pages that are lightweight and speedy to load, particularly on mobile devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*C-7UfNYT8g5tfUIIpMFp5Q.jpeg" /></figure><p>Notice the “AMP” text on the rich cards? This means that these links are AMP enabled and will load faster on your mobile. Thus, Google gives them priority over other links.</p><p>AMP HTML is entirely built on existing web technologies. It achieves reliable performance by restricting some parts of HTML, CSS and JavaScript. To make up for those limitations AMP HTML defines a set of custom elements for rich content beyond basic HTML.</p><p>AMP HTML documents MUST</p><p>i. start with the doctype &lt;!doctype html&gt;. <br>ii. contain a top-level &lt;html ⚡&gt; tag (&lt;html amp&gt; is accepted as well). <br>iii. contain &lt;head&gt; and &lt;body&gt; tags (They are optional in HTML). <br>iv.contain a &lt;link rel=”canonical” href=”$SOME_URL”&gt; tag inside their head that points to the regular HTML version of the AMP HTML document or to itself if no such HTML version exists. <br>v. contain a &lt;meta charset=”utf-8&quot;&gt; tag as the first child of their head tag. <br>vi. contain a &lt;meta name=”viewport” content=”width=device-width,minimum-scale=1&quot;&gt; tag inside their head tag. It’s also recommended to include initial-scale=1. <br>vii. contain a &lt;script async src=”<a href="https://cdn.ampproject.org/v0.js">https://cdn.ampproject.org/v0.js</a>&quot;&gt;&lt;/script&gt; tag inside their head tag. <br>viii. contain the AMP boilerplate code (head &gt; style[amp-boilerplate] and noscript &gt; style[amp-boilerplate]) in their head tag</p><p>Here is the reference link : <a href="https://www.ampproject.org/docs/getting-started/">https://www.ampproject.org/docs/getting-started/</a> if you would like to deep dive into AMP.</p><p><strong>4. Og-tags</strong></p><p>The Open Graph (Og) protocol enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook. The result of following this protocol is when you share your web page on let’s say Facebook, this is how it looks -&gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*8oUUlZ4CObDWC3IRRbuZ2A.png" /><figcaption>As I entered the URL on post, Facebook has read the og-tags and displayed rich card</figcaption></figure><p>To turn web pages into rich social graph objects, all you need to add is add &lt;meta&gt; tags in the &lt;head&gt; of your web page. Here are the four required og properties :</p><p>og:title — The title of your object as it should appear within the graph, e.g., “The Rock”.<br>og:type — The type of your object, e.g., “video.movie”. Depending on the type you specify, other properties may also be required.<br>og:image — An image URL which should represent your object within the graph.<br>og:url — The canonical URL of your object that will be used as its permanent ID in the graph, e.g., “<a href="http://www.imdb.com/title/tt0117500/">http://www.imdb.com/title/tt0117500/</a>&quot;.</p><p>There are various other og-properties which can be helpful to your website. Here is the link for reference — <a href="http://ogp.me/">http://ogp.me/</a></p><p>SEO should not be left as a Marketer’s forte and every developer should be equally responsibility in implementing SEO. In case you have any suggestions/comments on this post, do feel free to comment it out below :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48870c982248" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s New? (Android Style)]]></title>
            <link>https://medium.com/@balajiprasad/whats-new-android-style-ae7e09f5c32f?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae7e09f5c32f</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Sun, 11 Dec 2016 13:37:15 GMT</pubDate>
            <atom:updated>2016-12-13T04:55:11.317Z</atom:updated>
            <content:encoded><![CDATA[<p>While updating/releasing Android app on playstore, publisher has to write a small note for users which describes about the update being done. This is the “What’s New” section which can be seen on every app at playstore.</p><p>It’s been more than a year now of me being responsible for android apps at <a href="https://medium.com/u/3e38a19df9d2">Townscript</a>. Thanks to <a href="https://medium.com/u/bc44231f250d">Sachin Sharma</a>, I always had the free hand to write the “What’s New” section while updating the apps. No, I’m not saying thanks to him for allowing me to write but for always approving whatever I wrote :)</p><p>Let me share with you some “What’s New”’s I wrote. Shall we begin the show?</p><ol><li>What if Joker and Batman talked about Townscript?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*NKvqq3Jk3bzZTi4afdAgEA.png" /></figure><p>2. Probably, I can pitch this What’s New for a movie dialogue</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*9WMOTibtjCKVEPS5i6dbVA.png" /></figure><p>3. This is when I became senti about our user’s time</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*1q1oZ71SNZwe0hhTK8dWgQ.png" /></figure><p>4. This is when I showcased my lame side</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*E1PGP4eP1VWs2eRnWZNktw.png" /></figure><p>5. This is when I felt bad about our soldiers. RIP brave-hearts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*d1wgCv7MOxu997fKArHr4A.png" /></figure><p>Though this is not a What’s New, it’s the description I wrote for the Organizer app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*yzTxMry4DM-PssVFPeqyNg.png" /></figure><p>I don’t know how many people actually read this while browsing the apps, but this is a fun and exciting activity for me to exercise my writing skills. Looking forward for many more What’s New’s :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae7e09f5c32f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[101 on the Categories & Topics]]></title>
            <link>https://medium.com/townscript-product/a-101-on-the-categories-topics-466345330621?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/466345330621</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[event-organizer]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[event-planning]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Tue, 27 Sep 2016 12:11:11 GMT</pubDate>
            <atom:updated>2019-07-31T09:41:37.201Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OZ3DuzUkX9mc2HMdaVT8hA.jpeg" /></figure><p>I’m working on the most exciting feature of my career (Okay, it&#39;s not been too long-I’m just 1 and half year experienced) right now at <a href="https://medium.com/u/3e38a19df9d2">Townscript</a>. We are introducing categories and topics to our platform. It sounds very simple but there is a lot of work going on and changes are being done from the architecture level to UI level.</p><p>After a lot of brainstorming and keeping in mind our organizers and attendees behaviour, we came up with the below hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*MaU3a4fhAJsWnCY29jxZVg.png" /></figure><p>Every event will be assigned one category, maximum up to 3 topics and 1 event type. Category will be broad and the topic will be specific. For example, Entertainment will be a category and party, concert etc. will be its topics. There are some terms which cannot come under either category or topic. For example, terms like workshop, seminar etc. That is why we came up with the concept of the event type. Type captures the event organizing structure and topics capture event content.</p><p>While entering topics, organizer might not know the exact topic name which is present in our database. For instance, let&#39;s suppose an organizer is creating a marathon event. The correct topic for the event is marathon but he might be entering running or say sprinting as a topic. That’s why we came with the concept of keywords. Keywords will be synonyms of topics. Our code at backend will convert the keywords assigned by organizer to its respective topics.</p><p>There are 8000+ events right now in our database. The additional challenge here is to make and run an algorithm on these events for assigning appropriate category, topics and event type to them. **insert 1 week time here**. Algorithm done and with the help of it, we are able to identify and add missing topics and keywords to our database. Also thanks to the business team of Townscript for helping me in building the database. Finally, we are trying to make our database as comprehensive and rich as possible.</p><p>What will organizers gain with categories &amp; topics?</p><ul><li>Every category/topic/keyword will have a URL respectively. Hence, the overall SEO of Event will be enhanced.</li><li>It will be easy to find the target customers and promote the Event. For instance, a marathon organizer in Pune can send an emailer to the attendees who have attended marathon in Pune previously.</li></ul><p>What will attendees gain?</p><ul><li>Navigation on our website/app will become smooth and interest-driven. One can easily find the exact kind of events he/she is looking for.</li><li>Attendees can follow the topics they are interested in and get notified when any new event is created in that domain.</li></ul><p>What will Townscript gain?</p><ul><li>Whatever our attendees and organizers gained :)</li></ul><p>We are planning to release the first phase of categories &amp; topics in mid-October. This phase will include assigning topics and event type to the existing events in the database and giving organizer the provision to add/edit topics assigned to his events from the dashboard. Looks fun right?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=466345330621" width="1" height="1" alt=""><hr><p><a href="https://medium.com/townscript-product/a-101-on-the-categories-topics-466345330621">101 on the Categories &amp; Topics</a> was originally published in <a href="https://medium.com/townscript-product">Townscript Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 months at a Startup]]></title>
            <link>https://medium.com/townscript-product/6-months-at-a-startup-9b6ce21fdf9?source=rss-3018fccf28b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b6ce21fdf9</guid>
            <category><![CDATA[training]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Balaji Prasad]]></dc:creator>
            <pubDate>Mon, 29 Feb 2016 14:20:21 GMT</pubDate>
            <atom:updated>2019-07-31T09:36:18.041Z</atom:updated>
            <content:encoded><![CDATA[<p>February 27, 2016. I complete 6 months as a developer at a product based startup <a href="http://www.townscript.com/">Townscript</a> which is a do-it-yourself platform for event ticketing. These 6 months have been very eventful. I can confidently say that I have learned a lot and grown as a person. Let me rewind and share with you what happened in these 180 days.</p><p><strong>Training phase</strong></p><p>Being a fresher when I joined Townscript, I had to undergo training to get on-board. My training was a practical and self-driven program which encompassed the use of almost all the technologies used by the product team. There weren’t any theory or KT sessions. In the first hour of my first day, I was told clearly what to accomplish i.e. to build a To-do-list application from scratch. First I completed the backend REST-based application using Hibernate, Spring, log4j etc. and then made the UI based application using Angular JS and other front end technologies. I completed 11 courses on Codeshool to make myself comfortable with various technologies. Being a newbie I took around 45 days to complete the entire project. You can have a look at the <a href="https://github.com/balajiprasad1994/TodoListRest">back end application</a> and <a href="https://github.com/balajiprasad1994/TodoListUI">front end application </a>code.</p><p><strong>Android app</strong></p><p>After completing Todolist, I had to work on Townscript’s <a href="https://play.google.com/store/apps/details?id=com.dyulok.android.townscriptapp&amp;hl=en">Events android application</a>. It is a B2C app for customers to explore, discover and book tickets for happening events in the city. I knew little about android app development before working on this. I had to learn and implement stuff on the go. I also learned a bit of photoshop as most of the screen designs given to me were PSDs. Generally, freshers’ first production task is to fix bugs or write small parts of code in applications. I completed my first production task by developing a major part of the company’s Android app and publishing it on play store. I also had the free hand of writing <em>What’s new</em> section while publishing the app. Here is the latest <em>What’s new</em> I wrote for the recent update :</p><p><em>Joker: If you’re good at something, never do it for free.</em></p><p><em>Batman: Sorry Joker, Townscript is good at making your idle time awesome but it is free.</em></p><p>Though I don’t completely spend time on Android now, I manage the app work with another developer. Once decided, I discuss with him the tasks to be done and help in completing them. I feel like Product Manager for Android at times ;)</p><p><strong>Full-stack development</strong></p><p>Post coding for the app, I’m working on the dashboard revamp of Townscript. This is a huge and crucial task going on right now. We are writing new API’s, implementing new features and enhancing the existing ones. I’m writing API’s and integrating them as per the screen designs. I have worked on Android, now working on backend REST layer and also the front end. Thus justifying my role — Full stack developer :)</p><p><strong>Hiring</strong></p><p>As part of hiring an intern, I was given the responsibility of shortlisting resumes and taking interviews along with another developer. In last August, I was applying on AngelList for jobs at startups and within a few months, I was at the other side of the table. I was shortlisting the applications received on AngelList and other online job portals. I had a rich experience of attending 20+ tech startup interviews before joining Townscript. Overall I had a fair idea regarding what candidates are supposed to be asked in interviews. One hack I used was to ask the same good questions which were asked to me during my interviews.</p><p>I had the opportunity to attend Internship mela on behalf of Townscript along with <a href="https://medium.com/@99sachins">Sachin Sharma</a>, Founder. Students from colleges across Pune looking for internships attended this mela. In the span of 8 hours, we scanned 300+ resumes and took 100+ on the spot interviews. This is one experience I will never forget. Being a 21-year-old graduate, I was taking interviews of postgraduates and also people of my age. There were instances during that day when people thought I was a student volunteer instead of a company representative.</p><p><strong>Experience</strong></p><p>During the last November, team Townscript participated in fintech hackathon #heroesvshackers organized by Barclays which happened for 36 hours straight with a crowd of 300+ people. Though we did not win, it was a fun and memorable experience for each one of us. Check out this <a href="https://productblog.townscript.com/what-happens-in-hackathon-stays-in-hackathon-32a96a16d471#.zar3i8in1">blog post</a> to know what happened during a hackathon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*NcmCXtZarfrFImWS03WcvA.jpeg" /><figcaption>From left: Sushant Pawar, Sachin Nagargoje, myself and Sachin Sharma</figcaption></figure><p>We powered ticketing for Comic-Con Express Pune which happened for 2 days in February. Around 2500+ people attended each day. On both the days, we were managing registration desks i.e. checking tickets of attendees and giving them passes. In between, whenever we got bored we took turns and entered the venue with organizer badges to enjoy the event. I have been to many events in the past but seeing an event of this scale from the other side was a memorable experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*53In_OFbOhFWXCWJgXAPdA.jpeg" /><figcaption>Me and Sushant Pawar busy checking in attendees while Sachin giving us Redbull</figcaption></figure><p>Lastly, I will conclude with a meme I made for our android app promotion which was shared on social media. See, you get to do cool things like making memes when working for a startup :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*xLkYBlLrvdCHPUnZrVQvQw.jpeg" /></figure><p>This is a brief account of how the first six months of my first job were. I have become a tech enthusiast and started appreciating code more than before. I look forward and hope for more learning and eventful experiences in future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b6ce21fdf9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/townscript-product/6-months-at-a-startup-9b6ce21fdf9">6 months at a Startup</a> was originally published in <a href="https://medium.com/townscript-product">Townscript Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>