<?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 Palak on Medium]]></title>
        <description><![CDATA[Stories by Palak on Medium]]></description>
        <link>https://medium.com/@palaklive?source=rss-5d0d749bccfc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7PMMquSjUDv83_ObNVDNbQ.png</url>
            <title>Stories by Palak on Medium</title>
            <link>https://medium.com/@palaklive?source=rss-5d0d749bccfc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:15:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@palaklive/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[Boost Your API Performance with These Sneaky Tricks! ]]></title>
            <link>https://medium.com/@palaklive/boost-your-api-performance-with-these-sneaky-tricks-608d5b43eb3e?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/608d5b43eb3e</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[api-best-practices]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Sun, 09 Jul 2023 17:55:43 GMT</pubDate>
            <atom:updated>2023-07-09T17:55:43.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8XlLlXf39IqPZ9q6v8jUfg.png" /></figure><p>Attention, API Enthusiasts! <br>Get ready to unleash the true potential of your APIs with this exhilarating article. We’re diving deep into the world of API performance optimization, armed with a treasure trove of sneaky tricks that will elevate your API game to new heights. So fasten your seatbelts and get ready for an epic journey filled with adventure, efficiency, and a dash of API magic.</p><ol><li>Caching: Picture this, you’re running a marathon, and suddenly you find a secret shortcut that shaves off precious minutes from your time. That’s caching for your API! Implement caching mechanisms like Redis to store frequently accessed API responses. It’s like having a magical cache genie that saves you from doing the same heavy lifting repeatedly. ⚡️</li><li>Efficient Database Queries: Let’s navigate through the treacherous realms of databases with the grace of a ninja! Optimize your database queries by using indexes, avoiding unnecessary joins, and fetching only the needed data. It’s like being a master thief, swiftly grabbing the desired data without getting tangled in unnecessary information. Stealthy and efficient! 🥷</li><li>API Pagination: Embark on an Epic Adventure of Data Exploration! Imagine diving into a Choose Your Adventure book but with your API responses as thrilling chapters. With API pagination, you’ll break down those massive result sets into bite-sized portions, just like turning the pages of a captivating story. Each step reveals the perfect amount of data, fueling your curiosity and guiding you through an exhilarating quest. Get ready for epic adventures in the world of APIs! 🚀</li><li>Throttling and Rate Limiting: Let’s be honest, we all need some order in our lives, even APIs! Implement throttling and rate limiting to keep things in check. It’s like being the wise bouncer at an exclusive API club, ensuring that only the VIP requests get in, while politely asking the rowdy ones to step back. Classy and fair! 🎩</li><li>Request and Response Compression: Imagine having a shrink ray for your API! Compress those chunky API requests and responses using techniques like gzip or deflate. It’s like packing your API data into a tiny suitcase, making it travel faster through the network and arrive at its destination in record time. Small, but mighty! 💼</li><li>Database Indexing: Think of indexing as a treasure map for your database! Properly index those relevant fields to speed up query execution. It’s like having a compass that guides you straight to the buried gold, avoiding unnecessary detours and saving valuable time. X marks the spot! 🗺️</li><li>Scaling and Load Balancing: Let’s throw a massive party for your API! Scale your infrastructure like a pro by adding more servers and using load balancers to distribute the load. It’s like hosting a legendary fiesta where everyone gets their fair share of tacos, margaritas, and API requests. 🌮</li><li>Monitoring and Profiling: Become the Sherlock Holmes of API performance! Use performance monitoring tools and profilers to solve the mysteries of bottlenecks and optimize your way to success. It’s like having a trusty magnifying glass that reveals the hidden culprits slowing down your API. Elementary, my dear Watson! 🔍</li><li>Database Connection Pooling: Let’s carpool our way to database efficiency! Use connection pooling to reuse existing database connections, like sharing a ride with your fellow API travelers. It’s like cruising in the HOV lane, bypassing the traffic of connection establishment and reaching your destination faster. Together, we go farther! 🚗</li><li>Webhooks and Asynchronous Processing: Time to add a touch of magic to your API operations! Offload those time-consuming tasks to background workers or queues. It’s like having a team of reliable wizard apprentices who handle the heavy lifting while you sip your magical potion of productivity. Enchanting efficiency! 🧙</li></ol><p>So, my fellow API adventurers, equip yourselves with these powerful tricks, sprinkle some humor, and watch your API performance skyrocket! Prepare to impress your users and leave your competitors in awe. Happy optimizing, and may the API force be with you! 🚀✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=608d5b43eb3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Development in 2022: Recap]]></title>
            <link>https://medium.com/@palaklive/web-development-in-2022-recap-f25f0197f897?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f25f0197f897</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[2022]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Fri, 30 Dec 2022 07:09:49 GMT</pubDate>
            <atom:updated>2022-12-30T07:09:49.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mqWAZhzUxu6qXESCdFMxWQ.png" /></figure><p>It’s been an exciting year for web development in 2022, with new tools and technologies emerging and established ones continuing to evolve. In this comprehensive recap, we’ll take a look at some of the key trends and tools that have shaped the world of web development this year.</p><h3>AI is finally making its way into developer’s lives</h3><p>One of the biggest trends in web development this year has been the increasing integration of artificial intelligence (AI) into tools and workflows. Tools like GitHub Copilot and OpenAI Chat GTP have made it easier for developers to incorporate AI into their projects, and we’ve seen a proliferation of AI-powered services and platforms that are designed to help developers build smarter, more efficient applications.</p><h3>JavaScript continues to reign supreme</h3><p>JavaScript has long been the go-to language for web development, and that hasn’t changed in 2022. It’s still the top choice for programming and scripting. Whether you’re building a simple website or a complex web application, there’s a good chance that you’ll be using JavaScript in some form.</p><h3>TypeScript on the rise</h3><p>TypeScript, a typed superset of JavaScript, has become increasingly popular among web developers this year. It’s a great choice for large-scale projects that require a high level of type-checking and strong typing.</p><h3>SQL databases continue to dominate the market</h3><p>SQL databases like PostgreSQL and MySQL are still going strong in the world of web development. These powerful, reliable databases are used by a wide range of applications and are known for their ability to handle large amounts of data with ease. Further cementing their position as top choices for developers.</p><h3>Rust growing in popularity for building tooling systems</h3><p>Rust, a programming language designed for performance, safety, and concurrency, has been gaining traction among web developers this year. It’s particularly popular for building tooling systems, and we’ve seen a number of new tools and libraries emerge that are designed to make it easier for developers to use Rust for web development.</p><h3>Server-rendered web frameworks on the rise</h3><p>Web frameworks that use server rendering, like Astro Build, Qwik, and Next JS 13 with React Server Components, are gaining popularity among web developers. These frameworks allow developers to build faster, more efficient web applications by pre-rendering content on the server and serving it to the client. We’ve seen a number of updates and new features rolled out for these frameworks this year, making them more powerful and easier to use.</p><h3>Docker becoming a fundamental tool for professional developers</h3><p>Docker, a tool that allows developers to package applications in lightweight containers, has become increasingly important for professional web developers in 2022. It’s a great way to ensure that applications can be easily deployed and run in different environments, and we’ve seen a number of updates and new features rolled out for Docker this year.</p><h3>Visual Studio Code remains the preferred IDE</h3><p>Visual Studio Code, a popular integrated development environment (IDE), has continued to be the preferred choice for many web developers this year. It offers a wide range of features and tools that make it easy for developers to write, debug, and deploy code, and we’ve seen a number of updates and new features rolled out for Visual Studio Code in 2022.</p><h3>Jira is the most used tool for work management</h3><p>Jira, a project management and issue-tracking tool has been widely adopted by web developers this year for work management. It offers a range of features that make it easy for developers to track and manage tasks, collaborate with team members, and stay organized.</p><h3>Zoom and Microsoft Teams are the choice for communication</h3><p>Zoom and Microsoft Teams have become the go-to tools for communication this year. These platforms offer a range of features that make it easy for developers to connect with team members, share files, and collaborate in real time.</p><h3>AWS remains the most used and loved cloud platform</h3><p>AWS, a cloud computing platform, has continued to be the most widely used and loved platform. It offers a wide range of services and tools that make it easy for developers to build, deploy, and manage applications, and we’ve seen a number of updates and new features rolled out for AWS in 2022.</p><h3>Notion is the most loved growing tool for collaboration</h3><p>The notion, of a collaboration and productivity tool, has gained a lot of popularity. It offers a range of features that make it easy for everyone to collaborate with team members and organize their work, priority, and other stuff. Its popularity has continued to grow in 2022.</p><p>In conclusion, it’s been a dynamic year for web development, with new tools and technologies emerging and established ones continuing to evolve. As we move into the future, it will be interesting to see how these trends and tools continue to shape the world of web development.</p><p>Thanks for reading, I appreciate feedback and would love to hear your thoughts on this topic! It takes hours of research and attention to create this article. Please give it a few claps to motivate me to keep writing.</p><p><em>If you’re interested in web development 🔥</em><strong><em><br></em></strong><em>Feel free to reach out to me on</em><strong><em> </em></strong><a href="https://twitter.com/palaklive_"><strong><em>Twitter</em></strong></a><strong><em> | </em></strong><a href="https://www.linkedin.com/in/palaklive/"><strong><em>LinkedIn</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f25f0197f897" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[State of the React JS in 2021]]></title>
            <link>https://medium.com/@palaklive/state-of-the-react-js-in-2021-ce8af5e7a36a?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce8af5e7a36a</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Mon, 18 Oct 2021 20:44:38 GMT</pubDate>
            <atom:updated>2022-01-28T04:17:28.353Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YLzz_vtHLOk1K6Z08h6xhg.png" /></figure><h4>In 2021, what every React developer needs to know!</h4><p>React JS has held the top spot among JavaScript frontend frameworks for the past three years in a row. It is important to note that while developers can construct various React applications using several coding patterns, tools, and technologies, each has its own set of best practices and is suited to different business needs. In the following article, I’ll present a list of potential uses for React, along with a few additional perks that make this technology so special.</p><blockquote>Regardless of whether you intend to use React, taking a look at its ecosystem can inspire you. So, Let’s explore the State of React JS!</blockquote><h4>We will cover various topics in this article, including:</h4><ul><li><strong>Programing language</strong></li><li><strong>Component approach</strong></li><li><strong>Routing</strong></li><li><strong>State Management</strong></li><li><strong>Data Fetching</strong></li><li><strong>Bundlers</strong></li><li><strong>Forms</strong></li></ul><h3>Programing language</h3><p>Let’s take a look at history. As React is a JavaScript library, we know React developers are familiar with writing Javascript code using ES6 and ES-Next. Fundamentally, they will use JSX as syntax sugar. In order to improve static type checking, developers use prop types and add features like auto-completion. For larger codebases, developers are recommended to use Flow or TypeScript instead of prop types.</p><p>At that moment, Create React App does not officially support flow or typescript causes the vast majority of developers to choose Javascript. Angular is the only framework that fully adopts typescript as a programming language.</p><blockquote>In the last few years, typescript has grown in popularity in the market, and for good reason. When starting out, React Developers prefer typescript over javascript. The official support for typescript is also shared by Create React App.</blockquote><p>TypeScript can be helpful to React developers in many ways. Below are just a few benefits of using TypeScript in React.</p><h4>Community</h4><p>TypeScript is a free, open-source programming language developed and maintained by Microsoft. It is a superset of JavaScript that adds optional static typing and class-based, object-oriented programming to the language.</p><h4>JavaScript and More</h4><p>TypeScript adds additional syntax to JavaScript to support a <strong>tighter integration with your editor.</strong> Catch errors early in your editor.</p><h4>A Result You Can Trust</h4><p>TypeScript code converts to JavaScript which <strong>runs anywhere JavaScript runs</strong>: In a browser, on Node.js or Deno, and in your apps.</p><h4>Safety at Scale</h4><p>TypeScript understands JavaScript and uses type inference to give you great tooling without additional code.</p><p><em>You can find more details in the </em><a href="https://create-react-app.dev/docs/adding-typescript/#getting-started-with-typescript-and-react"><strong><em>Getting Started with TypeScript and React</em></strong></a><em>.</em></p><h3>Component approach</h3><p>Components let you split the UI into independent, reusable pieces, and think about each piece in isolation. In the world of React, there are two ways of writing a React component. One uses a function and the other uses a class.</p><p>Recently functional components are becoming more and more popular, so why is that?</p><h4>Rendering JSX</h4><p>A functional component is nothing more than a plain JavaScript function that returns JSX as its output. Class components are JavaScript classes that extend React.Component, which has a render method. Furthermore, when we use classes we have to deal with this and binding. Neither the developer nor the compiler will enjoy this.</p><p>A bit confusing? Let’s take a look at a simple example:</p><pre>// Class Component<br>import React from &quot;react&quot;;</pre><pre>class ClassComponent extends React.Component {<br> render() {<br>   return &lt;h1&gt;Hello, world&lt;/h1&gt;;<br> }<br>}</pre><p>When defining a class component, you have to make a class that extends React.Component. The JSX to render will be returned inside the render method.</p><pre>// Function Component<br>import React from &quot;react&quot;;</pre><pre>function FunctionalComponent() {<br> return &lt;h1&gt;Hello, world&lt;/h1&gt;;<br>}</pre><p>As you can see, there is no additional rendering method or extension for the function component. On a larger scale, we don’t have to deal with constructors, binds, and other things.</p><h4>Passing props</h4><p>Passing props can be confusing, but let’s see how they are written in both class and functional components. Let’s say we are passing props of the name “Palak” like below.</p><pre>// Passing props<br>&lt;Welcome name=&quot;Palak&quot; /&gt;</pre><pre>// Function component<br>function Welcome(props) {<br> return &lt;h1&gt;Hello, {props.name}&lt;/h1&gt;;<br>};<br> <br>// Function component with Destructuring<br>function Welcome({name}) {<br> return &lt;h1&gt;Hello, {name}&lt;/h1&gt;;<br>};</pre><pre>// Class Component<br>class ClassComponent extends React.Component {<br> /* constructor is optional<br>  * In ideal case we have to deal with it <br>  * state and handle click mentioned for the same<br>  * for simple Hello Message not need for it<br>  */<br> constructor(props) {<br>  super(props);<br>  // this.state = { counter: 0 };<br>  // this.handleClick = this.handleClick.bind(this);<br> }<br> render() {<br>    // Work with class developer have to deal with this<br>    const { name } = this.props;<br>    return &lt;h1&gt;Hello, { name }&lt;/h1&gt;;<br> }<br>}</pre><h4>Handling state</h4><p>As part of React 16.8, useState was introduced to make it possible to write stateful functional components. You can learn more about Hooks from the <a href="https://reactjs.org/docs/hooks-overview.html"><strong>official documentation</strong></a>.</p><p>Here we will create a simple counter component.</p><pre>// Handling state in functional components<br>function Counter() {<br> const [count, setCount] = React.useState(0);</pre><pre> return (<br>    &lt;div&gt;<br>      &lt;p&gt;count: {count}&lt;/p&gt;<br>      &lt;button onClick={() =&gt; setCount(count + 1)}&gt;Click&lt;/button&gt;<br>    &lt;/div&gt;<br>  );<br>};</pre><p>To use state variables in a functional component, we need to use the useState Hook, which takes an argument of the initial state. In this case, we start with a count of zero.</p><pre>// Handling state in class components<br>class Counter extends React.Component {<br> constructor(props) {<br>   super(props);<br>   this.state = {<br>     count: 0<br>   };<br> }</pre><pre>render() {<br>   return (<br>     &lt;div&gt;<br>       &lt;p&gt;count: {this.state.count} times&lt;/p&gt;<br>       &lt;button onClick={() =&gt; this.setState({ count: this.state.count + 1 })}&gt;<br>         Click<br>       &lt;/button&gt;<br>     &lt;/div&gt;<br>   );<br> }<br>}</pre><p>In the class component, without implementing the constructor and calling super(props), all the state variables that you are trying to use will be undefined. So let’s define the constructor first. Inside the constructor, you will make a state object with a state key and initial value. And inside JSX, we use this.state.count to access the value of the state key we defined in the constructor to display the count.</p><h4>Lifecycle Methods</h4><p>Finally, let’s talk about lifecycles. Don’t worry, we’re almost there! As you already know, lifecycles play an important role in the timing of rendering. For those of you who are migrating from class components to functional components, you might wonder what would replace lifecycle methods. The answer is <strong>useEffect</strong>.</p><p>React counter class component that updates the document title right after React makes changes to the DOM:</p><pre>// Class Component<br>class Page extends React.Component {<br>  constructor(props) {<br>    super(props);<br>    this.state = {<br>      count: 0<br>    };<br>  }</pre><pre>componentDidMount() {<br>    document.title = `You clicked ${this.state.count} times`;<br>  }<br>  componentDidUpdate() {<br>    document.title = `You clicked ${this.state.count} times`;<br>  }</pre><pre>render() {<br>    return (<br>      &lt;div&gt;<br>        &lt;p&gt;You clicked {this.state.count} times&lt;/p&gt;<br>        &lt;button onClick={() =&gt; this.setState({ count: this.state.count + 1 })}&gt;<br>          Click me<br>        &lt;/button&gt;<br>      &lt;/div&gt;<br>    );<br>  }<br>}</pre><p>The Effect Hook lets you perform side effects in function components:</p><pre>// Function Component<br>import React, { useState, useEffect } from &#39;react&#39;;<br>function Page() {<br>  const [count, setCount] = useState(0);<br><br>  // Similar to componentDidMount and componentDidUpdate:</pre><pre>  useEffect(() =&gt; {<br>   // Update the document title using the browser API<br>   document.title = `You clicked ${count} times`;<br>  });<br>  return (<br>    &lt;div&gt;<br>      &lt;p&gt;You clicked {count} times&lt;/p&gt;<br>      &lt;button onClick={() =&gt; setCount(count + 1)}&gt;<br>        Click me<br>      &lt;/button&gt;<br>    &lt;/div&gt;<br>  );<br>}</pre><p>You can find more details in the <a href="https://reactjs.org/docs/hooks-reference.html#useeffect"><strong>official documentation</strong></a> of the useEffect.</p><h3>Routing</h3><p>Routing in the internet world refers to the capability of moving between separate parts of an application when the user clicks a link within the application. They allow your user to move between the components of your app while preserving the user state and can provide unique URLs for these components to make them more shareable. With routers, you can improve your app’s user experience by simplifying site navigation.</p><h4><strong>Routing tradition can be divided into two categories:</strong></h4><ol><li><strong>client-side rendering</strong></li><li><strong>server-side rendering</strong></li></ol><h4><strong>client-side rendering</strong></h4><p>In order to implement routing capabilities in the React application on the client-side, developers tend to use the popular <a href="https://reactrouter.com/web/guides/quick-start"><strong>React-Router library</strong></a>. React Router is a standard library for routing. It allows navigation between the views of various components in a React Application, changes the browser URL, and synchronizes the UI with the URL.</p><h4><strong>server-side rendering</strong></h4><p>Frameworks like Next JS and Gatsby have a file-system-based router built on the concept of pages. When a file is added to the page&#39;s directory it’s automatically available as a route. The router supports nested files. If you create a nested folder structure files will be automatically routed in the same way still.</p><p>The Next.js router also allows users to do client-side route transitions between pages, similar to a single-page application.</p><p>You can find more details in the official documentation of <a href="https://nextjs.org/docs/routing/introduction"><strong>NextJS Routing</strong></a> | <a href="https://www.gatsbyjs.com/docs/reference/routing/creating-routes/"><strong>GatsbyJS Routes</strong></a>.</p><h3>State Management</h3><p>Having grown tremendously, React.JS has given birth to many state management libraries. There are a lot of controversies surrounding this topic this year, so let me give you my suggestions and references.</p><h4>Before we begin, familiarize yourself with the terms commonly used:</h4><ul><li>UI State — State used for controlling interactive parts of our application (e.g. dark mode toggle, modals).</li><li>Server Cache State — State from the server, which we cache on the client-side for quick access (e.g. call an API, store the result, use it in multiple places).</li><li>Form State — The many different states of a form (e.g. loading, submitting, disabled, validation, retrying). There’s also a controlled &amp; uncontrolled form state.</li><li>URL State — State managed by the browser (e.g. filter products, saving to query parameters, and refreshing the page to see the same products filtered)</li><li>State Machine — An explicit model of your state over time (e.g. a stoplight goes from green → yellow → red, but never green → red).</li></ul><h4>Top Mentions:</h4><ul><li><a href="https://redux-toolkit.js.org/"><strong>Redux Toolkit</strong></a></li><li><a href="https://xstate.js.org/docs/"><strong>XState</strong></a></li><li><a href="https://mobx.js.org/README.html"><strong>MobX</strong></a></li><li><a href="https://github.com/facebookexperimental/recoil"><strong>Recoil</strong></a></li><li><strong>Context API + useContext</strong></li></ul><h4>Reference:</h4><ul><li><a href="https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367"><strong>Dan Abramov: You Might Not Need Redux</strong></a></li><li><a href="https://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet/"><strong>Mark’s Dev Blog: Redux — Not Dead Yet!</strong></a></li><li><a href="https://leerob.io/blog/react-state-management"><strong>Past, Present, and Future of React State Management</strong></a></li><li><a href="https://stackoverflow.com/a/49569183/7762250"><strong>React Context vs React-Redux, when should I use each one? [closed]</strong></a></li></ul><h3>Data Fetching</h3><p>Out of the box, React applications do not come with an opinionated way of fetching or updating data from your components so developers end up building their own ways of fetching data. This usually means cobbling together component-based state and effect using React hooks or using more general-purpose state management libraries to store and provide asynchronous data throughout their apps.</p><p>While most traditional state management libraries are great for working with client states, they are not so great at working with async or server states.</p><p>As you learn more about the server state in your application, you will encounter even more challenges. For example:</p><ul><li>Caching</li><li>Updating “out of date” data in the background</li><li>Performance optimizations like pagination and lazy loading data</li><li>Memoizing query results with structural sharing</li></ul><p>Consider the following query approach, hands down the best list of libraries for managing server state. It works amazingly well out-of-the-box, with zero configuration, and it can be customized to fit your needs as you grow.</p><h4>Top Mentions:</h4><ul><li><a href="https://react-query.tanstack.com/"><strong>React Query</strong></a></li><li><a href="https://redux-toolkit.js.org/tutorials/rtk-query"><strong>RTK Query | Redux Toolkit</strong></a></li><li><a href="https://www.apollographql.com/docs/react/"><strong>Apollo Client</strong></a></li><li><a href="https://formidable.com/open-source/urql/"><strong>URQL</strong></a></li></ul><h3>Bundlers</h3><h4>Top two Mentions:</h4><ol><li><strong>Webpack</strong></li><li><strong>ESBuild</strong></li></ol><h4>Webpack</h4><p>Webpack is a module bundler. Webpack can take care of bundling alongside a separate task runner. However, the line between bundler and task runner has become blurred thanks to community-developed webpack plugins. Sometimes these plugins are used to perform tasks that are usually done outside of webpack, such as cleaning the build directory or deploying the build although you can defer these tasks outside of webpack.</p><p>The use of Webpack is almost universal. The topmost starter kit is like create-react-app using webpack under the hood. The same is used by modern frameworks such as NextJS and Gatsby.</p><h4>ESBuild</h4><p>ESBuild is an extremely fast bundler and minified for JavaScript and CSS. The main goal of the ESBuild bundler project is to bring about a new era of build tool performance and create an easy-to-use modern bundler along the way.</p><p><strong>Major features:</strong></p><ul><li>Extreme speed without needing a cache</li><li>ES6 and CommonJS modules</li><li>Tree shaking of ES6 modules</li><li>An API for JavaScript and Go</li><li>TypeScript and JSX syntax</li></ul><p>Next Generation Frontend Tooling likes <a href="https://vitejs.dev/"><strong>Vite</strong> </a>using ESBuild under the hood.</p><h3>Forms</h3><p>In React, dealing with forms can be a real challenge. In addition, most form helpers do a lot of magic and are costly in terms of performance. So, we need some utilities to keep things sorted.</p><h4>Top Mentions:</h4><ul><li><a href="https://react-hook-form.com/"><strong>React Hook Form</strong></a></li><li><a href="https://formik.org/"><strong>Formik</strong></a></li></ul><blockquote>Thanks for reading, I appreciate feedback and would love to hear your thoughts on this topic! It takes hours of research and attention to create this article. Please give it a few claps to motivate me to keep writing.</blockquote><p><em>If you’re interested in front-end development or UI-UX hacks 🔥</em><strong><em><br></em></strong><em>Feel free to reach out to me on</em><strong><em> </em></strong><a href="https://twitter.com/palaklive_"><strong><em>Twitter</em></strong></a><strong><em> | </em></strong><a href="https://www.linkedin.com/in/palaklive/"><strong><em>LinkedIn</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce8af5e7a36a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Hacks to optimize your React app]]></title>
            <link>https://medium.com/@palaklive/7-hacks-to-optimize-your-react-app-231f4a034f2d?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/231f4a034f2d</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Sun, 10 Oct 2021 06:10:41 GMT</pubDate>
            <atom:updated>2022-01-28T04:18:39.626Z</atom:updated>
            <content:encoded><![CDATA[<h3>7 Hacks to Optimize Your React app</h3><p>In this post, I have put together React to specific best practices to have the best load time and runtime performance</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*flz48OAf_REo_uR1A7hzNg.png" /><figcaption>Image credit goes to Toptal</figcaption></figure><p>React is an amazing JavaScript library for building user interfaces and is well suited for developing large and small apps built to get the highest performance possible today on the web. But sometimes we as a developer end up doing things that result in the poorly performing app.</p><p>In this post, I have put together React-specific best practices to boost runtime performance. Also, apart from React. My intention in this post is just to list down the best practices and avoiding the detailed explanation thus keeping the post small.</p><h3>Identify Performance Issues</h3><p>In react-dom 16.5+ the React team has provided enhanced profiling capabilities in DEV mode through the React DevTools. This is always the first tool that I grab when investigating potential performance optimizations. You can find them here:</p><ul><li><a href="https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en">Chrome Browser Extension</a></li><li><a href="https://addons.mozilla.org/en-GB/firefox/addon/react-devtools/">Firefox Browser Extension</a></li><li><a href="https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil">Edge Browser Extention</a></li><li><a href="https://www.npmjs.com/package/react-devtools">Standalone Node Package</a></li></ul><ol><li>React DevTools Profiler</li></ol><ul><li>Profiling the performance of a React app can be a difficult and time-consuming process. By installing the React developer tools, you can record and interrogate the performance of individual components in your app and make this process much easier.</li><li>The React DevTools Profiler is usually the first place I will look. There is an official <a href="https://reactjs.org/blog/2018/09/10/introducing-the-react-profiler.html">blog post</a> and <a href="https://youtu.be/nySib7ipZdk">video walkthrough</a> that goes into great detail on using the profiler to gather performance data.</li></ul><p>2. React DevTools Update Highlighting</p><ul><li>React maintains a virtual DOM that it reconciles against to determine which parts of the UI need to re-render based on props or state changing. This is great, but it also means we don’t really know which parts of our application are updating at any given time. In the React DevTools, there is a setting you can turn on that will visually highlight elements on the screen as they render (or re-render).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*WIWCsDYHAmfYB5AiSH-mEA.png" /><figcaption>React DevTools</figcaption></figure><p>3. Why Did You Render</p><ul><li>Sometimes you know a certain React component should not be re-rendered unless there’s a very good reason. But how can you identify it? Let me share an incredible utility called <a href="https://github.com/welldone-software/why-did-you-render">@welldone-software/why-did-you-render</a> this will notify you of to cause of the re-rendering. After configuring your console will fill with information to help you track when and why certain components re-render.</li></ul><p>4. shouldComponentUpdate</p><ul><li>The <a href="https://reactjs.org/docs/react-component.html#shouldcomponentupdate">shouldComponentUpdate()</a> method is the first real life cycle optimization method that we can leverage in React. We can look at our current and new props &amp; state and make a choice if we should move on.</li><li>The purpose of shouldComponentUpdate is to indicate if render should be called. In your case, some parent component has rendered and indicated it wanted to also render an instance of your child component.</li><li>shouldComponentUpdate is your opportunity to short-circuit that render and say ‘don’t bother, nothing changed down here’.</li><li>Now, to your question, “why was it even called since nothing changed”? React does not compare the old and new props itself. You can get a mixin to do it for you, (ie. PureRenderMixin), but by default React just lets the render run.</li></ul><pre>class CounterButton extends React.Component {<br>  constructor(props) {<br>    super(props);<br>    this.state = {count: 1};<br>  }</pre><pre>shouldComponentUpdate(nextProps, nextState) {<br>    if (this.props.color !== nextProps.color) {<br>      return true;<br>    }<br>    if (this.state.count !== nextState.count) {<br>      return true;<br>    }<br>    return false;<br>  }</pre><pre>render() {<br>    return (<br>      &lt;button<br>        color={this.props.color}<br>        onClick={() =&gt; this.setState(state =&gt; ({count: state.count + 1}))}&gt;<br>        Count: {this.state.count}<br>      &lt;/button&gt;<br>    );<br>  }<br>}<br>}</pre><ul><li>The reason React doesn’t do the comparison itself is for a couple of reasons. Firstly, the performance savings of skipping render may be negligible compared to analyzing props and state. Since React’s render mechanism is already optimized to avoid unnecessary DOM manipulation it can just assume the component needs to update and expect reasonable performance. Secondly, doing the comparison is not exactly straight-forward. Is your prop a primitive?, an Immutable? an array? a complex object? will a deep comparison be necessary?</li><li>React’s model is “We will render everything asked by default. If you want something to opt-out for performance, then go ahead and tell us by implementing shouldComponentUpdate”.</li></ul><p>5. React.PureComponent</p><ul><li>When a class component extends <a href="https://reactjs.org/docs/react-api.html#reactpurecomponent">React.PureComponentbase</a> class then React treated the component as a Pure component. The major difference between React.Component class and React.PureComponent is the implementation of shouldComponentUpdate(). In React.Component shouldComponentUpdate() will always return true on the other hand in React.PureComponent will compare the current state and props with the new state and props.</li></ul><pre>import React, {PureComponent} from ‘react’;<br>export default class Test extends PureComponent{<br>   render(){<br>      return ‘’;<br>   }<br>}</pre><p>But, the point is React.PureComponent’s shouldComponentUpdate() only shallowly compares the objects. If these contain complex data structures, it may produce false negatives for deeper differences. Only extend PureComponent when you expect to have simple props and state, or use forceUpdate() when you know deep data structures have changed. Or, consider using immutable objects to facilitate fast comparisons of nested data.</p><p>Furthermore, React.PureComponent’s shouldComponentUpdate() skips prop updates for the whole component subtree. Make sure all the children components are also “pure”.</p><p>6. React.memo</p><ul><li>React.memo provides similar functionality if you use function components instead of class-based components.</li><li>React.memo is a <a href="https://reactjs.org/docs/higher-order-components.html">higher order component.</a></li><li>If your component renders the same result given the same props, you can wrap it in a call to React.memo for a performance boost in some cases by memoizing the result. This means that React will skip rendering the component, and reuse the last rendered result.</li><li>React.memo only checks for prop changes. If your function component wrapped in React.memo has a useState or useContext Hook in its implementation, it will still rerender when state or context change.</li><li>By default, it will only shallowly compare complex objects in the props object. If you want control over the comparison, you can also provide a custom comparison function as the second argument.</li></ul><pre>function MyComponent(props) {<br>  /* render using props */<br>}<br>function areEqual(prevProps, nextProps) {<br>  /*<br>  return true if passing nextProps to render would return<br>  the same result as passing prevProps to render,<br>  otherwise return false<br>  */<br>}<br>export default React.memo(MyComponent, areEqual);</pre><p>7. Virtualize large lists with react-window</p><ul><li>There may be times where you need to display a large table or list that contains many rows. Loading every single item on such a list can affect performance significantly.</li><li>List virtualization, or “windowing”, is the concept of only rendering what is visible to the user. The number of elements that are rendered at first is a very small subset of the entire list and the “window” of visible content moves when the user continues to scroll. This improves both the rendering and scrolling performance of the list.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*oKc42QexiAHtFJ76JI4UgA.jpeg" /><figcaption>Virtualize large lists with react-window</figcaption></figure><p><a href="https://react-window.now.sh/#/examples/list/fixed-size">react-window</a> is a library that allows large lists to be rendered efficiently. <a href="https://web.dev/virtualize-long-lists-react-window/">Here is a beautiful article on this topic</a>.</p><p>Thanks for reading, I appreciate feedback and would love to hear your thoughts on this topic!</p><blockquote>If you’re interested in front-end developement or UI-UX hacks <em>🔥</em><strong><br></strong>Feel free to reach out to me on<strong> </strong><a href="https://twitter.com/palaklive_"><strong>Twitter</strong></a><strong> | </strong><a href="https://www.linkedin.com/in/palaklive/"><strong>LinkedIn</strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=231f4a034f2d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blind men and an elephant]]></title>
            <link>https://medium.com/@palaklive/blind-men-and-an-elephant-cf41b513d8a2?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf41b513d8a2</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[truth]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 13:26:52 GMT</pubDate>
            <atom:updated>2020-07-02T13:26:52.070Z</atom:updated>
            <content:encoded><![CDATA[<p>Once upon a time, there lived six blind men in a village. One day the villagers told them, “Hey, there is an elephant in the village today.”</p><p>They had no idea what an elephant is. They decided, “Even though we would not be able to see it, let us go and feel it anyway.” All of them went where the elephant was. Everyone of them touched the elephant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyvn6RL7VK5jia_HDub4Ww.png" /><figcaption>Blind men and an elephant</figcaption></figure><p>“Hey, the elephant is a pillar,” said the first man who touched his leg.</p><p>“Oh, no! it is like a rope,” said the second man who touched the tail.</p><p>“Oh, no! it is like a thick branch of a tree,” said the third man who touched the trunk of the elephant.</p><p>“It is like a big hand fan” said the fourth man who touched the ear of the elephant.</p><p>“It is like a huge wall,” said the fifth man who touched the belly of the elephant.</p><p>“It is like a solid pipe,” Said the sixth man who touched the tusk of the elephant.</p><p>They began to argue about the elephant and everyone of them insisted that he was right. It looked like they were getting agitated. A wise man was passing by and he saw this. He stopped and asked them, “What is the matter?” They said, “We cannot agree to what the elephant is like.” Each one of them told what he thought the elephant was like. The wise man calmly explained to them, “All of you are right. The reason every one of you is telling it differently because each one of you touched the different part of the elephant. So, actually the elephant has all those features what you all said.”</p><p>“Oh!” everyone said. There was no more fight. They felt happy that they were all right.</p><p><em>The moral of the story is that there might be some fact to what somebody says. We might not agree with it at first because we have our own reasons. But, Truth can be stated in different ways.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf41b513d8a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything within you.]]></title>
            <link>https://medium.com/@palaklive/everything-within-you-5a05efc19adc?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a05efc19adc</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[inner-engineering]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Sat, 03 Aug 2019 16:08:03 GMT</pubDate>
            <atom:updated>2019-08-03T16:08:03.606Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*282PsMP6U_yJxcQF6Ku2pA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@zacdurant?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Zac Durant</a> on <a href="https://unsplash.com/@joshuaearle?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>On a certain day, a bull and a pheasant were grazing on a field. The bull was grazing and the pheasant was picking ticks off the bull — a perfect partnership. Looking at the huge tree at the edge of the field, the pheasant said, “Alas, there was a time I could fly to the topmost branch of the tree. Now I do not have enough strength in my wing to even get to the first branch.”</p><p>The bull said nonchalantly, “Just eat a little bit of my dung every day, and watch what happens. Within two weeks, you’ll get to the top.”</p><p>The pheasant said, “Oh come on, that’s rubbish. What kind of nonsense is that?”</p><p>The bull said, “Try it and see. The whole of humanity is onto it.”</p><p>Very hesitantly, the pheasant started pecking. And lo, on the very first day, he reached the first branch. Within a fortnight, he had reached the topmost branch. He sat there, just beginning to enjoy the scenery.</p><p>The old farmer, rocking on his rocking chair, saw a fat old pheasant on top of the tree. He pulled out his shotgun and shot the bird off the tree.</p><blockquote>Moral of the story: bullshit may get you to the top, but it never lets you stay there!</blockquote><p>So, you can bullshit yourself into all kinds of emotional states, you can somehow crank up some well-being for yourself, but the problem is, it doesn’t last. The weather could bring it down. The stock market could make it come crashing down. And even if it does not collapse, living in anticipation that it might is bad enough! The impending possibility that it will fall apart one day is torture — often worse than the actual disaster. So, as long as your inner life is enslaved to external situations, it will remain a precarious condition. There is no other way for it to be.</p><p>What then is the way out?</p><blockquote>The way out is a very simple change in direction. You just need to see that the source and basis of your experience is <em>within</em> you. Human experience may be stimulated or catalyzed by external situations, but the source is within. Pain or pleasure, joy or misery, agony or ecstasy, happens only inside you. Human folly is that people are always trying to extract joy from the outside. You may use the outside as a stimulus or trigger, but the real thing always comes from within.</blockquote><p>Right now, you are holding a cell. Where do you see the text? Use your finger and point to where you see it. Do you think the image is outside you?</p><p>Think again.</p><p>You remember how it works? The light comes through it, reflecting, going into the lens of your eyes, and projected as an inverted image on your retina — you know the whole story. So, you are actually seeing <em>within</em> yourself.</p><p>Where do you see the whole world?</p><p>Again, within yourself.</p><blockquote>Everything that ever happened to you, you experienced right within you. Light and darkness, pain and pleasure, agony and ecstasy — all of it happened within you. If someone touches your hand right now, you may think you are experiencing their hand, but the fact of the matter is you are only experiencing the sensations in your own hand. The whole experience is contained within. All human experience is one hundred percent self-created.</blockquote><p><a href="https://www.amazon.in/dp/0143428845/ref=cm_sw_r_tw_dp_U_x_3ESECb9A5A5X6">Source: Inner Engineering: A Yogi’s Guide to Joy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a05efc19adc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The one thing they miss is life]]></title>
            <link>https://medium.com/@palaklive/the-one-thing-they-miss-is-life-78effca05fc8?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/78effca05fc8</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[inner-engineering]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Sun, 28 Jul 2019 04:32:24 GMT</pubDate>
            <atom:updated>2019-08-03T15:59:30.420Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ngZOraEfm2mVq-agE14HQ.jpeg" /></figure><blockquote>Every moment there are a million miracles happening around you: a flower blossoming, a bird tweeting, a bee humming, a raindrop falling, a snowflake wafting along the clear evening air. There is magic everywhere. If you learn how to live it, life is nothing short of a daily miracle.</blockquote><blockquote>It doesn’t matter who you are, life doesn’t work for you unless you do the right things. You may consider yourself a good person, but if you don’t water your garden, will it flower? You need to do the right things if you want results.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78effca05fc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inner Engineering]]></title>
            <link>https://medium.com/@palaklive/inner-engineering-8ba7fb952b61?source=rss-5d0d749bccfc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ba7fb952b61</guid>
            <category><![CDATA[inner-engineering]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Palak]]></dc:creator>
            <pubDate>Sat, 02 Mar 2019 18:44:18 GMT</pubDate>
            <atom:updated>2019-07-28T04:38:26.582Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eQabgmO12miK6qsXFPcnpw.jpeg" /></figure><p><em>Everything you have done in your life so far has been in pursuit of a single thing. Whether you seek a career, started a business, made money, or built a family, it was always because you wanted just one simple thing: </em><strong><em>joy</em></strong><em>.</em></p><blockquote>But somewhere along the way, life got complicated.</blockquote><p>If you had been born as any other creature on this planet, it would have been very simple. Your needs would have just been physical. A full stomach would have been equivalent to a great day. Take a look at your dog or your cat: the moment their stomach is full, they are quite peaceful.</p><p>But when you come into this world as a human being, things change. An empty stomach is one problem: hunger. But a full stomach? A hundred problems! When our survival is in question, it is a big issue in our lives. But the moment it is taken care of, it doesn’t seem to mean anything. Somehow, for a human being, life doesn’t seem to end with survival; life begins with survival.</p><blockquote>Today, as a generation of people, our survival process is better organized than ever before. You can go to a supermarket and buy everything you need for the entire year. You can do it without even stepping out of your home! Never before in the history of humanity has such a thing been possible. Things that even royalty could not afford a hundred years ago are accessible to the average citizen. We are the most comfortable generation to have ever lived on this planet. The rub is that we are definitely not the most joyful, or the most loving, or the most peaceful.</blockquote><p>Why is this so? We have tried our best to fix the outside environment. If we fix it any more, there will be no planet left! But we are still no happier than our ancestors a thousand years ago. If it is not working, isn’t it time to look at what’s wrong? How can we continue to do something that has not worked for a thousand years? How much longer are we going to live with blueprints that clearly haven’t delivered their promise?</p><p>It is time for a paradigm shift.</p><h4>Let us start with a single question: what do we consider to be a state of well-being?</h4><p>Very simply, well-being is just a deep sense of <em>pleasantness </em>within. If your body feels pleasant, we call this health. If it becomes very pleasant, we call this pleasure. If your mind becomes pleasant, we call this peace. If it becomes very pleasant, we call this joy. If your emotions become pleasant, we call this love. If they become very pleasant, we call this compassion. If your life energies become pleasant, we call this bliss. If they become very pleasant, we call this ecstasy. This is all that you are seeking: pleasantness within and without. When pleasantness is within, it is termed peace, joy, happiness. When your surroundings become pleasant, it gets branded success. If you’re not interested in any of this and want to go to heaven, what are you seeking? Just otherworldly success! So, essentially all human experience is only a question of pleasantness and unpleasantness in varying degrees.</p><blockquote>But how many times in your life have you lived an entire day blissfully — without a single moment of anxiety, agitation, irritation, or stress? How many times have you lived in utter and absolute pleasantness for twenty-four hours? When was the last time it happened to you?</blockquote><p>The amazing thing is that for most people on this planet, not a <em>single</em> day has happened exactly the way they want it! Of course, there is no one who has not experienced joy, peace, even bliss, but it is always fleeting. They are unable to sustain it. They manage to get there, but it keeps collapsing. And nothing earth-shattering needs to happen for it to collapse. The simplest things throw people off balance, out of kilter.</p><h4>It is like this. You go out today and someone tells you that you are the most beautiful person in the world: you’re floating on cloud nine. But then you come home, and the folks at home tell you who you <em>really</em> are: everything crashes!</h4><p>Sound familiar..?</p><p>Why do you need to be pleasant within? The answer is self-evident. When you are in a pleasant inner state, you are naturally pleasant to everyone and everything around you. No scripture or philosophy is needed to instruct you to be good to others. It is a natural outcome when you are feeling good within yourself. Inner pleasantness is surefire insurance for the making of a peaceful society and a joyful world.</p><blockquote>Besides, your success in the world depends essentially on how well you harness the prowess of the body and mind. So, in order to achieve success, pleasantness has to be the fundamental quality within you.</blockquote><p>Above all, there is substantial medical and scientific evidence today that your body and mind function at their best when you are in a pleasant state. It is said that if you can remain blissful for twenty-four hours, your intellectual capabilities can be almost doubled. Just settling the internal muddle and allowing clarity to the surface can achieve this.</p><blockquote>Now, the same life energy that you refer to as “myself” has sometimes been very happy, sometimes miserable, sometimes peaceful, sometimes in turmoil. The same life energy is capable of all those states. So, if you were given a choice about the kind of expression your life energies should find, what would you choose? Joy or misery? Pleasantness or unpleasantness?</blockquote><p>The answer is self-evident. The ways may vary from person to person. But whether you’re trying to make money, hitting the bottle, or attempting to get to heaven, pleasantness is the only goal. Even if you say you are not interested in this world and your mission in life is only to get to heaven, you’re still only searching for pleasantness. If people had told you since your childhood that God lives in heaven, but heaven is a horrendous place, would you want to go there? Definitely not! Essentially, the highest level of pleasantness is heaven; unpleasantness is hell. So, some think it’s in the wine, and others think it’s in the divine, but pleasantness is what everyone’s seeking.</p><p>The only thing that stands between you and your well-being is a simple fact: you have allowed your thoughts and emotions to take instruction from the outside rather than the inside.</p><p>On a certain day, a lady went to sleep. In her sleep, she had a dream. She saw a hunk of a man, staring at her. Then he started coming closer — closer and closer.</p><p><em>He was so close that she could even feel his breath.</em></p><p><em>She trembled — not in fear.</em></p><p><em>Then she asked, “What will you do to me?”</em></p><p><em>The man said, “Well, lady, it’s your dream!”</em></p><p>What’s happening in your head is <em>your</em> dream. At least your dream should happen the way you want it, shouldn’t it? Even if the world doesn’t happen the way you want it, at least your thoughts and emotions should happen the way you want them to. Right now, these aren’t taking instructions from you because you are handling the whole human mechanism accidentally.</p><p>The human mechanism is the most sophisticated physical form on the planet. You are the greatest piece of technology, but the problem is you don’t know where the keyboard is. It’s like you’re handling a supercomputer with a pickaxe and a wrench! As a result, the simple life process is taking a toll upon humanity. Just to earn a living, to reproduce, to raise a family, and then one day to fall dead — what a challenge! It is amazing how human beings struggle just to do what every worm, insect, bird, and animal does quite effortlessly.</p><p>Put simply, our inner ecology is a mess. Somehow we think that fixing outer conditions will make everything okay on the inside. But these past 150 years are proof that technology will only bring comfort and convenience to us, not well-being. We need to understand that <em>unless we do the right things, the right things will not happen to us:</em> this is true not just of the outside world, but also the inside.</p><p><a href="https://medium.com/@palaklive/the-one-thing-they-miss-is-life-78effca05fc8">The one thing they miss is life</a></p><p><a href="https://www.amazon.in/dp/0143428845/ref=cm_sw_r_tw_dp_U_x_3ESECb9A5A5X6">Source: Inner Engineering: A Yogi’s Guide to Joy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ba7fb952b61" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>