<?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 Mutombo Jean-Vincent on Medium]]></title>
        <description><![CDATA[Stories by Mutombo Jean-Vincent on Medium]]></description>
        <link>https://medium.com/@sigmacool?source=rss-f3a00e25b9f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nWRoGS_TiKFcKhaICb1XtQ.jpeg</url>
            <title>Stories by Mutombo Jean-Vincent on Medium</title>
            <link>https://medium.com/@sigmacool?source=rss-f3a00e25b9f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:56:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sigmacool/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[The ultimate guide to learning ReactJS in 2021.]]></title>
            <link>https://medium.com/@sigmacool/the-ultimate-guide-to-learning-reactjs-in-2021-99df529c1964?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/99df529c1964</guid>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[guidelines]]></category>
            <category><![CDATA[learn-react-js]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Tue, 05 Oct 2021 21:10:43 GMT</pubDate>
            <atom:updated>2021-10-05T22:04:03.228Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>How to learn React is a priority for many JavaScript developers?<br>A recent survey of the state of JS showed that many developers are relying on React to build modern web applications.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*SbtbZ6GoaMlwSIxL" /><figcaption>Keep it simple: everything can be a component.</figcaption></figure><p>To learn React, you need to have the basics of HTML, CSS, and Javascript. Then you will need to learn React JS fundamentals from the official site, YouTube, FreeCodeCamp, or other learning resources. Finally, practice with concrete projects.</p><p>However, due to its popularity and demand for work, there are still a lot of JavaScript developers who want to learn React.</p><p><em>I would like to give beginners a comprehensive overview of how to approach learning React without getting distracted or overwhelmed by other topics along the way</em>.</p><h3>How to get started with React</h3><h4>Learn React or JavaScript in the first place?</h4><p>It’s important to understand at least the basics of JavaScript, often referred to as JavaScript ES5, and have a decent knowledge of HTML and CSS. React also uses JavaScript syntax, most commonly referred to as JavaScript ES6 and beyond. This is why it makes sense to get familiar with at least JavaScript ES6 to learn React.</p><p>Many people recommend learning web development and all the basics of JavaScript as a prerequisite to learning React.</p><p>Personally, I think most of the JavaScript concepts can be learned along the way by learning React.</p><h4>Learn React or JQuery?</h4><p>Historically, jQuery has bridged the gap between “vanilla” JavaScript and modern libraries such as React, Angular, and Vue. Since then, the tide has turned and basic JavaScript has everything you need to be able to do without jQuery!</p><blockquote>In 2021, you no longer need to learn jQuery to develop web applications.</blockquote><h4>Learn React or Angular?</h4><p>Angular is a full-fledged mobile and web development framework. React is a library intended solely for user interface development, which can be turned into a full-fledged solution with the help of additional libraries.</p><p>React seems simpler at first glance, and it takes less time to start working on a React project.</p><p>Angular is more complex and takes a while to learn. Still, it is a powerful tool that provides a good web development experience.</p><p>Both are constantly updated to keep pace with the competition. For example, while React was supposed to win thanks to its virtual DOM, Angular matched the score by implementing change detection.</p><p>While Angular was considered a winner because of its development by an authoritative company like Google; React’s huge, dedicated community fully compensated for Google’s reputation and made React similar to Angular.</p><blockquote>Ultimately, choosing React vs Angular is a matter of personal preference, skills, and habits. As a programming newbie, you would probably benefit from starting with React.</blockquote><h4>Learn React or VueJS?</h4><p>Vue.js and React are both great technologies for building UIs. To choose the best tool for your next project, you need to consider a number of factors, including your specific use case, needs, environment, developer availability, budget, and work schedule.</p><p>Vue is lightweight, easy to learn, and fun to write. With its familiar syntax and the use of components, integrating or migrating existing projects to Vue is faster and easier. For this reason, Vue.js, like React, is ideal for start-ups but can be used in large-scale applications just as well.</p><p>In terms of performance, Vue.js is comparable to React. However, the end results depend primarily on optimization efforts and the size of the application. The documentation is excellent, explaining everything in great detail.</p><p>Vue has official packages for state management, routing, or server-side rendering, which come with updated support and keep your system synchronized. With Vue CLI 3 and Vue UI, setting up a project and preparing for its deployment is lightning fast. This allows you to create MVPs quickly and efficiently.</p><p>React, on the other hand, is a veteran of the JS field. With the support of businesses, a large community, and an even larger ecosystem, React is ideal for building complex enterprise-level applications. Plus, the job market is booming with experienced React developers, so you won’t be short of specialists. Thanks to his maturity and his community, he is more or less guaranteed to get quick help and a detailed response.</p><h3>Why learn React?</h3><p><em>React is an open-source project created and maintained by Facebook. This front-end library is one of the most popular alongside Vue.JS and Angular. Learning React will not only allow creating websites but also mobile applications and Virtual Reality (VR) projects.</em></p><h3><em>Reactjs documentation</em></h3><p>Referencing library documentation as a newbie to web development can be intimidating. But I firmly believe that this is the best way to learn something new.</p><p>Knowing how to read documentation pages is one of the skills useful for a developer career. And you’re lucky, the one for React is well written and has tutorials!</p><h3>Best online resources to learn ReactJs</h3><p>Apart from the official Reactjs documentation and tutorials, there are many qualitative courses on the internet. You will find tutorials in the form of articles, and videos as well as books and interactive courses.</p><p>Among these, there are, for example:</p><ul><li>The OpenClassrooms tutorial</li><li>Books to learn React</li><li>YouTube channels like Traversy Media, Academind, The Net Ninja, etc.</li><li>Twitch channels</li><li>Interactive courses like FreeCodeCamp</li><li>Advanced tutorials on Udemy</li></ul><h3>Important concepts in React</h3><p>Before going any further, make sure you understand the key concepts in React. These includes:</p><ul><li>JSX syntax, Components, and Props</li><li>State management</li><li>React Virtual DOM</li><li>Javascript High Order Function</li><li>Promises and async-await syntax</li><li>Fetch API for HTTP requests</li></ul><p>After taking the beginner&#39;s tutorials on the React documentation and learning React basics from scratch, keep learning by building a <strong>real-world project</strong> yourself before learning any other technology. It is not always easy to come up with project ideas, but there is a lot of inspiration: I personally started by creating a TODO app with CRUD features (Create-Read-Update-Delete).</p><h3>How to start a project in React?</h3><p>If you want to take your first steps and code directly, without installing anything, you can use <a href="https://codepen.io/">CodePen</a> or <a href="https://codesandbox.io/">CodeSandbox</a>. If not, you can use <strong>Create-React-App</strong> or any other boilerplate.</p><h3>Advanced React Notions</h3><p>After learning React basics, React’s props, states, and JSX syntax for returning valid HTML to JavaScript, you can take more advanced React concepts a step further. Among these concepts, there are:</p><ul><li>React hooks</li><li>Higher-Order Components</li><li>Render Prop Components</li><li>Correctly use the Context API</li></ul><p>By knowing these advanced React techniques, you should be comfortable getting started in developing more complex React applications.</p><h3>Complementary libraries to React</h3><p>Only after learning React and feeling comfortable with its basic and advanced implementation details, there are many learning paths you can take to improve your React skills. The React ecosystem is not about opinion, but about innovation and scale. Some recommendations:</p><h4>React Router</h4><p>React comes without navigation. As mentioned earlier in this article, React is not a framework but a library. Therefore, the react library does not come with a navigation system. Several packages have emerged and to start easily, I recommend React vient sans moyen de navigation. Je vous l’ai répété plusieurs fois dans cet article mais React n’est pas un framework mais une libraire. De ce fait, la librairie react ne vient pas avec un système de navigation. Plusieurs package ont vu le jour et pour commencer facilement, je vous conseille <a href="https://reactrouter.com/"><strong>React Router</strong></a>.</p><h4>AWS Amplify</h4><p>To easily learn <strong>AWS</strong> (Amazon Web Services), <a href="https://aws.amazon.com/amplify/"><strong>AWS Amplify</strong></a> allows to easily launch back-ends services and focus on the front-end, here React.</p><h4>Firebase</h4><p><a href="https://firebase.google.com/">Firebase</a> also goes very well with React! Google’s cloud tool will allow focusing on the front-end application while using powerful back-end technologies.</p><h4>Typescript</h4><p>If you choose to use Typescript, not only will vanilla JavaScript code be typed with TypeScript, but also your React components and everything that goes with them. I do not recommend that you start learning React using Typescript because it will just add complexity to your learning curve.</p><h4>Redux</h4><p>Redux is a popular state management library for JavaScript. Again, learn React and its built-in health management first before accessing a sophisticated external health management library for use in large, complex applications. React already comes with a number of tools for managing the state in your application. The vast majority of React applications don’t even need Redux or some other state management library. Learn how to manage the state in React before running another problem library. Redux makes React more complicated for beginners.</p><h4>Gatsby</h4><p>Gatsby.js has become quite popular lately. It is the ideal solution for creating <strong>static websites</strong> such as personal websites, blogs, and landing pages. However, Gatsby comes with its own learnings such as <strong>GraphQL</strong>, its great plugin system, and the issues that come with React applications rendered on the server-side. So don’t confuse Gatsby.js with easier React learning. It makes it easy to write static websites with React, but not to learn React itself.</p><h4>NextJS</h4><p>Like Gatsby, Next.js is an open-source development framework built on top of <strong>Node.js</strong> enabling React-based web applications functionalities such as <strong>server-side rendering</strong> and generating <strong>static websites</strong>. React documentation mentions Next.js among <em>“Recommended Toolchains”</em> advising it to developers as a solution when “building a server-rendered website with Node.js”.</p><p>Traditional React apps render all their content in the client-side browser, Next.js is used to extend this functionality to include applications rendered on the server-side.</p><p>The copyright and trademarks for Next.js are owned by company Vercel (previously named <strong>ZEIT</strong>), which also maintains and leads its open-source development.</p><h3>Conclusion</h3><blockquote><em>There you go, that’s all on my end. Now you know why and how to learn React JS efficiently and for free.</em></blockquote><blockquote><em>Stay curious, practice every day with your hands dirty, do it publicly and see your learning as a marathon and not as a sprint. Challenge yourself to improve your skills as a programmer and become a React developer this year 2021!</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99df529c1964" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identifying the Highest Priority Problem & Recommending solutions]]></title>
            <link>https://medium.com/@sigmacool/identifying-the-highest-priority-problem-recommending-solutions-b16f1784e4e6?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b16f1784e4e6</guid>
            <category><![CDATA[problems]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[highest]]></category>
            <category><![CDATA[identify]]></category>
            <category><![CDATA[priorities]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 20:49:08 GMT</pubDate>
            <atom:updated>2019-07-15T20:52:19.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JIUAoGgKceTWZuRX" /><figcaption>Photo by <a href="https://unsplash.com/@ikukevk?utm_source=medium&amp;utm_medium=referral">Kevin Ku</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Software development or any other project facing multiple requirements, feature constraints, and tight deadlines often necessitate the need to prioritize stakeholders’ requirements. At some point, it’s usually necessary to make decisions on which set of requirements need to be implemented first and which ones can be delayed until a later release.</p><blockquote>How can we prioritize our tasks? We know that it’s more efficient to solve the most important tasks first. But how do we determine which ones are the most important? And how do we do that without lighting the project on fire first?</blockquote><p>Prioritization as a principle means “doing the first thing first”. As a process, it means “<em>evaluating a group of items and ranking them in their order of importance or urgency</em>”. Actually, prioritization is our everyday activity. We continuously make choices and direct our activity to some task.</p><p>Here are steps to undertake when it comes to problem priority and recommending solutions:</p><ul><li>Define the problem</li><li>Look at potential causes for the problem</li><li>Identify alternatives for approaches to resolve the problem</li><li>Select the implementation of the best alternative</li><li>Verify if the problem has been resolved or not.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*4xtmAbHxYMrfRbE5" /><figcaption>Own draw using Lucidart.com</figcaption></figure><h3>Description of one problem I identified as a problem worth solving</h3><p>During our simulation, we had a bunch of problems. I am going to talk about one that we encountered when working on our backend project.</p><p>The problem in question happened when documenting our API, in fact, another teammate picked a PT story in which he supposed to configure swagger for API documentation. He did it successfully, and we were able to document our endpoints.</p><h4>Define the problem</h4><p>To be precise, we felt into an issue with Git <strong>merge</strong> conflict, every time we were writing API documentation on the swagger JSON file.</p><p>In Git, “merging” is the act of integrating another branch into your current working branch. You’re taking changes from another context and combine them with your current working files.</p><h4>Look at potential causes for the problem</h4><p>The problem was caused by the fact that we were all of us editing the same swagger JSON file. So, the conflict was almost impossible to be solved as the JSON file structure was insane.</p><h4>Identify alternatives for approaches to resolve the problem</h4><p>Among alternatives, I thought about using other utilities to write our API:</p><ul><li>Swagger HUB</li><li>Swagger-jsdoc to document on the fly as the <a href="https://dev.to/akshendra/generating-documentation-on-the-fly-in-express-2652">link</a> is showing</li><li>Swagger Editor</li><li>Splitting swagger spec into multiple files</li></ul><h4>Select the implementation of the best alternative</h4><p>After a different analysis of the problem, 3 alternatives were not suitable for solving the problem. So I chose the last alternative: Splitting swagger spec into multiple files.</p><p><strong><em>Why I found the last solution suitable?</em></strong> It is because, in order to avoid Git merge conflict, we need to structure our project in a way to avoid all the team to edit the same files.</p><p>So, I read an <a href="https://medium.com/the-andela-way/splitting-your-swagger-spec-into-multiple-files-in-a-node-project-2019575b0ced">article</a> created by an Andelan about decentralizing swagger documentation with swagger-jsdoc. The article was really helpful as I learned an effective way of documenting APIs with swagger. Shoutout to <a href="https://medium.com/@cwizard2011">Peter Adeoye</a>.</p><h4>Verify if the problem has been resolved or not.</h4><p>The solution to the problem was accurate in my opinion, even if there can still a better solution for the swagger documentation issue. But now look at our <a href="https://github.com/andela/ah-kgl-wakanda-backend/tree/develop/server/docs">documentation</a> structure, we never had Git merge conflict on swagger.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b16f1784e4e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adaptability, motivation and Commitment: “important ingredients for the Andela Bootcamp”]]></title>
            <link>https://medium.com/@sigmacool/adaptability-motivation-and-commitment-important-ingredients-for-the-andela-bootcamp-a96f9fe4a160?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a96f9fe4a160</guid>
            <category><![CDATA[kigali-01]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 15:11:59 GMT</pubDate>
            <atom:updated>2018-11-28T09:34:56.693Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>It is said: “Nothing is permanent, except change”. In our lives, changes are multiplying and, at work, are numerous and frequent. They involve other ways of doing things, new values and sometimes role changes. As a result, they constantly challenge our ability to adapt and cope with novelty.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Dcen1XxNkJCSt6yP" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=medium&amp;utm_medium=referral">Headway</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For companies, changes are needed … Restructuring, mergers, reconfiguration of processes are, among other things, as many major transformations that are set in motion. Can human impacts be adequately measured?</p><p>In the Andela Bootcamp, one of the learned lessons I can never forget is that:</p><p>— The flexibility of a structure, the versatility, and technological mastery, make it easier for a team of software developers to adapt to different working situation and development methodology. Effective communication also can give us the necessary reactivity to adapt to changes.</p><p>Personally, when working on my challenges for the Bootcamp, and passing all days in the workshop, I have demonstrated adaption to new conventions in terms of project structure and version control standards. In the beginning, it was not easy but after practices, it becomes rapid for me to make every commit following the Andela naming conventions, use a different approach when creating Pull Request and writing effective pivotal tracker stories.</p><p>Apart from Adaptability, I can say that a software developer has to be passionate and love this job. To code, it is a must to have a logical mind, to understand the logic of things and know how they work.</p><p>However, there comes a time when this motivation decreases, you are not as excited about your work as before. You may be going through a difficult challenge that may not be related to your work, but actually affects it. The commitment can be the key to solve this problem.</p><p>I can define commitment as a pledge or a promise, an obligation to something. I prefer the definition that describes commitment as dedication. The commitment is linked to a voluntary decision to participate in a project, an action, or other, falling within the time. It can be made through a personal or collective project, which then serves as a support for the commitment. It can be total or partial.</p><p>In my case, every time I feel overwhelmed in my project, I am thinking about opportunities and advantages I could get if I adapt myself to the Andela workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a96f9fe4a160" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Andela Bootcamp, a better way to quickly learn]]></title>
            <link>https://medium.com/@sigmacool/andela-bootcamp-i-better-way-to-quickly-learn-6c9a39d832fd?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c9a39d832fd</guid>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[kigali-01]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 15:00:45 GMT</pubDate>
            <atom:updated>2019-06-11T09:19:12.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_RYDQ_cGFFh4YRvJ" /><figcaption>Photo by <a href="https://unsplash.com/@nikarthur?utm_source=medium&amp;utm_medium=referral">Nik MacMillan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>To listen to certain people, programming is something difficult, reserved for intellectuals, engineers, people who are gifted in mathematics, “<em>geeks</em>”…. You can hear all kinds of things around this. But in reality, programming uses only one thing: <strong>logic</strong>! And that’s the key word in history. Whether you want to make a program, a game, software, a website, an application or other, it is enough to have a minimum of logic and patience to be able to concretize your project.</blockquote><p>At the Andela Bootcamp, I am learning the best way to work as a software developer, the right tools to use, the best way to organize ideas and the project, and the most important: how to collaborate and the efficient way to improve skills.</p><p>I have been programming since longtime in Javascript and PHP, using frameworks like Angular and Ionic. I was feeling myself an advanced developer because such frameworks seem not to be easy for a beginner developer. Even if I was already using advanced tools, At the Andela Bootcamp I had the opportunity to use more tools that so benefited for me. The Bootcamp is not finished yet, but I feel confident to become great compared to before because I created my first API-Restful in NodeJS and Express. This has added powerful knowledge in my life as a developer since this API follows development rules, meets the standard and design pattern “Model-Route-Controller”. If I have to explain all that I learned during the first four days of Bootcamp, my words could have the same number of pages as a dictionary. I admit it, I exaggerate in my expression! But it’s just to say that I’ve met so many fascinating things in such a short time. Moreover, the Bootcamp is not yet finished, so many surprises are still waiting. So I would dive into my Bootcamp experience in few words:</p><p><strong>The understanding of the Agile Model by practices</strong>: At the University, I had the notion of theory about the Software Development Life Cycle without basically catching the interest and the need of such habitude. In the Andela Bootcamp, I started using <strong><em>Pivotal Tracker</em></strong>, one of the greatest tools in terms for project management and planning: it helps to gather user and system requirements, subdividing the project into small manageable tasks and avoid to be lost if the project starts to become large. As project managers, we’re always looking for new ways to enhance the work that we do and to get more out of the limited amount of time available to us. We’re all too aware of how a couple of minutes here and a couple of minutes there will add up and lead to huge efficiencies over time. Because of that, it’s important to try new tools and techniques whenever they become available. We can measure the impact that they have and stick with anything that helps to manage projects more easily, more efficiently or more profitably.</p><p><strong>What is continuous integration in the Agile Model? </strong>When we make the choice to set up a continuous integration environment, it is essential to plan the implementation of tests. Without these, the interest of such an environment is severely limited (concretely: check that the code compiles).</p><p>The idea is to develop in “test-driven” mode, which consists of writing the tests before the developments. This provides a real projection of the objectives to achieve in terms of implementation, functionality, performance, integration, etc.</p><p><strong>What is code coverage in the Agile Model? </strong>It<strong> </strong>is used to evaluate the quality of a test set by checking which parts of the code are called during the tests. If the code is called during a test, this portion of code is considered covered; on the other hand, all non-called code is considered as uncovered. Coverage is therefore expressed as a percentage representing the proportion of code covered on the total amount of code.<br>There are different ways to measure the coverage, we distinguish in particular: <strong>function coverage or method coverage</strong> which verifies that each method (public, protected or private) of a class has been executed, <strong>Statement coverage or line coverage</strong> which verifies that each instruction has been executed, <strong>branch coverage</strong> which checks that each possible course.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c9a39d832fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How eslint, and airbnb style guide changed my javascript coding skill]]></title>
            <link>https://medium.com/@sigmacool/how-eslint-and-airbnb-style-guide-changed-my-javascript-coding-skill-3fd2a5a33fb8?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fd2a5a33fb8</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[kigali-01]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Wed, 21 Nov 2018 15:00:21 GMT</pubDate>
            <atom:updated>2018-11-28T09:55:38.646Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Eslint, and Airbnb style guide changed my javascript coding skill</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NWh7pH_sXcwOyuRt" /><figcaption>Photo by <a href="https://unsplash.com/@photohunter?utm_source=medium&amp;utm_medium=referral">Jimmy Chang</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once in my life, me and 4 friends have decided to create a startup and as the product, we were supposed to build an application helping people to rent or sell houses online.</p><blockquote>After starting the project planning and gathering user requirements, we jumped into writting codes. But there is one challenge, a small and with no particular importance; this forced the team to explode and make other member to leave the group. The consequence was terrible, as the project was cancelled immediately. <strong>Can you guess what was this problem?</strong></blockquote><p>It was absolutely the lack of coding style as all members of the group were coming from different area and thus different way of formatting codes, different style of writing functions or methods, etc. This created a very big problem: <em>we were not able to read and understand the code that our colleagues have written.</em> So, it was impossible to integrate or combine our codebase in one project.</p><p>But, when working in the first and second challenge for the Andela Bootcamp, I embraced the use Style Guide and it made me understand the importance of using such tools. Andela introduced me to the use of <strong><em>Javascript Airbnb style guide</em></strong> and <strong><em>Eslint</em></strong>: this changed my life forever!! Let us take a look at this two tools that I would imperatively recommend my any software developer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8RooAXk61tLudcEw" /><figcaption>Photo by <a href="https://unsplash.com/@grohsfabian?utm_source=medium&amp;utm_medium=referral">Fabian Grohs</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’ve been coding for a while, you’ll no doubt have a style that you’ve grown to <em>like</em>. This is what happens when you write certain patterns hundreds or thousands of times, you start to find your way of coding aesthetically pleasing. All of a sudden someone else comes along and starts throwing brackets down in odd places and leaves spaces hanging off the end of lines. There may need to be words. <strong>Breathe deeply</strong>, your placement of brackets or choice of white-space doesn’t make your programs any more correct, it’s <em>personal</em> preference.</p><p>Each programming language has a <em>dominant</em> style, sometimes like in the case of Python an official <a href="https://www.python.org/dev/peps/pep-0008/">style guide</a> is presented as the <em>correct</em> way to author programs. Hold on, did you say <em>4 spaces</em> for indentation?</p><p>Coding in the dominant style of a language will help your program fit into the language’s ecosystem. You’ll also find it easier to contribute to open source projects and have others contribute to your own if things are familiar and agreed upon at the outset. One of the most well known and used standard similar to ours is <a href="https://github.com/airbnb/javascript"><strong>Airbnb JavaScript Style Guide</strong></a>. They have rules for new ES6 features, they also use react hence. Their rules are more strict than ours, it’s a good move for our codebase.</p><p>Airbnb Style Guide format code following a set of rules, among them we can look at some, which I personally used in my Andela challenge:</p><ul><li><strong>Semicolon:</strong> Required</li><li><strong>Trailing Commas:</strong> Required</li><li><strong>Template strings:</strong> Prefer</li><li><strong>Import Extensions:</strong> None</li><li><strong>Space before function parentheses:</strong> None</li><li><strong>Object Curly Spacing:</strong> Yes</li><li><strong>Array Bracket Spacing:</strong> None</li><li><strong>Underscored functions:</strong> None</li><li><strong>Object Destructuring:</strong> Prefer</li><li><strong>Arrow Functions Return Assignment:</strong> No</li><li><strong>Object Property Shorthand:</strong> Prefer.</li></ul><h4>Why should we lint our code?</h4><p>Linting code is already an established part of any (popular) JavaScript project and, in my opinion, and has a lot of benefits such as:</p><ul><li>Readability</li><li>Pre-code review</li><li>Finding (syntax) errors before execution</li></ul><p>As we have the possibility to define a set of styling rules, this increases the readability of our code towards the effort of having our codebase look like it was written by “<a href="http://www.slideshare.net/ThoughtWorks/tech-leadskillsfordevelopers/10-ProgrammingPPeoplePProcessPProgrammingPeopleProcess">one person</a>”. This is important, as it can happen that software engineers move from codebase to codebase within projects meaning a lot of people become involved. A common set of rules makes it easier to really understand what the code is doing.</p><p>Further linting rules help to improve code reviews, as it already acts as a pre-code review, checking against all the basic issues such as syntax errors, incorrect naming, the tab vs. spaces debate, etc. It increases the value of having code reviews, as people are then more willing to check the implementation rather than complain about syntax errors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fd2a5a33fb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A way to understand, live and apply the Andela’s honor code]]></title>
            <link>https://medium.com/@sigmacool/a-way-to-understand-live-and-apply-the-andelas-honor-code-1381f26f05cd?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1381f26f05cd</guid>
            <category><![CDATA[epic]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[kigali-01]]></category>
            <category><![CDATA[honor-code]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Tue, 20 Nov 2018 15:54:45 GMT</pubDate>
            <atom:updated>2019-06-06T13:08:26.101Z</atom:updated>
            <content:encoded><![CDATA[<h3>A way to understand, live and apply Andela’s honor code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RbCxsPWKtBGwj1Kq" /><figcaption>Photo by <a href="https://unsplash.com/@tbelabuseridze?utm_source=medium&amp;utm_medium=referral">Tbel Abuseridze</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>An organization, even if it’s a big company or a SME of 20 people, in a complex world of global competition that we have known for a few years, cannot live without values. These ​​are fundamentals and form the basis of all management. They must be aligned with the vision of the entrepreneur. Values ​​make it possible to clearly construct the behavioral model of the company managers and all employees. They participate in building a corporate culture. These are the basic constituents that go into the foundation of culture and rules of good conduct within the company. As in a recipe, an ingredient is part of a good dish! Missing one or two, the dish loses its flavor and interest! It is the same with the values.</p><blockquote>At Andela, the code of honor is an acronym <strong>EPIC</strong>: Excellence, Passion, Integrity and Collaboration.</blockquote><p><strong>Excellence:</strong> In my opinion, the term can be defined as the character of something or a person corresponding to the ideal representation of its nature or its function. It’s also a person who manifests a very clear superiority in a given field. At Andela, excellence is the character that pushes someone to go beyond what is expected from him, to excel and learn continuously to confirm his experience. In more technical terms, it means forcing yourself to write code or work with tools that follow standards, best practices. To reach this point, you will always have to learn without stopping.</p><p><strong>Passion:</strong> <a href="https://medium.com/@zachang/this-could-have-been-written-as-the-job-of-a-developer-must-be-a-passionate-one-or-some-other-51459cc5f6f2?source=post_info_responses---------0---------------------">the job of a developer must be a passionate one</a>! It’s a craft business, where you rarely do the same thing twice, where you have to innovate every day. The eco-system moves very quickly, existing languages ​​evolve (not very quickly, but still), new languages ​​are emerging (are they adapted to my needs? or not), new libraries are regularly released, today’s revolutionary technologies will be replaced by others even better in 3 or 6 months. Not to mention the good practices that I see evolve and refine constantly. Being a programmer is a “job” and a “passion”. Developers must be aware of it, with the contributions that come with it, but also the obligations.</p><p><strong>Integrity</strong>: This is where Andela puts a lot of emphases, and will not hesitate to punish in a serious way if it is violated. At my point of view, a person who obeys the integrity rule does not accept things that do not fit him for the wrong reasons. And in this case, he sincerely explains things and why he says no. He is careful not to promise something or say yes, just to be nice, to be seen or to avoid conflict. He is not <em>blessed-yes-yes</em>. He does what is right with good motives, not to gain favors or serve his interests. He does what he thinks right, even when others do not see it. And above all else, he treats others as he wishes to be treated himself.</p><p><strong>Collaboration</strong>: When learning to code, collaboration gets applied to a large, effective scale. Learning from each other and from the situation is what the programming learning process can provide learners with. Participation in teams of programmers enables coding experts to become more prepared and even more aware of issues that might appear when mixing a certain piece of code with another one. To develop the collaboration in a team it is necessary to respect each member of the group and to trust each other.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1381f26f05cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous learning, the key to survive and grow up]]></title>
            <link>https://medium.com/@sigmacool/continuous-learning-the-key-to-survive-and-grow-up-616ab30dfa5d?source=rss-f3a00e25b9f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/616ab30dfa5d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[kigali-01]]></category>
            <dc:creator><![CDATA[Mutombo Jean-Vincent]]></dc:creator>
            <pubDate>Mon, 19 Nov 2018 15:19:42 GMT</pubDate>
            <atom:updated>2018-11-28T10:05:40.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J3Oyw-qqo-L8pvK_" /><figcaption>Photo by <a href="https://unsplash.com/@rangel?utm_source=medium&amp;utm_medium=referral">David Rangel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Niels Bohr has said: “An expert is a man who has made all the mistakes which can be made, in a narrow field”. Another way to understand this sentence is that we must learn from our mistakes to grow up and improve our skills. Possibilities belong to those who dream and dare as each path is full of challenges. Without a growth mindset, I will not have benefited from what I know today. In fact, I might have left software engineering. Every year has brought me new challenges. Every year, I learned. I welcomed each New Year of study with enthusiasm. Have I had any empty moments when I felt unable to start again? Absolutely.</p><p>It all started when I received the email that said I was accepted for Andela’s Bootcamp which should take two weeks. My first time to realize that I still have a lot to learn felt when we were given two challenges to achieve and around that, we had to work with tools that I never used before, to know: Git and the Github workflow for the project versioning, Pivotal Tracker for story writing used for Agile model, Continuous Integration tools such as Travis CI, code coverage with Code Climate and Coveralls.</p><p>The work was based on the realization of a web application named ‘send-it’: a courier service that helps users deliver parcels to different destinations. This one is separated into two challenges, on the one hand, we had to create the user interface in HTML, CSS, and JavaScript, as for the second challenge, we had to create an API in NodeJS and ExpressJS which will contain routes to create new parcel delivery order, display all parcel delivery orders made by a specific user, integrate Google Map and many others.</p><p>All this does not seem difficult enough to do, but the pain is the obligation to accomplish these tasks by following the best practices, Git naming convention, writing scripts for test-driven development (TDD) and above all, the use of tools such as Mocha, Babel, Eslint and so on. By adopting this new way of working, I gained in a short time an important knowledge that I will have probably missed if I did not attend the two day’s workshop to prepare the Bootcamp or simply if I had not been accepted for this Bootcamp. Beyond this technical knowledge, I also learned a lot of morality lesson about integrity, excellence and the fruit of passion for software development.</p><p>In conclusion, I would say that curious software developers are often the least stuck in their progress — the most open to change. They certainly need to ask the right questions before changing the way of working if it is presented as better. But if it is a question of improving the production and releasing more time to devote to the interesting problems, they will adopt the approach with a minimum of hesitation. Curiosity breeds creativity, another characteristic desired by the developer. A strong will to establish the cause of a problem and to resolve it helps to motivate oneself to evolve by making tangible progress. It is this type of mindset that stimulates, develops original and relevant thinking, and then induces creative coding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=616ab30dfa5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>