<?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 Raj Maharjan on Medium]]></title>
        <description><![CDATA[Stories by Raj Maharjan on Medium]]></description>
        <link>https://medium.com/@raj_maharjan?source=rss-36b5dc266515------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0p_gCcJGs9N7T2cMJsa6Yw.jpeg</url>
            <title>Stories by Raj Maharjan on Medium</title>
            <link>https://medium.com/@raj_maharjan?source=rss-36b5dc266515------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:48:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@raj_maharjan/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[Constructors vs Literals in JavaScript]]></title>
            <link>https://javascript.plainenglish.io/javascript-constructors-vs-literals-2d19e8b5f2d9?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d19e8b5f2d9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Sun, 21 Jun 2020 07:41:51 GMT</pubDate>
            <atom:updated>2020-06-21T20:34:57.081Z</atom:updated>
            <content:encoded><![CDATA[<p>In JavaScript, we do have the freedom to get the same result in different ways. We can create strings, numbers, objects, arrays, etc. values using both constructors and literals approach. You can get the same values using any of those approaches. However, there are still some differences to know which might be useful to avoid runtime bugs.</p><blockquote>For those who is only reading this quote, long story short, creating values with <br><strong>literals are better than built-in constructors.</strong></blockquote><p>First, if you are wondering what these are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NkBJh2g_db1RRVt6dotgyw.png" /></figure><p>You can just go on and use literals without knowing the differences and no one is going to say anything to you. I know, if you have a curious mind you will continue reading. But especially, for those who have come from class-based programming languages, you might be tempted to use the constructor approach. If you are then you must read the following before you continue coding.</p><p>Normally, you should <strong>prefer literals</strong> <strong>and primitives</strong> and <strong>avoid built-in constructors</strong>.</p><h4><strong>Why prefer literals and primitives?</strong></h4><p>1. Literals are shorter and easy to read and write.</p><pre>let o = new Object();</pre><pre>let o = {}; // easier and actual representation</pre><p>2. Literals can still benefit from properties and methods that are provided by the objects created from constructors.</p><pre>let a = [1, 2, 3];<br>a.length // 3<br>a.slice(2) // [3]</pre><p>3. When you invoke a method on primitives, it is implicitly converted to a temporary object behind the scene.</p><pre>let a = &quot;Hello world&quot;;<br>a.toLowerCase() // hello world<br>a.length // 11</pre><h4><strong>Why avoid built-in constructors?</strong></h4><p>1. new Object(), when used with dynamic arguments can lead to unexpected results, which can create confusion.</p><pre>let n = new Object(1) // Number {1}<br>typeof n // &quot;object&quot;<br>n.constructor === Number // true</pre><pre>let b = new Object(true) // Boolean {true}<br>typeof b // &quot;boolean&quot;<br>b.constructor === Boolean // true</pre><p>2. new Array() gives different results with different numbers of arguments.</p><pre>let a = new Array(3) // [undefined, undefined, undefined]<br>a.length // 3</pre><pre>let a = new Array(1, 2, 3) // [1, 2, 3]<br>a.length // 3</pre><pre>let a = new Array(3.14) // Uncaught RangeError</pre><p>3. new RegExp(), escaping characters like backslash and quotes are boring and reduces readability.</p><pre>let reg = /\\/g; // /\\/g<br>let reg = new RegExp(&quot;\\\\&quot;, &quot;g&quot;) // /\\/g</pre><p>4. In JavaScript, you can call built-in constructor functions like Array, String, etc. without using a “new” operator, which might sometimes make you forget to call custom constructor functions with a “new” operator that uses “this”.</p><pre>function Person(name) {<br>  this.name = name;<br>}</pre><pre>let p = Person(&quot;Kelina&quot;);<br>p.name // undefined</pre><p>Of course, preceding statements are not bugs nor reduces any performance but might lead to unexpected results and hence introduce bugs if you are not careful. You can still either use constructors or literals, it really depends upon your preference and necessity.</p><h4><strong>Summary</strong></h4><pre>Literals and primitives   |  Built-in constructors</pre><pre>let o = {};               |  let o = new Object();</pre><pre>let a = [];               |  let a = new Array();</pre><pre>let s = “”;               |  let s = new String();</pre><pre>let n = 0;                |  let n = new Number();</pre><pre>let b = false;            |  let b = new Boolean();</pre><pre>let reg = /[a-z]/g;       |  let reg = new RegExp( &quot;[a-z]&quot;, &quot;g&quot; );</pre><pre>throw {                   |  throw new Error(“oops... error”);<br>  name: “Error”, <br>  message: “oops... error” <br>};<br>throw Error(“oops... error”);</pre><p>While each approach has its own benefit, generally, using literals is enough for most of the cases. As always, thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d19e8b5f2d9" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/javascript-constructors-vs-literals-2d19e8b5f2d9">Constructors vs Literals in JavaScript</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript Prototype — Understanding The Basics]]></title>
            <link>https://javascript.plainenglish.io/javascript-prototype-understanding-the-basics-1d323166fbf8?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d323166fbf8</guid>
            <category><![CDATA[prototype]]></category>
            <category><![CDATA[objects]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Mon, 04 May 2020 06:36:04 GMT</pubDate>
            <atom:updated>2020-05-10T05:10:06.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>JavaScript Prototype — Understanding The Basics</h3><p>The prototype is often associated with inheritance when comparing to Object-Oriented programming. But <strong>why</strong>? And what even prototype means in JavaScript. In this blog, I will explain <strong>what</strong> the prototype is and <strong>how</strong> it is designed and structured in JavaScript. And of course, the why part.</p><blockquote><em>In JavaScript, all functions are objects, the only difference is that functions can be called.</em></blockquote><pre>// Here is a simple function<br>function Superman() {<br>  // ...<br>}</pre><pre>// Since function Superman is also an object we can add properties and methods like in objects.<br>Superman.isHero = true;<br>Superman.test = function() {<br>  console.log(&#39;test ok&#39;)<br>}</pre><pre>console.log(Superman.isHero) // true<br>console.log(Superman.test()) // test ok</pre><p>In this blog, I am going to tell you a short story in which we have superheroes like Superman, Batman, and Wonderwoman each with their unique superpowers. And some scientists.</p><blockquote><em>Superman</em>: flight, superhuman strength, x-ray vision, heat vision, cold breath, super-speed, enhanced hearing, and high-invulnerability, etc.</blockquote><blockquote><em>Batman</em>: gadgets, superhuman level strength, agility, intellect, etc.</blockquote><blockquote><em>Wonderwoman</em>: superhuman strength and durability, flight, superhuman speed, reflexes, and agility; enhanced senses, including smell, vision, and hearing, etc.</blockquote><p>Let’s slightly tweak the story where superpowers of each superhero are stored in a bag where they have access only to their own bag.</p><p>In JavaScript, we all have seen standard build-in objects like Array, Date, Object, Set, Promise, String, Number, etc. Let’s think of them as superheroes of JavaScript, and like in the story, their superpowers are also stored in a bag labeled ‘prototype’. Yes, that’s prototype, details to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZTh_b5xpOUVNCrAexEkVw.jpeg" /></figure><p>I am sure that we all have used superpowers in JavaScript quite a lot of times. Here they are:</p><blockquote><em>Array</em>: forEach, filter, sort, slice, concat, length, etc.</blockquote><blockquote><em>String</em>: toUpperCase, toLowerCase, replace, substr, etc.</blockquote><blockquote><em>Set</em>: has, add, delete, clear, values, etc.</blockquote><blockquote><em>Promise</em>: then, catch, finally, etc.</blockquote><p>All these properties (or methods) are stored in a property named ‘prototype’ of every function objects. That means a prototype is also an object. You can see all these properties (or methods) by accessing their prototype directly in the browser’s console — Array.prototype, Set.prototype, and so on. Below are some related images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*g88BSOWvUqNp2E2OIyzzAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*x_kxRjRQbCSniJvJpsAT9w.png" /><figcaption>showing properties and functions that are stored inside prototype properties</figcaption></figure><blockquote><em>superheroes =&gt; function objects (</em>Array, Set, Date, Promise, Map, etc.<em>)</em></blockquote><blockquote><em>superpowers =&gt; properties and methods (</em>length, forEach, map, size, etc.<em>)</em></blockquote><blockquote><em>bag =&gt; prototype</em></blockquote><p>Now introducing a group of scientists, who can create or clone these superheroes. Let’s call one of those scientists <em>constructor </em>who uses <strong>new</strong> operator to create instances of superheroes. Other scientists can be called <em>Object.create</em>, <em>Object.setPrototypeOf, and syntax constructs. </em>They have different approaches to prototyping.</p><pre><em>// Lets first create our own Superhero in LAB1</em></pre><pre>function Superhero(name, faction) {<br>  this.name = name;<br>  this.faction = faction;<br>  this.XRayVision = false;<br>  this.fly = false;  <br>}</pre><pre>// add toggleXRayVision method to Superhero prototype<br>Superhero.prototype.toggleXRayVision = function() {<br>  this.XRayVision = !this.XRayVision;<br>  console.log(`Superhero ${this.name} has turned ${this.XRayVision ? &quot;on&quot; : &quot;off&quot;} X Ray vision.`);<br>};</pre><pre>// add toggleFlight method to Superhero prototype<br>Superhero.prototype.toggleFlight = function() {<br>  this.fly = !this.fly;<br>  console.log(`Superhero ${this.name} ${this.fly ? &quot;is now flying&quot; :       &quot;has stopped flying&quot;} over ${this.faction}.`);<br>};</pre><pre>// create instances s1 &amp; s2 using new operator<br>let s1 = new Superhero(&quot;Hero1&quot;, &quot;Asia&quot;);<br>let s2 = new Superhero(&quot;Hero2&quot;, &quot;Europe&quot;);</pre><pre>// **************</pre><pre>s1.toggleXRayVision(); <br><em>// Superhero Hero1 has turned on X Ray vision.<br></em>s2.toggleXRayVision(); <br><em>// Superhero Hero2 has turned on X Ray vision.</em></pre><pre>// update method so that changes reflect in all instances<br>Superhero.prototype.toggleXRayVision = function() {<br>  this.XRayVision = !this.XRayVision;<br>  console.log(`Modified: Superhero ${this.name} has turned ${this.XRayVision ? &quot;on&quot; : &quot;off&quot;} X Ray vision.`);<br>};</pre><pre>s1.toggleXRayVision(); <br>// Modified: Superhero Hero1 has turned off X Ray vision.<br>s2.toggleXRayVision(); <br><em>// </em>Modified: Superhero Hero2 has turned off X Ray vision.</pre><pre>// **************</pre><pre>s1.toggleFlight(); <em>// Superhero Hero1 is now flying over Asia.<br></em>s2.toggleFlight(); <em>//Superhero Hero2 is now flying over Europe.</em></pre><pre><em>// this is called </em><a href="https://en.wikipedia.org/wiki/Method_overriding"><strong><em>method shadowing</em></strong></a><em> or </em><a href="https://en.wikipedia.org/wiki/Method_overriding"><strong><em>method overriding</em></strong></a><em>, affect only s1 instance but not prototype<br></em>s1.toggleFlight = function()  {<br>  this.fly = !this.fly;<br>  console.log(`Defect: Superhero ${this.name} flying has been defected`);<br>};</pre><pre>s1.toggleFlight();<br><em>// Defect: Superhero Hero1 flying has been defected<br></em>s2.toggleFlight();<br><em>// Superhero Hero2 has stopped flying over Europe.</em></pre><pre><em>// dynamically update toggleFlight method for all instances<br></em>Superhero.prototype.toggleFlight = function()  {<br>  this.fly = !this.fly;<br>  console.log(`Fly Repaired: Superhero ${this.name} ${this.fly ? &quot;is now flying&quot; : &quot;has stopped flying&quot;} over ${this.faction}.`);<br>};</pre><pre><em>// if s1 hadn&#39;t overridden this method, it would have been repaired too, so update on prototype level will not affect this method<br></em>s1.toggleFlight(); <br><em>// Defect: Superhero Hero1 flying has been defected<br></em>s2.toggleFlight(); <br><em>// Fly Repaired: Superhero Hero2 is now flying over Europe.</em></pre><blockquote>Note: For every new instance created, no new copy of prototype is created but all of them share (or are linked to) the same prototype.</blockquote><p>How? Each instance (object) has a private property that holds a link to another object called its prototype (parent object). In most browsers, the private property is named <strong><em>__proto__</em></strong> which is linked to the property prototype of a function object. You can find it in every object in JavaScript as shown in the below picture (<em>__proto__</em> is at last).</p><blockquote>Note: Standard notation for <em>__proto__</em> is [[prototype]].</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*n_uhbfC2WhAEPjMPUcy-1A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*ioa_Rw4vl-Sy14UfFtSKrA.png" /></figure><p>This concept of proto creates a <strong>prototype chain</strong> (explained below) where children have access to the prototype. This is how properties and methods are inherited in JavaScript.</p><p>However, if you replace or modify the <em>__proto__</em> of any object, the chain might get broken which may cause the inheritance to not work properly. So updating it is not advisable unless it’s necessary and you know what you are doing.</p><pre>// few expressions<br>let array = new Array(); // constructor<br>or, let array = []; // syntax constructs<br>array.<em>__proto__</em> === Array.prototype // true</pre><pre>let set = new Set();<br>set.<em>__proto__</em> === Set.prototype // true</pre><blockquote>Note: set inherits from Set.prototype not Set itself, which means property prototype literally is its prototype (parent object) and not Set.</blockquote><p>In JavaScript, nearly all objects are instances of the Object.</p><pre>// Array.prototype inherits from Object.prototype</pre><pre>Array.prototype.<em>__proto__</em> === Object.prototype // true</pre><pre>array.<em>__proto__</em>.<em>__proto__</em> === Object.prototype // true</pre><pre>Object.prototype.<em>__proto__</em> // null</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*5MvCM6g42KyV2XK_H1nLIw.png" /><figcaption>prototypal structure in JavaScript</figcaption></figure><p>As shown in the above picture, you can see a chain of prototypes connecting all the way up to Object prototype object. This means Object sits at the top of the <strong>prototype chain</strong> whose <em>__proto__</em> is null.</p><p>The interesting thing about the prototype chain is that when accessing a property, if a property is not found in an object, its <em>__proto__ </em>is looked through<em> </em>and if it is not found in<em> __proto__ </em>then <em>__proto__</em> of <em>__proto__</em> is looked through and it goes on until the end of the chain is reached i.e. null which finally returns <em>undefined</em>. And yes, console.log(array2[0]) from above picture prints 1.</p><p>So, for performance reasons, try to make the chain as small as possible. Also, you can use the <em>hasOwnProperty </em>method which every object inherits from Object.prototype to check if a property exists on the current object or not, and prevents traversing through the chain. Although it doesn’t check if the value of a property is <em>undefined</em>.</p><p>Lastly, we already know that initiating an object from a function inherits its prototype. However, we can also inherit from an object using <strong>Object.create</strong> method, which makes the first argument a prototype for new objects.</p><pre>let obj = {a: 1, b: 2};<br>obj ---&gt; Object.prototype ---&gt; null</pre><pre>let o = Object.create(obj); // obj is prototype for o<br>o ---&gt; obj --&gt; Object.prototype ---&gt; null<br>console.log(o.a) // 1</pre><pre>let arr = [1, 2];<br>arr ---&gt; Array.prototype ---&gt; Object.prototype ---&gt; null</pre><pre>let a = Object.create(arr);<br>a --&gt; arr --&gt; Array.prototype ---&gt; Object.prototype ---&gt; null<br>console.log(a[1]) // 2</pre><blockquote>In general, prototype in JavaScript is an object (not necessarily stored in property prototype), to which new objects created from it are linked and thus can use its properties and methods.</blockquote><blockquote>In JavaScript, objects are king. If you understand objects, you understand JavaScript. — copied</blockquote><p>If you want to learn more about prototype or prototype chain, here is the link: <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Inheritance_and_the_prototype_chain">https://developer.mozilla.org/en-US/docs/Web/JavaScript/Inheritance_and_the_prototype_chain</a></p><p>Thanks for reading. Comments are greatly appreciated. Please feel free to comment on how you think about this blog or have any questions.</p><p>Link to my previous blog: <a href="https://medium.com/swlh/react-render-optimization-few-tips-360837d98e91">React Render Optimization Few Tips</a></p><h4><strong>A note from JavaScript In Plain English</strong></h4><p>We have launched three new publications! Show some love for our new publications by following them: <a href="https://medium.com/ai-in-plain-english"><strong>AI in Plain English</strong></a>, <a href="https://medium.com/ux-in-plain-english"><strong>UX in Plain English</strong></a>, <a href="https://medium.com/python-in-plain-english"><strong>Python in Plain English</strong></a><strong> </strong>— thank you and keep learning!</p><p>We are also always interested in helping to promote quality content. If you have an article that you would like to submit to any of our publications, send us an email at <a href="/service/mailto:submissions@plainenglish.io"><strong>submissions@plainenglish.io</strong></a><strong> </strong>with your Medium username and we will get you added as a writer. Also let us know which publication/s you want to be added to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d323166fbf8" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/javascript-prototype-understanding-the-basics-1d323166fbf8">JavaScript Prototype — Understanding The Basics</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Render Optimization Few Tips]]></title>
            <link>https://medium.com/swlh/react-render-optimization-few-tips-360837d98e91?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/360837d98e91</guid>
            <category><![CDATA[render]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Mon, 20 Apr 2020 03:54:46 GMT</pubDate>
            <atom:updated>2020-04-23T17:59:50.661Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are a few tips on optimizing big and complex components by controlling re-renders. Or you can use it for small and simple components too. In fact, these tips are my notes. These notes have helped me a lot when writing complex react components. I am sharing these so that it might help you too. While everyone has their own opinion, these are few things I keep in mind as good practices.</p><h4>1. Use hooks effectively</h4><p>If you are using React version of at least 16.8.0, use hooks such as <strong>useEffect</strong>, <strong>useMemo</strong>, and <strong>useCallback</strong> to wrap any complex data processing like filtering or sorting an array to avoid unnecessary re-calculation on every re-render. Hooks are similar to life-cycles from class components. <em>Also, don’t forget to wrap all functions with useCallback that are passed as a prop into a component that are wrapped with React.memo().</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*ggZR4BQaQVLkGb9du5x-Xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/729/1*EpofAT-9qYZhMTby3G4dKQ.gif" /><figcaption>without useMemo hook</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*gkWLDdclOUouXRXSvYXZyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*Q-O6M-GI9egnylbAE7OCfA.gif" /><figcaption>with useMemo hook</figcaption></figure><p>Using useMemo prevent filter to run on every re-renders unless the dependency list changes.</p><h4>2. Branching / Breakdown components to a single responsibility</h4><p>Break down components to new smaller components rather than having a big gigantic component, mainly when it contains states or hooks (such as useSelector that subscribes to states such as Redux). Great examples are forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*A2rZHEAdW4MUvCPJYRXkeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*3m-Kp9P7K_eaU-R49Xjjdw.gif" /><figcaption>Highlighting a gigantic component when re-rendered by each input</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*WRDI0LW28B-ucT0V3BxYLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*3FSaPR-ByunOl5bayW8fUA.gif" /><figcaption>Highlighting after components breakdown, only child components are re-rendered</figcaption></figure><p>Here, I broke down the main component into child components and moved each state to its own component.</p><h4>3. Render only required components.</h4><p>Components that are rendered but not visible due to some styles can reduce rendering performance. For example: In collapsible, hidden list of elements which aren’t visible yet will still render which is unnecessary as shown below. You can use chrome extension <a href="https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en">React Developer Tools</a> to see if any unnecessary components are mounted or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*WcGUf6U7w2ItvPAWdsWz5Q.gif" /><figcaption>Items are collapsed using CSS styles but components are still rendered</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*i_4J1FMFnT0dI9rDhiWEaw.gif" /><figcaption>Items are collapsed and components are not rendered</figcaption></figure><p>At first, I hid the list by using CSS styles. Then to optimize, I returned the mapped list to render only if the state is not collapsed, otherwise returned null.</p><h4>4. Memoization</h4><p>If you don’t know what Memoization is, I know it sounds quite technical and you might be thinking of skipping because I did when I started developing or you may not be as lazy as I was. But it’s very important that you know about it as it can make <em>level 10 boss</em> look like <em>level 1 boss</em> and save your program execution a lot of time (of course in ms). I will try to explain it as simply as I can. <a href="https://en.wikipedia.org/wiki/Memoization">Memoization</a> is a technique for storing the result of complex and expensive calculations or function calls, similar to making a cache. It always returns cached values without running expensive calculations, unless any of its input dependency changes. Here are 2 images I found which I believe will make it easier to understands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*per8jVABGpDvrgXh" /><figcaption>fib(n) is function to find the <a href="https://en.wikipedia.org/wiki/Fibonacci_number">Fibonacci</a> sequence. The red-colored function will not execute again</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*XGyVseFYG4MPLpMm.png" /><figcaption>I know it’s in python, but its the best illustrative pic I found but you will understand as it’s not that different 😜</figcaption></figure><p>How is this related to React???<br>Suppose you have a dashboard with multiple components that display a list of people with the same age and profession in different cities stored in redux state.</p><pre>// Suppose you have a selector selectInfo() subscribed to redux state which given an age and a city name, finds the number of people with given age and then calculates and returns its percentage compared to total population of the city. Also, returns a list of all the people with same age whose profession is &#39;software developer&#39; sorted by their name. <br>// You can add more criterias in order to make it more complex.</pre><pre>function selectInfo (state, age, city) {</pre><pre>  const allPeople = state.peoplesData; // fetch data from redux</pre><pre>  const filteredPeople = allPeople.filter(p =&gt; p.city === city);</pre><pre>  const filteredAge = filteredPeople.filter(a =&gt; a === age);</pre><pre>  const percentage = (filteredAge / allPeople) * 100%;<br>  <br>  // filter software developers<br>  // sort them and so on...</pre><pre>  return { percentage, softwareDevelopers: [...] };<br>}</pre><p>Here, we can save the results in memory and return the same value when the information is requested for the same input (age and city). The more expensive your function call is the more time it saves. Isn’t that awesome?</p><p>You can create your own memoization tool or you can search for such a tool online. <a href="https://github.com/reduxjs/reselect">Reselect</a> is a selector library for redux just to do that.</p><h4>4. Fetch only necessary data</h4><p>This one is my favorite as it keeps props simple and clean. How many of you fetch the whole array of object data from the redux state in the parent component and pass each object data to child components? It will work but as your components get bigger you will notice some decrease in rendering performance. For example:<br>Suppose you run a popular restaurant and have a reservation system and your state and looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*WDOxZhBaCUJZTj6yMeTilw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*pJsZLDtP79Hb6EzA5X_fAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*hGI2LWVdm7i9xQ1AtCJlvw.png" /><figcaption>Pseudo state, Component, View</figcaption></figure><p>The common approach here would be to map the array of tables and render them as shown above. Let’s say there are 100 tables and orders come in every few seconds. Now if you want to add, update or remove any order the first thing we would probably do is map the whole array and update orders, which returns a new array — JavaScript Array map(), filter(), reduce(), concat() all return a new array. Now, React detects a new array and it will re-render the whole list. One change in any table will affect all the hundreds of tables.</p><p>To prevent this, we can do a few things:</p><ul><li>Data <a href="https://en.wikipedia.org/wiki/Database_normalization">Normalization</a></li><li>Component breakdown</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/475/1*kbl9IEn6vafWmfMS1tYeMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*8PLMxEpA79mIAWg7R8M_Ew.png" /><figcaption>Data normalization and Component breakdown</figcaption></figure><p>As shown above, we can make an array of ids and keep them separate from data. Breakdown and make a new Table component. Then we can first get ids of all tables in the main Tables component and pass only table id to the Table component. Then Table component itself can fetch its own data and display them. Now changes in each table will not affect other tables. Moreover, you can further normalize and breakdown orders from each table so changes in only order don’t affect the whole table. Also, it’s good to pass as few props as possible.</p><p><em>You can also normalize API response data to the required structure whenever it is needed before storing them to redux state.</em></p><p>And a few more tips:</p><ul><li>Make components as small as possible by extracting elements to a function or a new component. Use the <a href="https://en.wikipedia.org/wiki/Single-responsibility_principle">Single Responsibility Principle</a> technique so that each component do ideally only one thing.</li><li>Extract logic codes to custom hooks to make your component clean.</li><li>Find and remove unnecessary codes after adding or updating components. More importantly respective CSS codes.</li><li>Use primitive values (string, boolean, number) instead of Arrays and Objects when passing data to the props if possible. It’s okay to pass Arrays and Objects as long as you can maintain their reference to not change frequently.</li></ul><p>I think this is it for now. You are outstanding if you read this whole thing. I hope it helps you write your React app to run fast and smoothly.</p><p>You can comment if you have any questions.</p><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=360837d98e91" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/react-render-optimization-few-tips-360837d98e91">React Render Optimization Few Tips</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YoungInnovations Weekly Blog #232 — Corona Virus and work from home, Demola Workshop, YI sessions…]]></title>
            <link>https://medium.com/younginnovations-blog/younginnovations-weekly-blog-232-corona-virus-and-work-from-home-demola-workshop-yi-sessions-a0d1bee70d55?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0d1bee70d55</guid>
            <category><![CDATA[booqnow]]></category>
            <category><![CDATA[demola]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[yi-session]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 08:04:14 GMT</pubDate>
            <atom:updated>2020-03-27T08:16:43.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>YoungInnovations Weekly Blog #232 — Corona Virus and work from home, Demola Workshop, YI sessions, Stored procedures and fetching data as JSON in MySQL, booqnow dot com</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qRbqVSTbiwCWzjdWeiELcw.png" /></figure><p>Hello everyone.</p><p>It has been 5 days since <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> commenced ‘Work From Home’ due to the pandemic Corona Virus — COVID19. I hope everyone is doing well and are in good health and staying in their homes safely. The number of COVID19 confirmed cases have crossed 532,000 and still increasing exponentially. The more shocking news is that now confirmed cases of the US have surpassed China with more than 85,000 cases and are now at the top. I guess the US wants gold medals pretty badly 😄. I thought the US could do better. China is now at second place with about 81,000 confirmed cases followed by Italy with about 80,000 confirmed cases. On the other hand, there are some good news too. Due to the shutdown of many industries and vehicles, there has been a dramatic drop-off in Carbon dioxide and Nitrogen dioxide emission on large scale. This has made our air and environment a lot cleaner. Finally, nature can breathe in peace even it’s for a short period of time 🍏. So despite all the worries and problems, I promise there will be a fruitful outcome on the other side of this pandemic if we stay in our homes, keep social distance and take safety measures meticulously.</p><h4>Demola Workshop</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HONinTP2Q9u6QOzheMpxbQ.jpeg" /></figure><p>YoungInnovations is participating in the current edition of <a href="https://www.demola.net/">Demola </a>which is being organized by <a href="https://www.kingscollege.edu.np/">King’s College</a>. Demola is an international innovation challenge platform that brings together students and leading brands. With Demola, global and local organizations challenge university students to create a better future. We have been working on a <a href="https://applications.demola.net/cases/584">challenge </a>with students of King’s College. This week we had Jam 1, where we worked on identifying and understanding the core problem of the challenge. Due to the current situation with the CORONA Virus, the whole session was conducted online over two days. It was a very interactive and productive session despite being online.</p><h4>YI session</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hzC9gw5pFbUW4_hLXaHMXw.jpeg" /></figure><p>Also, this week on the YI session, <a href="https://medium.com/u/3119645406d4">Prashant Shrestha</a> gave a short talk on balancing weight. He spoke about what causes weight loss and what are the factors affecting weight loss. He also gave some tips on how one can lose weight. This session was also held online.</p><p>Also, <a href="https://medium.com/u/4a8faa4d7207">Kushal Raj Shrestha</a> provided his list of movies to cope up with staying home during the lockdown.</p><p><a href="https://www.imdb.com/user/ur34392948/watchlist">Kushal_dai&#39;s Watchlist</a></p><p>And lastly, one of our colleague’s friend, Sophie provided us information about the situation of Covid 19 pandemic in the valley. Since Sophie is a working nurse, she suggested to be calm and take care of our hygiene properly.</p><h3>Stored procedures and fetching data as JSON in MySQL</h3><p>Moreover, thanks to our colleague <a href="https://medium.com/u/bca477fca0fb">Birendra Gurung</a> for sharing information on how we can optimize our database queries by using GROUP CONCAT and STORED PROCEDURE in MySQL.</p><p><a href="https://blog.yipl.com.np/fetching-data-as-json-and-stored-procedures-in-mysql-39a382d7dc57">Fetching data as JSON and stored procedures in MySQL</a></p><h3>Booqnow dot com</h3><p>Furthermore, our colleague <a href="https://medium.com/u/4d8602ad9759">Nirazan Basnet</a> has created a website that can be used to submit or track, and get information about the service providers such as drinking water, medicines, gases, groceries and so on, amid this situation. Thanks, Nirajan, this can be very helpful.</p><p>Stay safe and healthy everyone. Thank you for reading to the end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0d1bee70d55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/younginnovations-blog/younginnovations-weekly-blog-232-corona-virus-and-work-from-home-demola-workshop-yi-sessions-a0d1bee70d55">YoungInnovations Weekly Blog #232 — Corona Virus and work from home, Demola Workshop, YI sessions…</a> was originally published in <a href="https://medium.com/younginnovations-blog">YoungInnovations&#39; Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YoungInnovations Weekly #198]]></title>
            <link>https://medium.com/younginnovations-blog/younginnovations-weekly-198-e2930c35945f?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2930c35945f</guid>
            <category><![CDATA[weekly]]></category>
            <category><![CDATA[open-data-fellowship]]></category>
            <category><![CDATA[everest-hackathon-2019]]></category>
            <category><![CDATA[birthday]]></category>
            <category><![CDATA[graduation]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Fri, 26 Jul 2019 06:03:00 GMT</pubDate>
            <atom:updated>2019-07-26T06:03:00.322Z</atom:updated>
            <content:encoded><![CDATA[<h4>Everest Hackathon 2019, Congratulation Sonika, Akita’s birthday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5iKra5x_JO3CrpR9skwqrA.png" /></figure><blockquote>You don’t learn to walk by following rules. You learn by doing, and by falling over. — Richard Branson</blockquote><p>It’s been a while since I last wrote my last weekly.</p><h3>Everest Hackathon 2019</h3><p>Everest hackathon happened from 19th to 21st of July; it was a focused 24-hour event where entrepreneurs, programmers, designers, students and problem solvers came together in small teams to share ideas and build something new and exciting, alongside a whole bunch of like-minded people.<br>The theme of the hackathon was based on either sponsor challenge or open theme. There were more than 230 participants from 15+ nations and they worked together on 50+ projects.</p><p><a href="https://medium.com/u/da30bff6a3c">Mani Bibek Acharya</a> from Young Innovations attended the event as a mentor. Also <a href="https://medium.com/u/6b9db7f3a1f2">Sonika Baniya</a> from Young Innovations, along with her team of four participated in the event where the team made Furniture in Augmented Reality.</p><p><em>‘Furniture in AR’ is an easy to use AR-based application targeted for furniture buyers and sellers. The application mainly serves the customer by allowing them to know what a 3D model of furniture looks in the ambiance of the room.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcO88DnkHv12mHtoUcOHqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3YehcpshSemzDpRrqGpuMA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6wZg4oQ3JUPXBNq3TClHA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dWerA1HumYjNJhebfxEhNw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EqJcyu-SVBKL7PJP2la_bg.jpeg" /><figcaption>From Everest Hackathon 2019</figcaption></figure><h3>Congratulation Sonika</h3><p><a href="https://medium.com/u/6b9db7f3a1f2">Sonika Baniya</a> graduated from Open Data fellowship. She was placed in YI, being one of the host organizations, from the start of May 2019 for one month. This graduation is the celebration and certification of our completion of placement and fellowship. The celebration was joined by fellows and their representative from their respective host organizations. <a href="https://medium.com/u/da30bff6a3c">Mani Bibek Acharya</a> was there representing YoungInnovations as her mentor. She shared her experience about being in <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> family and how this family is giving her space to explore and grow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*hvMaDG9iu0qPoN75xTwaiw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*EPjO-uwH6joJ8-FElu0CUg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*SuWVLFiOxGz1XjBBx_mtCg.jpeg" /><figcaption>Sonika at her Graduation</figcaption></figure><h3>Happy Birthday Akita</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*VaLVkObJFJI_ydFxncwb7g.jpeg" /></figure><p>Happy birthday to <a href="https://medium.com/u/d2c5a24d4f26">Akita Nakarmi</a>. Wishing you a beautiful day with good health and happiness forever. Thank you for the delicious chocolates.</p><p>Thank you for reading.</p><p>This week we published,</p><ul><li><a href="https://blog.yipl.com.np/backend-knowledge-sharing-9-cdccc97dd8d0">Backend Knowledge Sharing #9</a></li><li><a href="https://blog.yipl.com.np/frontend-design-knowledge-sharing-8-e02d35ef9ba4">Frontend-Design Knowledge Sharing #8</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2930c35945f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/younginnovations-blog/younginnovations-weekly-198-e2930c35945f">YoungInnovations Weekly #198</a> was originally published in <a href="https://medium.com/younginnovations-blog">YoungInnovations&#39; Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YoungInnovations Weekly #139: Tender Alert, Knowledge Sharing Session on Symbol, KTMJS Meetup…]]></title>
            <link>https://medium.com/younginnovations-blog/younginnovations-weekly-139-tender-alert-knowledge-sharing-session-on-symbol-ktmjs-meetup-84b39f09825d?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/84b39f09825d</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ktmjs]]></category>
            <category><![CDATA[tender-alert]]></category>
            <category><![CDATA[sketch-symbols]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Fri, 18 May 2018 09:40:03 GMT</pubDate>
            <atom:updated>2018-05-18T09:40:03.089Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>YoungInnovations Weekly #139: </strong>Tender Alert, Knowledge Sharing Session on Symbol, KTMJS Meetup, Farewell Rajan</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blnvKfEb96w9ZoPsRAW3EA.jpeg" /></figure><p>Hello everyone, welcome to this week’s blog, hope you enjoy reading it.</p><blockquote>The master has failed more times than the beginner has even tried.<br>- Stephen McCranie</blockquote><h3>Tender Alert</h3><p>On Thursday, Saurav (<a href="https://medium.com/u/66d29161eb3b">xaurav sharma</a>) and <a href="https://medium.com/u/6eb7d734f5d6">Saroj Bista</a> gave a demo of <strong>Tender Alert, </strong>among key officials of the FCAN. Tender Alert is an app developed for the use of contractors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4hlq-NSFgyuAmpwG0ggcVA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vLl9sTh11WRtTQz9tAS_w.jpeg" /><figcaption>Tender Alert being presented to the officials of FCAN</figcaption></figure><h3>Knowledge Sharing Session on Symbol</h3><p>On May 17, 2018 (Thursday), <a href="https://medium.com/u/63430dc524ea">Rohit Shrestha</a> (UI/UX Designer) gave knowledge sharing session on sketch symbols. He shared his understanding on symbols, text styles and also talked about his working experience with it. Moreover, he explained how symbols can be useful when designing layouts with live examples. The session was interesting and interactive. Hope all the designers will use the power of symbols in our future design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fjNaqTvoxReHqo_H4R6Aw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWsoeWpmhBG7W-bV4K9GxQ.jpeg" /><figcaption>Rohit presenting on Symbol to fellow frontenders</figcaption></figure><h3>KTMJS Meetup</h3><p>Do you love programming in JavaScript? You will once you know how awesome it is 😎. Whether you are a front end developer or backend developer, JavaScript has it covered from just a DOM manipulation to trending Single Page Application frameworks such as Reactjs, Angular, Vuejs, etc. to backend frameworks such as Expressjs, Socket.io, etc. based on Nodejs. It doesn’t end here, you can also develop a native app using JavaScript libraries like React Native.</p><p>Many of you might know that JavaScript is being extensively used in our daily browsing activities. In old days, JavaScript was mainly built for browsers. So actually, there would be no JavaScript without browser. All graphical browsers have JavaScript built in. But the <strong>JavaScript Engines</strong> behind each browser could be different. Chrome use <strong>v8 </strong>engine, Firefox use <strong>spidermonkey</strong>, Microsoft edge use <strong>chakra. </strong>Going way back, JavaScript was the language for Netscape Navigator back when that was the dominant browser. Specifically, it was the language for dynamic front-end development. But as Netscape had submitted their JavaScript standard to <a href="https://en.wikipedia.org/wiki/Ecma_International">Ecma International</a>, their version just became the standard, better known as <a href="https://en.wikipedia.org/wiki/ECMAScript">ECMAScript</a>.</p><p>Basically, developers would like to have one programming language to be used on both the front-end and back-end. JavaScript is the first language that could do this. So, learning javascript/ecmascript and its related related frameworks and libraries might leverage your developing skill.</p><p>If you want to learn more about javascript, there is going to be a <strong>KTMJS Meetup</strong> in Lalitpur (details given in below pictures) where two speakers <a href="https://medium.com/u/7410ae043b4d">Biju Nakarmi</a> and <a href="https://medium.com/u/6816dd13a71c">Bhojendra Rauniyar</a><strong> </strong>from <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> are going to be sharing their experiences on JavaScript projects and some insight about different JavaScript libraries. <a href="https://www.facebook.com/events/403511480059002/">Link to facebook event</a>. <strong>See you there!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*6tq2rG38UZAk9nSw86_YcQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*lWX6vxd4lwJ53qMuFrQp8w.png" /></figure><blockquote>The thing that is really hard, and really amazing, is giving up on being perfect and beginning the work of becoming yourself.<br>- Anna Quindlen</blockquote><h3>Farewell Rajan</h3><p>Lastly, <a href="https://medium.com/u/214a5529e972">Rajan Paneru</a> is moving on to take the next step to further build his career. Thank you for all your contribution and good luck for your future!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZJL-Fb7Wt5vxAZVwVWZzw.jpeg" /><figcaption>Prashant presenting Token of Appreciation to Rajan</figcaption></figure><p>Happy weekend! 🍹</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84b39f09825d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/younginnovations-blog/younginnovations-weekly-139-tender-alert-knowledge-sharing-session-on-symbol-ktmjs-meetup-84b39f09825d">YoungInnovations Weekly #139: Tender Alert, Knowledge Sharing Session on Symbol, KTMJS Meetup…</a> was originally published in <a href="https://medium.com/younginnovations-blog">YoungInnovations&#39; Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Young Innovations Weekly #118 : FightVAW launched, Secret Santa, YoungInnovation’s participation in…]]></title>
            <link>https://medium.com/younginnovations-blog/young-innovations-weekly-fightvaw-launched-secret-santa-younginnovations-participation-in-ogp-b778be123197?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/b778be123197</guid>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 13:40:18 GMT</pubDate>
            <atom:updated>2017-12-28T10:59:27.554Z</atom:updated>
            <content:encoded><![CDATA[<h3>Young Innovations Weekly #118 : FightVAW launched, Secret Santa, YoungInnovation’s participation in OGP Peer to Peer Learning event in Jakarta, Indonesia &amp; Farewell Bishal Timilsina</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8044KkmUVNRUS3OfKYc1LA.jpeg" /></figure><blockquote>The more you think and talk about your goals, the more positive and enthusiastic you become.<br>- Billy Cox</blockquote><h4>Launch of NWC Helpline — Khabar Garaun 1145</h4><p><a href="http://nwchelpline.gov.np/">National Women Comission’s helpline ‘Khabar Garaun 1145’</a> was launched on December 10, 2017 during the closing ceremony of 16 days of activism against Gender based Violence (GBV) in Kathmandu. The ceremony was jointly organized by Minstry of Women, Children and Social Welfare (MoWCSW) and National Women Commission (NWC). The event was filled with representatives of government, civil society organizations, media and individuals. With the launch of the helpline, survivors of violence against women and girls (VAWG) and good samaritans (who witness such incidents) can report the incidents by dialing 1145 (from NT and Ncell).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k6TGZhbTbFuCkNG0Oh2a3A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*itj1LcM4hV_5t19aO0fq6Q.jpeg" /><figcaption>Left: Stall of YoungInnovations during the event, Right: Launch of Khabar Garaun 1145</figcaption></figure><p>The calls are toll-free i.e., callers will not be charged. The helpline will be operational for 24/7 providing necessary services to survivors. Also, they can report using online form and SMS (currently under development). We are looking after the technology part developing the system for helpline. Besides helpline, to manage the reports received, we have developed a case management system for NWC. On the day, we had our stall to explain how the systems works for participants of the program.</p><h4>YI Secret Santa has been announced</h4><p>When we were kids there was nothing better then receiving a gift. A wrapped present was a mystery story with an ending that was guaranteed to be excellent. You didn&#39;t know exactly what was inside, but you knew it was for you, and it was probably something you wanted. We all eventually reach an age at which giving gifts becomes just as thrilling as it was receiving them as a child. You grow up to find that the joy of making someone happy is more powerful than you could have possibly imagined.</p><blockquote>We make a living by what we get. We make a life by what we give.<br>- Winston Churchill</blockquote><p>We had so much fun last year exchanging gift from a secret Santa. It is a small game we play as part of the Christmas holiday celebration, where us <strong>Young Innovators</strong> become a Secret Santa for individuals whom we pick randomly, two weeks before the celebration. The theme of the game is getting to know the individual better and get them some thoughtful gifts along with a short note saying why they picked the gift, creating a happy and healthy working environment.</p><h4>YoungInnovation’s participation in OGP Peer to Peer Learning event in Jakarta, Indonesia</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-7kN8Iv1xu6-nyBTrY7kUA.jpeg" /></figure><p>YoungInnovations, represented by our CEO, <a href="https://medium.com/u/89196caed02e">bibhusan</a> (Bibhusan Bista), participated in Open Government Partnership Workshop on Anti-Corruption Framework in Budgeting and Public Contracting in Jakarta, Indonesia on December 13–14, 2017. During the workshop Bibhusan was involved in sharing our company’s experience on Open Contracting, specifically our work on Public Procurement Transparency Initiative in Nepal (<a href="http://www.ppip.gov.np/">http://www.ppip.gov.np</a>). Among 11 countries from Asia Pacific region participating in the workshop, the Open Contracting implementation example of Nepal was perhaps the first of its kind that was well appreciated by the participants. Along with the value of Open Contracting on procurement reform agenda of countries, key lessons that we have learned in Nepal was shared by Bibhusan during his delivery. It was vivid that our practical experience of implementing Open Contracting in Nepal was enlightening for other countries grappling with practical challenges for similar kind of implementation in their respective countries.</p><p>During the event, Bibhusan also participated in the High Level Asia Pacific Leadership Forum 2017 on OGP that was organized by the Government of Indonesia and the OGP Secretariat. He was the only participant from Nepal, that saw over 700 participants from the Asia Pacific region.</p><p>Do note that <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> is one of the few companies in the region providing technical and holistic support around the themes of Open Data, including Open Contracting in Nepal and several other countries. Do get in touch if you want to know more about our engagement in this area.</p><h3>Goodbye Bishal</h3><p>And lastly, we had so much fun working with our friendly and funny lad <a href="https://medium.com/u/79252b53e747">Bishal Timilsina</a>. He and I joined <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> on same day, since then he had helped me with different problems at work. Thanks for all the laughs and help over the years. Wishing you all the best moving on with your new professional life. You will be missed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b778be123197" width="1" height="1" alt=""><hr><p><a href="https://medium.com/younginnovations-blog/young-innovations-weekly-fightvaw-launched-secret-santa-younginnovations-participation-in-ogp-b778be123197">Young Innovations Weekly #118 : FightVAW launched, Secret Santa, YoungInnovation’s participation in…</a> was originally published in <a href="https://medium.com/younginnovations-blog">YoungInnovations&#39; Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[YoungInnovations Weekly #63: Nepal Administrative Staff College, new meeting room & Chocolates]]></title>
            <link>https://medium.com/younginnovations-blog/younginnovations-weekly-63-nepal-administrative-staff-college-new-meeting-room-chocolates-2c371bb5897f?source=rss-36b5dc266515------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c371bb5897f</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[open-contracting]]></category>
            <dc:creator><![CDATA[Raj Maharjan]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 09:45:35 GMT</pubDate>
            <atom:updated>2016-11-21T08:05:44.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtTMZ5cZ2KWWVFATIr3dpQ.png" /></figure><p>This week, <a href="https://medium.com/u/89196caed02e">bibhusan</a> was invited by Nepal Administrative Staff College (NASC) to conduct classes on e-governance to newly recruited section officers of Government of Nepal. During the sessions, he delivered theoretical as well as practical in-sights of e-governance and the role that they as future leaders of Nepalese bureaucracy can play in making government system effective and efficient in Nepal. Based on <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a>’ direct experience in new frontiers of governance using concepts like open data, civic engagement, open contracting, transparency and accountability, participants received first hand information on how the government institutions can embrace technology innovations to make efficient governance system in Nepalese context.</p><p>This week, our partner Open Contracting Partnership had a mission in Nepal in relation to Open Contracting project that <a href="https://medium.com/u/9d6b00a4800b">YoungInnovations</a> is implementing at Public Procurement Monitoring Office (PPMO) of Government of Nepal. Mr. Karilos Garnickas from Open Contracting Partnership was here in Nepal to discuss project activities and next steps of the project. Yes, we were swamped with marathon meetings and planning meetings for past few days. We will share more details about the project later but for now, we can say that we are super excited to be part of this project. It’s time that our knowledge and expertise for wider public procurement reform in Nepal. We hope we can make a difference !!!</p><p>New meeting room has been painted red and white and decorated with comfy bean bags. The room has not been decorated completely but we have already started using it for meetings, work and relaxation. The room definitely looks different than any other rooms in the building as it consist of comfortable environment. We are hoping to solve many issues in future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tt3nWIbSvUOqlSOs1lcSmA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-QmH2gwWgea5GqEx_XP4g.jpeg" /></figure><p>And at last but not the least, after a week long learning tour organized by the World Bank in Colombo, Sri Lanka, <a href="https://medium.com/u/e7a5e24386fd">Prawesh</a> has returned safely and brought everyone of us chocolates. Thank you <a href="https://medium.com/u/e7a5e24386fd">Prawesh</a> for the chocolates!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c371bb5897f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/younginnovations-blog/younginnovations-weekly-63-nepal-administrative-staff-college-new-meeting-room-chocolates-2c371bb5897f">YoungInnovations Weekly #63: Nepal Administrative Staff College, new meeting room &amp; Chocolates</a> was originally published in <a href="https://medium.com/younginnovations-blog">YoungInnovations&#39; Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>