<?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 Adarsh Nanwani on Medium]]></title>
        <description><![CDATA[Stories by Adarsh Nanwani on Medium]]></description>
        <link>https://medium.com/@adarsh.nanwani?source=rss-ce3062470fe1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aan7cjiqfZHM8BUqOLBTBg.jpeg</url>
            <title>Stories by Adarsh Nanwani on Medium</title>
            <link>https://medium.com/@adarsh.nanwani?source=rss-ce3062470fe1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:08:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adarsh.nanwani/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[Let’s implement Promise in TypeScript from scratch]]></title>
            <link>https://medium.com/@adarsh.nanwani/lets-implement-promise-in-typescript-from-scratch-c25c5d66c14f?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c25c5d66c14f</guid>
            <category><![CDATA[promises-in-javascript]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Mon, 20 Oct 2025 09:37:37 GMT</pubDate>
            <atom:updated>2025-10-20T09:37:37.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NK8jTGfdEp0gGIuO" /><figcaption>Photo by <a href="https://unsplash.com/@andrewwwpetrov?utm_source=medium&amp;utm_medium=referral">Andrew Petrov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">Promises</a> in JavaScript are a critical tool for asynchronous programming. They provide a cleaner API to handle asynchronous operations compared to callbacks.</p><p>Promises are crucial to building a deeper understanding of JavaScript and are equally important for mid-level to senior-level Frontend developer interviews.</p><p>A <em>Promise</em> is basically a placeholder object that will have some value in the future. You can handle both success and error cases by utilizing <em>then</em> and <em>catch</em> methods provided on the promise object. For example,</p><pre>const orders = fetch(&#39;/api/orders&#39;, {method:&quot;GET&quot;}); // returns a Promise<br><br>orders<br>.then(function(response) {<br>  return response.json()<br>})<br>.then(function(data) {<br>  console.log(data) // logs the orders on the console<br>})<br>.catch(function(err){<br>  console.log(err) // logs the error<br>})</pre><h3>Anatomy of a Promise</h3><p>A Promise can be in one of three states:</p><ol><li><strong>Pending</strong> — When a Promise has neither been fulfilled nor rejected</li><li><strong>Fulfilled</strong> — When the current asynchronous task is successful</li><li><strong>Rejected</strong> — When the current asynchronous task has failed</li></ol><p>These states are internal to the Promise and cannot be directly accessed, but we can know if a Promise is <em>fulfilled</em> or <em>rejected</em> when one of its methods gets called.</p><p>Which brings us to the methods available on a Promise:</p><ol><li><strong>then</strong> — Gets called when a Promise is fulfilled</li><li><strong>catch</strong> — Gets called when a Promise is rejected</li><li><strong>finally</strong> — Always gets called at the very end</li></ol><p>But, how does a Promise get <em>fulfilled</em> or <em>rejected, </em>you ask? Well, that brings us to the callback function of the Promise constructor.</p><p>Every time you instantiate a new Promise, you can pass a callback function to it. This callback function receives two functions as arguments:</p><ol><li><strong>resolve</strong> — You call the resolve function (possibly with a value), which marks the Promise as <em>resolved,</em> and the argument passed to the <em>resolve</em> function is passed along to the <em>then</em> function.</li><li><strong>reject</strong> — You can call the reject function (possibly with a reject reason) to mark the Promise as rejected, and the argument passed to the <em>reject</em> function is passed along to the <em>catch</em> function.</li></ol><p>Now, let’s put all that we’ve learnt into action. Take a look at the code below:</p><pre>console.log(&quot;start&quot;) <br><br>const myPromise = new Promise(function(resolve, reject) {<br>  setTimeout(function(){<br>    resolve(&quot;done&quot;)<br>  }, 2000)<br>});<br><br>myPromise.then(function(val){<br>  console.log(&quot;then: &quot;, val)<br>});<br><br>myPromise.finally(function(){<br>  console.log(&quot;final&quot;) <br>});<br><br>console.log(&quot;end&quot;) </pre><p>What should be the output of the above? If you guess this, then you’d be correct.</p><pre>// start<br>// end<br>// then: done<br>// final</pre><p>Why? Because in the Promise callback, we call the resolve function with a timeout of 2000ms. So, when the above code starts executing, these things happen in this order:</p><ol><li>The first console log gets printed with the value “start”</li><li>A new instance of a Promise is created with the name <em>myPromise</em>. The callback is executed immediately, and the callback function for <em>setTimeout</em> gets placed on the <em>callback</em> queue. It will be executed <strong><em>at least</em></strong> 2000ms later. <em>myPromise</em> is currently in the <em>PENDING</em> state.</li><li>The callback function for <em>myPromise.then()</em> gets registered. It will be executed if and when <em>myPromise’s</em> state changes to <em>FULFILLED</em>.</li><li>The first console log gets printed with the value “end”</li><li>After 2 seconds (2000ms) have elapsed, the callback function for <em>setTimeout</em> gets executed, which executes the <em>resolve</em> function with “<em>done</em>” as an argument, and <em>myPromise’s</em> state now changes to <em>FULFILLED</em>.</li><li>The callback function for <em>myPromise.then()</em> gets executed with the value passed in resolve earlier. The parameter <em>val</em> (with the value of “<em>done</em>”) gets printed on the console.</li><li>The callback function for <em>myPromise.finally()</em> gets executed, and “<em>final</em>” gets printed on the console.</li></ol><p>I hope you now understand how <em>Promises</em> work. Now let’s get to building one of our own.</p><p>We are going to build our own Promise API in TypeScript. Let’s call it CustomPromise.</p><p>Before writing any actual code, let us go ahead and define type definitions and class structure based on the anatomy of a Promise we just learned.</p><pre>enum PROMISE_STATE {<br>  PENDING,<br>  FULFILLED,<br>  REJECTED,<br>}<br><br>type ThenCallback = (value?: any) =&gt; void | any | null | undefined;<br><br>type ErrorCallback = (reason: any) =&gt; any | undefined | null;<br><br>type FinallyCallback = () =&gt; void;<br><br>type Resolve = (value?: any) =&gt; void;<br><br>type Reject = (reason?: any) =&gt; void;<br><br>type ExecutorCallback = (<br>  resolve: ResolveType,<br>  reject: RejectType<br>) =&gt; void;<br><br>class CustomPromise {<br>  private state: PROMISE_STATE;<br><br>  constructor(executor: ExecutorCallback) {<br>    this.state = PROMISE_STATE.PENDING;<br>    executor(this.resolve, this.reject);<br>  }<br><br>  private resolve(value?: any): void {}<br><br>  private reject(reason: any) {}<br><br>  public then(onfulfilled?: ThenCallback) {}<br><br>  public catch(onrejected?: ErrorCallback) {}<br><br>  public finally(onfinally?: FinallyCallback) {}<br>}</pre><p>Let’s try creating a promise with our class and see what output we get for the same above:</p><pre>console.log(&quot;start&quot;) <br><br>const myPromise = new CustomPromise(function(resolve, reject) {<br>  setTimeout(function(){<br>    resolve(&quot;done&quot;)<br>  }, 2000)<br>});<br><br>myPromise.then(function(val){<br>  console.log(&quot;then: &quot;, val)<br>});<br><br>myPromise.finally(function(){<br>  console.log(&quot;final&quot;) <br>});<br><br>console.log(&quot;end&quot;) </pre><p>Output:</p><pre>// start<br>// end</pre><p>If this is what you expected, then great. You are on the right path. If not, then don’t worry. Just stick with me.</p><p>Why did we get this output? Because we have only <strong>defined</strong> our class members till now, we have not written any code inside them. So, the code doesn’t do what it should. Yet.</p><p>Now, let’s implement these methods:</p><p>The <em>constructor </em>method:</p><pre>constructor(executor: ExecutorCallback) {<br>    this.state = PROMISE_STATE.PENDING; // initialise the promise state to pending<br>    executor(this.resolve, this.reject); // execute the executor by passing<br>                                           // instance of resolve and reject functions<br>}</pre><p>We set the <em>state</em> to <em>PENDING</em> and immediately execute the callback for the <em>executor</em> function by passing the <em>resolve</em> and <em>reject</em> methods as arguments.</p><h4>Quick aside for “this”</h4><p>Notice how we’re using <em>this</em> here to access the class members. Inside a <em>class</em> method, <em>this</em> refers to the current instance of the class, and we can access both <em>private </em>and <em>public</em> members.</p><p>But what are <em>private</em> and <em>public</em> members, you ask? Well, private members are the ones declared with the <em>private</em> keyword; these methods and properties are <strong>only accessible inside the class methods</strong>. These cannot be accessed on the instance of the object.</p><p>Only public properties and methods are accessible on the instance. For our class CustomPromise, see below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*brucRH0r7v7hZxLHBp2nhw.jpeg" /></figure><p>As you can see, only <em>catch</em>, <em>finally</em>, and <em>then</em> methods are accessible because they’re declared as public.</p><p>The <em>this.resolve</em> method:</p><pre> private resolve(value?: any) {<br>    this.state = PROMISE_STATE.FULFILLED<br>    this.then()<br> }</pre><p>Here, we first set the <em>state</em> of the promise to <em>FULFILLED</em>. Now, we have to call the <em>then</em> method. But this is where we run into our first problem. <br>The <em>then</em> method expects the callback function that was supplied by the user of the class, which means we need to store the <em>then</em> callback, i.e., the <em>onfulfilled</em> function, so that it can be executed later.</p><p>Similarly, we also need to store callbacks for <em>catch</em> and <em>finally</em> methods.</p><p>Also, to pass the actual <em>resolved</em> and <em>rejected</em> values to these callbacks, we need to store them as well.</p><p>Let’s quickly update our <em>CustomPromise</em> class to support those.</p><pre>class CustomPromise {<br>  private state: PROMISE_STATE;<br> /** EXISTING */<br> /** CODE */<br> /** ABOVE */<br>  private resolvedValue: any;<br>  private rejectedReason: any;<br>  private onfulfilled?: ThenCallback;<br>  private onrejected?: ErrorCallback;<br>  private onfinally?: FinallyCallback;<br> /** EXISTING */<br> /** CODE */<br> /** BELOW */<br>}</pre><p>As you can see, we have added three new private members to store the callbacks to be executed later.</p><p>Let’s first implement the <em>then</em>, <em>catch,</em> and <em>finally</em> methods, and then we’ll get back to the <em>resolve</em> and <em>reject</em> methods.</p><pre>class CustomPromise {<br>/** EXISTING */<br>/** CODE */<br>/** ABOVE */<br>  public then(onfulfilled?: ThenCallback) {<br>    if (this.state === PROMISE_STATE.PENDING &amp;&amp; onfulfilled) {<br>      this.onfulfilled = onfulfilled;<br>    }<br>    if (this.state === PROMISE_STATE.FULFILLED &amp;&amp; this.onfulfilled) {<br>      this.onfulfilled(this.resolvedValue);<br>    }<br>  }<br><br>  public catch(onrejected?: ErrorCallback) {<br>    if (this.state === PROMISE_STATE.PENDING &amp;&amp; onrejected) {<br>      this.onrejected = onrejected;<br>    }<br>    if (this.state === PROMISE_STATE.REJECTED &amp;&amp; this.onrejected) {<br>      this.onrejected(this.rejectedReason);<br>    }<br>  }<br><br>  public finally(onfinally?: FinallyCallback) {<br>    if (<br>      (this.state === PROMISE_STATE.FULFILLED ||<br>        this.state === PROMISE_STATE.REJECTED) &amp;&amp;<br>      onfinally<br>    ) {<br>      this.onfinally = onfinally;<br>    }<br>    if (<br>      (this.state === PROMISE_STATE.FULFILLED ||<br>        this.state === PROMISE_STATE.REJECTED) &amp;&amp;<br>      this.onfinally<br>    ) {<br>      this.onfinally();<br>    }<br>  }<br> /** EXISTING */<br> /** CODE */<br> /** BELOW */<br>}</pre><p>The code has a lot of conditions for <em>PENDING</em>, <em>FULFILLED,</em> and <em>REJECTED</em>. Let’s add some private helper methods to make this code more readable.</p><pre>class CustomPromise {<br> /** EXISTING */<br> /** CODE */<br> /** ABOVE */<br>  private isPromisePending() {<br>    return this.state === PROMISE_STATE.PENDING;<br>  }<br><br>  private isPromiseRejected() {<br>    return this.state === PROMISE_STATE.REJECTED;<br>  }<br><br>  private isPromiseFulfilled() {<br>    return this.state === PROMISE_STATE.FULFILLED;<br>  }<br><br>  private isPromiseFulfilledOrRejected() {<br>    return this.state !== PROMISE_STATE.PENDING;<br>  }<br><br>  public then(onfulfilled?: ThenCallback) {<br>    if (this.isPromisePending() &amp;&amp; onfulfilled) {<br>      this.onfulfilled = onfulfilled;<br>    }<br>    if (this.isPromiseFulfilled() &amp;&amp; this.onfulfilled) {<br>      this.onfulfilled(this.resolvedValue);<br>    }<br>  }<br><br>  public catch(onrejected?: ErrorCallback) {<br>    if (this.isPromisePending() &amp;&amp; onrejected) {<br>      this.onrejected = onrejected;<br>    }<br>    if (this.isPromiseRejected() &amp;&amp; this.onrejected) {<br>      this.onrejected(this.rejectedReason);<br>    }<br>  }<br><br>  public finally(onfinally?: FinallyCallback) {<br>    if (this.isPromisePending() &amp;&amp; onfinally) {<br>      this.onfinally = onfinally;<br>    }<br>    if (this.isPromiseFulfilledOrRejected() &amp;&amp; this.onfinally) {<br>      this.onfinally();<br>    }<br>  }<br> /** EXISTING */<br> /** CODE */<br> /** BELOW */<br>}</pre><p>This looks much better, and it is instantly much more readable.</p><p><strong>Let’s quickly go through the <em>then</em> method:</strong></p><p>It is first executed when the user of our class <em>registers</em> a callback by using the <em>.then()</em> method on the instance object. In that case, we first check if the promise is in the <em>PENDING</em> state, then we store the value of the callback in the <em>onfulfilled</em> private property and pass the <em>resolvedValue </em>as an argument.</p><p>After that, when the user calls the <em>resolve</em> callback, we call the <em>then()</em> callback again, and by this time the promise is already marked as <em>FULFILLED,</em> and we execute the callback function stored in the private <em>onfulfilled </em>property</p><p>The same thing happens for the <em>.catch()</em> method, but it will get executed when the <em>reject</em> method is executed and the promise is marked as <em>REJECTED</em>.</p><p>And for the .<em>finally()</em> method, we register the callback in <em>onfinally,</em> and it gets executed at the very end.</p><p>Now, let’s execute the test code again:</p><pre>console.log(&quot;start&quot;); <br><br>const myPromise = new CustomPromise(function (resolve, reject) {<br>  setTimeout(function () {<br>    resolve(&quot;done&quot;);<br>  }, 2000);<br>});<br><br>myPromise.then(function (val) {<br>  console.log(&quot;then: &quot;, val); <br>});<br><br>myPromise.finally(function () {<br>  console.log(&quot;final&quot;); <br>});<br><br>console.log(&quot;end&quot;); </pre><p>What should be the output now?</p><pre>// start<br>// end<br>// then: done<br>// final</pre><p>This, right? Well, that’s what it should be. But we get an error instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ej9CkTZ7wZcHv-f-mf_X3A.jpeg" /></figure><p>The error happens on line 33 above, where we’re setting the <em>state</em> of the promise to <em>FULFILLED</em>. The error says that <em>this</em> is <em>undefined</em>.</p><p>Why would <em>this</em> be <em>undefined</em> here?</p><h4>Quick aside for “this” (once again)</h4><p>In JavaScript, <em>this</em> is a <em>keyword</em> and an object, which means it is part of the language and holds a special meaning. But what is it, actually?</p><p>In simple terms, <em>this</em> object refers to the current execution environment, i.e., the <strong>current value</strong> of <em>this</em> depends on where the function is <strong>invoked, </strong>not where it is defined.</p><p>There are a few rules of thumb:</p><ol><li>The value of <em>this</em> refers to the object itself inside a class method, when that method is called using the dot notation. e.g. person.getAge()</li><li>The value of <em>this</em> refers to the <em>global</em> object or <em>undefined</em> (in strict mode) when a function is called directly.</li></ol><p>The 2nd rule is what’s causing our issue. Notice as we pass <em>this.resolve</em> method to the <em>executor</em> function as a callback method. When the <em>resolve</em> function is finally called inside our promise, it gets executed as a standalone method. It is not associated with or, dare I say, <strong>bound</strong> with the object anymore.</p><p>Now, can we do anything to fix it? Yes! There are 2 ways we can supply the correct value for <em>this</em>.</p><h4>1st option: Using the bind method</h4><p>In the constructor, we can create <em>bound</em> instances of both <em>resolve</em> and <em>reject</em> methods and pass those instances. Like this:</p><pre>class CustomPromise {<br>  constructor(executor: ExecutorCallback) {<br>    this.state = PROMISE_STATE.PENDING;<br>    const boundResolve = this.resolve.bind(this);<br>    const boundReject = this.reject.bind(this);<br>    executor(boundResolve, boundReject);<br>  }<br><br>  private resolve() { }<br><br>  private reject() { }<br>}</pre><h4>2nd option: By using an arrow function</h4><p>We can declare the <em>resolve</em> and <em>reject</em> methods as <strong>arrow functions</strong>. Arrow functions change the behavior of <em>this</em> by ensuring that <em>this</em> always points to the <strong>parent scope at the time of definition</strong>.</p><pre>class CustomPromise {<br>  constructor(executor: ExecutorCallback) {<br>    this.state = PROMISE_STATE.PENDING;<br>    executor(this.resolve, this.reject);<br>  }<br><br>  private resolve = () =&gt; { }<br><br>  private reject = () =&gt; { }<br>}</pre><p>You are free to choose whichever way you like. For this article, I will use the 1st approach.</p><p>Now we can finally finish writing our resolve and reject methods:</p><pre>class CustomPromise {<br> /** EXISTING */<br> /** CODE */<br> /** ABOVE */<br><br>  private resolve(value?: any): void {<br>    this.state = PROMISE_STATE.FULFILLED;<br>    this.resolvedValue = value;<br>    this.then();<br>    this.finally();<br>  }<br><br>  private reject(reason: any) {<br>    this.state = PROMISE_STATE.REJECTED;<br>    this.rejectedReason = reason;<br>    this.catch();<br>    this.finally();<br>  }<br><br> /** EXISTING */<br> /** CODE */<br> /** BELOW */<br>}</pre><p>Let’s try running this code and see the output:</p><pre>console.log(&quot;start&quot;);<br><br>const myPromise = new CustomPromise(function (resolve, reject) {<br>  setTimeout(function () {<br>    resolve(&quot;done&quot;);<br>  }, 2000);<br>});<br><br>myPromise.then(function (val) {<br>  console.log(&quot;then: &quot;, val);<br>});<br>myPromise.catch(function (err) {<br>  console.log(&quot;catch: &quot;, err);<br>});<br>myPromise.finally(function () {<br>  console.log(&quot;final&quot;);<br>});<br><br>console.log(&quot;end&quot;);</pre><p>Output:</p><pre>// start<br>// end<br>// then: done<br>// final</pre><p>Let’s quickly also test for the case where we <em>reject</em> the promise:</p><pre>const myPromise = new CustomPromise(function (resolve, reject) {<br>  setTimeout(function () {<br>    reject(&quot;failed&quot;);<br>  }, 2000);<br>});<br><br>myPromise.then(function (val) {<br>  console.log(&quot;then: &quot;, val);<br>});<br>myPromise.catch(function (err) {<br>  console.log(&quot;catch: &quot;, err);<br>});<br>myPromise.finally(function () {<br>  console.log(&quot;final&quot;);<br>});<br><br>console.log(&quot;end&quot;);</pre><p>Output:</p><pre>// start<br>// end<br>// catch: failed<br>// final</pre><p>Ah! Sweet success! Congratulations! We have successfully built our own Promise. If you are preparing for a frontend developer interview, then doing this much would be enough. But we’re missing a very critical feature. Can you guess what it is?</p><p>Yes! We are calling then, catch, and finally methods on different lines instead of chaining them. As you may find, our code doesn’t support chaining these methods yet.</p><p>The good news is that this is pretty trivial. We can achieve this functionality by adding just 1 line of code.</p><pre>return this</pre><p>Just that, at the end of both <em>then</em> and <em>catch</em> methods. But how will this help us chain these methods? As we learnt before, here <em>this</em> refers to the current instance of the object which has <em>then</em>, <em>catch,</em> and <em>finally</em> methods on it. So, when we return <em>this</em> from <em>then</em> and <em>catch</em> methods, we have all these methods accessible on the result, and because of that, we are now able to chain them.</p><p>Let’s rewrite and test our code, shall we?</p><pre>class CustomPromise {<br>   public then(onfulfilled?: ThenCallback) {<br>    if (this.isPromisePending() &amp;&amp; onfulfilled) {<br>      this.onfulfilled = onfulfilled;<br>    }<br>    if (this.isPromiseFulfilled() &amp;&amp; this.onfulfilled) {<br>      this.onfulfilled(this.resolvedValue);<br>    }<br>    return this; // &lt;=== Add this line<br>  }<br><br>  public catch(onrejected?: ErrorCallback) {<br>    if (this.isPromisePending() &amp;&amp; onrejected) {<br>      this.onrejected = onrejected;<br>    }<br>    if (this.isPromiseRejected() &amp;&amp; this.onrejected) {<br>      this.onrejected(this.rejectedReason);<br>    }<br>    return this; // &lt;=== Add this line<br>  }<br>}</pre><p>So, our test code will become:</p><pre>console.log(&quot;start&quot;);<br><br>new CustomPromise(function (resolve, reject) {<br>  setTimeout(function () {<br>    resolve(&quot;done&quot;);<br>  }, 2000);<br>})<br>  .then(function (val) {<br>    console.log(&quot;then: &quot;, val);<br>  })<br>  .catch(function (err) {<br>    console.log(&quot;catch: &quot;, err);<br>  })<br>  .finally(function () {<br>    console.log(&quot;final&quot;);<br>  });<br><br>console.log(&quot;end&quot;);</pre><p>Output:</p><pre>// start<br>// end<br>// then: done<br>// final</pre><p>And similarly for the rejected case:</p><pre>console.log(&quot;start&quot;);<br><br>new CustomPromise(function (resolve, reject) {<br>  setTimeout(function () {<br>    reject(&quot;failed&quot;);<br>  }, 2000);<br>})<br>  .then(function (val) {<br>    console.log(&quot;then: &quot;, val);<br>  })<br>  .catch(function (err) {<br>    console.log(&quot;catch: &quot;, err);<br>  })<br>  .finally(function () {<br>    console.log(&quot;final&quot;);<br>  });<br><br>console.log(&quot;end&quot;);</pre><p>Output:</p><pre>// start<br>// end<br>// catch: failed<br>// final</pre><p>Perfect!</p><p>There’s just one piece missing in this puzzle — <strong>Types</strong>.</p><p>We are using TypeScript after all. Yet, our Promise doesn’t enforce any types. Let’s fix that… with <strong>Generics</strong>.</p><p>What are generics, you ask? Good question!</p><p>In TypeScript, Generics allow us to define certain <em>placeholders</em> at the time of <em>class/type</em> definition. The consumers of those <em>classes/types</em> can fill in those placeholders with a <em>type</em> of their choosing when they use it. Isn’t that cool?</p><p>Let’s see how we can do that. This only shows the lines that have been changed:</p><pre>type ThenCallback&lt;T&gt; = (value?: T) =&gt; void | any | null | undefined | T;<br><br>type Resolve&lt;T&gt; = (value?: T) =&gt; void;<br><br>type ExecutorCallback&lt;T&gt; = (resolve: Resolve&lt;T&gt;, reject: Reject) =&gt; void;<br><br>class CustomPromise&lt;T&gt; {<br>  private resolvedValue: T | undefined;<br>  private onfulfilled?: ThenCallback&lt;T&gt;;<br><br>  constructor(executor: ExecutorCallback&lt;T&gt;) { }<br><br>  private resolve(value?: T) {}<br><br>  public then(onfulfilled?: ThenCallback&lt;T&gt;) {}<br>}</pre><p>All we’ve done here is allow the users of our class to specify a type when using the <em>class</em>, denoted here as &lt;T&gt; Now, say the user picks the type string then every appearance of &lt;T&gt; will be treated as string by the TypeScript compiler as well as your linter, i.e., you will get this error in real-time.</p><p>Let’s see how this changes how we use the CustomPromise class:</p><pre>new CustomPromise&lt;string&gt;(function (resolve, reject) {<br>  setTimeout(function () {<br>    resolve(&quot;done&quot;);<br>  }, 2000);<br>})<br>  .then(function (val) {<br>    console.log(&quot;then: &quot;, val);<br>  })<br>  .catch(function (err) {<br>    console.log(&quot;catch: &quot;, err);<br>  })<br>  .finally(function () {<br>    console.log(&quot;final&quot;);<br>  });<br></pre><p>Notice how we’ve added &lt;string&gt; between CustomPromise and the opening ( . This will ensure that the value passed in the resolve function is a string</p><p>If it’s not a string then you’ll see an error like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgqYZ1vNqJ1g9EJ1vj29Eg.jpeg" /></figure><p>And we’re done. For now.</p><p>There are a bunch of features remaining, such as:</p><ol><li>Promise chaining</li><li><em>Then</em> and <em>Catch</em> methods nested chaining</li><li>Nested promises</li></ol><p>We’ll implement all of these to fully replicate the Promise API. Let’s do that in a <strong>follow-up post</strong>.</p><p>So, please 👏 and follow me if you liked this post.</p><p>I hope you found this useful. Let me know your thoughts in the comments.</p><p>All the code in this post can be found in this repository:</p><p><a href="https://github.com/adarshnanwani/promise">GitHub - adarshnanwani/promise: Implementation of Promise API in TypeScript and JavaScript</a></p><p>These are the files you need to look for:</p><pre>.<br>├──js/<br>│  └── basic-promise.js<br>├──ts/<br>│  ├── basic-promise.ts<br>│  └── basic-typed-promise.ts</pre><p>Don’t forget to <a href="https://github.com/adarshnanwani">follow me on GitHub</a> and ⭐ the repo.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c25c5d66c14f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choosing between Maestro and Detox on Jupiter | QA Automation]]></title>
            <link>https://life.jupiter.money/choosing-between-maestro-and-detox-on-jupiter-qa-automation-7b94e6f8759d?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b94e6f8759d</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[qa-automation]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 12:16:35 GMT</pubDate>
            <atom:updated>2025-09-30T12:16:35.537Z</atom:updated>
            <content:encoded><![CDATA[<h3>Choosing between Maestro and Detox for our app QA Automation needs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsRCLTH7MOjRYjObM7M__Q.jpeg" /></figure><p>At Jupiter, we continuously strive to deliver a seamless and reliable experience to our users, which makes testing a critical part of our development process.</p><p>Shipping high-quality mobile apps is brutal with manual testing alone. Slow regression cycles, human errors, and gaps in coverage creep in as features pile up. Manual testing strains under modern mobile complexity, with multiple OS versions and devices, varied network conditions, feature flags, and various user states. Regression passes get slower, coverage becomes uneven, and “works on my phone” bugs slip through. That’s where automated end-to-end (E2E) testing steps in as a repeatable safety net.</p><p>End-to-End (E2E) QA Automation is a testing approach that validates the entire user journey of an application by simulating real-world scenarios from start to finish. Unlike unit or integration tests that focus on individual components or modules, E2E automation ensures that all interconnected systems i.e. frontend, backend, APIs, databases, and third-party services, work together seamlessly to deliver the intended functionality.</p><p>By automating these flows, teams can quickly detect regressions, reduce manual testing effort, and build confidence that critical user experiences (like onboarding, transactions, or checkout) consistently perform as expected across different environments and releases.</p><p>This article takes a practical look at two leading E2E test framework options for React Native apps — <strong>Maestro</strong> (flow-driven, black-box style) and <strong>Detox</strong> (gray-box runner with deep app hooks). We’ll compare them across the criteria that actually matter day to day: setup effort and learning curve, test authoring expressiveness, flakiness and stability, execution speed, CI/CD fit, debugging and observability, data seeding and mocking strategies, cross-platform behavior, maintenance cost, etc.</p><p>Both of these frameworks aim to help developers ship reliable apps faster, but they take slightly different approaches.</p><h3>Maestro</h3><p>Maestro is a modern open-source mobile UI testing framework built for simplicity and speed. It emerged as a response to the complexity of existing frameworks, focusing on a YAML-based declarative syntax that makes writing and maintaining tests approachable, even for non-engineers. Comes with Maestro Studio and Maestro Studio Desktop app with support for AI assisted test-writing with a paid option to run your tests on the cloud.</p><ul><li><strong>History:</strong> Created by Mobile.dev, Maestro has quickly gained traction as a developer-friendly alternative for UI flow testing.</li><li><strong>Key idea: </strong>Tests are described in YAML flows, enabling fast iteration without complex setup.</li><li><strong>Usage:</strong> Popular for smoke tests, regression testing, and automating real-world user flows like onboarding, payments, or navigation.</li><li><strong>Adoption:</strong> Increasingly used in CI/CD pipelines thanks to its lightweight setup and support for both iOS and Android.</li></ul><p>Learn more: <a href="https://docs.maestro.dev/">Official Docs</a>, <a href="https://github.com/mobile-dev-inc/maestro">GitHub</a></p><h3>Detox</h3><p>Detox is a gray-box end-to-end testing library built by Wix, designed specifically for React Native apps (though it also supports native). Unlike Maestro, Detox runs inside the app process, giving it deep integration with React Native’s asynchronous nature.</p><ul><li><strong>History:</strong> Developed at Wix to solve reliability issues in mobile UI testing, it has been around since ~2017 and remains one of the most battle-tested RN testing frameworks.</li><li><strong>Key idea:</strong> Detox synchronises test execution with the app’s lifecycle (e.g., network requests, animations, timers), making tests less flaky compared to black-box tools.</li><li><strong>Usage: </strong>Best suited for component-level and E2E validation where precise control and synchronisation with React Native’s internals are needed.</li><li><strong>Adoption: </strong>Widely used across React Native companies for production-grade apps; actively maintained with a strong community.</li></ul><p>Learn more: <a href="https://wix.github.io/Detox/">Official Docs</a>, <a href="https://github.com/wix/detox">GitHub</a></p><p><strong>Key Differences</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9NlVfgjIQ6JBb7f8rZkjhA.png" /></figure><p>Before getting started with either of the frameworks, we worked on identifying critical functionalities/features that any framework should have. We ended up identifying more than 25 such functionalities and assessed both frameworks on each criteria.</p><p>Here are some of those:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nsy1I8Ufw654rzdrudkUsg.png" /><figcaption>Features of a Framework</figcaption></figure><p>We kept refining the functionalities/features matrix as we tried out both the frameworks. We’ll return to the detailed matrix at a later time in this article. For now, let’s continue with our experience of setting up and running tests for each framework.</p><h3>Experience of Setting Up Maestro and Test Execution</h3><p>In this section, we go through over our experience of setting up each framework and compare it across crucial parameters</p><h3>A. Set up experience</h3><h4>Maestro</h4><ul><li>Setting up Maestro is a breeze. The installation is painless with no changes required in the app codebase. Just run one command on the terminal (two on Mac) and you’re ready for writing tests.</li><li>Writing test cases in YAML feels very intuitive.</li><li>The Maestro framework with the complementary Maestro Studio and Maestro Studio Desktop (with AI assisted test writing) apps together create a solid ecosystem to write and execute tests.</li></ul><h4>Detox</h4><ul><li>The setup, though it is a one-time activity, can be a very complex and time-consuming. We need to make changes in the native iOS and Android apps and create new Detox specific build targets for both debug as well as release and Android as well as iOS. We also need to ensure these changes are not pushed to production during CI.</li><li>We tried setting it up for a newly bootstrapped React Native app and it just worked. But doing it for our much more complex app took much longer and we had to stray a bit from the official documentation.</li><li>We couldn’t get the tests to run in the release mode. The app launcher complained of not finding the package while the package did exist. We couldn’t spend too much time on this due to timing and budget constraints and put it on the back burner as we wanted to get started with Test executions and comparison with Maestro. We’ll return to this after a one-on-one comparison.</li></ul><h3>B. Observations</h3><h4>Maestro</h4><ul><li><strong>App launch delay</strong> — The app launch takes a long time(around 30 seconds) on some devices but works well on most (around 10 seconds)</li><li><strong>Some actions take longer than others</strong> — In a screen where a 4 digit PIN has to be entered, the time duration between each tap was around 4–6s. This is specific to screens where user mandatorily needs to tap on buttons one after another and input data cannot be pasted.</li><li><strong>Test reports </strong>— Maestro allows generation of test reports in the JUnit and HTML formats while artefacts(screenshots, videos, logs, etc.) are also published for each test run.</li><li><strong>Scrolling issue</strong> — Tests freeze during scrolling behaviour when they encounter nested scrolls, e.g. A horizontal scroll inside a vertical scroll. We solved this by writing our own utility which used the swipe command instead of scroll command.</li><li><strong>Build changes</strong> — None. Maestro can work with any build flavour.</li></ul><h4>Detox</h4><ul><li><strong>Element access issues</strong> — On some protected screens (such as MPIN screen), Detox tap event wouldn’t work. We decided to manually enter the MPIN for the time being and continued writing test cases.</li><li><strong>App launch issues</strong> — Tests would only launch the app 2/10 times on a physical device. On using an emulator instead, it worked 8/10 times. The issue needed a lot more dedicated time to resolve than we had budget for.</li><li><strong>Synchronisation issues</strong> — Certain animations/loaders would cause the test to wait endlessly and fail. We had to either disable synchronisation altogether or turn off all animations. Your mileage may vary.</li><li><strong>Scrolling issue</strong> — Tests freeze during scrolling behaviour when they encounter nested scrolls, e.g. A horizontal scroll inside a vertical scroll. We think this issue can be fixed in a similar way as we did with Maestro.</li><li><strong>Test reports</strong> — No inbuilt report generation support. But, allows tests report generation via the jest runner (Jest, Mocha, etc). Detox also produces artefacts(screenshots, videos, logs) and these are handles via the artefact config.</li><li><strong>Build changes</strong> — Detox require creating new release targets with custom code for Detox and test runners for both Android and iOS which should not to be shipped to production. Detox can’t work directly with the release build.</li></ul><h3>C. Learning curve</h3><h4>Maestro</h4><ul><li>Extremely easy to setup and requires no changes in app codebase.</li><li>Extremely easy to learn and write test cases.</li><li>Maestro Studio Desktop provides app inspection with pre-generated code for asserts, interactions and conditionals that can directly be injected in a test and code autocomplete features with AI support.</li></ul><h4>Detox</h4><ul><li>Setup is a more complicated and requires changes in app codebase. It took multiple tries to get it right. Though, it is a one-time activity. But, it still can take a lot of effort. Detox</li><li>Writing tests is easier for people well-versed with JavaScript/TypeScript but has a medium-to-high learning curve with no experience in JS/TS or for a team transitioning from manual to automation QA.</li></ul><h3>D. Sample test code</h3><p>Below is the sample code for a simple test case written for both Maestro as well as Detox.</p><p>This sample test case has asserts based on element id, element text, taps as well as scroll behavior.</p><h4>Maestro</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4JfKOUwFCG75LhpJcXj_Lw.png" /></figure><h4>Detox</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hx0NRs9KMfhXz0TX34QgDA.png" /></figure><h3>Summary — Comparative experience of each framework</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cctdyzOuad3vcCqhMlTQ9A.png" /></figure><p>*The <strong>test run experience</strong> aspect is mentioned here as we encountered it during out testing. We didn’t devote dedicated time to dig deeper into it.</p><h3>A/B comparison with a real world test</h3><p>Jupiter is a modern money management app designed to simplify banking and personal finance for Indian consumers. Built with a focus on usability and transparency, it offers features like smart insights into spending, investments, loans and credit management, UPI payments, and rewards, etc. Unlike traditional banking apps, Jupiter emphasises a customer-first experience with intuitive design, real-time tracking of finances, and tools that help users save more effectively while making informed financial decisions.</p><p>Let’s take a look at one of the test cases from our sanity test suite:</p><p><strong>Test case:</strong> Validate filters on the global transaction List</p><p><strong>Description: </strong>In this test case, we log into the app by entering MPIN and navigate to the global transaction list and validate the filters available.</p><p>Here’s a video demonstration of the test case:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeRWKIJIhO0w&amp;type=text%2Fhtml&amp;schema=youtube&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeRWKIJIhO0w%3Ffeature%3Doembed" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/de18f409a1356efbd56be8f511f0a78b/href">https://medium.com/media/de18f409a1356efbd56be8f511f0a78b/href</a></iframe><h3>The Bottleneck</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GW2CdD9fQ__ezb_I2Rb7w.png" /></figure><p>As it can be seen from the test execution data above, the test execution experience is fairly similar after the MPIN screen. But the MPIN screen is where Maestro takes a lot of time and that turns into a bottleneck. Since the MPIN screen has to be a part of every test and it will add a lot of time to a large test suite and overall test execution duration.</p><p>We <strong>found a solution</strong> to this problem by utilising the <strong><em>runScript</em></strong> command from Maestro, which allows us to run JavaScript by utilising the Rhino engine under the hood (with an option to switch to GraalJS engine). We created a simple NodeJS/Express server which exposes an API endpoint and the server utilises ADB to issue commands to the connected device. The same approach also helped us enter the MPIN directly on Detox.</p><p>Following this approach, we were able to bring down the time it takes to enter MPIN from 16–18s to under 1s, and the time delta between Maestro and Detox now stood between less than 10%.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNvv6UrQGe_s%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FNvv6UrQGe_s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNvv6UrQGe_s%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4e6e487ab55771e58eb99bc921144636/href">https://medium.com/media/4e6e487ab55771e58eb99bc921144636/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FttOH5xWkMpA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FttOH5xWkMpA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FttOH5xWkMpA%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf59e9d61d57126994dd1bcfbf3cc4dc/href">https://medium.com/media/bf59e9d61d57126994dd1bcfbf3cc4dc/href</a></iframe><p>We ran a few more tests after this enhancement and here are the results for that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZHngWyC-eqa2-wIeAPRHg.png" /></figure><p>It was evident from the above data that Detox still has a slight edge in the execution speed but Maestro has managed to achieve comparable numbers.</p><h3>Functionalities/Feature Matrix</h3><p>It’s finally time to dive deeper into the Functionalities Matrix and see how each framework fares on our evaluation criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DgSq5kFkzKS_HybCsBpCww.png" /></figure><p>Out of all these, the <strong>most critical ones</strong> for us are:</p><ul><li><strong>Platform support</strong> (But mostly Android as &gt;90% of our users use Android)</li><li><strong>Learning curve</strong> (We have a fairly large manual QA team and we want to onboard them ASAP)</li><li><strong>Targeted test runs</strong> (Useful for feature testing)</li><li><strong>Execution speed </strong>(The tests should not take exceptionally long to run)</li><li><strong>CI/CD integration </strong>(It is non-negotiable with our huge scope with a bi-weekly release cadence)</li></ul><p>After evaluating both frameworks in depth, we decided to go with <strong>Maestro</strong>. While Detox offers deep integration with React Native, its heavier setup, higher learning curve, and flakiness made it less practical for our needs. Maestro, on the other hand, aligned better with our priorities — Fast onboarding of our QA team, reliable execution, minimal app code impact, and seamless CI/CD integration.</p><h3>Why we decided to go with Maestro</h3><p>1. <strong>Ease of setup and zero codebase changes</strong></p><p>Maestro required <strong>no modifications to the app codebase</strong> and could be set up within minutes. This contrasted sharply with Detox, which needed native code changes, custom build configurations, and was error-prone during initial setup. For a team that wanted to get productive quickly, Maestro’s “install and go” setup was a decisive factor.</p><p>2. <strong>Low learning curve for manual QA team</strong></p><p>Since a large manual QA team needed to be onboarded to contribute to automation with minimal learning curve, Maestro’s <strong>YAML-based declarative syntax</strong> was far more approachable compared to Detox’s JavaScript/TypeScript tests. On top of that, <strong>Maestro Studio</strong> allowed functional testers to visually inspect the app, auto-generate test steps, and leverage AI-assisted test writing, making the transition to automation much smoother.</p><p>3. <strong>Test stability and reliability</strong></p><p>During evaluation, Maestro consistently launched and executed tests reliably across devices, whereas Detox suffered from <strong>frequent app launch failures, flaky synchronisation, and scrolling issues</strong>. For day-to-day regression and smoke testing, Maestro offered <strong>more predictable and stable test runs</strong> without requiring deep debugging.</p><p>4. <strong>Targeted test runs and flexibility</strong></p><p>Maestro’s <strong>built-in tagging functionality</strong> made it easy to selectively run specific tests or subsets, which aligned well with the need for targeted feature testing. In Detox, this required custom implementation. This flexibility helped optimise CI/CD pipelines and reduced execution time when validating only affected features.</p><p>5. <strong>Seamless CI/CD integration</strong></p><p>Maestro’s <strong>lightweight setup and cross-platform support</strong> made it straightforward to integrate into CI/CD pipelines. The absence of native build dependencies and simpler configuration meant the automation setup could scale faster across teams.</p><p>6. <strong>Workarounds for execution speed bottlenecks</strong></p><p>Initially, Maestro tests (e.g. MPIN entry) were slower compared to Detox by about 50%. However, by using the <strong><em>runScript</em> </strong>command to call a NodeJS/ADB-based helper, the team reduced PIN entry time from ~18s to under 1s. <strong>This narrowed the execution time gap to less than +-10%</strong>, removing speed as a blocker. Given Maestro’s smoother overall experience, this optimisation tipped the balance further in its favour.</p><h4>Cases where we may consider using Detox in future</h4><ul><li>Mocking API Calls</li><li>Testing error states</li><li>Intercepting RN modules</li></ul><p>But for now, <strong>Maestro</strong> seems to fit the bill perfectly.</p><p>If you have any questions/feedback let me know in the comments below.<br>Do check our other blogs on <a href="https://life.jupiter.money/">Life-At-Jupiter</a> related to fintech, design language, tech innovations and more!</p><p><a href="https://life.jupiter.money/">life-at-jupiter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b94e6f8759d" width="1" height="1" alt=""><hr><p><a href="https://life.jupiter.money/choosing-between-maestro-and-detox-on-jupiter-qa-automation-7b94e6f8759d">Choosing between Maestro and Detox on Jupiter | QA Automation</a> was originally published in <a href="https://life.jupiter.money/">life-at-jupiter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to Do When Programming Overwhelms You]]></title>
            <link>https://medium.com/better-programming/what-to-do-when-programming-overwhelms-you-9270743c075d?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9270743c075d</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Mon, 10 Feb 2020 03:30:04 GMT</pubDate>
            <atom:updated>2020-02-10T03:30:04.820Z</atom:updated>
            <content:encoded><![CDATA[<h4>“If you get tired, learn to rest, not to quit.” — Banksy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ewfzFevvYLjy1Pm1" /><figcaption>Photo by <a href="https://unsplash.com/@noahsilliman?utm_source=medium&amp;utm_medium=referral">Noah Silliman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><p>If you’re anything like me, you believe that programming is a way to do some real good in the world and make a decent buck in the process. Since I was a child, I was obsessed with technology and computers. That’s why I decided to get my graduate degree in computer science. I also couldn’t see myself doing anything else.</p><p>Today, after four years of grad school and four years of working full-time as a software developer, I still find myself overwhelmed now and then. The world of software development — especially web development — is fast-paced. There’s a new library/framework getting released every day and there are so many different little things you want to learn and do. There are so many buzz words you want to get familiar with: Docker, Cloud, machine learning, PWA, and the list goes on. At times, you end up feeling overwhelmed.</p><p>After being in this field for a few years, I can say that it’s pretty normal to feel overwhelmed. It is even more common to burn out trying to do a lot of things in very little time. In this piece, I’m going to tell you what you should do when that happens. So, here’s a list of things I do when I’m overwhelmed and close to burnout.</p><h3>1. Take a Walk and Introspect</h3><p>Sometimes, you need to take a step back and take stock of your situation. It helps when you know how far you’ve come and how much you’ve grown. Brain fog can make some very simple situations seem convoluted. It is always a good idea to clear your mind. You can try meditation too. It has helped me a lot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VmvEWs9RKGIB1s0i" /><figcaption>Photo by <a href="https://unsplash.com/@dingzeyuli?utm_source=medium&amp;utm_medium=referral">Dingzeyu Li</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>2. Do Something That Makes You Happy</h3><p>No matter how crazy life seems, there’s always something that’ll bring you happiness. For example, you could:</p><ul><li>Spend time with your loved ones.</li><li>Play an instrument.</li><li>Go for a hike.</li><li>Read a book.</li><li>Do some gardening.</li><li>Go shopping.</li></ul><p>Sometimes, all you need is a distraction to reset your mind and put it back on the learning path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lwrbt6Ruf3Gp9kfb" /><figcaption>Photo by <a href="https://unsplash.com/@lidyanada?utm_source=medium&amp;utm_medium=referral">Lidya Nada</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>3. Take a Break and Make a Plan</h3><p>This one is a bit methodical. When you feel too overwhelmed, decide to take a break. Chances are you’ll find it hard, but push through that. You have to give yourself time. Then, make a plan about what you want to do. A bit of clarity about your life can sometimes make a world of difference. The plan you make will help you see where you will be and in how many days/weeks. And it will free up your mental space that is currently filled with worry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KCMiyNjfzhWGO6a-" /><figcaption>Photo by <a href="https://unsplash.com/@martenbjork?utm_source=medium&amp;utm_medium=referral">Marten Bjork</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>4. Go for a Run or Exercise</h3><p>There are countless studies out there that show that exercise can have a positive impact on your mood and well-being. It’s OK if you are not a gym person. You can do any physical activity you like. It could be a game of badminton or tennis. You could go for a run. You could skip rope. Spend some time in the zone and there’s a good chance that after you’re done sweating, you’ll feel refreshed and ready to take on the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sawDfBw5Utl9_PiU" /><figcaption>Photo by <a href="https://unsplash.com/@andrewtanglao?utm_source=medium&amp;utm_medium=referral">Andrew Tanglao</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>5. Positive Self-Talk</h3><p>A lot of our problems are a result of low self-esteem and negative self-talk. Avoid using phrases like “I’m not smart enough,” “This is too hard for me,” “I can’t take it,” “I’ll never be a …”</p><p>You have to tell yourself that you have it in you. Just say it to yourself. And it works even better when you say it out loud. It reinforces your belief in yourself. You can do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E0kGyS5B-gwUO2yG" /><figcaption>Photo by <a href="https://unsplash.com/@littleforestowl?utm_source=medium&amp;utm_medium=referral">Katrina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>6. Set Realistic Goals</h3><p>Setting a bar too high is a surefire way to get overwhelmed all the time and burn out in the process. You have to be realistic about your goals and consider different factors, such as:</p><ul><li>How much free time you have in a day</li><li>How much time you need to give your family</li><li>A mandatory technology-free break time</li><li>Any prior engagements/commitments/etc.</li></ul><p>Give yourself time to absorb the information you learn. Remember, when you’re learning something new, you’re like a sponge that can soak up a lot of knowledge. But when you don’t set realistic goals and you’re under pressure, you lose that knowledge the same way a sponge would lose the liquid it’s accumulated when pressed. You have to be mindful of your limits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gZGoZjEHE6buRY8W" /><figcaption>Photo by <a href="https://unsplash.com/@sabrituzcu?utm_source=medium&amp;utm_medium=referral">Sabri Tuzcu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><h3>7. Learn Something That You Find Interesting</h3><p>Most of our efforts in learning are focused on our career and the things that would get us a good job. But in the process, we often forget that we aren’t just doing it for a job. We’re doing it for the joy of programming. It is OK to spend some time learning something that you find interesting even if it doesn’t make sense at the time — even if it’s not going to help you in your career right away or ever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hn6icdAZ3G5CIgC7" /><figcaption>Photo by <a href="https://unsplash.com/@joshstyle?utm_source=medium&amp;utm_medium=referral">JOSHUA COLEMAN</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><p>Always remember, feeling overwhelmed is an important milestone in your journey. It shows that you’re trying to do something that is outside your comfort zone. After all, it is a marathon — not a sprint.</p><p>Thank you for reading. I hope this piece helps you beat that feeling and makes you realize that it’s not so bad to be overwhelmed sometimes. It is a minor setback and you’ll soon be right back on your feet. All the best!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9270743c075d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/what-to-do-when-programming-overwhelms-you-9270743c075d">What to Do When Programming Overwhelms You</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[THE EPIDEMIC OF LONELINESS]]></title>
            <link>https://medium.com/@adarsh.nanwani/the-epidemic-of-loneliness-1b37b6dacfde?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b37b6dacfde</guid>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 03:00:30 GMT</pubDate>
            <atom:updated>2020-01-07T03:00:30.849Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Epidemic Of Loneliness</h3><h4>Life in the times of instant gratification</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oMoGbgkOL9SFrcps" /><figcaption>Photo by <a href="https://unsplash.com/@samaustin?utm_source=medium&amp;utm_medium=referral">Samuel Austin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When was the last time you were alone? Truly alone.</p><p>Without your mobile phone. Without the internet. Without music. Without friends. Without family. Without movies. Just you. All by yourself.</p><p>Finding it difficult to remember? Well, you’re not the only one.</p><p>In a recent study in the United States, when asked if one would like to spend 15 minutes alone all by themselves or get an electric shock. Surprisingly, 60% of men and 36% of women chose the electric shock.</p><p>When did this happen? When did we become so afraid of loneliness? Being born in the early 90s, a millennial if you will, I can vividly remember the sultry summer afternoons when my mother would put me down for an afternoon siesta and I being the frantic child that I was, just won’t fall asleep. I would just pretend to sleep for some time and then I’d just lie in bed, looking at the clock, waiting for the time to wake up. And I’d be thinking this and that and everything under the sun. Everything that my 8-years old self could think of.</p><p>I haven’t done that since God knows when. Be all by myself, that is. I do not mean that I haven’t been lonely. I have. I enjoy solitude. I have driven up to the mountains alone to sit on a public bench and read a book. I have sat alone in a coffee shop to write a business proposal and enjoyed doing that. And I’d do that again. But, even in the middle of a conversation, I find myself randomly taking out my phone and staring at the screen. Also, when I’m just sitting, reading, or working. And I would tell myself that maybe I needed to check what time it was. I have seen almost everyone do the same. Ever so often. But I don’t think we need to check the time 10 times in 20 minutes. It is an excuse or at least a symptom of a bigger problem.</p><p>I figured that my dependency (addiction?) to social media has me hooked on this thing called instant gratification. I need IT, and I need IT now. What’s IT, you ask? Everything. Everything has to be quick and instantaneous.</p><p>I didn’t realize when living with distractions became a norm for me. I’m always on the lookout — for a notification, for an email, to see how many likes my last post gathered, to see what people are up to in their lives, to see where that old friend of mine is going to travel next, to see who in my followers list is getting married or having children. And the result, after all that endless scrolling, is never pretty.</p><p>On social media, we see what people want us to see. You don’t believe me? Just take a look at your social media feed. Technology did bring us together by making the distances irrelevant and reducing the time it takes to communicate. But the downside is, we have started to expect replies too in the same way. Instantly. It’s called Instant Messaging for a reason and not Instant Conversation or Instant Replies. Because only the message transfer is faster and enhanced, not the human capacity to digest information and focus. It didn’t magically make us capable of living these high-speed lives where someone out there is always expecting a reply from you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t6M3AHzIwCL4QL-Z" /><figcaption>Photo by <a href="https://unsplash.com/@timbennettcreative?utm_source=medium&amp;utm_medium=referral">Tim Bennett</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>An email from work, an SMS from a friend, a DM from a follower, they all want replies right away. They all want your attention. And you’re eager to give it away too. Because replying in an instant is a sign of being proactive. It’s a virtue, they say. It shows that you value the other person. And it smartly hides the fact that we don’t value the work at hand or ourselves as much.</p><p>During my college years, I used to do this thing where I would deactivate my Facebook account for a month or so during finals. I never thought anything of it. I knew it helped me focus and I scored better because of it. But, now I realize I was trying to get away from the distraction and ultra-connectivity addiction. But the issue is not just about productivity.</p><p>Coming back to the root problem posed by this story “The Epidemic Of Loneliness”. It took root when you created your first social media account. When you sent out your first tweet. When you Instagrammed your first picture.</p><p>And with time it has grown and became part of our conscience in a way that we don’t even notice anymore. We have normalized our fear of loneliness. We accept it at face value. This isn’t natural. We are not supposed to fear the occasional solitude. If one can’t enjoy it, that’s okay. But, one shouldn’t be choosing electric shocks over it either.</p><p><strong>Franklin D. Roosevelt</strong> rightly said, “<em>The only thing to fear is fear itself.</em>” And here I am trying to do the same. One has to venture out of her comfort zone to truly get a measure of her person.</p><blockquote>Without challenge, without a deep-rooted need to focus, without a goal to chase, life is meaningless.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bmdFiS9jVAbY93j8" /><figcaption>Photo by <a href="https://unsplash.com/@fuuj?utm_source=medium&amp;utm_medium=referral">Fuu J</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We don’t realize this at all because of the shiny world of social media. It bombards us with distractions every other minute, giving us a false sense of belonging when there is none.</p><p>It’s about time we realize this and look within ourselves. So just take some time off social media and see how deep down you can go. Try to find what’s hidden in your intellect.</p><p><strong>And maybe in a moment of joyous and voluntary loneliness, you might find yourself.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b37b6dacfde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review — Roads to Mussoorie by Ruskin Bond]]></title>
            <link>https://medium.com/@adarsh.nanwani/book-review-roads-to-mussoorie-by-ruskin-bond-789b6c8082ec?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/789b6c8082ec</guid>
            <category><![CDATA[ruskin-bond]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[better-humans]]></category>
            <category><![CDATA[book-recommendations]]></category>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Sat, 26 Jan 2019 09:00:56 GMT</pubDate>
            <atom:updated>2019-01-26T09:00:56.152Z</atom:updated>
            <content:encoded><![CDATA[<h3>Book Review — Roads to Mussoorie by Ruskin Bond</h3><h4>Book 1 (of 12) for the year 2019</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b8fImxftCwnJoPpr" /><figcaption>Photo by <a href="https://unsplash.com/@dearseymour?utm_source=medium&amp;utm_medium=referral">Ksenia Makagonova</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I decided to read at least 1 book every single month. These days, with a smartphone in every hand, we are bombarded with so much content at all times of the day (and night) that it becomes addicting to us. We’re always watching something on YouTube, or tagging our friends in memes on Facebook and or sharing stories on Instagram and Snapchat, or having a conversation (or silently reading the group texts) on WhatsApp. It takes a lot of will power to actually pick up a book and READ it.</p><h3>Some backstory</h3><p>In my school days, I used to be an avid reader. In the prime of my reading habit, I must have read about 300 books in 8 months. But those were the days before we had infinite streams of content available for consumption at our fingertips. So, I have been meaning to get back into the habit of reading for a while now.</p><blockquote>And to be a better writer, you must read a lot first.</blockquote><p>Hence, I decided to read at least 1 book each month of this year(2019). I wanted to start with something light, and <strong><em>Roads to Mussoorie</em></strong> by <strong><em>Ruskin Bond</em></strong> seemed exactly the kind of book I should read.</p><h3>The book review</h3><p>Title: <strong>Roads to Mussoorie</strong><br>Author: <a href="https://www.wikiwand.com/en/Ruskin_Bond"><strong>Ruskin Bond</strong></a><br>Publisher: <strong>Rupa Publications<br></strong>Buy it on <a href="https://www.amazon.in/dp/812910699X/ref=cm_sw_r_wa_apa_i_.ZbtCbJJ5VN0S">Amazon</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HiNe-gAxEjG-gmUkf7Tr5A.jpeg" /><figcaption>My copy of Roads to Mussoorie</figcaption></figure><p>This book is filled with many anecdotes from the author’s life in the mountains, especially in and around his home in Mussoorie. The book itself is rather unique in character, as the introduction is titled “Backward” and the author tells you to read the book backwards, i.e. read the last chapter first, then the second-last and so on. So, I did just that.</p><p>While reading, you would surely develop a connection with the people and places mentioned in the book. Many a time, you would chuckle at his dry and natural sense of humor.</p><blockquote>If you love mountains and lust for untouched and unspoiled treasures of Himalayas like I do. You would love this book.</blockquote><p>It’s like a window to the author’s pure soul and his reminiscence of the past spill a feeling of nostalgia so strong that you would too want to retire quietly in your childhood playground and watch the child in you grow older. It’s a feeling we all feel, but we find it hard to convey. The author has done a fantastic job doing it. I doubt anyone will ever come close to that.</p><p>I wouldn’t spoil the book for you and I can’t even if I wanted to because you just can’t spoil this feeling of nostalgia and this emotion called life portrayed so beautifully in such simple words. I want you to get yourself a copy and read this gem of a book.</p><p>And I assure you would be amazed by the historical facts spread across the chapters in this book which give a fresh perspective to the things you know of, places you have been to and the places you will go to. I certainly felt surprised and crushed under the weight of history to know that the Ganga canal which I have seen in <em>Haridwar</em>, <em>Narora</em> and <em>Aligarh</em> was built in 1850(s) and it was one man’s dream to build it, who did so and walked away from the fame and glory of it all. The next time I would stand on the steps of a ghat on the Ganga canal I would certainly remember that man and his work and soak in the feeling that we are survived by our work and our stories.</p><p>I leave you with a saying that’s in the book.</p><blockquote>“All men are my friends. I have only to meet them.”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=789b6c8082ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Understand and Embrace Change]]></title>
            <link>https://medium.com/@adarsh.nanwani/how-to-understand-and-embrace-change-673c72e9bc23?source=rss-ce3062470fe1------2</link>
            <guid isPermaLink="false">https://medium.com/p/673c72e9bc23</guid>
            <category><![CDATA[corporate-team-building]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Adarsh Nanwani]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 08:56:25 GMT</pubDate>
            <atom:updated>2018-10-03T08:56:25.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*T27EYqUyryEKCOcRYgKVAg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kylejglenn?utm_source=medium&amp;utm_medium=referral">Kyle Glenn</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It requires utmost dedication and commitment to undergo a successful transformation. The essence of this activity lies in the belief that you’re doing this for good and to get better. You will have to trust yourself before others can start trusting you.</p><p>Though, your foundations will be scrutinized, and your beliefs will be shrugged off, by everyone including your own conscience. But, you must latch on to them and keep reminding yourself why you decided to do that in the first place.</p><p><strong>Hurdles will be in the way, you must keep dodging them and move on.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ONo3oCCfUb4q4z9o" /><figcaption>Photo by <a href="https://unsplash.com/@paucasals?utm_source=medium&amp;utm_medium=referral">Pau Casals</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Now, if you’re not driving the change but the you’re being affected by it. Then, you’ll be on a journey of your own. A 3-part journey to be precise.</p><h3>Part 1: Resistance</h3><p>It will begin with disbelief, such as<br> — I don’t need this change and I am better off without it<br> — I don’t see the benefits of this change<br> — I don’t trust the person leading it<br> — I think there are better ways to do it, and many more.</p><p>And these will make sense to you at that moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JqnhXfLOcjOF4GM7" /><figcaption>Photo by <a href="https://unsplash.com/@sweeticecreamwedding?utm_source=medium&amp;utm_medium=referral">Sweet Ice Cream Photography</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We have all been there, myself included. We always want to be in control because change is scary and usually it takes us out of our comfort zone.</p><h3>Part 2: Introspection</h3><p>You’ll need deeper introspection to realize that your disbeliefs are arising from one or more thoughts such as<br> — I am very comfortable with the current state of affairs and do not want it to change<br> — I am scared of the change<br> — I think I can lead it better<br> — I think the change might disrupt the status quo and impact my positioning negatively, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hDoveK_7JKFWL87a" /><figcaption>Photo by <a href="https://unsplash.com/@lensinkmitchel?utm_source=medium&amp;utm_medium=referral">Mitch Lensink</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You will need to realize the truth about yourself and about your attitude toward the change.</p><blockquote>Your goal must be to understand why you are afraid. Only then you can overcome it.</blockquote><h3>Part 3: Acceptance</h3><p>It is here, where you need to change your point of view from your personal space to the point of view of the community because you might be able to shift the narrative and block the change for the time being. But, it will impact the community badly in the long run and in case you haven’t noticed already, you’re too a part of the community.</p><blockquote>You must take it with an open mind and be ready to embrace the change positively.</blockquote><p>These are rapidly changing times and there is a dearth of responsible and accountable people. The market dynamics change sooner than the weather. Every day, there are more problems created than the total number of steps you take in a day. And all of them need critical thinking and out-of-the-box and innovative solutions. In order to get the best out of this change, you need to internalize it and think about it and ponder on a few things such as<br> — how can I use this opportunity to get better<br> — I should trust the person leading it<br> — I should be supportive of the change and be a facilitator<br> — think about how the change is going to make the community better and improve everyone</p><blockquote>If you can understand and accept all these things and let yourself be a vehicle for change. It is when you transform.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EZLpC847Qg_5N2bO" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>To understand its true impact, think of it at the scale of a community or an organization.</p><p>If you are a leader who is driving the change, you need to consider all these things to be successful and achieve the transformation you have set as your goal. It is extremely difficult to change just one person, and to change a community you’ll need a lot more than strong willpower and a plan. You’ll have to sacrifice self for a higher goal. <strong>You’ll need a rock-solid belief in your goal and an undying thirst to achieve it.</strong></p><p>If you are being affected by the change and if you have read this far, <strong>you would understand by now it is never about one person</strong>. You’ll need to see the big picture and understand the challenges of community and/or organization. Like the person driving it, you too will have to sacrifice self for a higher goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Iaowh8CE9bckSmDz" /><figcaption>Photo by <a href="https://unsplash.com/@xangriffin?utm_source=medium&amp;utm_medium=referral">Xan Griffin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>It is not possible without you because ultimately you are the change.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=673c72e9bc23" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>