<?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 ANil Kotur on Medium]]></title>
        <description><![CDATA[Stories by ANil Kotur on Medium]]></description>
        <link>https://medium.com/@anilkotur?source=rss-88cfdf3df09c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EO7okVLWSgTSaoTvCCOUrw.png</url>
            <title>Stories by ANil Kotur on Medium</title>
            <link>https://medium.com/@anilkotur?source=rss-88cfdf3df09c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:40:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anilkotur/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[The Effective Engineer in Action: Practical Strategies for High Impact]]></title>
            <link>https://anilkotur.medium.com/the-effective-engineer-in-action-practical-strategies-for-high-impact-2d26d4ee17c4?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d26d4ee17c4</guid>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[engineer]]></category>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Fri, 23 Aug 2024 09:14:34 GMT</pubDate>
            <atom:updated>2024-08-23T09:14:34.739Z</atom:updated>
            <content:encoded><![CDATA[<h3>About Edmond Lau</h3><p>In the world of software engineering, maximizing your impact is key to a successful career. This blog is inspired by the insights of Edmond Lau, a seasoned engineer and the author of <em>The Effective Engineer</em>. With a career that includes impactful roles at Google, Quora, and Ooyala, Edmond has spent years refining his understanding of what it takes to be an effective engineer. His advice has helped countless engineers elevate their careers, and today, we’ll explore some of his most actionable strategies.</p><h3>Key Points</h3><h4>1. Optimize for Learning</h4><p><strong>Key Idea:</strong> Continuous learning is the quickest route to becoming a more effective engineer. By deliberately choosing projects that challenge you and push you out of your comfort zone, you can accelerate your growth and increase your impact.</p><p><strong>Practical Tip:</strong> If you’re uncomfortable speaking in team meetings, take up the challenge of giving a tech talk. This will not only build your knowledge but also boost your confidence in public speaking. Additionally, if you’re looking to familiarise yourself with new code or projects, start by reviewing code and Technical Review Documents (TRDs). Code reviews will expose you to different coding styles, while TRDs will enhance your understanding of system design.</p><h4>2. Invest in Iteration Speed</h4><p><strong>Key Idea:</strong> The faster you can iterate on your work, the quicker you learn and improve. Speeding up the cycle from idea to execution allows for more rapid feedback and better outcomes.</p><p><strong>Practical Tip:</strong> Streamline your development process by automating repetitive tasks, optimizing your development environment, and setting up continuous integration. These improvements can drastically reduce friction and enable faster progress.</p><h4>3. Validate Your Ideas Aggressively and Iteratively</h4><p><strong>Key Idea:</strong> Don’t spend months on an idea without testing it. Validating your concepts early and often helps you avoid wasted effort and ensures that you’re on the right track.</p><p><strong>Practical Tip:</strong> Implement A/B testing, gather user feedback, and create quick prototypes to validate your assumptions. If an idea doesn’t pan out, be ready to pivot swiftly and try a different approach.</p><h4>4. Minimize Operational Burden</h4><p><strong>Key Idea:</strong> Time spent on operational tasks, like managing servers or fixing bugs, can detract from more impactful work. Reducing these burdens allows you to focus on what truly drives value.</p><p><strong>Practical Tip:</strong> Invest in tools and practices that automate operational tasks. For instance, use monitoring tools to catch issues early, or leverage auto-scaling to handle traffic spikes effortlessly.</p><h3>Conclusion</h3><p>Applying these principles — focusing on continuous learning, speeding up iteration, validating ideas early, and minimizing operational burdens — can significantly enhance your effectiveness as an engineer. Start implementing these tips today and watch your productivity soar.</p><h3>Acknowledgment</h3><p>Credit goes to Edmond Lau for his invaluable insights shared in <em>The Effective Engineer</em>. His work continues to inspire and guide engineers toward making a greater impact in their careers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d26d4ee17c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uncle Bob’s Clean Code: Simple and Effective Tips]]></title>
            <link>https://anilkotur.medium.com/uncle-bobs-clean-code-simple-and-effective-tips-458ddcd7606a?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/458ddcd7606a</guid>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Fri, 31 May 2024 09:04:16 GMT</pubDate>
            <atom:updated>2024-05-31T09:06:58.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwrTobbZ35ne6HvsWLm4IA.png" /></figure><p>Clean code is essential for maintainable and readable software. Inspired by Uncle Bob’s principles from his video on clean code, here are some key takeaways and practical tips to help you write cleaner, more effective code using Swift.</p><h3>Function Names Should Be Verbs, Not Nouns</h3><p>Function names should clearly describe the action they perform. This makes your code more readable and easier to understand.</p><p><strong>Example:</strong></p><pre>// Bad<br>func dataProcessor(data: Data) {<br>    // process data<br>}<br><br>// Good<br>func processData(data: Data) {<br>    // process data<br>}</pre><h3>Characteristics of Bad Functions</h3><h4>Large Number of Lines</h4><p>Functions should be concise. A function with too many lines is hard to understand and maintain.</p><h4>Doing More Than One Thing</h4><p>A function should do one thing and do it well. If a function is performing multiple tasks, it should be split into smaller functions.</p><h4>Mixing High and Low-Level Implementation</h4><p>Functions should operate at a single level of abstraction. Mixing high-level logic with low-level details makes the function harder to read.</p><p><strong>Example:</strong></p><pre>// Bad<br>func processOrder(order: Order) {<br>    // high-level logic<br>    validateOrder(order)<br>    // low-level details<br>    for item in order.items {<br>        if item.stock &lt; 1 {<br>            fatalError(&quot;Item out of stock&quot;)<br>        }<br>    }<br>    // more high-level logic<br>    saveOrder(order)<br>}<br><br>// Good<br>func processOrder(order: Order) {<br>    validateOrder(order)<br>    checkStock(order)<br>    saveOrder(order)<br>}<br><br>func checkStock(order: Order) {<br>    for item in order.items {<br>        if item.stock &lt; 1 {<br>            fatalError(&quot;Item out of stock&quot;)<br>        }<br>    }<br>}</pre><h3>Unit Tests Give Confidence in Refactoring Legacy Code</h3><p>Unit tests ensure that your code works as expected. They are particularly valuable when refactoring legacy code, as they provide a safety net that helps prevent the introduction of bugs.</p><h3>Write Code for the Reader, Not Just for It to Work</h3><p>When writing code, consider the reader. Write your code as if the next person to read it is a sociopath who knows where you live.</p><p><strong>Example:</strong></p><pre>// Bad<br>func cnvrt(v: Double) -&gt; Double {<br>    return v * 0.393701<br>}<br><br>// Good<br>func convertCentimetersToInches(centimeters: Double) -&gt; Double {<br>    return centimeters * 0.393701<br>}</pre><h3>Use Explanatory Variables</h3><p>Explanatory variables make your code more understandable by providing context for what values represent.</p><p><strong>Example:</strong></p><pre>// Bad<br>func calculateSpeed(distance: Double, time: Double) -&gt; Double {<br>    return distance / time<br>}<br><br>// Good<br>func calculateSpeed(distanceInMeters: Double, timeInSeconds: Double) -&gt; Double {<br>    let speedInMetersPerSecond = distanceInMeters / timeInSeconds<br>    return speedInMetersPerSecond<br>}</pre><h3>Have Small Functions</h3><p>Small functions are easier to read, understand, and maintain.</p><h4>When Is a Function Small Enough?</h4><p>A function is small enough if you can still extract another function from it.</p><p><strong>Example:</strong></p><pre>// Initial function<br>func processOrder(order: Order) {<br>    validateOrder(order)<br>    for item in order.items {<br>        if item.stock &lt; 1 {<br>            fatalError(&quot;Item out of stock&quot;)<br>        }<br>    }<br>    saveOrder(order)<br>}<br><br>// Refactored with smaller functions<br>func processOrder(order: Order) {<br>    validateOrder(order)<br>    checkStock(order)<br>    saveOrder(order)<br>}<br><br>func checkStock(order: Order) {<br>    for item in order.items {<br>        if item.stock &lt; 1 {<br>            fatalError(&quot;Item out of stock&quot;)<br>        }<br>    }<br>}</pre><h4>Use Switch Statements Only if Cases Are Independently Deployable</h4><p>Switch statements can be useful, but only if each case can be independently deployed. This ensures modular and maintainable code.</p><p><strong>Example:</strong></p><pre>// Bad<br>func handleEvent(event: Event) {<br>    switch event.type {<br>    case .click:<br>        handleClick(event)<br>    case .hover:<br>        handleHover(event)<br>    default:<br>        break<br>    }<br>}<br><br>// Good<br>func handleEvent(event: Event) {<br>    let eventHandlers: [EventType: (Event) -&gt; Void] = [<br>        .click: handleClick,<br>        .hover: handleHover<br>    ]<br>    if let handler = eventHandlers[event.type] {<br>        handler(event)<br>    }<br>}</pre><h3>Golden Rule in Naming Variables</h3><h4>Length of Variable Name Should Be Proportional to Scope</h4><p>The length of a variable name should be proportional to its scope. Shorter names are fine for small scopes, while longer names are better for larger scopes.</p><p><strong>Example:</strong></p><pre>// Small scope<br>for i in 0..&lt;10 {<br>    print(i)<br>}<br><br>// Large scope<br>func calculateAnnualRevenue(totalMonthlyRevenue: Double) -&gt; Double {<br>    let annualRevenue = totalMonthlyRevenue * 12<br>    return annualRevenue<br>}</pre><h3>Golden Rule in Naming Functions</h3><h4>Length of Function Name Should Be Inversely Proportional to Scope</h4><p>The length of a function name should be inversely proportional to its scope. General-purpose functions with broad applicability should have shorter names, while more specific functions with narrower scope should have longer, more descriptive names.</p><p><strong>Example:</strong></p><pre>// Small scope, very specific function<br>func calculateTotalAnnualRevenueWithTax(monthlyRevenue: Double, taxRate: Double) -&gt; Double {<br>    let annualRevenue = monthlyRevenue * 12<br>    let totalRevenueWithTax = annualRevenue + (annualRevenue * taxRate)<br>    return totalRevenueWithTax<br>}<br><br>// Large scope, general-purpose function<br>func add(_ a: Int, _ b: Int) -&gt; Int {<br>    return a + b<br>}</pre><h3>References</h3><ul><li><a href="https://www.youtube.com/watch?v=8SMOB6k3hkM">Clean Code with Uncle Bob</a></li><li><a href="https://www.youtube.com/watch?v=7EmboKQH8lM&amp;list=PLmmYSbUCWJ4x1GO839azG_BBw8rkh-zOj">Clean code full series</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=458ddcd7606a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maximising Your Job Application Success]]></title>
            <link>https://anilkotur.medium.com/maximising-your-job-application-success-8e8367fe1e26?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e8367fe1e26</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Sat, 13 Apr 2024 17:24:33 GMT</pubDate>
            <atom:updated>2024-04-14T05:40:51.767Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Practical Guide.In today’s competitive job market, standing out from the crowd is essential to secure your dream job.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*W4YrdIO44_69g85gUfNPSA@2x.jpeg" /></figure><p>Having recently posted a job opportunity for an <a href="https://www.linkedin.com/posts/anilkumar-kotur-65a33288_ios-developer-sde-2-activity-7184438234825867264-W0-U?utm_source=share&amp;utm_medium=member_ios">iOS engineer on LinkedIn</a>, I was overwhelmed with responses. However, I noticed several common mistakes that applicants made, which could have hindered their chances of success.</p><p>Here’s how you can avoid these pitfalls and increase your likelihood of landing your desired role</p><h4>Read Carefully:</h4><p>One of the most critical steps in the application process is thoroughly reading and understanding the job posting. Take the time to assess the requirements and responsibilities to ensure that your skills and experiences align with what the role demands. Tailoring your application to address these specifics demonstrates your attention to detail and genuine interest in the position.</p><h4>Skip Obvious Questions:</h4><p>Asking questions that are clearly answered in the job posting can give the impression of carelessness and lack of attention. Instead, use your application to highlight your relevant experiences and skills that make you a strong candidate for the role. This shows the hiring manager that you’ve done your homework and are serious about the opportunity.</p><h4>Be Honest</h4><p>It’s tempting to exaggerate your qualifications in the hopes of securing an interview, but honesty is always the best policy. If you don’t meet all the qualifications listed in the job posting, don’t try to convince the hiring manager otherwise. Instead, focus on showcasing your strengths and experiences that align with the role, being transparent about areas where you may need additional support or development.</p><h4>Respect Time</h4><p>Hiring managers sift through numerous applications, often within tight timeframes. Acknowledging and respecting their time by crafting a concise and relevant application can set you apart from the competition. Be mindful of the hiring manager’s workload and make it easy for them to see why you’re a strong fit for the role.</p><h4>Avoid Spamming:</h4><p>Sending generic, mass applications to multiple job postings may seem efficient, but it’s unlikely to yield positive results. Instead, take the time to personalize each application to the specific role and company. Highlighting your understanding of the company’s values, mission, and culture demonstrates genuine interest and enthusiasm for the opportunity.</p><blockquote>Remember, it’s not just about applying to as many jobs as possible but about crafting targeted and impactful applications that showcase your unique qualifications and experiences.</blockquote><p>Good luck on your job search journey!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e8367fe1e26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leading a Tech Team: Navigating Tech and People Skills]]></title>
            <link>https://anilkotur.medium.com/leading-a-tech-team-navigating-tech-and-people-skills-31da21011934?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/31da21011934</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[people-management]]></category>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Tue, 23 Jan 2024 11:09:17 GMT</pubDate>
            <atom:updated>2024-01-23T11:09:17.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*v3FIgD8sAgpbKqBR-8ZY-g@2x.jpeg" /></figure><h3><strong>Introduction</strong></h3><p>Hey tech enthusiasts! In this blog I will share my experience and learning’s as lead iOS engineer at leading fintech startup.</p><p>My top five learning’s as team lead</p><h4><strong>The Many Roles of a Team Lead</strong></h4><p>In tech, some folks think a team lead’s job is just coding. But it’s more than that. Imagine being not just a code whiz but also a savvy negotiator and a people person. Great team leads know how to bring a bunch of talented folks together to work as one awesome team.</p><h4><strong>Problem-Solving in the Real World</strong></h4><p>Leading is about solving problems in the real world, considering what the company needs. It’s asking the right questions, understanding the big picture, and making sure your team’s work matches the company’s goals. It’s not just about finding the best techie solution; it’s about finding the right one for your company.</p><h4><strong>Clear Expectations for Success</strong></h4><p>Good leaders talk straight. It’s about setting real expectations for your team and making sure everyone knows where the team is headed. It’s not just about finishing projects; it’s about everyone moving in the same direction and feeling accountable.</p><h4>A Positive Workplace</h4><p>A happy workplace is key to a great team. It’s about working together, trusting each other, and growing as a team. Make sure your team feels supported, and they’ll bring their A-game. It’s not just about finishing tasks; it’s about creating a space for your team to do their best work.</p><h4>Staying Sharp Every Day</h4><p>Tech is always changing. Keep your tech skills updated, but don’t forget people skills. Leading is about balancing tech smarts with understanding people. Keep up with both, and your team will thank you.</p><blockquote>Leading isn’t just about writing best code, it’s about being a good negotiator, team player, and staying on top of both tech and people skills</blockquote><h4>Conclusion</h4><p>So, that’s a quick tour of what it takes to lead a tech team. It’s about being a coder, a talker, a problem-solver, and a team builder. In the fast-changing tech world, the best leaders are the ones who roll with the changes, bring folks together, and push their teams to do awesome things. Here’s to leading the way in India’s tech scene!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31da21011934" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Percentage vs. Percentile: What’s the Difference?]]></title>
            <link>https://anilkotur.medium.com/understanding-percentage-vs-percentile-whats-the-difference-889764490180?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/889764490180</guid>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Thu, 12 Oct 2023 11:20:22 GMT</pubDate>
            <atom:updated>2023-10-12T11:34:51.908Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQL3s4asXP5s2sDQscvkFQ@2x.jpeg" /></figure><h3><strong>Introduction:</strong></h3><p>When it comes to understanding data and statistics, two terms that often cause confusion are “percentage” and “percentile.” In this blog, we’ll break down the key differences between these two concepts using simple examples. Whether you’re a student, a data enthusiast, or just curious, this guide will help you grasp the distinction between percentage and percentile.</p><h3>What is Percentage?</h3><p>Percentage is a way of expressing a part of a whole as a fraction of 100. It’s a familiar concept that we encounter regularly in our daily lives. To calculate a percentage, you take a part (numerator) and divide it by the whole (denominator) and then multiply by 100.</p><p><strong>Example 1:</strong> Imagine you scored 85 out of 100 on a math test. To find the percentage, you would do:</p><blockquote>(85 / 100) * 100 = 85%</blockquote><p>This means you scored 85% on the test.</p><h3>What is Percentile?</h3><p>Percentile, on the other hand, is a statistical concept used to rank and compare data within a dataset. It tells you the position of a particular value within the entire dataset.</p><p><strong>Example 2:</strong> Let’s say you took a standardized test, and your score is at the 90th percentile. This means that you scored better than 90% of the test-takers.</p><blockquote>To break it down further:</blockquote><ul><li>If there were 100 test-takers, and you scored better than 90 of them, you would be at the 90th percentile.</li><li>- Your score doesn’t represent a percentage; instead, it indicates your rank within the group.</li></ul><h3><strong>Key Differences:</strong></h3><p><strong>1. Calculation Method:</strong></p><ul><li>Percentage is calculated as a fraction of 100.</li><li>Percentile represents a rank within a dataset.</li></ul><p><strong>2. Representation</strong>:</p><ul><li>Percentage is expressed as a number followed by the “%” symbol.</li><li>Percentile is expressed as a number followed by “th” (e.g., 90th percentile).</li></ul><p>3. <strong>Use Case</strong>:</p><ul><li>Percentage is used to express proportions, ratios, or parts of a whole.</li><li>Percentile is used to rank data within a group</li></ul><h3>Conclusion:</h3><p>Understanding the difference between percentage and percentile is crucial for various fields, from education to data analysis. Percentage expresses parts of a whole, while percentile ranks data within a dataset. By using these simple examples, we hope you now have a clearer grasp of these concepts. So next time you encounter these terms, you’ll know exactly what they mean. Happy learning!</p><p>If like to support the work buy me a coffee here</p><p><a href="http://buymeacoffee.com/anilsk">https://www.buymeacoffee.com/anilsk</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/489/1*cWC-iCic1rRGxASQiiY6-w@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=889764490180" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we won GOJEK’s internal hackathon]]></title>
            <link>https://anilkotur.medium.com/how-we-won-gojeks-internal-hackathon-f47275c6f037?source=rss-88cfdf3df09c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f47275c6f037</guid>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[gojek]]></category>
            <dc:creator><![CDATA[ANil Kotur]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 09:34:36 GMT</pubDate>
            <atom:updated>2019-03-01T17:54:09.546Z</atom:updated>
            <content:encoded><![CDATA[<p>On Dec 5, 2018, GoJek hosted an internal hackathon at Bangalore office and Team ⚡️(me and three others) won the second price with our new product GO-Calendar.</p><h3><strong>About GO-JEK</strong></h3><p>Established in 2010 as a motorcycle ride-hailing phone service in Indonesia, GO-JEK has since evolved to provide on-demand transport and lifestyle services that move the city.</p><h3><strong>The Idea</strong></h3><blockquote>Making Go-Jek super smart app.</blockquote><p>Gojek has 18 products which make it a super app, what if we make it smart by serving a personalized experience to the user. Achieving the personalized experience is not an easy task but user always choose convenience over privacy by giving access to their data like push notification, mail, calendar etc. so we decided to study the user behavior and suggest appropriate service like Go-Ride every morning to office and Go-Food at lunch and Go-Send to send a gift to loved once on their birthday.</p><p>It also solves the following problems</p><ol><li>Recurring events.</li><li>Reminder for important events (paying a premium or recharging talk time).</li></ol><h3>Challenges</h3><p>Building an algorithm which understands user behavior and Processing data requires expertise in data science and machine learning but these are clearly not our strength.</p><h3><strong>Solution</strong></h3><p>What if users themselves schedule calendar events with services based on his/her requirements. like booking a Go-Ride to the office/home or order Go-Food for lunch. Go-Bill for monthly bills and likewise.</p><h3>Time to Hack</h3><p>The venue was filled with 35 teams, 100 engineers and a lot of discussions so we choose one of the meeting room as our battleground and started the brainstorming. As we have good knowledge of the product, its flows and iOS code base we decide to add Go-Calender as a new product on GoJek iOS app’s home screen. Yes even though we were building event scheduler we still call it as a calendar because it serves as a platform to Go-Jek’s services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibUFxbCfrGOifnZIIh1xjg.png" /><figcaption>That smile when you see first output at 4 am in the morning</figcaption></figure><h3>Product flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*46pIYe1vd3VNl_2crT3JXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*W3AIBshx181XeDTRfVO_TA.png" /></figure><p>After a couple of iterations, we come up with the flow that doesn’t even require any Backend effort (apart from push notification service ). this is how flow looks</p><ol><li>Open Go-Calender</li><li>Add an event by choosing a service (Go-Ride, Go-Send)</li><li>Create a booking and schedule it.</li></ol><p>That’s it, the user will receive a push notification at the scheduled time click it to make a booking. Simple and a life saver.</p><h3><strong>Presentation</strong></h3><p>We presented a fulling working product with full vision in terms of business use case, like</p><ol><li>The product will help us understand user behavior.</li><li>It will help retain user as it saves the user time and helps them become organized.</li><li>It will be a new entry point for other products.</li></ol><h3><strong>Prizes</strong></h3><p>We got awesome <a href="https://www.amazon.in/JBL-Pulse-Wireless-Portable-Lightshow/dp/B074Q4S2NJ/ref=sr_1_1?s=electronics&amp;ie=UTF8&amp;qid=1548339650&amp;sr=1-1&amp;keywords=jbl+pulse+3">JBL Pulse 3</a> as a prize and we love it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CLm9d-FslRziwDOK-nqOtw.png" /><figcaption>that&#39;s how we look after 24 hours of continues coding and brainstorming.</figcaption></figure><h3><strong>Team ⚡️</strong></h3><p><a href="https://twitter.com/karthik_mrt">Karthik</a></p><p><a href="https://twitter.com/ratneshnavlakhe">Ratnesh Navlakhe</a></p><p><a href="https://twitter.com/AnilSk7">Anil Kotur</a></p><p><a href="https://twitter.com/csbhalerao">Chetan Bhalerao</a></p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2IVAl0TbsfES9cFGYr40g.png" /></a></figure><p>📝 Read this story later in <a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_read_later_text">Journal</a>.</p><p>🗞 Wake up every Sunday morning to the week’s most noteworthy Tech stories, opinions, and news waiting in your inbox: <a href="https://usejournal.com/newsletter/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=guest_post_text">Get the noteworthy newsletter &gt;</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f47275c6f037" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>