<?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 Ayush Singh on Medium]]></title>
        <description><![CDATA[Stories by Ayush Singh on Medium]]></description>
        <link>https://medium.com/@alphaayush?source=rss-25a08b9a9a36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0lz6Eplkp75SKpJ2vsZWUg.jpeg</url>
            <title>Stories by Ayush Singh on Medium</title>
            <link>https://medium.com/@alphaayush?source=rss-25a08b9a9a36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:16:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alphaayush/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[I instructed GitHub Copilot to code an Instagram profile feed in React. Here’s what happened.]]></title>
            <link>https://javascript.plainenglish.io/i-instructed-github-copilot-to-code-instagram-profile-feed-infinite-scroll-in-react-this-is-a863e7ce3a0d?source=rss-25a08b9a9a36------2</link>
            <guid isPermaLink="false">https://medium.com/p/a863e7ce3a0d</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[github-copilot]]></category>
            <dc:creator><![CDATA[Ayush Singh]]></dc:creator>
            <pubDate>Sat, 18 Sep 2021 10:23:43 GMT</pubDate>
            <atom:updated>2021-09-19T16:47:35.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evrFB2bkMgKZsE_pTM9_Ng.jpeg" /></figure><h3>How it started</h3><p>I got my hands on GitHub Copilot a month ago, I was already amazed by Copilot <a href="https://www.youtube.com/watch?v=FHwnrYm0mNc">crushing Leetcode problems in seconds</a>. The very fact that it is trained upon billions of lines of public code is fascinating. 👀</p><p><em>Yes, it’s all cool and stuff, but can it solve the day-to-day problems I face as a Frontend Engineer?</em></p><p><strong>So I took it for a spin!</strong></p><h4>My Initial Setup</h4><p>I had a Next.js (also React, if you don’t know) scaffold ready which I used during my Interview stints. So I started with the setup. <a href="https://github.com/ayush013/ig-clone-copilot">Github link here</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E45TzAHuC25vVRgX0chRVA.png" /><figcaption>Initial setup</figcaption></figure><h4>End Goal</h4><p>I was expecting to end up with a UI like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*B_k8jJ5uJdSdGSzFX8yA_A.jpeg" /><figcaption><a href="https://www.figma.com/community/file/878318142103232907">Mockup by Ashey on Figma community</a></figcaption></figure><ul><li>3 images stacked in each row</li><li>Ability to load more images (from paginated API) when I hit the bottom of the viewport</li><li>Maintain the state (loaded images) using the useState hook</li></ul><h3>This is how it w<strong>ent</strong></h3><h4>1. Warmup — Tile component</h4><p>I began writing comments to create a simple Tile component.</p><ul><li>Tile takes URL as a prop</li><li>Renders image with the URL</li><li>Has some classes for basic styling</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e83emQWsUM-om3tq9ZHq7Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*ZvbdNdW9yQEx_Cg8WSOWaA.jpeg" /><figcaption>Result as per the context — Not a bad start, I’d say</figcaption></figure><p>Sweet! It looked accurate to me at the first glance. I went ahead with it. CSS classes were added to the div instead of the image, which I corrected manually. Also added a CSS grid tailwind class on the div for the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*ZK6Spz1a-GJL5hyPHEY8kg.png" /><figcaption>With minor tweaks to CSS</figcaption></figure><h4>2. Feed component</h4><p>I got a little creative at this point 😝. Instructed copilot to do the following:</p><ul><li>Create a component that looks like an Instagram feed 🤣</li><li>it accepts a list of images as a prop</li><li>it renders a list of Tile components</li><li>each Tile component has a URL prop</li></ul><p>By the way, Copilot was kind enough to predict the comments as well 😉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*skWjIb6B4ubBrgreYyxdtQ.png" /><figcaption>After 2 seconds of processing</figcaption></figure><p>Seems like I was expecting too much 😅. It surely didn’t add the right CSS classes for a 3-column split layout. But notice how it was able to loop through images that came in as an array and rendered our Tile component correctly as we were expecting.</p><p>Accepted this solution after minor tweaks to CSS classes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*xWb4aQeg1V2hgHcvkJ9Bxw.png" /><figcaption>Feed component</figcaption></figure><h4>3. The Final component!</h4><p>Guess, this is what you’re here for! Can it predict the logic for Infinite Scroll? Can it accurately fetch from a paginated API?</p><p>Let’s find out! Provided the following context this time around:</p><ul><li>Create a Home component with Infinite Scroll</li><li>It fetches images from the API_URL and stores them in state</li><li>It renders a Feed component with the images</li></ul><p>By this time, it started predicting the next comments, this is what it came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*368ZSMUs0Rvu3Ojemidh1A.png" /><figcaption>The context for Home Component</figcaption></figure><p>3…2…1…Here we go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*en-pgIt0nfdyiw72ABXtXg.png" /><figcaption>Produced output</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*iUZBLCYM0XrxyUa76CkqPQ.jpeg" /></figure><p>I’m impressed! It surely did not generate the logic for Infinite Scroll, but the rest of the things like useState for images and useEffect for API calling look solid at the first glance. So I accepted this result (with a few caveats that I would discuss later).</p><p>At this point, I saved the file to check the output, I also removed Loading &amp; Error components for now and also did a minor API-specific tweak.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*7Q2PaPqZLaGhMYBLGu3jJw.png" /><figcaption>Minor tweak for API and styling</figcaption></figure><p>It rendered the images kinda as we wanted. Only the pagination and infinite scroll were missing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*MlWiRJR87g9BgGF7L6OfFw.png" /><figcaption>Produced output</figcaption></figure><p>In another attempt to fix the problems, Gave the following hints:</p><ul><li>Added a Button with ref to be observed</li><li>Specifically wrote IntersectionObserver API in the context</li><li>Added page in the state, to hint the pagination</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*Aqem5EuB4yD26RhMiWmY0w.png" /><figcaption>Produced output</figcaption></figure><p>It finally handled for pagination just the way we wanted, Also notice on the line:59, how it tried to handle concatenation to the previous dataset on subsequent API calls. But we’re still not there yet!</p><p>Final Attempt with the following context (which it also tried predicting):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*vxK4NmoZETD5M_tfccIv8w.png" /></figure><ul><li>Create a function that uses IntersectionObserver to observe the btn ref</li><li>It detects when the button is in the viewport</li><li>It calls the loadMore function when it is in the viewport</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*CUmsEOm3aPWMUcirL1T12Q.png" /></figure><p>Yes, this is what was the missing piece in our puzzle. A method that observes the button when it is visible in the viewport to initiate the next API call.</p><p>Some last tweaks to get it running:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*-XQnKMKrsYKCwLzuVsgm-Q.png" /></figure><p>Added a useEffect (also predicted by Copilot) to call the generated function, passing in btn and page as side effects to the dependency array. Manually added a cleanup to unobserve on component unmount.</p><h4>End result</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*sph15HjhGGPOey0nbwi0Ow.gif" /><figcaption>End result</figcaption></figure><p>Full video of the entire process-</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEvCF833XOIg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEvCF833XOIg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEvCF833XOIg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a1909976aa3077774068b9133015840/href">https://medium.com/media/2a1909976aa3077774068b9133015840/href</a></iframe><p>The very fact that we’re getting all this free is amazing. It’s still not there yet, but it’s constantly improving. It can be a great utility to handle mundane tasks so that we as a developer can spend more time doing quality work. Can’t wait to use it for day-to-day tasks at work 😜. What if it takes over our jobs? Let me know your thoughts in the comments!</p><p><em>Also, can it center a div?</em> Yes!</p><p><em>More content at </em><a href="http://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a863e7ce3a0d" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/i-instructed-github-copilot-to-code-instagram-profile-feed-infinite-scroll-in-react-this-is-a863e7ce3a0d">I instructed GitHub Copilot to code an Instagram profile feed in React. Here’s what happened.</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ace a UI Engineer Interview]]></title>
            <link>https://javascript.plainenglish.io/how-to-ace-a-ui-engineer-interview-1cfbdcf2ec83?source=rss-25a08b9a9a36------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cfbdcf2ec83</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Ayush Singh]]></dc:creator>
            <pubDate>Sat, 11 Sep 2021 14:23:19 GMT</pubDate>
            <atom:updated>2021-09-28T14:48:01.744Z</atom:updated>
            <content:encoded><![CDATA[<h4>I was recently interviewed at Flipkart, Paytm, RazorPay, PhonePe, BharatPe, and others. I received multiple offers (and a few rejections as well). Sharing a consolidated guide where I document everything.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_gtAff9V5bL7RHzTtpl8Bg.jpeg" /><figcaption>Road to UI Engineering</figcaption></figure><blockquote>As a UI/frontend Engineer, you have to keep up with a lot of things. This guide will enable you to link missing pieces in your equation, and hopefully, land you your dream job!</blockquote><h3>Prerequisite — Prepare a plan</h3><p>I started my preparation journey without keeping a track of things 1.5 years ago. I was doing things all over the place. As you might imagine, things didn’t work out. It was time to prepare a strategy!</p><blockquote>If you <strong>fail</strong> to <strong>plan</strong>, you <strong>plan</strong> to <strong>fail</strong>!</blockquote><h4>I documented my learnings on Notion</h4><p>It was a game-changer. Everything you learn, topics you need to revisit, topics that are relatively hard, all under one roof as a Drag-Drop Kanban board.</p><figure><img alt="My Kanban on Notion" src="https://cdn-images-1.medium.com/max/1024/1*9VGO7drYYSni4WmuK_XdBA.png" /><figcaption><a href="https://alphaayush.notion.site/alphaayush/2e13395deff94a428d45b3aa88dc7ee7?v=06b5c5617b8442bc878bd210257786ad">My Kanban on Notion</a></figcaption></figure><p>I am sharing the link of my Kanban Board, Feel free to create a copy of it, and customize it as per your needs.</p><p><a href="https://alphaayush.notion.site/2e13395deff94a428d45b3aa88dc7ee7?v=06b5c5617b8442bc878bd210257786ad">UI Engineer - Prep Resources</a></p><h4>Okay, but how to use it?</h4><ul><li><strong>Document Everything!</strong></li></ul><p>Read an informative article? Embed it! Eureka moment? Note that down!</p><ul><li><strong>List down everything you already know.</strong></li></ul><p>For all the topics which you already understand, create cards for those.</p><ul><li><strong>Feel free to divide things into subtasks</strong></li></ul><p>If you feel the topic has too many things to cover in a single go, that is your hint to divide it into subtasks.</p><ul><li><strong>Assign a difficultly level based on your understanding of the topic</strong></li></ul><p>This will come in handy when it’s show-time and revision.</p><ul><li><strong>Don’t hesitate to keep expanding the scope.</strong></li></ul><p>For things, you don’t realize you don’t know.</p><ul><li><strong>Read interview experiences for preparing the list.</strong></li></ul><p>Confused about where to start? Read interview experiences online (from Leetcode discuss, Team Blind, Online blogs, GeeksForGeeks) to prepare a list of topics you need to study.</p><blockquote>Don’t try to mug things up for the sake of the interviews. Enjoy the learning process &amp; be consistent with your plan.</blockquote><h3>Execute your plan 🚀</h3><p>Okay, now that you’re ready with a solid plan, It’s time for execution!</p><h4>My 5 pillar approach to UI Engineering</h4><ol><li>JavaScript (In-Depth)</li><li>Data Structures and Algorithms</li><li>Problem Solving</li><li>Frontend frameworks &amp; libraries</li><li>UI Technologies &amp; Challenges</li></ol><p>I will touch on these topics in brief over here. All links and resources for a detailed plan can be found on my Notion.</p><h4>1. JavaScript (In-Depth)</h4><figure><img alt="Javascript" src="https://cdn-images-1.medium.com/max/1000/1*xFKNZicAbYqBDiNszynrzQ.jpeg" /><figcaption><a href="https://dev.to/mr_victor/the-history-of-javascript-1fp3">Pic Courtesy: Victor</a></figcaption></figure><p>Goes without saying how important it is to know JavaScript. Here are some topics to know well:</p><ul><li>Inheritance + Prototype Chain</li><li>Closures &amp; Hoisting</li><li>Scope &amp; Execution context</li><li>this Keyword</li><li>Functional Programming</li><li>Latest features: ES6, ES7, ES8, ES9, ES10, ES2020</li><li>Module Patterns — ES6/AMD/UMD/FESM</li><li>Object-Oriented Programming</li><li>Event Loop and how JS works under the hood</li><li>Event Delegation/Event Bubbling</li><li>Array, String, Object, Function, and Promise methods</li><li>and much more I forgot</li></ul><p>Refer to the JavaScript module in my Notion board.</p><h4>2. Data Structures and Algorithms</h4><figure><img alt="Data Structures and Algorithms" src="https://cdn-images-1.medium.com/max/737/1*hp07Q6qWlQrhGuk-zYGhrA.jpeg" /></figure><p>I always dreaded DSA back in college time. Questioned that why a Frontend Engineer needs to know all this. I started learning DSA back in 2019, with no intention to finish by any deadline. Had to revisit the same concepts multiple times.</p><p>Finally, a year ago, I decided to change this. Started learning from a DSA Udemy course. Began with easy questions on Hackerrank and Leetcode. Eventually gained confidence and started the Blind 75 &amp; LC Interview series for learning problem-solving patterns. I quickly realized how much this has helped me in my day-to-day tasks as a Frontend Engineer.</p><p>How much PS/DSA for UI Engineers?</p><ul><li>Linked Lists (SLL/DLL)</li><li>Strings / Arrays</li><li>Trees (BST)</li><li>Stack/Queues</li><li>Heap (Priority Queue)</li><li>Hash Maps</li><li>Graphs (Basic)</li><li>Dynamic Programming (Memoization)</li></ul><p>For more insights, Refer to the DSA module in my Notion board.</p><h4>3. Problem Solving</h4><p>Frontend problem solving can be divided as follows:</p><ul><li><strong>Polyfill based problems</strong></li></ul><p>E.g: Write a polyfill for Array map/reduce/filter, Set, Map, Promise.all, Object.create, setInterval, EventEmitter, Observable, etc</p><ul><li><strong>DOM API related problems</strong></li></ul><p>E.g.: Traverse DOM level by level, Implement Virtual DOM like React, Write a basic Diffing algorithm, Find unique tags in a given DOM tree, DOM tree height, etc</p><ul><li><strong>Function-based problems</strong></li></ul><p>Lodash methods like _.get, _.set, _.cloneDeep, etc. Flattening a multi-dimensional array, Currying problems, Generic composition &amp; pipes, debounce, throttling, etc</p><figure><img alt="BFE.dev" src="https://cdn-images-1.medium.com/max/482/1*v6FpMx_x0sF2VWM-V2xHrg.png" /></figure><p><a href="https://bigfrontend.dev/problem">BFE.dev</a> is a great resource for the above-mentioned problems. Also, you can find my solutions for all kinds of problems in my Notion BFE card.</p><h4>4. Frontend frameworks and libraries</h4><figure><img alt="Frontend frameworks and libraries" src="https://cdn-images-1.medium.com/max/1024/1*--69eZ7Mh28oE6udIATmMA.jpeg" /><figcaption><a href="https://chsvk.medium.com/vue-vs-angular-vs-react-in-2019-answered-4ec8dc96e602">Pic courtesy: Vamshi</a></figcaption></figure><p>Frameworks and libraries can be very opinionated. I personally learned Angular (v2+, not v1) back in 2016 for a college project. I did multiple large-scale enterprise projects using the framework. Last year, I decided to jump on React train. If you’re well versed with how SPAs work, it’s easy to switch between the ecosystems. I like both Angular and React, and both can be useful in different use cases. But, that’s a topic for another day.</p><p>I would suggest picking one and learn in-depth. Question everything! How does routing actually work? What are EventEmitter/Observables? How to prevent re-renders in your app. Advantages of components? Or maybe, do you even need a framework/library for your project?</p><p>Since I was getting started with React a year ago, I have curated resources that I used to learn. Refer to React card on my Notion.</p><h4>5. UI Technologies &amp; Challenges</h4><p>Once you’re well versed with JavaScript and a framework. It’s time to study more advanced concepts. Some topics you can find on my Notion:</p><ul><li>Web Performance and JANK reduction (Very important skill)</li><li>Progressive Web Application (PWAs)</li><li>State management strategies — Redux, RxJS</li><li>Data flow — Flux architecture, 2-way data binding</li><li>Change detection/Reconciliation</li><li>Server-side rendering/Static site generation</li><li>Web security — XSS/CSRF/Clickjacking/Auth</li><li>Virtual Scroller</li><li>Infinite Scroller</li><li>JavaScript Proxy</li><li>Deployment strategy — CDN/Caching/HTTP2/SSL</li><li>Core Web Vitals</li><li>Symbols, Generators, and Iterators</li><li>Frontend System Design</li></ul><p><strong>Some UI challenges that I developed on Vanilla JS (</strong><a href="https://github.com/ayush013/ui-bootcamp"><strong>Github link</strong></a><strong>):</strong></p><ul><li>Calendar</li><li>Todo</li><li>Carousel</li><li>nth-level comment widget</li><li>Giphy search engine with the infinite scroller</li><li>Task tracker (kanban)</li><li>JS-only SPA like Routing</li><li>Email app (Gmail/Outlook)</li><li>Tic tac toe</li></ul><figure><img alt="UI challenges" src="https://cdn-images-1.medium.com/max/1024/1*DPTnJJWubT9m-3JwE2Iv9Q.jpeg" /></figure><p>Usually, you might encounter these challenges in MC/OA rounds of interviews. Many companies recommend these to be developed without frameworks on Vanilla JS. Use of module bundlers is allowed so you can prepare scaffold beforehand. Split your code into an MVC pattern. Give yourself around 2–3 hours while developing these to mock the interview environment. More details on the Notion.</p><h3>Bringing it all together — It’s Showtime!</h3><p>A sample 5 week training plan could look something like this:</p><figure><img alt="5 week plan" src="https://cdn-images-1.medium.com/max/1024/1*f7rGnKbQ7xrGtX3WtQDYyg.jpeg" /><figcaption>Can be repeated for multiple weeks until you’ve covered all the topics</figcaption></figure><p>Remember I told you, don’t study for the sake of interviews. Eventually, you will feel so confident about the topics that you can answer questions/write code right off the bat! Once you’ve gone through your Prep strategy at least once, all you have to do is to revise your weak areas before the interview.</p><figure><img alt="Last read on cards" src="https://cdn-images-1.medium.com/max/1024/1*vbH5Ei6jEUVHkBRwZSfxxQ.png" /></figure><p>You already know what you need to revise because everything is well documented. Notice how every card has a key for capturing ‘Last Read’.</p><p>This will help you pick the right cards before going through a loop.</p><p>PS: Don’t study new topics right before the interviews</p><h3>My interview experiences</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEjRsS5Tkmztj-preG-JOQ.png" /><figcaption>An onsite a day keeps nervousness away</figcaption></figure><p>Now the fun stuff! With all this preparation, it was time to attempt the interviews. As I mentioned, I won’t be sharing exact questions. You should be able to answer these if you’ve followed the prep guide.</p><h4>1. Paytm</h4><p><strong>How did I apply- </strong>I contacted the recruiter.</p><p>The entire process took about 10 days. There were 4 rounds in total:</p><ol><li><strong>Online Assessment:</strong></li></ol><p>A Mettl test link was shared. There were around 20 questions in total:</p><ul><li>One question for implementing IE compatible DOM APIs for a layout</li><li>5–6 questions on AngularJS (Yes! Angular 1 😅)</li><li>5–6 questions on React.</li><li>7–8 JavaScript &amp; HTML/CSS output based questions.</li></ul><p><strong>2. Problem-Solving round:</strong></p><ul><li>Questions about my Resume projects</li><li>Problem-solving question on Array/Hashmap</li><li>JS Concepts like Promises, async/await, event loop, call, bind</li><li>CSS basics and HTML semantics</li><li>Basic React questions</li></ul><p><strong>3. Data Structures round:</strong></p><ul><li>Questions about my recent project and why I used SSR/SSG approach</li><li>Output-based questions on type coercion, sparse arrays</li><li>Array data structure problem</li><li>Binary tree problem involving DFS</li></ul><p><strong>4. Hiring Manager round:</strong></p><ul><li>Questions about my Resume projects</li><li>Web security questions</li><li>Discussion on culture, roles, and responsibilities</li></ul><h4>2. Flipkart</h4><p><strong>How did I apply- </strong>I applied on the careers portal 2–3 months before getting a call.</p><p>The entire process took about 8 days. There were 4 rounds in total:</p><p><strong>1. Machine Coding round:</strong></p><ul><li>Create an application based on a written problem statement.</li><li>API endpoints were provided</li><li>Vanilla HTML/CSS/JS was expected</li><li>I followed the ES6 module and MVC pattern</li><li>Webpack bundler was allowed, so prepare a scaffold beforehand</li><li>Finished a running code in about 1 hour 20 mins, we later discussed things I would improvise if I had more time.</li><li>We discussed about Intersection Observer and Symbols.</li></ul><p><strong>2. UI Tech round:</strong></p><ul><li>Questions about my Resume projects</li><li>A problem statement involving Recursion</li><li>An in-depth discussion on Web performance</li><li>Some JavaScript concepts</li></ul><p><strong>3. Problem-solving round (PS/DS)</strong></p><ul><li>A problem on linked lists (leetcode easy)</li><li>A problem related to array intervals</li><li>A problem related to strings</li></ul><p><strong>4. Hiring manager round</strong></p><ul><li>An in-depth discussion on my background and journey so far</li><li>In-depth analysis on my decisions and work on one of my projects</li><li>Pretty standard HM questions</li></ul><h4>3. BharatPe</h4><p><strong>How did I apply- </strong>I applied on their careers portal when I saw they’re offering BMW bikes and 1 month Dubai workation 😛</p><p>The entire process took about 10 days. There were 5 rounds in total:</p><ol><li><strong>Technical discussion with CTO:</strong></li></ol><ul><li>About my journey, interests, and future plans</li><li>1 question around a simple lodash helper method implementation</li><li>Discussion about BharatPe and future plans</li></ul><p><strong>2. UI Technologies</strong></p><ul><li>Questions about my Resume projects</li><li>React concepts like Pure Components, Reconciliation, Memoization, etc</li><li>JS questions on closures, event loop, Microtasks/Macrotasks</li><li>Service workers and web workers</li><li>Other basic frontend questions</li></ul><p><strong>3. Home Assignment</strong></p><p>Take-home assignment to be made in under 48 hours. Use of frameworks was allowed, Bonus points for React, Good UI, and Optimised code. Since I already practiced UI challenges during my prep, I made my submission in 4 hours.</p><p><strong>4. Technical Discussion:</strong></p><ul><li>Introduction and resume based questions</li><li>Code reviews and practices</li><li>Tech stack I use</li></ul><p><strong>5. Cultural Fitment round:</strong></p><ul><li>My Career aspirations</li><li>What is my plan for the next 5 years</li><li>Questions on my entrepreneurial gig</li><li>Basically checking if I am fit culturally</li></ul><h4>4. RazorPay</h4><p>At this point, I was already holding the above offers. Had signed an offer with Flipkart. The entire process took 5 days, there were 4 rounds in total:</p><ol><li><strong>Tech Deep Dive</strong></li></ol><ul><li>Fair discussion on my resume pointers</li><li>SSR/SSG and why did I use</li><li>An in-depth discussion on UI scenarios (React)</li><li>Redux v/s Context API</li></ul><p>Expectations: Solid frontend career, React knowledge was a must</p><p>2. <strong>UI Challenge:</strong></p><ul><li>Create an application based on a written problem statement.</li><li>Use of React was recommended, I prepared a scaffold beforehand.</li><li>Styling wasn’t expected, I did basic styling and layout using Tailwind</li><li>Solved the problem using Intersection Observer and React Hooks</li><li>Finished a running code (with one bug) in about 1 hour 10 mins, we discussed the strategies to mitigate it.</li></ul><p><strong>3. Web fundamentals round:</strong></p><ul><li>An in-depth discussion on Cross-origin resource sharing</li><li>Scenario-based problems assessing my decision making</li><li>Open-ended conversation on Web performance and JANK reduction</li><li>Web security and vulnerability mitigation strategies</li><li>React v/s Angular — key differences, pros/cons</li></ul><p><strong>4. HM round</strong></p><p>I was ghosted for a while, One of those days when I did not perform well so I didn’t contact either. The above rounds were the learning experience I was looking for.</p><h4>5. PhonePe</h4><p>The entire process took about 1 month, I had applied 3–4 months before actually receiving OA over email. There were 4 rounds in total:</p><ol><li><strong>Online Assessment</strong></li></ol><ul><li>90-minute test on Codesignal IDE with Camera and Screen sharing</li><li>1 DSA question on Strings/DP (hard)</li><li>2 JS Debugging questions</li><li>5 React MCQ</li><li>5 JS MCQ</li><li>Some other HTML/CSS questions that I forgot</li></ul><p><strong>2. UI Tech round</strong></p><ul><li>Questions from my resume and introduction I gave</li><li>JANK reduction strategy, Critical rendering path entire lifecycle</li><li>Standard CSS questions</li><li>React Memoization and a problem to code a generic memo function</li><li>One question on writing a polyfill</li><li>Redux pattern and data flow, React lifecycle hooks</li></ul><p><strong>3. Problem solving round (PS/DS)</strong></p><ul><li>One question around an n-ary tree to code a React-like diffing algorithm.</li><li>Sample inputs for Virtual DOM and Real DOM objects were given</li><li>It was a BFE style problem, with multiple edge cases</li><li>I coded 2 out of 3 edge cases</li><li>Discussion on time complexity and optimizations I would do to my code</li><li>Overall, the best DSA round experience I ever had</li></ul><p><strong>4. HM round</strong></p><p>I was ghosted for a while. I got a rejection mail after 2 weeks, which I didn’t expect considering I performed pretty decently. Nonetheless, free practice :)</p><p><strong>Other offers: </strong>2 early-stage startups, had similar interview experiences.</p><h3>Mindset &amp; Personality Development</h3><p>No matter how skilled you are, if you aren’t a good communicator, things can turn against you. There are certain questions that interviewers ask almost every candidate, in an attempt to get a read on their personality and potential. You’ll likely be asked about your strengths and weaknesses, your leadership style, and other basic professional attributes. This LinkedIn course will help you understand the psychology behind the questions.</p><p><a href="https://www.linkedin.com/learning/expert-tips-for-answering-common-interview-questions/">Expert Tips for Answering Common Interview Questions Online Class | LinkedIn Learning, formerly Lynda.com</a></p><p>Lastly, some underrated advice. You can skip this if you feel too confident :)</p><h4>Dopamine detox</h4><p>I don’t know where you’re coming from, but if you are someone who gets distracted easily, you may follow these steps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/237/1*c3dhgsGOMxF3rSi8ipGNbw.jpeg" /><figcaption>Dopamine detox</figcaption></figure><ul><li>Try to incorporate a fitness regime</li><li>Eat clean food</li><li>Caffeine, maybe?</li><li>Envision yourself in your dream company — Yes, that should be your dopamine rush</li><li>Meditation can be helpful too</li></ul><p>I personally am a fitness freak. I’ve been lifting for the past 6 years now. Every morning I chugged my caffeine pills and hit an intense weight training session. That helped me stay focused for the rest of the day.</p><h4>Enjoy the process than the outcome</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*hG7ipQZ_zj2QYi6XYOGTXg.jpeg" /><figcaption>IKIGAI</figcaption></figure><ul><li>It’s the passion that should drive the fire inside you.</li><li>Good things take time.</li><li>Results are just a matter of time.</li><li>The interview always has a touch of a lottery.</li><li>A big part of it is pure luck.</li><li>Stop taking this personally and start treating it like a game or a sport that requires strategy and prep.</li><li>An interview is a 2-way street, think of it as a discussion</li></ul><blockquote>Rejection? I call it free practice!</blockquote><p>Just do what needs to be done and don’t care about results.</p><p>I recently joined the company I was literally dreaming of! Had lots and lots of learnings during my prep and interview cycles. And what gets me excited is that this is just the beginning of my journey at Flipkart. I hope this will help you ace your interviews. But what about landing an interview? Well, that’s a story for another day!</p><p>For more updates give me a follow:</p><ul><li><a href="https://www.linkedin.com/in/alphaayush/">Ayush Singh - UI Engineer - Flipkart | LinkedIn</a></li><li><a href="https://twitter.com/ayush013">JavaScript is not available.</a></li></ul><p><em>More content at </em><a href="http://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cfbdcf2ec83" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/how-to-ace-a-ui-engineer-interview-1cfbdcf2ec83">How to Ace a UI Engineer Interview</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 more mistakes frontend developers commit that UX engineers hate]]></title>
            <link>https://uxdesign.cc/5-mistakes-frontend-developers-commit-that-ux-engineers-hate-part-2-7833b3bd80be?source=rss-25a08b9a9a36------2</link>
            <guid isPermaLink="false">https://medium.com/p/7833b3bd80be</guid>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Ayush Singh]]></dc:creator>
            <pubDate>Sun, 09 Aug 2020 15:27:53 GMT</pubDate>
            <atom:updated>2021-09-08T11:57:50.113Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eBFmXX9SvObbHwIf" /><figcaption>Photo by <a href="https://unsplash.com/@punttim?utm_source=medium&amp;utm_medium=referral">Tim Gouw</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>In continuation to my previous article, Here’s another set of five common examples of Bad UX we see in everyday life over the web. In case you haven’t read Part-1, here’s the link:</em></p><p><a href="https://uxdesign.cc/5-mistakes-frontend-developers-commit-that-ux-engineers-hate-and-how-to-fix-part-1-e1175af60bbb">5 mistakes frontend developers commit that UX engineers hate</a></p><h3>So what’s the deal?</h3><p>User experience is how a person feels when interacting with a system. Undoubtedly, UX is driven by good frontend aesthetics and architecture. A good UX leaves an everlasting imprint on the user. But oftentimes things are missed and overlooked on the frontend level which can be a dealbreaker. Here’s the list of 5 things which you shouldn’t be doing:</p><h3>6. Layout Shifts / Content Reflow</h3><figure><img alt="Layout instability" src="https://cdn-images-1.medium.com/max/1024/1*lbPHYbFOBwMs7yN4hcmjeA.gif" /><figcaption>Layout instability — Source: <a href="https://web.dev/cls/">https://web.dev/cls/</a></figcaption></figure><p>Indeed, that was a memorable User Experience! Layout shifts usually happen due to one of these:</p><ul><li>Resources asynchronously inserted in DOM, Like an info-box for a completed action</li><li>An image/video of unknown dimensions</li><li>A random third-party ad pops in out of nowhere</li></ul><p>Luckily, for us, Google has laid down great tooling and web vital metrics for detecting and quantifying Layout shifts. The Cumulative Layout Shift (CLS) metric helps you address this problem by measuring how often it’s occurring for real users. Head over to <a href="https://web.dev/cls/">https://web.dev/cls/</a> for detailed info.</p><figure><img alt="CLS Rating" src="https://cdn-images-1.medium.com/max/1024/1*SpCKdPuBlNZP2WG0q2S5rg.jpeg" /><figcaption>CLS score ratings</figcaption></figure><p><strong>Always do the following:</strong></p><ul><li>Pre assign height and widths on images and video elements</li><li>Try to serve low-quality placeholders for images beforehand so that user knows what’s incoming</li><li>Reserve the required space for dynamic content</li></ul><h3>7. Lack of State management</h3><p>State management is an art of managing ‘state’ like:</p><ul><li>Data persistence</li><li>Information flow</li><li>I/O (networking and caching)</li><li>and so on...</li></ul><p>The web we consume in 2020 is mostly based on Single Page Applications (SPAs). As soon as the bundle is loaded, route handling is taken care of by the Client-side. Oftentimes, switching between the routes there are a bunch of API calls associated with the data to be consumed.</p><p><strong>Should you make multiple API calls switching back and forth from routes? No!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*trrKT-ijc0FFPCUUqROw1g.gif" /><figcaption>Unnecessary API calls switching back and forth routes</figcaption></figure><p>Leverage the use of state management, if not using a full-fledged library, at least on the service layer.</p><p>Here’s an example of state management at the Service layer using rxjs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*oFHtAWXYiBzfOWJe35nXMA.gif" /><figcaption>Notice how popstate is not causing new API Calls</figcaption></figure><p>With this approach, you can also implement Websockets to request any new data without interrupting/blocking the user.</p><h3>8. Doing heavy lifting on Client-side</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*9ldqWQpaE7eZ7M2rdnxIZw.png" /><figcaption>Pic courtesy: <a href="https://www.instagram.com/p/CDmXzNHJNaA/">Omar Isuf</a></figcaption></figure><p>Every user has a different device, especially on mobile with limited resources it’s not possible to expect the same performance as the desktop browser. While this is improvising with continuous efforts by Chromium and Mozilla, you should always consider before doing such operations:</p><ul><li>Image optimization/Compression in the web browser</li><li>Video conversion in browser</li><li>Non-vector image manipulations</li></ul><p>Always perform these operations on the Web Server. It’s more capable and can be scaled according to the use case.</p><h3>9. Scroll Hijacker</h3><p>It’s really annoying when a native scroll event doesn’t happen the way it should. The reason hijacking is controversial as browser scrollbars belong to the browser window and they’re meant to provide a uniform experience. Scroll hijacking is typically accomplished through JavaScript, so it’s not controlled via the browser or the operating system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*lJRNar7fK_zCVvSn4v7GDQ.gif" /><figcaption>Inertia Scroll example</figcaption></figure><p>Momentum scroll, while may look eye-pleasing at first gets really dizzy and annoying. Scroll hijacking leaves users confused than satisfied.</p><blockquote>Just because you can do it, doesn’t mean you should do it.</blockquote><p>Let browser take the control. Don’t hijack it! Stop forcing people to watch mediocre transitions with terrible in-betweens when you stop scrolling.</p><h3>10. The mobile hater</h3><p>Back in 2010, when I first started consuming the web on a mobile device, things were different. I never heard about UX, RWD. For most of the websites, they used to be loaded as one big canvas as seen on desktop and we had to pinch-zoom in to consume content on rather tiny 2.5-inch screens. Things have changed now. Mobile accounts for approximately<a href="https://www.statista.com/statistics/277125/share-of-website-traffic-coming-from-mobile-devices/#:~:text=Mobile%20accounts%20for%20approximately%20half,since%20the%20beginning%20of%202017."> half of the web traffic worldwide</a>. In the second quarter of 2020, mobile devices (excluding tablets) generated 51.53 percent of global website traffic, consistently hovering around the 50 percent mark since the beginning of 2017.</p><p><strong>“But it works on my Desktop!” — </strong>Every Developer ever</p><blockquote>A good design should work great on every screen resolution. Period!</blockquote><p>Don’t assume, Prepare for the worst. Regardless of your system configuration test the layout for every breakpoint. Chrome dev tools offer great tools for testing websites against common breakpoints. Also, as tech is evolving users are having screen resolutions up to 4k. Test for those as well.</p><p>Great CSS utility and frameworks are available too:</p><ul><li>Tailwind CSS</li><li>Twitter Bootstrap</li><li>Dead Simple Grid</li></ul><p>Use rem units in CSS, They’ll save you time and effort. They are a savior for RWD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*r-8ZC2x-xuqXZaZA" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7833b3bd80be" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-mistakes-frontend-developers-commit-that-ux-engineers-hate-part-2-7833b3bd80be">5 more mistakes frontend developers commit that UX engineers hate</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 mistakes frontend developers commit that UX engineers hate]]></title>
            <link>https://uxdesign.cc/5-mistakes-frontend-developers-commit-that-ux-engineers-hate-and-how-to-fix-part-1-e1175af60bbb?source=rss-25a08b9a9a36------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1175af60bbb</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Ayush Singh]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 16:36:19 GMT</pubDate>
            <atom:updated>2020-07-05T15:37:59.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Facepalm" src="https://cdn-images-1.medium.com/max/1024/1*zDIngyvjckSJ3AG4ErO9RQ.jpeg" /><figcaption>Stab to the UX, which we often see</figcaption></figure><p><em>This is Part-1 of the series of articles where I discuss the most common examples of Bad UX we see in everyday life over the web.</em></p><h3><strong>So what’s the deal?</strong></h3><p>User experience is how a person feels when interacting with a system. Undoubtedly, UX is driven by good frontend aesthetics and architecture. A good UX leaves an everlasting imprint on the user. But oftentimes things are missed and overlooked on the frontend level which can be a dealbreaker. Here’s the list of 5 things which you shouldn’t be doing:</p><h3><strong>1. Unhandled FOUC 😳</strong></h3><p>Have you ever noticed an annoying <em>“flash of unstyled content”</em> (FOUC) when a web page first loads? This happens when markup is rendered prior to loading an external stylesheet/javascript bundle.</p><figure><img alt="FOUC on wikipedia page" src="https://cdn-images-1.medium.com/max/1000/1*1sZWtm7HhrJqNisjHaJujA.jpeg" /><figcaption>Wikipedia&#39;s page for FOUC definition getting owned by FOUC</figcaption></figure><p>The problem is more prominent for users with slow internet connections, and trust me it creates a bad first impression for a potential customer.</p><p><strong>Alright, so how do I fix it?</strong></p><p>Well, there are many solutions, The classical solution recommends hiding the body until DOMContentLoadedis fired. But how about UX? Not so intuitive!</p><p>I recommend the use of a nice preloader, It keeps the user engaged for those milliseconds, and reduces the perceived time.</p><p><strong>So should I throw in a Spinner? NO! </strong>Let’s be honest, Spinners are too mainstream.</p><blockquote>It’s important to give the user a context of what’s happening.</blockquote><p>Here’s what you could do instead:</p><ul><li>Use Attractive animations rather than a spinner</li><li>Give them the actual reason-</li></ul><p>Example: “Please wait while we are setting things up” message clubbed with an animated company logo or something. I personally use <a href="https://github.com/airbnb/lottie-web">Bodymovin</a> or <a href="https://greensock.com/gsap/">GSAP</a> for creating one.</p><figure><img alt="Android Boot animation by Google" src="https://cdn-images-1.medium.com/max/800/1*f50TsdVSRAp2I7rmg6Dy1g.gif" /><figcaption>Notice how android bootsplash is intuitive enough to reduce perceived load time</figcaption></figure><h3>2. Indeterminate loaders 😓</h3><p>Talking about spinners, there’s a wrong and right way to use them. Spinners and progress bars are <strong>explicit loading paradigms </strong>which<strong> </strong>I often see being used almost everywhere in the application.</p><figure><img alt="Traditional loaders" src="https://cdn-images-1.medium.com/max/1024/1*AZZCtAOuUem_vQbzKAfgUg.jpeg" /><figcaption>Common loading paradigms</figcaption></figure><p><strong>The solution: Skeletons</strong></p><p>Skeleton screens are blank pages that are progressively populated with content, such as text and images, as they become available (i.e. when network latency allows).</p><blockquote><strong>Skeletons reduce perceived loading time. </strong><a href="https://uxdesign.cc/what-you-should-know-about-skeleton-screens-a820c45a571a"><strong>Read more here</strong></a></blockquote><figure><img alt="Skeleton loader" src="https://cdn-images-1.medium.com/max/1024/1*KXjzlXJDQ_6oVarlrNezmw.png" /><figcaption>Usage of shimmer skeletons gives a predictable structure before the actual content is loaded</figcaption></figure><p><em>NOTE: Content should replace skeleton objects when the data is available</em></p><h3>3. Too many change detections 😱</h3><p>If you’re using a frontend framework like Angular you might have used HostListeners for scroll events. While they’re not problematic for the most part unless there are too many different listeners from different components. This results in performance degrade and a noticeable decrease in FPS. Moreover, If there’s some variable being re-evaluated and sent as an input to other components, it only adds up to the issue.</p><figure><img alt="Change detections on devtools" src="https://cdn-images-1.medium.com/max/546/1*g2OyjpgCNCAbl4oPDBYzjg.gif" /><figcaption>Change detection cycles in faulty component using a counter and ngDoCheck() hook</figcaption></figure><p><strong>How to fix change detections?</strong></p><ul><li><strong>Method 1:</strong> Angular uses <strong>Zone</strong>. <strong>js </strong>for encapsulating and intercepting asynchronous activities in the browser (e.g. setTimeout, addEventListener, etc). Each time the event is fired, NgZone notifies Angular, which causes a new change detection cycle to run unless your component change detection strategy is set to onPush or Detach</li></ul><p>Luckily for us, we can instruct ZoneJS with events not to be patched. I won’t be covering the solution here,<a href="https://netbasal.com/optimizing-angular-change-detection-triggered-by-dom-events-d2a3b2e11d87"> refer to a beautiful explanation over here</a></p><ul><li><strong>Method 2: </strong>If you’re using a custom animation library like GSAP or any other asynchronous calls activity (say setInterval) which you don’t want Angular to take care, leverage the use of <strong>runOutsideAngular. </strong><a href="https://medium.com/@krzysztof.grzybek89/how-runoutsideangular-might-reduce-change-detection-calls-in-your-app-6b4dab6e374d">Read more on this here</a></li></ul><h3>4. Lack of transition states and Microinteractions 😐</h3><p>Probably the biggest drawback of developer handoff is the lack of set guidelines for transition states and micro-interactions.</p><p>I blame it for the <strong>lack of a proper design system</strong>.</p><p>Instead of having property changes take effect immediately, you should prefer to have changes in a property to take place over a period of time.</p><p>Why? <strong>Animation matters</strong>. It can be used to improve the user experience.</p><figure><img alt="Transition states example" src="https://cdn-images-1.medium.com/max/600/1*65eIw9VQdY9KyuQ3xQ2w7Q.gif" /><figcaption>Transition states improve the experience (but don’t overdo it)</figcaption></figure><p>We have all the technology to do this page transitions stuff on the web. Why don’t we do it? Is it because we don’t want to? Is it because we don’t think that’s part of our job?</p><figure><img alt="Microanimation example" src="https://cdn-images-1.medium.com/max/600/1*5bUvL87Me5AISUZBLJF4Jw.gif" /><figcaption>Courtesy: Email validation micro-interaction by<a href="https://dribbble.com/shots/10197121-Email-validation"> Aaron of dribbble</a></figcaption></figure><ul><li>Using borders on hover state? Make sure your elements <strong>don’t</strong> shift to the bottom when the borders appear.</li><li>Using hover on buttons? Give it a nice little transition state.</li></ul><p>Spend some time learning about CSS transitions. Do it for the good. Inculcate a design system with values matching your company’s profile. With little effort, time, and a bit of code you can turn <strong>good experience to a great experience</strong>.</p><h3>5. The pessimistic UI rendering 😒</h3><p>This one is really common. Let me explain, Web has changed a lot in a decade. So have the users. The reactive paradigm has been a groundbreaking improvement in the overall experience, but with great power comes great responsibility!</p><blockquote>User hate to wait. They want everything in a blink of an eye.</blockquote><p>Being able to render content without having to refresh or switch pages has become a necessity in UI, and something that users expect out of the box. Users demand content to appear instantaneously but it still takes time to process requests and return content to the user. While this may only take a few seconds, it’s not *instantaneous* and it has a noticeable effect on user experience. It’s a pessimistic approach to UI.</p><p><strong>So how can a developer provide a more instantaneous experience?</strong></p><p>Leverage the use of optimistic user interface. In an optimistic UI, you don’t keep the user waiting for a response. Instead, you assume that the response will succeed, and provide them with the relevant response right away. So if a user is posting a comment, or sending a message, you render it immediately without waiting for the response. Then if the server responds with a failure to save the record, you may re-render the content section with an error message</p><figure><img alt="Optimistic UI rendering" src="https://cdn-images-1.medium.com/max/600/1*yQY6o8_CvT7C88WDlj8X0w.gif" /><figcaption>Optimistically adding table entry before receiving the actual response from the server.</figcaption></figure><p><strong>NOTE: Optimistic rendering is not appropriate for all use cases: Failure to complete the action should not result in a high cost. </strong>For actions like posting a comment, or liking content; you’re good to go!</p><p>And that’s a wrap! I have a lot more UI/UX quirks in my head. Will share them over the course of time. This is my first article on Medium, go easy on me, comments and suggestions are appreciated. Hope you enjoyed it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*njNPfwB97x_mgjTN" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1175af60bbb" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/5-mistakes-frontend-developers-commit-that-ux-engineers-hate-and-how-to-fix-part-1-e1175af60bbb">5 mistakes frontend developers commit that UX engineers hate</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>