<?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 Ranjan Kumar Thakur on Medium]]></title>
        <description><![CDATA[Stories by Ranjan Kumar Thakur on Medium]]></description>
        <link>https://medium.com/@ranjankumar1757?source=rss-a4cd62a783cb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lDGm32FQjB-3d5FPJPCPxw.jpeg</url>
            <title>Stories by Ranjan Kumar Thakur on Medium</title>
            <link>https://medium.com/@ranjankumar1757?source=rss-a4cd62a783cb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:06:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ranjankumar1757/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[Solid Principle With JavaScript:]]></title>
            <link>https://medium.com/@ranjankumar1757/solid-principle-with-javascript-7deb197617a0?source=rss-a4cd62a783cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7deb197617a0</guid>
            <category><![CDATA[solid-principles]]></category>
            <category><![CDATA[design-princples]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Ranjan Kumar Thakur]]></dc:creator>
            <pubDate>Tue, 26 Mar 2024 15:20:48 GMT</pubDate>
            <atom:updated>2024-03-26T15:40:48.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YL30P4ztk3vba36zTmC9GQ.png" /></figure><h3>What are SOLID Principles?</h3><p>SOLID is an acronym that stands for:</p><blockquote>Single Responsibility Principle (SRP)</blockquote><blockquote>Open-Closed Principle (OCP)</blockquote><blockquote>Liskov Substitution Principle (LSP)</blockquote><blockquote>Interface Segregation Principle (ISP)</blockquote><blockquote>Dependency Inversion Principle (DIP)</blockquote><p>The SOLID design principles are a subcategory of many principles introduced by the American computer scientist and instructor, Robert C. Martin (A.K.A Uncle Bob) in a 2000 paper.</p><ul><li><strong>The Single Responsibility Principle (SRP)</strong></li></ul><p>The single responsibility principle states that a class, module, or function should have only one reason to change, meaning it should do one thing.</p><p>For example, a class that shows the name of an animal should not be the same class that displays the kind of sound it makes and how it feeds.</p><p>Here’s an example in JavaScript:</p><pre>class Animal {<br>constructor(name, feedingType, soundMade) {<br>this.name = name;<br>this.feedingType = feedingType;<br>this.soundMade = soundMade;<br>}<br>nomenclature() {<br>console.log(`The name of the animal is ${this.name}`);<br>}<br>sound() {<br>console.log(`${this.name} ${this.soundMade}s`);<br>}<br>feeding() {<br>console.log(`${this.name} is a ${this.feedingType}`);<br>}<br>}<br>let elephant = new Animal(&#39;Elephant&#39;, &#39;herbivore&#39;, &#39;trumpet&#39;);<br>elephant.nomenclature(); // The name of the animal is Elephant<br>elephant.sound(); // Elephant trumpets<br>elephant.feeding(); // Elephant is a herbivore</pre><p>The code above violates the single responsibility principle because the class that’s responsible for printing the name of the animal also shows the sound it makes and its type of feeding.</p><p>To fix this, you have to create a separate class for the sound and feeding methods like this:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>nomenclature() {<br>console.log(`The name of the animal is ${this.name}`);<br>}<br>}<br>let animal1 = new Animal(&#39;Elephant&#39;);<br>animal1.nomenclature(); // The name of the animal is Elephant<br>// Sound class<br>class Sound {<br>constructor(name, soundMade) {<br>this.name = name;<br>this.soundMade = soundMade;<br>}<br>sound() {<br>console.log(`${this.name} ${this.soundMade}s`);<br>}<br>}<br>let animalSound1 = new Sound(&#39;Elephant&#39;, &#39;trumpet&#39;);<br>animalSound1.sound(); //Elephant trumpets<br>// Feeding class<br>class Feeding {<br>constructor(name, feedingType) {<br>this.name = name;<br>this.feedingType = feedingType;<br>}<br>feeding() {<br>console.log(`${this.name} is a/an ${this.feedingType}`);<br>}<br>}<br>let animalFeeding1 = new Feeding(&#39;Elephant&#39;, &#39;herbivore&#39;);<br>animalFeeding1.feeding(); // Elephant is a/an herbivore</pre><p>This way, each of the classes is doing only one thing:</p><ul><li>The first one prints the name of the animal</li><li>The second prints the kind of sound it makes</li><li>The third one prints its kind of feeding.</li></ul><p>That’s more code, but better readability and maintainability. A developer who didn’t write the code can come to it and understand what’s going on quicker than having it all in one class</p><h3>The Open-Closed Principle (OCP)</h3><p>The open-closed principle states that classes, modules, and functions should be open for extension but closed for modification.</p><p>This principle might seem to contradict itself, but you can still make sense of it in code. It means you should be able to extend the functionality of a class, module, or function by adding more code without modifying the existing code.</p><p>Here’s some code that violates the open-closed principle in JavaScript:</p><pre>class Animal {<br>constructor(name, age, type) {<br>this.name = name;<br>this.age = age;<br>this.type = type;<br>}<br>getSpeed() {<br>switch (this.type) {<br>case &#39;cheetah&#39;:<br>console.log(&#39;Cheetah runs up to 130mph &#39;);<br>break;<br>case &#39;lion&#39;:<br>console.log(&#39;Lion runs up to 80mph&#39;);<br>break;<br>case &#39;elephant&#39;:<br>console.log(&#39;Elephant runs up to 40mph&#39;);<br>break;<br>default:<br>throw new Error(`Unsupported animal type: ${this.type}`);<br>}<br>}<br>}<br>const animal1 = new Animal(&#39;Lion&#39;, 4, &#39;lion&#39;);<br>animal1.getSpeed(); // Lion runs up to 80mph</pre><p>The code above violates the open-closed principle because if you want to add a new animal type, you have to modify the existing code by adding another case to the switch statement.</p><p>Normally, if you’re using a switch statement, then it’s very likely you will violate the open-closed principle.</p><p>Here’s is the correct refactored the code to fix the problem:</p><pre>class Animal {<br>constructor(name, age, speedRate) {<br>this.name = name;<br>this.age = age;<br>this.speedRate = speedRate;<br>}<br>getSpeed() {<br>return this.speedRate.getSpeed();<br>}<br>}<br>class SpeedRate {<br>getSpeed() {}<br>}<br>class CheetahSpeedRate extends SpeedRate {<br>getSpeed() {<br>return 130;<br>}<br>}<br>class LionSpeedRate extends SpeedRate {<br>getSpeed() {<br>return 80;<br>}<br>}<br>class ElephantSpeedRate extends SpeedRate {<br>getSpeed() {<br>return 40;<br>}<br>}<br>const cheetah = new Animal(&#39;Cheetah&#39;, 4, new CheetahSpeedRate());<br>console.log(`${cheetah.name} runs up to ${cheetah.getSpeed()} mph`); // Cheetah runs up to 130 mph<br>const lion = new Animal(&#39;Lion&#39;, 5, new LionSpeedRate());<br>console.log(`${lion.name} runs up to ${lion.getSpeed()} mph`); // Lion runs up to 80 mph<br>const elephant = new Animal(&#39;Elephant&#39;, 10, new ElephantSpeedRate());<br>console.log(`${elephant.name} runs up to ${elephant.getSpeed()} mph`); // Elephant runs up to 40 mph</pre><p>This way, if you want to add a new animal type, you can create a new class that extends SpeedRate and pass it to the Animal constructor without modifying the existing code.</p><p>For example, I added a new GoatSpeedRate class like this:</p><p>This conforms to the open-closed principle.</p><pre>class GoatSpeedRate extends SpeedRate {<br>getSpeed() {<br>return 35;<br>}<br>}<br>// Goat<br>const goat = new Animal(&#39;Goat&#39;, 5, new GoatSpeedRate());<br>console.log(`${goat.name} runs up to ${goat.getSpeed()} mph`); // Goat runs up to 354 mph</pre><h3>The Liskov Substitution Principle (LSP)</h3><p>The Liskov substitution principle is one of the most important principles to adhere to in object-oriented programming (OOP). It was introduced by the computer scientist Barbara Liskov in 1987 in a paper she co-authored with Jeannette Wing.</p><p>The principle states that child classes or subclasses must be substitutable for their parent classes or super classes. In other words, the child class must be able to replace the parent class. This has the advantage of letting you know what to expect from your code.</p><p>Here’s an example of a code that does not violate the Liskov’s substitution principle:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>makeSound() {<br>console.log(`${this.name} makes a sound`);<br>}<br>}<br>class Dog extends Animal {<br>makeSound() {<br>console.log(`${this.name} barks`);<br>}<br>}<br>class Cat extends Animal {<br>makeSound() {<br>console.log(`${this.name} meows`);<br>}<br>}<br>function makeAnimalSound(animal) {<br>animal.makeSound();<br>}<br>const cheetah = new Animal(&#39;Cheetah&#39;);<br>makeAnimalSound(cheetah); // Cheetah makes a sound<br>const dog = new Dog(&#39;Jack&#39;);<br>makeAnimalSound(dog); // Jack barks<br>const cat = new Cat(&#39;Khloe&#39;);<br>makeAnimalSound(cat); // Khloe meows</pre><p>The Dog and Cat classes can successfully replace the parent Animal class.</p><p>On the other hand, let’s look at how the code below does violate the Liskov substitution principle:</p><pre>class Bird extends Animal {<br>fly() {<br>console.log(`${this.name} flaps wings`);<br>}<br>}<br>const parrot = new Bird(&#39;Titi the Parrot&#39;);<br>makeAnimalSound(parrot); // Titi the Parrot makes a sound<br>parrot.fly(); // Titi the Parrot flaps wings</pre><p>The Bird class violates the Liskov’s substitution principle because it’s not implementing its own makeSound from the parent Animal class. Instead, it’s inheriting the generic sound.</p><p>To fix this, you have to make it use the makeSound method too:</p><pre>class Bird extends Animal {<br>makeSound() {<br>console.log(`${this.name} chirps`);<br>}<br>fly() {<br>console.log(`${this.name} flaps wings`);<br>}<br>}<br>const parrot = new Bird(&#39;Titi the Parrot&#39;);<br>makeAnimalSound(parrot); // Titi the Parrot chirps<br>parrot.fly(); // Titi the Parrot flaps wings</pre><h3>The Interface Segregation Principle (ISP)</h3><p>The interface segregation principle states that clients should not be forced to implement interfaces or methods they do not use.</p><p>More specifically, the ISP suggests that software developers should break down large interfaces into smaller, more specific ones, so that clients only need to depend on the interfaces that are relevant to them. This can make the codebase easier to maintain.</p><p>This principle is fairly similar to the single responsibility principle (SRP). But it’s not just about a single interface doing only one thing — it’s about breaking the whole codebase into multiple interfaces or components.</p><p>Think about this as the same thing you do while working with frontend frameworks and libraries like React, Svelte, and Vue. You usually break down the codebase into components you only bring in when needed.</p><p>This means you create individual components that have functionality specific to them. The component responsible for implementing scroll to the top, for example, will not be the one to switch between light and dark, and so on.</p><p>Here’s an example of code that violates the interface segregation principle:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>eat() {<br>console.log(`${this.name} is eating`);<br>}<br>swim() {<br>console.log(`${this.name} is swimming`);<br>}<br>fly() {<br>console.log(`${this.name} is flying`);<br>}<br>}<br>class Fish extends Animal {<br>fly() {<br>console.error(&quot;ERROR! Fishes can&#39;t fly&quot;);<br>}<br>}<br>class Bird extends Animal {<br>swim() {<br>console.error(&quot;ERROR! Birds can&#39;t swim&quot;);<br>}<br>}<br>const bird = new Bird(&#39;Titi the Parrot&#39;);<br>bird.swim(); // ERROR! Birds can&#39;t swim<br>const fish = new Fish(&#39;Neo the Dolphin&#39;);<br>fish.fly(); // ERROR! Fishes can&#39;t fly</pre><p>The code above violates the interface segregation principle because the Fish class doesn’t need the fly method. A fish cannot fly. Birds can’t swim too, so the Bird class doesn’t need the swim method.</p><p>This is how I fixed the code to conform to the interface segregation principle:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>eat() {<br>console.log(`${this.name} is eating`);<br>}<br>swim() {<br>console.log(`${this.name} is swimming`);<br>}<br>fly() {<br>console.log(`${this.name} is flying`);<br>}<br>}<br>class Fish extends Animal {<br>// This class needs the swim() method<br>}<br>class Bird extends Animal {<br>// THis class needs the fly() method<br>}<br>// Making them implement the methods they need<br>const bird = new Bird(&#39;Titi the Parrot&#39;);<br>bird.swim(); // Titi the Parrot is swimming<br>const fish = new Fish(&#39;Neo the Dolphin&#39;);<br>fish.fly(); // Neo the Dolphin is flying<br>console.log(&#39;\n&#39;);<br>// Both can also implement eat() method of the Super class because they both eat<br>bird.eat(); // Titi the Parrot is eating<br>fish.eat(); // Neo the Dolphin is eating</pre><h3>The Dependency Inversion Principle (DIP)</h3><p>The dependency inversion principle is about decoupling software modules. That is, making them as separate from one another as possible.</p><p>The principle states that high-level modules should not depend on low-level modules. Instead, they should both depend on abstractions. Additionally, abstractions should not depend on details, but details should depend on abstractions.</p><p>In simpler terms, this means instead of writing code that relies on specific details of how lower-level code works, you should write code that depends on more general abstractions that can be implemented in different ways.</p><p>This makes it easier to change the lower-level code without having to change the higher-level code.</p><p>Here’s a code that violates the dependency inversion principle:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>}<br>class Dog extends Animal {<br>bark() {<br>console.log(&#39;woof! woof!! woof!!&#39;);<br>}<br>}<br>class Cat extends Animal {<br>meow() {<br>console.log(&#39;meooow!&#39;);<br>}<br>}<br>function printAnimalNames(animals) {<br>for (let i = 0; i &lt; animals.length; i++) {<br>const animal = animals[i];<br>console.log(animal.name);<br>}<br>}<br>const dog = new Dog(&#39;Jack&#39;);<br>const cat = new Cat(&#39;Zoey&#39;);<br>const animals = [dog, cat];<br>printAnimalNames(animals);</pre><p>The code above violates dependency inversion principle because the printAnimalNames function depends on the concrete implementations of Dog and Cat.</p><p>If you wanted to add another animal like an ape, you’d have to modify the printAnimalNames function to handle it.</p><p>Here’s how to fix it:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>getName() {<br>return this.name;<br>}<br>}<br>class Dog extends Animal {<br>bark() {<br>console.log(&#39;woof! woof!! woof!!!&#39;);<br>}<br>}<br>class Cat extends Animal {<br>meow() {<br>console.log(&#39;meooow!&#39;);<br>}<br>}<br>function printAnimalNames(animals) {<br>for (let i = 0; i &lt; animals.length; i++) {<br>const animal = animals[i];<br>console.log(animal.getName());<br>}<br>}<br>const dog = new Dog(&#39;Jack&#39;);<br>const cat = new Cat(&#39;Zoey&#39;);<br>const animals = [dog, cat, ape];<br>printAnimalNames(animals);</pre><p>In the code above, I created a getName method inside the Animal class. This provides an abstraction that the printAnimalNames function can depend on. Now, the printAnimalNames function only depends on the Animal class, not the concrete implementations of Dog and Cat.</p><p>If you want to add an Ape class, you can do so without modifying the printAnimalNames function:</p><pre>class Animal {<br>constructor(name) {<br>this.name = name;<br>}<br>getName() {<br>return this.name;<br>}<br>}<br>class Dog extends Animal {<br>bark() {<br>console.log(&#39;woof! woof!! woof!!!&#39;);<br>}<br>}<br>class Cat extends Animal {<br>meow() {<br>console.log(&#39;meooow!&#39;);<br>}<br>}<br>// Add Ape class<br>class Ape extends Animal {<br>meow() {<br>console.log(&#39;woo! woo! woo!&#39;);<br>}<br>}<br>function printAnimalNames(animals) {<br>for (let i = 0; i &lt; animals.length; i++) {<br>const animal = animals[i];<br>console.log(animal.getName());<br>}<br>}<br>const dog = new Dog(&#39;Jack&#39;); // Jack<br>const cat = new Cat(&#39;Zoey&#39;); // Zoey<br>// Use the Ape class<br>const ape = new Ape(&#39;King Kong&#39;); // King Kong<br>const animals = [dog, cat, ape];<br>printAnimalNames(animals);</pre><p>This is all about the brief explanation of Solid Principle with the use of JavaScript.</p><p>Credit:- freecodecamp</p><p>Thanks for reading till the end 😊😊😊😊.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7deb197617a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BookMyShow- (MERN Stack)]]></title>
            <link>https://medium.com/@ranjankumar1757/bookmyshow-mern-stack-d41f308c81ea?source=rss-a4cd62a783cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d41f308c81ea</guid>
            <dc:creator><![CDATA[Ranjan Kumar Thakur]]></dc:creator>
            <pubDate>Sun, 23 Jan 2022 16:39:43 GMT</pubDate>
            <atom:updated>2022-01-23T16:39:43.270Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Reader,</p><p><strong>BookMyShow</strong>-<strong> “Entertainment Ki Nayi Bhasha”,</strong></p><p><strong>BookMyShow- </strong>Bigtree Entertainment’s BookMyShow is <strong>India’s largest entertainment ticketing website</strong>. Headquartered in Mumbai, it is the only destination for movie and non-movie options like events, plays and sports. … Tickets can be booked through various platforms like internet, mobile application, WAP and the in — house call center.</p><p>Moving ahead I am <strong>Ranjan Kumar Thakur</strong> an <strong>Full Stack</strong> <strong>Developer</strong> in <a href="https://www.masaischool.com/"><strong>Masai School</strong></a> in the Batch FT WEB12. I am almost on the verge of completion of <strong>Unit-5</strong>. It was during the final week which is depicted as the construct week. We have done this project with group of 6 members and build the clone of a very popular E-Commerce website in the India for <strong>“Entertainment Ki Nayi Bhasha”</strong>, <em>“</em><a href="http://www.bookmyshow.com/"><strong>BookMyShow</strong></a><strong> </strong>”for Learning Purpose. This blog is all about our journey and the challenges we faced while building the project.</p><p>I have learnt the following things in this unit some of are-</p><ol><li>React</li><li>Router</li><li>React-Redux</li><li>UseState</li><li>UseEffect</li><li>Mongo DB.</li><li>Google Auth, Authorization</li><li>Dynamic Routing</li><li>RTK Query</li><li>Data Structure and Algorithm (Optimized Problem-Solving Technique).</li></ol><p><strong>Team Members</strong></p><ul><li>Rohit Baghel</li><li>Prakhar Bhalla</li><li>Ranjan Kumar Thakur</li><li>Kamesh Hedau</li><li>Imran Ali</li></ul><p>The project has reached their completion due to hard work and co-operation of our teammates and support of the faculties.</p><h3>Problem Statement-</h3><p>So, I had a problem statement that I have to create a clone of full-fledged full stack (Backend along with Frontend) of a website called <a href="http://www.bookmyshow.com/"><strong>BookMyShow</strong></a><strong> </strong>using Realtime cloud-based database-Mongo DB-Atlas, we have to use the skillset which I have learned throughout till now and We were six members in our group and finish the task with in deadline time.</p><h3>Team And Work Split Up</h3><p>While working on team, communication plays an important role and when working remotely in this situation like someone is sitting 1000Kms away from me so the communication becomes most vital to work on their ideas effectively, in a timed manner to complete the task within deadline.</p><p>We have discussed <strong>what and how to Clone</strong>, <strong>Most Vital Products (MVP)</strong>, <strong>functionality, Modules to consider </strong>while doing this we have used famous <strong>MOSCOW </strong>principle. We have breakdown our works accordingly.</p><h3>Collecting Project Data-</h3><p>Before working on this project, the first basic thing came up in the mind was first visit the Website and understand the functionality, visual, type of products etc. We are amazed to see the design of website, functional, features, support system, marketing ideas of showcasing the products etc. We have collected data from the <strong>original website</strong>, used some Npm <strong>libraries</strong>, Google, and <a href="https://github.com/"><strong>GitHub</strong></a> for whole <strong>project Collaboration</strong> etc.</p><p><strong>Tech Stack Used-</strong></p><p>We have used <strong>React, Redux</strong>, Styling was done with plain<strong> CSS</strong>, and <strong>Tailwind CSS, </strong>Functionality was accomplished by React. We have used <strong>Google Auth </strong>for Login, Mongo DB for preparing Database, Mongoose (Communication between Db and Express), <strong>Paytm Payment API</strong> for payment gateway etc.</p><p>We have used <strong>Express, NodeJS, Mongoose (Schema, Model) for Backend Crud operation for </strong>dealing with real-time data<strong>, React, Redux, CSS for Frontend.</strong></p><h3>Some Snapshots of our Project: -</h3><ul><li><strong>Homepage</strong></li></ul><p>Home page is built with beautiful components, it contains list of recommended movies and events and user can book tickets for any show. User can select a location and also sign-in or create an account before booking</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XD0xdB5IhBxqfuuu.png" /></figure><p>BookmyShow home page</p><ul><li><strong>Movies</strong></li></ul><p>in this page user can see all the movies for his selected city user can filter the movie according to language, genres and format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9m1E38YQoajdsbaq.png" /></figure><p>Movie page</p><ul><li><strong>Signup and Login</strong></li></ul><p>We have used manual account creation as well as auth for authentication and authorization, user can create new account and also sign-in with existing account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5tg9lvWKtwwM5UTU.png" /></figure><p>Sign-up page</p><h3>The outcome and important learning from the Project: -</h3><p>This entire journey of making the project was awesome. I have learned lots of things by applying to the real website and it gave us a lot of confidence. After doing this project my knowledge on how a team works on a database has been improved and also got to know how to interconnect frontend with backend.</p><p>There were some more functionalities that could have been done. yes, the time didn’t permit us to go further. But we will surely improve it during the course of time in future.</p><p>If you want to look at the project then you can go to this GitHub Repo.</p><p><a href="https://github.com/"><strong>GitHub</strong></a><strong>- </strong><a href="https://github.com/Rohitbaghel/book-my-show-clone">https://github.com/Rohitbaghel/book-my-show-clone</a></p><p>I would like to give credit to team member, Masai Support System, BookMyShow for such as wonderful website for awesome learning etc.</p><p><strong>Disclaimer: -</strong></p><p>All the content, images and other data taken while cloning this website is just for Learning Purpose.</p><p><strong>Thank You for Reading </strong>😊😊😊😊😊.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d41f308c81ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zoom Car — Clone (Learning Purpose)]]></title>
            <link>https://medium.com/geekculture/zoom-car-clone-learning-purpose-65675e5c064f?source=rss-a4cd62a783cb------2</link>
            <guid isPermaLink="false">https://medium.com/p/65675e5c064f</guid>
            <category><![CDATA[json-server]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[html5]]></category>
            <category><![CDATA[paytm-payment-gateway]]></category>
            <dc:creator><![CDATA[Ranjan Kumar Thakur]]></dc:creator>
            <pubDate>Sat, 13 Nov 2021 14:08:35 GMT</pubDate>
            <atom:updated>2024-03-29T06:37:15.945Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zoom Car — Clone (Learning Purpose)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/56/0*Q8rxhYjQO0yDObeE.png" /></figure><p>Hello Reader,</p><h4>Zoomcar-” <em>Self Drive For The Self Driven”.</em></h4><p><a href="https://www.zoomcar.com/"><strong>Zoomcar</strong></a> is very popular Indian self-drive car rental company, headquartered in Bangalore, India. The company was founded in 2013 by David Back and Greg Moran. It currently operates in 34+ cities. While riding on it, you will feel like you are in your Car.</p><p>I am <strong>Ranjan Kumar Thakur</strong> an <strong>Aspiring Full Stack Web Developer</strong> I am almost on the verge of completion of <strong>Unit-3</strong>. It was during the final week which is depicted as the construct week. We have done this project with a group of 6 members and built a clone of a very popular E-Commerce website in India for <strong>“Self Drive For Self Driven”</strong>, and <em>“</em><a href="https://www.zoomcar.com/"><strong><em>Zoom Car</em></strong><em>” </em></a>for Learning Purposes. This blog is all about our journey and the challenges we faced while building the project.</p><p>I have learnt the following things in this unit some of are-</p><ol><li>Node</li><li>Express.</li><li>React</li><li>NPM Packages (Mongoose, Jwt Token, Express-Authenticator etc)</li><li>Pagination</li><li>Mongo DB.</li><li>Google OAuth2.0, Authorization</li><li>Model View Control (MVC).</li><li>Event loop in NodeJS.</li><li>Data Structure and Algorithm (Optimised Problem-Solving Technique).</li></ol><p>Team Overview.</p><ol><li>Ranjan Kumar Thakur</li><li>Pankaj Kumar</li><li>Nikita Parekh</li><li>Mithlesh Kumar</li><li>Raoji Patil</li><li>Priyanshi Tiwari</li></ol><p>The project has reached its completion due to the hard work and cooperation of our teammates and the support of the faculties.</p><h3>Problem Statement-</h3><p>So I had a problem statement that I had to create a clone of a website called <a href="https://www.zoomcar.com/"><strong>Zoomcar</strong></a><strong> </strong>Also, I had to use the skillset which I have learned throughout till now We were six members in our group and finished the task within in deadline time.</p><h3>Team And Work Split-Up</h3><p>While working on a team, communication plays an important role and when working remotely in this situation where someone is sitting 1000 km away from me communication becomes most vital to work on their ideas effectively, and in a timed manner to complete the task within the deadline.</p><p>We have discussed <strong>what and how to Clone</strong>, the <strong>Most Vital Products (MVP)</strong>, <strong>functionality, and Modules to consider </strong>while doing this we have used the famous <strong>MOSCOW </strong>principle. We have split our work accordingly.</p><h3>Collecting Project Data-</h3><p>Before working on this project, the first basic thing that came to mind was first visit the Website and understand the functionality, visuals, type of products etc. We are amazed to see the design of the website, functional, features, support system, marketing ideas of showcasing the products etc. We have collected data from the <strong>original website</strong> and used some <strong>external libraries</strong>, Google, <a href="https://developer.paytm.com/"><strong>Paytm</strong></a> Payment test API, and <a href="https://github.com/"><strong>GitHub</strong></a> for whole <strong>project Collaboration</strong> etc.</p><p><strong>Tech Stack Used-</strong></p><p>We have used <strong>HTML-5</strong>, Styling was done with plain<strong> CSS</strong>, and Functionality was accomplished by <strong>advanced JavaScript</strong>. We have used <strong>Google API </strong>for dynamic location, Calendar for Trip Date,<strong> JSON Server</strong> for preparing Car Database, <strong>Fetch Web API</strong>, <strong>Paytm Payment API</strong> for payment gateway etc. We have used <strong>HTML, CSS , and JavaScript</strong> code using the methodology of <strong>DOM manipulation</strong>, for storing data We have used <strong>Local Storage.</strong></p><h3>Some Snapshots of our Project:-</h3><p><strong>Home Page-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6tNtKeTl3nO-Ht3pcdCl5Q.png" /><figcaption>Home-1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQDa4JnDFJUIJNKtKP9A4A.png" /><figcaption>Footer Section</figcaption></figure><p><strong>Login-Sign Up-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cS5PEGBP6A6qYRYfjBCCLw.png" /><figcaption>Login-Sign Up to Book you Trip</figcaption></figure><p><strong>Select City for trip Booking</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgRUnD2v1HTgEHIqTvujzw.png" /><figcaption>Select Your City</figcaption></figure><p><strong>Select Pick-up and Drop-Off Location-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ygIK1tEy0gX1RgWee4WKw.png" /><figcaption>Select Pick up and Drop-off Location from the Map</figcaption></figure><p><strong>Car Showroom for Booking-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-YBQfshzGJYRlyk24ZRBA.png" /><figcaption>Car for Booking your Trip</figcaption></figure><p><strong>Selected Car Description-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EQW4hAwz7R9ouFq_OWeo-A.png" /><figcaption>Selected Car Details</figcaption></figure><p><strong>Payment Breakup-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w6HRN_uxGQCMOTYHFSpNIQ.png" /><figcaption>Payment Breakup for the Selected Car</figcaption></figure><p><strong>Mode Of Payment-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W3KgXzWqO27PPAvdkfCFdg.png" /><figcaption>Mode of Payment Option</figcaption></figure><p><strong>Real Time Payment Gateway-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04RMn92IHiFoiPFjAYTY2Q.png" /><figcaption>Paytm Wallet</figcaption></figure><p><strong>Add Money to Paytm Wallet for the Payment-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*j7yjn_tVNSY9LFikMfVq-w.png" /><figcaption>Paytm Wallet-2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*wzQa4kW44wwh6iai9z4Z6Q.png" /><figcaption>Paytm-3</figcaption></figure><p><strong>Fill Card Details for the Payment-</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*hS6fF3G7BTxUfnjzWC5G1Q.png" /><figcaption>Fill Card Details-</figcaption></figure><p>Final Payment Confirmation-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aKe_3Zdf-jvvjrR5DECK7g.png" /><figcaption>Payment Confirmation</figcaption></figure><h3>The outcome and important learning from the Project:-</h3><p>This entire journey of making the project was awesome. I have learned lots of things by applying to the real website and it gave us a lot of confidence. some more functionalities could have been done. yes, the time didn’t permit us to go further. But we will surely improve it over time in future.</p><p>If you want to look at the project then you can go to this GitHub Repo.</p><p><a href="https://github.com/"><strong>GitHub</strong></a><strong>-</strong><a href="https://github.com/iampankajk/ZoomCar-Clone.git">https://github.com/iampankajk/ZoomCar-Clone.git</a></p><p>I would like to give credit to team members, Masai Support System, IA, and Zoom Car for such wonderful products for awesome learning etc.</p><p><strong>Disclaimer: -</strong></p><p>All the content which are used in this project such as images and other data taken from the original website and the internet are just meant for learning purposes.</p><p><strong>Thank You for Reading </strong>😊😊😊😊😊.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65675e5c064f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/zoom-car-clone-learning-purpose-65675e5c064f">Zoom Car — Clone (Learning Purpose)</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>