<?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 Jyoti Balwani on Medium]]></title>
        <description><![CDATA[Stories by Jyoti Balwani on Medium]]></description>
        <link>https://medium.com/@jyoti.balwani?source=rss-f283d7f5119b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-uWM5LXBvnVcREfAwQp6mg.jpeg</url>
            <title>Stories by Jyoti Balwani on Medium</title>
            <link>https://medium.com/@jyoti.balwani?source=rss-f283d7f5119b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:59:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jyoti.balwani/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[Wondering about the Transition from IC to Manager?]]></title>
            <link>https://medium.com/expedia-group-tech/wondering-how-is-the-transition-from-an-ic-to-a-manager-heres-my-journey-a2930358dc82?source=rss-f283d7f5119b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2930358dc82</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Jyoti Balwani]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 09:01:47 GMT</pubDate>
            <atom:updated>2023-01-06T17:30:38.713Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://medium.com/expedia-group-tech/engineering/home">EXPEDIA GROUP TECHNOLOGY — ENGINEERING</a></h4><h4>A transition is never easy. Here’s my experience in moving from Individual Contributor to People Manager for a software engineering team</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7SfNseGD90oqtCQc2CchBA.png" /></figure><p>As Individual Contributors (ICs) we are constantly contributing to our projects; developing the best technical solutions while working on our assigned tasks/projects. Our focus remains to own our team initiative technically, to work with our team and to deliver high-class software to our travellers!</p><p>When we think of a leadership role, a lot of things come into our mind — leading the team technically &amp; ensuring a development of quality product, mentoring team members, generating ample opportunities for team members to grow, ensuring team collaboration and trust, taking accountability of the deliverables, setting right expectations, managing team and app performance, and a lot of other tasks &amp; challenges.</p><p>While all of this may sound exciting (and challenging), we often wonder if we’ll be able to handle it together; especially when we don’t really have any prior experience in these. <em>Well, maybe not — we may feel we are not ready for it YET!</em> But being ready doesn’t happen overnight. It has to be a process that takes time. Transition is more effective and efficient when it takes place over time with a lot of practice.</p><p>Here are some of my learnings from when I moved from IC to a Manager role.</p><h3>Before the transition</h3><p>For anyone thinking to transition over, there comes a point where they want to try and move towards a leadership role. When they feel that they can help create, mentor and lead a team taking all the teammates together and contributing to everyone’s growth… when they want to try thinking strategically and also participate in defining “what to do” than just “how to do”.<br>This is when our managers can help us groom into that role, so when we transition it doesn’t come hard on us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pQpg4tTPn-suWGPu" /><figcaption>Photo by mohamed_hassan on Pixabay</figcaption></figure><p>Few areas that can help us groom better while being an IC:</p><h4>Own a project (or part of it) completely</h4><p>When we own a project not just technically but also from clearing any requirements till the end of delivery, helps us be more confident and accountable. We should try to take more responsibility and accountability of projects, ensuring to develop a quality product. There are times when we’d directly reach out to our PMs or TPMs, or maybe folks from other teams to get our work done in time.</p><h4>Participate in more discussions</h4><p>Discussions aren’t only about updating the status of our work, but also being able to voice out our opinions and views. If possible, we should try and look for opportunities where we can speak up about our views, and get feedback. These discussions can sometimes also be negotiations or debates around a tech approach or any RFC for example. Even listening to others in such discussions, helps us understand and learn.</p><p>This helps improve communication skills, speaking confidently with conviction.</p><h4>Be part of meetings where the objectives are set</h4><p>Being part of meetings where OKRs or milestones are set, gives us more understanding of the project and deliverables. It’s insightful and gives us a perspective on how tasks should be defined.</p><h4>Mentoring team members</h4><p>We always have some new joiners or juniors in our team who are new to the system and tools or just figuring out various how-tos. We should take this opportunity to help them, understand the problems they are facing, think and let them know how they could do better, not just them, but help us grow as well. Sometimes, they help us learn a few things as well.</p><h4>Receive &amp; give feedback</h4><p>While we may already be doing so in the quarterly connects, we should be open to giving and receiving feedback from anyone and everyone (no matter if someone’s senior or junior to you), at any given point in time. It’s not just about giving credit or appreciating others when they do something good, but also never hesitating is giving constructive feedback as well.</p><p>It’s amazing to see how others can also thank you for your constructive feedback that helped them grow as well.</p><h4>Self Introspect</h4><p>From time to time, we should take out some time to self-introspect our actions and how they affected others. The effect could be positive or negative, but thinking if there’s something we may have done differently, or in a more efficient way can help improve. After all, we all learn from our mistakes!</p><h3>After the transition</h3><p>Although a bit of grooming before the transition does help, it’s no surprise that there will still be some new challenges and situations along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-F5AQuiShZtXPSnZSltIVw.jpeg" /><figcaption>Photo by geralt on Pixabay</figcaption></figure><p>For new managers like us, Expedia Group™ does provide some great training materials. We have a Leader Learning Program, which is one such training, spread across 3 parts:</p><ol><li><strong>Leading at Expedia Group</strong> focussing on leadership foundations and team management.</li><li><strong>Leading for Success</strong> focussing on building trust, enabling performance, coaching mindset, and giving and receiving feedback.</li><li><strong>Leading for the Future</strong> focussing on strengthening trust, leading through change, effective communication, and continuous learning.</li></ol><p>These pieces of training also include very useful examples and scenarios, describing what we should and should not encourage as people leaders. There are a few other tools that help us through and are readily available for the leaders.</p><p>Even though these training sessions are good, while applying them practically there may still be a few times when we may have certain questions in our mind — W<em>ill I be successful at this? I have never faced this situation before... How do I handle this? I’m building or taking care of a new team... how do I build trust and improve collaboration? How do I review talent? etc…</em></p><h4>Helpful suggestions I got from my mentors around these:</h4><ul><li>When in a situation, think about if there were a time when you felt you had a similar problem in your team before (when you were an IC). How did your manager handle it?</li><li>Always remember how you felt about your manager’s reaction in any scenario. This helps us know how to, or how not to deal with a situation.</li><li>Everyone will have a different approach to any situation — there’s no right or wrong approach as such. There isn’t one fixed way/solution to anything, and everything’s learning.</li><li>Networking helps — there are people around you who will always be happy to discuss, mentor and help you! You can also continue to meet them and have regular feedback, this never hurts!</li></ul><h3>The journey continues</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gf-ax6L8u7TmTe601eGQBA.jpeg" /><figcaption>Photo by ar130405 on Pixabay</figcaption></figure><p>Of course, as said earlier it takes time. As we continue on this path, we continue to improve and grow and there will always be new challenges. What matters is how we deal with them! Being a People Leader is a bit different from being an IC. Along with being a tech lead, we also need to think about the big picture, help the team members grow, and ensure we are delivering high-class products timely!</p><h3>To Remember</h3><blockquote>Transitioning to a new role isn’t easy, but getting enough grooming throughout can help make the journey a bit smoother.</blockquote><p>As we continue to grow and learn new things in our role, we should always take some time to appreciate others. Not just the team members who do a great job, but also others who help, motivate and stand by you.</p><p>Thank you Ajit Singh, Amit Mangal, Ankur Singh Panesar, Hari Singh, Kelly-Marie Taylor, Muthu Sathiamurthy, Nancy Gupta, Nikunj Manocha, Ranjan Chhibber, Vinitha Mathew for giving me ample opportunities to grow, and being so approachable and honest and with your feedback. You have always encouraged me to improve and do better each day!</p><p>Lastly, something that stands by:</p><blockquote><em>“Everyone have their own style — find yours! It’s driven by your experience!</em>”</blockquote><p>(thanks Kshitij Chandiok for the advice above, it’s been really helpful).</p><p>And always remember:</p><blockquote>behind every big step, there’s a lot of hard work — not just by you, but by many others who believe in you!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2emNFVHbgnjtWeBJec7MUQ.jpeg" /><figcaption>Photo by Sydney Rae on Unsplash</figcaption></figure><blockquote><a href="https://lifeatexpediagroup.com/technology?utm_source=techblog&amp;utm_medium=career&amp;utm_campaign=postfooter">Learn more about technology at Expedia Group</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2930358dc82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/wondering-how-is-the-transition-from-an-ic-to-a-manager-heres-my-journey-a2930358dc82">Wondering about the Transition from IC to Manager?</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React India 2022]]></title>
            <link>https://medium.com/expedia-group-tech/react-india-2022-ae48ee74e8ff?source=rss-f283d7f5119b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae48ee74e8ff</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[tech-conference]]></category>
            <dc:creator><![CDATA[Jyoti Balwani]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 15:54:46 GMT</pubDate>
            <atom:updated>2022-12-14T22:11:42.335Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://medium.com/expedia-group-tech/engineering/home">EXPEDIA GROUP TECHNOLOGY — ENGINEERING</a></h4><h4>An opportunity to learn and connect with top developers</h4><figure><img alt="Photo of a welcoming sign for React India" src="https://cdn-images-1.medium.com/max/1024/1*yKRKtVakfkKA9mZtFnNXMg.jpeg" /></figure><p>A few weeks ago, while we were sitting together in our office, a teammate casually mentioned <em>React India 2022</em> conference, happening in hybrid mode this year. Looking at the agenda, it suddenly created a buzz among us. React India was about getting to listen some of the top developers across the globe and also connect with them. To top up the experience and excitement, it was happening in Goa this year!</p><blockquote><em>Tech conferences are a great medium to network with leading developers from your community and expand your knowledge and skills</em></blockquote><p>Looking at this huge opportunity around us, Expedia Group™ also became one of the silver sponsors to the event.</p><h3>The event</h3><figure><img alt="A speaker in front of a large screen with Hindi text reading “TBD”" src="https://cdn-images-1.medium.com/max/1024/0*YTaXmtvwzfnv7Qw_" /><figcaption>Translation in English — “What have we learnt”; Thanks Jyoti Dhyani (Expedia Group) for this capture!</figcaption></figure><p>This being one of the first events Expedia Group India was participating post-COVID, our organisation wanted to have a huge impact in terms of learnings for our developers with this opportunity to see how other leading companies are solving similar issues. We formed a group of React enthusiasts who would be eager to learn, network, and bring back learnings to the wider Expedia Group audience!</p><p>The React India conference was a three-day tech event split across in-person/remote workshops and talks with lot of topics of interest, all conducted by developers like us who are into ReactJS daily.</p><h4>Day 1</h4><p>This was a workshop and remote day, where we had numerous sessions on technologies and tools used in the industry along with hands-on experience in the workshop. These sessions were very engaging. I got to attend a few related to web performance and using GraphQL within our apps. It was great to see how the tools work and how we can apply them to our applications. Such interactive workshops also helped us clarify a lot of questions at the same time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy-HA-d265IrA0wdiDYLOQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qcvUP7JYQhruCOk7ujIB-Q.jpeg" /></figure><h4>Day 2 and day 3</h4><p>These days were packed with tech talks from developers and leaders across the world. The in-person talks started with Kent C. Dodds, who took us from the evolution of JavaScript in the past to the web’s next transformation. Next, we had various sessions on React hooks, concurrency, JavaScript bundlers, testing libraries and design systems. It was amazing to see the vast topics and speakers from multiple companies. To most of them, our reactions were “<em>oh, we at Expedia Group are also using a similar tech</em>”, or “<em>wow, that’s interesting... we should incorporate that in our architecture.”</em> We could figure out simple hacks and other enhancements that we could do while learning from others around what they are using, and it was just great to see everyone getting together on such a platform.</p><figure><img alt="Kent C. Dodds speaking at the conference" src="https://cdn-images-1.medium.com/max/1024/0*bMxNRiXaZ7ofZKva" /><figcaption>Picture credits — Kshitiz Rohatgi (Expedia Group)</figcaption></figure><p>All of the speakers were also available after their talks for anyone to just walk by and strike up a conversation!</p><h3>Talk from Expedia Group</h3><figure><img alt="Presentation title slide entitled “Pluggable virtual agents powered by React” by Mohit Gupta" src="https://cdn-images-1.medium.com/max/342/0*bYOrfzVW3Z_wr9eq" /></figure><p>We also got a chance to showcase our pluggable virtual agents (chatbots) built in React. Mohit Gupta (Sr. Manager, Expedia Group), presented one of our use cases that we solved and integrated using React. He described how we consumed our chatbot platform and made it available to our customers through a minimal code, pluggable chat widget across devices. Our internal clients had varied requirements to use this plugin. Our demo focussed on how we made it configurable along with providing rich user interfaces that our different clients could leverage through a single codebase of pluggable widgets.</p><h3>Expedia Group — the sponsor</h3><p>Expedia Group also sponsored the event and we saw a great footfall to our booth. We were quite excited to see how people want to know how Expedia Group works. They also wanted to connect with us to see how we can leverage their applications on our platform and similarly how they can use our platform in a better way.</p><figure><img alt="Projected slide at the conference with the Expedia Group logo" src="https://cdn-images-1.medium.com/max/1024/1*Ks7mGWmT5Lzm96iEkD0XHA.jpeg" /></figure><p>It was great to see the energy at the booth, and every other developer that we met was very eager to learn the tech stack at Expedia Group. They were also keen to know the current opportunities for them within our company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7QlMcFhgGGEEl4GA4ahkkQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FmmlmEt-2v8uFmfnm19H6Q.jpeg" /><figcaption>Thanks Nikunj Manocha (Expedia Group), for these captures!</figcaption></figure><h3>The relaxing venue</h3><p>With a 3-day workshop and tech talks, Goa was rightly picked. We were able to relax and enjoy the sandy beaches a bit during the evenings. This kept us going for the next day!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojFWvvgsBAyvmFRblQ066A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIbTRU6kqi5Y7Qe_urjrtA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ijx7Z6BqkqtC97FrvdxoCg.jpeg" /></figure><p>This also gave us time to connect better amongst ourselves and come up with stronger UI community at Expedia Group!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9I8eLvXHYkJhmGVr6IH5g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ykYrJZL4_YCSbBj22HpjWg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNVyEDvvzeHDWdkVG4llMA.jpeg" /><figcaption>Picture Credits — Jyoti Dhyani (Expedia Group)</figcaption></figure><h3>Key takeaways and learnings</h3><ul><li>This was our first conference focussed on ReactJS. This helped us bring together the UI community within Expedia Group.</li><li>Discussing tech trends in industry, we observed Expedia Group is using the latest technologies and evolving with time.</li><li>We got a chance to network with developers across organisations, and it was amazing to see the ideas people had to share with each other.</li><li>Our design system at Expedia Group is a great foundation to our apps.</li><li>Developers were very interested to know more about Expedia Group in general, and wanted to be part of it.</li></ul><figure><img alt="Expedia Group employees gathered around their company’s booth at the conference" src="https://cdn-images-1.medium.com/max/1024/1*DwBpKCWUNTj1Z9mL1LEAaw.jpeg" /><figcaption>Thanks Nitin Gupta (Expedia Group), for capturing this!</figcaption></figure><h3>Gratitude!</h3><p>I’m truly grateful to my manager Ajit Singh, who gave me this opportunity to attend this conference in person. Thanks to our leadership — Arun Dutta, Nikunj Manocha, and Amit Mangal — for planning, getting us all together, and organising the event for all of us at Expedia Group. We all came back with a lot of learnings. Looking forward to more such conferences and also more talks and speakers from Expedia Group!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hkV4YouVIy2PPppichyHYQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EGVRcEp2d8EVIvgsuMoWhA.jpeg" /></figure><blockquote><a href="https://lifeatexpediagroup.com/technology?utm_source=techblog&amp;utm_medium=career&amp;utm_campaign=postfooter">Learn more about technology at Expedia Group</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae48ee74e8ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/react-india-2022-ae48ee74e8ff">React India 2022</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mistakes to Avoid While Designing an API]]></title>
            <link>https://medium.com/expedia-group-tech/mistakes-to-avoid-while-designing-an-api-abe4ec9c60b5?source=rss-f283d7f5119b------2</link>
            <guid isPermaLink="false">https://medium.com/p/abe4ec9c60b5</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Jyoti Balwani]]></dc:creator>
            <pubDate>Thu, 09 Sep 2021 13:03:43 GMT</pubDate>
            <atom:updated>2021-09-09T13:03:43.688Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/expedia-group-tech/software/home">EXPEDIA GROUP TECHNOLOGY — SOFTWARE</a></h4><h4>Ever found yourself re-working the same API design again and again?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RIph0qYRkZoNFJOvJ-Oqug.jpeg" /><figcaption>Photo by Charles Deluvio on Unsplash</figcaption></figure><p>Please avoid these common mistakes when you next find yourself designing an API!</p><h3>Mistake #1 — Using an existing codebase to understand product requirements</h3><p>How many times during our professional career have we come across the situation where we’re looking at existing code to understand the whole product flow. While that can give a good idea of how things are implemented, we may miss out on one aspect or another while only looking at the current codebase. Let’s not forget that AB experiments can also add to the risk of missing out on product paths.</p><p>For instance, consider the following:</p><p><strong>Situation: </strong>We have to design an API that returns a currency code &amp; format to use across pages. To understand all the use-cases, we look at the various existing apps and debug to find how currency is used today.<br>We reviewed most pages and concluded that they were rendering the traveler’s chosen currency. Hence, we designed our API to return the traveler’s chosen currency and format.</p><figure><img alt="Emoticon with caption saying “Oh no! I just spend a month figuring out the product flows, while going through this code and I still don’t know them all!”" src="https://cdn-images-1.medium.com/max/1024/1*C_3MMuOFkZM4mLbjk-MVGg.png" /><figcaption>Image from pixabay.com</figcaption></figure><p><strong>Problem: </strong>We were not aware of another page which showed the host currency instead, and this lead to a bug! <em>We missed that flow. </em>Now, we have to update the API to cater to more use-cases like this one.</p><p><strong>Solution:</strong> Reach out to the Product Manager of the applications, they can list all the product flows and help with our use-cases.</p><blockquote>While it may be good to understand how the code is implemented for a product flow, it may be best to reach out to the product team working on that part of the project instead.</blockquote><h3>Mistake #2 — Rushing to finalize a design</h3><p>Designing a system or an API has to be an iterative approach. We cannot wait indefinitely for all the use-cases to unfold before we start designing.</p><p>For instance, consider the following:</p><p><strong>Situation:</strong> We have to design a new API for a property description. For now, we only know that it’ll return some description text, however we <em>must</em> finalize the design around it.</p><figure><img alt="Emoticon with caption saying “Why didn’t they tell me this basic requirement before I started to design this?”" src="https://cdn-images-1.medium.com/max/1024/1*K_Mz9U8PTkQlvNg7lU-Ryw.png" /><figcaption>Image from pixabay.com</figcaption></figure><p><strong>Problem:</strong> At a later stage, we learn that returning just the plain property description isn’t sufficient. The requirement is to also filter by attributes (like room type, property type, etc.) and we must return a map of description attributes.<br><em>We’ll have to re-iterate on the design.</em></p><p><strong>Solution: </strong>Gather all the basic requirements but expect to update your API design as you learn more.</p><blockquote>It’s best to make designing an iterative approach, where we can refactor and refactor till we have a good system design.</blockquote><h3>Mistake #3 — Not thinking about how an end-user would use your design/solution</h3><p>Another common mistake that we tend to make is not thinking about how our design will be consumed. <em>Will it be easy or difficult to use?</em> We must think about end-user use cases.</p><figure><img alt="Emoticon with caption saying “I have no clue how the client will understand and use this!”" src="https://cdn-images-1.medium.com/max/1024/1*afUZc4LLo61s3kKNq1wlEw.png" /><figcaption>Image from pixabay.com</figcaption></figure><p>For instance, consider the following:</p><p><strong>Situation:</strong> We have designed an API returning an unstructured list of property details specific to some type (location/stay policy/amenities, etc). Each property detail can further have secondary text and an availability flag, where applicable.</p><p><strong>Problem:</strong> Team A only wants to read the availability for a specific detail of a property. But they have to iterate through the entire list to find the required detail and then read if it’s availability.<br><em>This led to unnecessary &amp; avoidable code to read the data they need.</em></p><p><strong>Solution:</strong> Design the API in such a way that the end-user doesn’t need to do any avoidable work, reducing complexities at their end. Maybe return a structured response in the above given situation, or request for just that detail/or all available details and return only that.</p><blockquote>While designing &amp; implementing the system, we should keep in mind the challenges that end-users may face while using it.</blockquote><h3>Mistake #4 — Not thinking about extensible solutions</h3><p>Having an extensible design does not only mean having code which can be extended further, but also that the solution can be extended to other consumers of your design.</p><p>For instance, consider the following:</p><p><strong>Situation:</strong> We designed an API to return booking policies that are to be displayed on Page A. We modeled our API in a way that it’s easy for the team working on Page A to display them.</p><figure><img alt="Emoticon with caption saying “This solves for my current client. But wait, what if some other client also wants to use it?”" src="https://cdn-images-1.medium.com/max/1024/1*RZ6jtRXT37IXZm-fz88l2w.png" /><figcaption>Image from pixabay.com</figcaption></figure><p><strong>Problem:</strong> Team B working on Page B has a similar requirement to display the same booking policies, and also wants to use our API. But because the API was too tightly coupled to how Team A uses it, Team B can’t use it directly.<br><em>We have to refactor/redesign it all over again!</em></p><p><strong>Solution: </strong>An API design shouldn’t be tightly coupled to the needs of the current/only consumer, which also means that our changes shouldn’t affect the other systems using it.</p><blockquote>Our design should be able to cater to similar needs of other consumers as well.</blockquote><h3>Mistake #5 — Trying to add too many features leading to a complex design</h3><p>While it’s true that we shouldn’t have a separate system/endpoint for every related requirement, we must also ensure that our system is not complicated because it’s handling too much stuff, especially if it could have been separated better.</p><p>We should always try to optimize the features our design caters to, while also maintaining separation of concerns.</p><figure><img alt="Emoticon with caption saying “I have added all the features here. But this looks complex now. I have added EASE OF USE as another feature requirement.”" src="https://cdn-images-1.medium.com/max/1024/1*KkteYXm6UOvddkVw6ExS5A.png" /></figure><p>For instance, consider the following:</p><p><strong>Situation:</strong> We have to design an API for a library, which can return a list of books and also supports updating book details (E.g. type, author, and name) by both librarians and book issuers. The API can also return filtered lists of books and sort them. It can also search for books by any of their attributes.<br>We added all the functionality at a single place in the code (data model to our API).</p><p><strong>Problem:</strong> We have to separate out the few features specific to librarians only.<br><em>It’s complex to understand all features implemented at one place, to be able to identify specific ones.</em></p><p><strong>Solution:</strong> Design a system in such a way, that related features/functionalities are together. Separate out the concerns by customers (librarians vs borrowers), and also by functionality.</p><blockquote>The design shouldn’t get too complex to use and understand.</blockquote><h3>Conclusion</h3><p>While it’s important to follow standard principles when designing a new API, avoiding the above mistakes can make the process more efficient!</p><figure><img alt="Emoticon with caption saying “I’ll keep all of these in mind now!”" src="https://cdn-images-1.medium.com/max/1024/1*ehF8h5dQQMlnWsZWjbNIFg.png" /><figcaption>Image from pixabay.com</figcaption></figure><p>Have I missed a mistake that you’ve made? Please share in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abe4ec9c60b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/expedia-group-tech/mistakes-to-avoid-while-designing-an-api-abe4ec9c60b5">Mistakes to Avoid While Designing an API</a> was originally published in <a href="https://medium.com/expedia-group-tech">Expedia Group Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>