<?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 Vanessa Ating on Medium]]></title>
        <description><![CDATA[Stories by Vanessa Ating on Medium]]></description>
        <link>https://medium.com/@atingenkay?source=rss-2d51aaaaf5d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uZ9bmGzkqOHsARmDdNk1zg.jpeg</url>
            <title>Stories by Vanessa Ating on Medium</title>
            <link>https://medium.com/@atingenkay?source=rss-2d51aaaaf5d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:42:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@atingenkay/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[8 Job searching tips for Software Engineers]]></title>
            <link>https://medium.com/@atingenkay/8-job-searching-tips-for-software-engineers-86b0b9dea413?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/86b0b9dea413</guid>
            <category><![CDATA[job-hunting-tips]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[podcast]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Tue, 21 Apr 2020 15:32:37 GMT</pubDate>
            <atom:updated>2020-04-21T15:32:37.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xmBRJobCKKSPmzzzUEoleA.jpeg" /><figcaption>Photo by Free To Use Sounds on Unsplash</figcaption></figure><p>Job hunting for Software Engineers can be tedious and sometimes very discouraging and difficult, especially when you’ve just lost a current job or you probably just want a change.</p><p>Technical interviews can be very challenging and stressful especially when you are not just applying to just one company. it can even sometimes get overwhelming and in the process discourage you from ever finding and getting your dream job.</p><p>Sometimes, you prepare and you still never know how hard it would be until you start getting knee-deep into each one of them, and as Software Engineers we go through various types of interviews ranging from behavioral to different types of technical interviews and most times knowing how to code could be the least of our worries, which is why I think knowing how to search and find the right job that ticks all your boxes could go a long way when you actually start interviewing.</p><p>So, I came up with 8 tips that could help improve your job searching process and they are as follows:</p><p>1.<strong> Get your Cv/Résume in order</strong></p><p>2.<strong> Find an area you are passionate about </strong>(eg. Entertainment, Media, Health care, Tourism, Security, Transportation, etc When it comes to cover letter writing this actually helps because you get to tie your passion for what the company does to how exactly you can add value and improve their Product using technology and also it helps with narrowing down your search to companies that fit exactly what you want)</p><p>3. <strong>Be stack specific</strong> (This really helps when you actually start preparing for interviews, so you get to focus on a particular technology/stack eg. React/Postgres, Angular/Mongo, etc hence doing so well during the interview process)</p><p>4.<strong> Find a role that fits</strong> (When you read through the requirements for the job, does it sound like something you want to do? Are you excited about the kind of work you’d get to put out? Is this something that’s in line with your long term career goals? Are you confident enough using the technologies listed in their requirements?)</p><p>5. <strong>Try not to apply directly from job advertising sites </strong>(You always get a better chance when you apply directly from the company’s website, and also you can use the opportunity of going to their website to find out more about them and if they are in line with what you want next for your career)</p><p>6. <strong>Keep track of your job applications</strong> (Calls, Steps, Feedback, etc. it’s important to keep track of it all, so you know what is coming next, and you don’t miss any calls or overbook yourself. You can keep track of every interview cycle by either making use of Google spreadsheet or Airtable)</p><p>7. <strong>Do your research on the interview process</strong> (Researching the interview process simply means checking the duration of the company’s interview process? How many technical stages are involved during the interview process? Does their interview involve solving algorithms online or on a whiteboard or do they give take-home projects? as this would really help you prepare well ahead of time)</p><p>and the last but very important one,</p><p>8. <strong>Rest. Sleep well </strong>(Interviewing can be very draining and you need to have a clear head and mind whenever you go in for a different one. So you need all the rest you can get to continue to stay healthy and sharp)</p><p>If you want to learn more about these 8 tips and also get some more examples on how you should structure things listen to <strong>Episode 11 of My Life As A Software Engineer Podcast</strong> where I elaborate and throw more light on them:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fanchor.fm%2Fmylifeasasoftwareengineer%2Fembed%2Fepisodes%2FEP--11-8-Job-searching-tips-for-Software-Engineers-ecvfvr&amp;display_name=Anchor+FM+Inc.&amp;url=https%3A%2F%2Fanchor.fm%2Fmylifeasasoftwareengineer%2Fepisodes%2FEP--11-8-Job-searching-tips-for-Software-Engineers-ecvfvr&amp;image=https%3A%2F%2Fd3t3ozftmdmh3i.cloudfront.net%2Fproduction%2Fpodcast_uploaded_nologo400%2F2597600%2F2597600-1572750324322-5eec44deb06ce.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=anchor" width="400" height="102" frameborder="0" scrolling="no"><a href="https://medium.com/media/1630d4d13dd6a38a9cc54a008ec0d248/href">https://medium.com/media/1630d4d13dd6a38a9cc54a008ec0d248/href</a></iframe><p>As always, Thank you for reading!</p><p><em>Originally published on </em><a href="https://www.mylifeasasoftwareengineer.com/"><em>https://www.mylifeasasoftwareengineer.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86b0b9dea413" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PreCommit Hooks!]]></title>
            <link>https://medium.com/backticks-tildes/precommit-hooks-e92ca813df8a?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e92ca813df8a</guid>
            <category><![CDATA[git-hooks]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[husky]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Tue, 26 Mar 2019 00:36:25 GMT</pubDate>
            <atom:updated>2021-01-03T05:57:31.044Z</atom:updated>
            <content:encoded><![CDATA[<p>Setup pre-commit hooks for an existing project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNCvaJoz27hcyN3WzHFwNg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Rs5BQj5zbf8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Efe Kurnaz</a> on <a href="https://unsplash.com/search/photos/hooks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A Pre-commit hook is run just before a commit is added to a new revision. They are mainly used to point out issues in code such as a missing semicolon, trailing white spaces, and debug statements. Often a pre-commit hook can be used to run your test before a new commit is added, just in case there is a defined threshold limit for the test, and if the coverage is less than the threshold limit the test would fail — this, in particular, helps keep code coverage high throughout development.</p><p>To set up our Pre-commit hook we would be using <a href="https://github.com/typicode/husky"><strong>Husky</strong></a><strong> </strong>which describes itself as — <em>‘Git hooks made easy’.</em></p><p>Let’s get started by first installing husky</p><pre>npm install husky</pre><pre>or</pre><pre>yarn add husky</pre><p>The hooks can be added into your package.json file and can either be used to run your test or lint your code.</p><p><strong>Linting your code (React + Tslint):</strong></p><p>Using Pre-commit hook to lint your code is quite straightforward, for example when using Typescript in a React project you’d set up rules in your <a href="https://palantir.github.io/tslint/">Tslint</a> for linting your code. To ensure that your code follows the specified rule in your Tslint you can add the following to the scripts section of your package.json</p><pre>&quot;scripts&quot;: {<br>   &quot;lint:ts&quot;: &quot;tslint --project tsconfig.json --config tslint.json&quot;,<br> }</pre><p>Now to ensure that any new revision adheres to the standard you have to add this to your package.json so that it can be referenced by husky</p><pre>&quot;lint-staged&quot;: {<br>    &quot;*.ts&quot;: &quot;yarn lint:ts&quot;,<br>    &quot;*.tsx&quot;: &quot;yarn lint:ts&quot;,<br> }</pre><p>and then calling husky to lint your code before adding a new revision would be like this:</p><pre>&quot;husky&quot;: { <br>   &quot;hooks&quot;: {<br>      &quot;pre-commit&quot;: &quot;lint-staged&quot;<br>   }<br> }</pre><p><strong>Linting your code (Vue + Eslint):</strong></p><p>This is quite similar and straight forward to the above method, especially if you bootstrapped your project with the vue-cli-3 you would already have a lint script in your package.json</p><pre>&quot;scripts&quot;: {<br>   &quot;lint&quot;: &quot;vue-cli-service lint&quot;,<br>}</pre><p>So all that’s left to do, is to go ahead and install husky just like we did earlier and then we can add our husky command to the package.json just like this:</p><pre>&quot;lint-staged&quot;: {<br>   &quot;*.js&quot;: [ &quot;lint&quot; ],<br>    &quot;*.vue&quot;: [ &quot;lint&quot; ]<br>}</pre><p>Husky command — lints file and runs the test afterward:</p><pre>&quot;husky&quot;: { <br>   &quot;hooks&quot;: {<br>      &quot;pre-commit&quot;: &quot;lint-staged &amp;&amp; yarn run test:unit&quot;<br>   }<br> }</pre><p>Screenshot of husky linting and running test before adding a revision if everything is fine — in a Vue project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNTXTixSuQ2g91si9OPxEw.png" /><figcaption>screenshot of Husky running in a Vue project</figcaption></figure><p>From the screenshot above you can see that husky runs the linters against staged files before it goes to add the new a revision.</p><p><strong>Update:</strong></p><p>Based on the responses to this article, if you get this error:</p><pre>sh: lint-staged: command not found</pre><p>all you need to do is install the lint stage package:</p><pre>npm i lint-staged --save-dev or yarn add lint-staged</pre><p><strong>Conclusion:</strong></p><p>This is just a way to make development easier while also making sure that everyone adheres to the project guidelines. I hope this has been able to help you get started with using Git hooks in your projects.</p><p>Thank you for reading. As always feedback, suggestions, etc are welcomed.</p><p><em>For more articles like this, visit:</em><a href="https://www.mylifeasasoftwareengineer.com/"><em> My Life As A Software Engineer Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e92ca813df8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/backticks-tildes/precommit-hooks-e92ca813df8a">PreCommit Hooks!</a> was originally published in <a href="https://medium.com/backticks-tildes">Backticks &amp; Tildes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webpack 4 + React with Typescript]]></title>
            <link>https://medium.com/@atingenkay/webpack-4-react-with-typescript-996eb78ff348?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/996eb78ff348</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[webpack]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 10:01:21 GMT</pubDate>
            <atom:updated>2020-03-27T15:52:50.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4DdvmVCieeBVJE4NUv_wg.png" /><figcaption>Photo Credit — <a href="https://webpack.js.org/">https://webpack.js.org/</a></figcaption></figure><p>Webpack is a static module bundler for Javascript applications. It takes modules(either installed or custom) and generates static assets to represent those modules.</p><p>And we are going to set up our own Webpack configuration to React with Typescript.</p><p>As stated in the documentation getting started is quite easy, as you only need to understand its core concepts — Entry, Output, Loaders, and plugins.</p><p><strong>Entry:</strong> The entry point such as /src/index.js which is the default for Webpack 4 is what Webpack will use to start building out/resolving its dependencies.</p><p><strong>Output:</strong> The<strong> </strong>output property such as<strong> </strong><strong>./</strong>dist<strong> </strong>(default for Webpack 4) tells Webpack where to output the<em> bundles </em>it creates and how to name them.</p><p><strong>Loaders: </strong>Since Webpack only understands native Javascript code, these loaders enable it to process different types of imported files and convert them into valid modules when it encounters a specific type of file. Loaders have 2 properties in the configuration file</p><ul><li>The test property which identifies which file or files should be transformed</li><li>The use property which indicates which loader can be used to do the transforming</li></ul><p><strong>Plugins: </strong>This allows you to extend Webpack capabilities to perform a wider range of tasks like bundle optimization, asset management and injection of environment variables. You can check out some of the plugins provided by Webpack <a href="https://webpack.js.org/plugins/">here</a></p><p><strong>Installing Webpack:</strong></p><p>To get started, initialize your newly created project folder npm init -y</p><p>Install webpack and webpack cli as dev dependencies</p><pre># yarn<br>yarn add webpack webpack-cli -D</pre><pre># npm<br>npm i webpack webpack-cli -D</pre><p><strong>Configuring Webpack:</strong></p><p>Let’s create a Webpack config file webpack.config.js in the root of our project folder and add the following to it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6a9dddae33ea5fe1498c2caf17a7a650/href">https://medium.com/media/6a9dddae33ea5fe1498c2caf17a7a650/href</a></iframe><ul><li>In the above snippet, we specified src/index.tsx as the entry point</li><li>We told Webpack to output the bundle into the dist folder with the name bundle.min.js</li></ul><p><strong>Adding Typescript:</strong></p><p>Install Typescript’s dependencies</p><pre># yarn<br>yarn add typescript awesome-typescript-loader -D</pre><pre># npm<br>npm i typescript awesome-typescript-loader -D</pre><p>We need to add compilation settings for our Typescript so let’s go ahead and create a <a href="https://www.typescriptlang.org/docs/handbook/tsconfig-json.html">tsconfig.j</a>son in the root of our project folder and add the following to it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/111c70b996992b67c9f1e4251bf6dcea/href">https://medium.com/media/111c70b996992b67c9f1e4251bf6dcea/href</a></iframe><p><strong>Add Typescript configuration to Webpack:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3178618c17e6a1cc842a1c28ca7668af/href">https://medium.com/media/3178618c17e6a1cc842a1c28ca7668af/href</a></iframe><p>Here we are telling Webpack to:</p><ul><li>Resolve file extensions with .tsx, .ts and .js</li><li>All files with the extension .tsx or .ts should be processed by awesome-typescript-loader</li></ul><p><strong>Adding React:</strong></p><p>Since we are using Typescript we need to add React and React Dom along with their type declaration</p><pre># yarn<br>yarn add react react-dom @types/react @types/react-dom</pre><pre># npm<br>npm i react react-dom @types/react @types/react-dom</pre><p>Before we go ahead to add our example file let’s modify our package.json to have a start script to run Webpack</p><pre>&quot;scripts&quot;: { <br>  &quot;start&quot;: &quot;webpack --mode development&quot;, <br>  &quot;build&quot;: &quot;webpack --mode production&quot; <br>}</pre><p>You can enable Webpack’s built-in optimization that corresponds to each environment by setting the mode to either development, production or none.</p><p>Note: The default value is<em> production</em></p><p>Before we create our React component let’s create a simple interface file that would be used by this component. In the src folder create a PageInterface.ts file and add the following to it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d810db1b02145ff5fe44f4e69a721c5/href">https://medium.com/media/8d810db1b02145ff5fe44f4e69a721c5/href</a></iframe><p>Now, let’s create a simple React component App.tsx in the src/components folder:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/73efd682bd7040036a3c4e9a1ca93525/href">https://medium.com/media/73efd682bd7040036a3c4e9a1ca93525/href</a></iframe><p>The index.tsx file will now contain:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d29beb62eb84a72dc79f1f31251826cc/href">https://medium.com/media/d29beb62eb84a72dc79f1f31251826cc/href</a></iframe><p><strong>Adding HTML:</strong></p><p>For this, we need to use a Webpack plugin html-webpack-plugin which helps simplifies the creation of HTML files to help serve our Webpack bundles</p><pre># yarn <br>yarn add html-webpack-plugin -D</pre><pre># npm <br>npm i html-webpack-plugin -D</pre><p>Update the Webpack config file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69ae0ffa6da3232a98536d5ab217b737/href">https://medium.com/media/69ae0ffa6da3232a98536d5ab217b737/href</a></iframe><p>Now, let’s create the index.html template in the src folder:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5774344a3ebaafe414b5e8942b8709c9/href">https://medium.com/media/5774344a3ebaafe414b5e8942b8709c9/href</a></iframe><p>Running yarn start or npm start will now create the dist folder with our bundled Javascript files and an HTML file with a script tag inside the body</p><p><strong>Development Server:</strong></p><p>Finally, we are going to set up a development server using the <a href="https://webpack.js.org/configuration/dev-server/">webpack-dev-server</a> which will open up a default browser when we do npm start and also provide us with live reloading on the fly</p><pre># yarn <br>yarn add webpack-dev-server --D</pre><pre># npm <br>npm i webpack-dev-server --D</pre><p>Update our package.json</p><pre>&quot;scripts&quot;: { <br>  &quot;start&quot;: &quot;webpack-dev-server --mode development --open --hot&quot;, <br>  &quot;build&quot;: &quot;webpack --mode production&quot; <br>}</pre><p>Here we are telling Webpack to run on development mode while watching for changes, using the --hot option to enable Webpack’s HMR(Hot Module Replacement) and then --open to open up a default browser.</p><p>Running yarn start or npm start now will open up the default web browser on localhost:8080</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpVLxhSu779D_FTMcvD5qA.png" /></figure><p><strong>Conclusion:</strong></p><p>This is just a basic way of setting up Webpack with React and Typescript a lot can still be done here by adding more loaders and plugins but I hope this has been able to get you started.</p><p>Thank you for reading. As always feedback, suggestions, etc are welcomed.</p><p><em>For more articles like this, visit:</em></p><p><a href="https://www.mylifeasasoftwareengineer.com/">My Life As A Software Engineer Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=996eb78ff348" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lets code the TDD way!]]></title>
            <link>https://medium.com/@atingenkay/lets-code-the-tdd-way-2b3d70ac7cf2?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b3d70ac7cf2</guid>
            <category><![CDATA[chai]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[mocha]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Sun, 16 Sep 2018 17:50:41 GMT</pubDate>
            <atom:updated>2020-03-26T17:57:19.944Z</atom:updated>
            <content:encoded><![CDATA[<p>TDD — Test Driven Development</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q81rloVhN1bBIWBQtm_Wg.png" /></figure><p>Testing is a crucial part of software development. It is very important for finding bugs, verifying the functionality and improving the general stability of any piece of software. Almost all developers test their code in one way or the other. There are basically two ways to test:</p><ul><li>Manually run the program and try out all functionality to see if everything is working as expected.</li><li>Write automated tests that are or will run every time the code changes, (this is probably the best way).</li></ul><p>And because ‘2’ is the best way we will be focusing on that, but first let&#39;s understand what exactly TDD is</p><p><strong>What is Test Driven Development?</strong></p><p>TDD is a software development approach where the test is written out or defined before actual development is done. It actually follows a defined pattern which goes as follows:</p><ul><li>Write some tests</li><li>Run all tests with the expectation that they will all fail</li><li>Write some code</li><li>Run tests</li><li>Refactor code until all the tests pass</li></ul><p>And this method is often referred to as <strong>RED-GREEN-REFACTOR</strong></p><p>There are a few advantages that come with adopting this pattern of software development</p><ul><li>cleaner and more concise code</li><li>A deeper understanding of the functionality of the software</li><li>Good test leads to lesser bugs during the production or deployment of a software</li></ul><p><strong>A practical example of TDD using Javascript</strong></p><p>This practical example will mainly focus on an introduction to mocha, chai and environment setup for writing tests in ES6.</p><p><a href="https://mochajs.org/"><strong>Mocha</strong></a><strong> — </strong>This is a BDD testing framework, that runs both on N<a href="https://nodejs.org/en/">odejs</a> and in the browser. It has so many little pieces to it but there are just a few that are needed for our test.</p><ul><li><em>describe()</em></li></ul><p>Your test suites may consist of many parts and the describe block can be used to distinguish between them in a clear manner. It takes in 2 parameters — the description and the function that will contain your test afterward.</p><pre>describe(&quot;Function A&quot;, () =&gt; {</pre><pre>// Test for function A here</pre><pre>})</pre><pre>describe(&quot;Function B&quot;, () =&gt; {</pre><pre>// Test for function B here</pre><pre>})</pre><ul><li><em>it()</em></li></ul><p>This is where your code for the test will be located</p><pre>describe(&quot;Function A&quot;, () =&gt; {</pre><pre>  it(&quot;should equal 9&quot;, () =&gt; {</pre><pre>     expect(FunctionA(6, 4)).to.be.equal(9)</pre><pre>   })</pre><pre>})</pre><p>and if you are writing an asynchronous test — which means that your testing code may end later without the whole block waiting for it, you can pass a done to the callback function of <em>it()</em></p><pre>describe(&quot;Function A&quot;, () =&gt; {</pre><pre>   it(&quot;should return 2 when we pass 1 and 1&quot;, function(done){</pre><pre>     expect(addTwo(1, 1)).to.be.equal(2)</pre><pre>    done();</pre><pre>   })</pre><pre>})</pre><ul><li><em>hooks</em></li></ul><p>Because of its BDD style, Mocha provides hooks ( before(), after(), beforeEach(), and afterEach()) that can be used to set up preconditions and clean up after your tests.</p><pre>describe(&#39;Function A&#39;, () =&gt; {</pre><pre>before(() =&gt; {</pre><pre>// runs before all tests in this block</pre><pre>})</pre><pre>after(() =&gt; {</pre><pre>// runs after all tests in this block</pre><pre>})</pre><pre>beforeEach(() =&gt; {</pre><pre>// runs before each test in this block</pre><pre>})</pre><pre>afterEach(() =&gt; {</pre><pre>// runs after each test in this block</pre><pre>})</pre><pre>// your test cases</pre><pre>it(&quot;should do something&quot;, () =&gt; {</pre><pre>// test codes here</pre><pre>})</pre><pre>})</pre><p><a href="https://www.chaijs.com/"><strong>Chai</strong></a><strong> — </strong>This<strong> </strong>is a BDD / TDD assertion library for N<a href="http://nodejs.org/">ode</a> and the browser that can be delightfully paired with any javascript testing framework. It majorly provides 3 types of assertions which can all be found here</p><pre><a href="https://www.chaijs.com/guide/styles/">https://www.chaijs.com/guide/styles/</a><br></pre><p><strong>Setup for ES6 Testing:</strong></p><p>We are going to write a function to get the factorial of a number and since we are going by the TDD way we would go ahead and write the test for our function.</p><p>First, we have to install our needed dependencies — Mocha and Chai</p><pre>npm init --yes<br>npm i mocha chai -D</pre><p>Let&#39;s also go ahead and setup babel for converting our code into a compatible version by installing the following</p><pre>npm i babel-register babel-preset-env babel-preset-stage-0 -D</pre><p>Then, create a .babelrc file and add the following</p><pre>{<br>  &quot;presets&quot;: [<br>    &quot;env&quot;,<br>   &quot;stage-0&quot;<br>  ]<br>}</pre><p>In your project folder create a file test.js then import the above-installed dependencies along with the test for our factorial function.</p><pre>//<em>import libraries needed for assertion</em></pre><pre><em>import</em> { assert } <em>from</em> &#39;chai&#39;;<br></pre><pre>//<em>import the main file for test</em></pre><pre><em>import</em> computeFactorial <em>from</em> &#39;../src/main.js&#39;;<br></pre><pre>describe(&quot;factorial&quot;, () =&gt; {</pre><pre>  describe(&quot;handle valid input&quot;, () =&gt; {</pre><pre>     it(&quot;should return 6 as factorial for 3&quot;, () =&gt; {</pre><pre>      assert.equal(computeFactorial(3), 6);</pre><pre>   });</pre><pre>    it(&quot;should return 120 as factorial for 5&quot;, () =&gt; {</pre><pre>      assert.equal(computeFactorial(5), 120);</pre><pre>   });</pre><pre> });</pre><pre>  describe(&quot;handle invalid input&quot;, () =&gt; {</pre><pre>     it(&quot;should return undefined as factorial for -5&quot;, () =&gt; {</pre><pre>      assert.equal(computeFactorial(-5), &#39;undefined&#39;);</pre><pre>    });</pre><pre>      it(&quot;should return undefined as factorial for &#39;demo&#39;&quot;, () =&gt; {</pre><pre>        assert.equal(computeFactorial(&#39;demo&#39;), &#39;undefined&#39;);</pre><pre>    });</pre><pre>  });</pre><pre>});</pre><p>Without adding our factorial function we can go ahead and run this test expecting that it would fail because the factorial function is not present</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSBUk0jDO16sjnV7kR3NVA.png" /></figure><p>Now we can go ahead and add our function</p><pre>const computeFactorial = (value) =&gt; {</pre><pre><em>  if</em> (typeof (value) != &#39;number&#39;) {</pre><pre><em>    return</em> &#39;undefined&#39;;</pre><pre>  } <em>else</em> <em>if</em> (value &lt; 0) {</pre><pre><em>    return</em> &#39;undefined&#39;;</pre><pre>  } <em>else</em> {</pre><pre>     let factorial = 1;</pre><pre><em>      for</em> (let i = value; i &gt;= 1; i--) {</pre><pre>        factorial = factorial * i;</pre><pre>  }</pre><pre><em>    return</em> factorial;</pre><pre>  }</pre><pre>}</pre><pre><em>export</em> <em>default</em> computeFactorial;</pre><p>To run our test lets go ahead and edit the scripts line in our package.json</p><pre>&quot;scripts&quot;: {<br>&quot;test&quot;: &quot;mocha test/*.js --require babel-register --reporter spec -exit&quot;<br>}</pre><p>Then run the test with the command npm test and you’ll get the following result</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gINlQdX1c_bMuH89uRrcxw.png" /></figure><p>I hope you enjoyed reading this article, please reach out to me if you have any feedback or ways I can improve things.</p><p>Thanks for reading.</p><p><em>For more articles like this, visit:</em></p><p><a href="https://www.mylifeasasoftwareengineer.com/">My Life As A Software Engineer Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b3d70ac7cf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving on…]]></title>
            <link>https://medium.com/@atingenkay/moving-on-8813d4f63471?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8813d4f63471</guid>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Mon, 30 Oct 2017 15:23:18 GMT</pubDate>
            <atom:updated>2020-03-26T16:40:43.950Z</atom:updated>
            <content:encoded><![CDATA[<p>Guys, I got in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MMUGog287dmWdnZPw42ezw.jpeg" /><figcaption>photo — unsplash.com</figcaption></figure><p>I’ve been on a high since I got the mail inviting me to the 2nd week of the Andela Bootcamp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*a8NMhGtDnIPLz7Lch9mimw.gif" /><figcaption>Photo — giphy</figcaption></figure><p>Last week was very challenging but it’s a big relief I made it through and I made it in, the amount of work I put in finally paid off.</p><p>While writing my blog post, I have been able to reflect on my experiences from last week to this very moment and I have noticed a lot of changes and progress on my path. I’ve moved from a timely person to a very timely person, I know how important time is now, that if I run into an issue I really cannot fix I reach out immediately rather than stay too long debugging with no fruitful result. I’ve been able to build meaningful and lasting relationships with everybody around me, I’ve been able to learn and apply new skills almost immediately and most importantly I’ve been able to step out of my comfort zone and ask questions whenever the need be. I use to be that child in the class that may know the answer to that question but will never raise a hand to answer, now I look forward to the short skill session we have every morning where we get to input whatever Idea or what exactly we have learned.</p><p>The challenges for this week are looking tougher than the last which was expected but with hard work and team spirit, I’ll scale through. I always and still do have this belief that as long as it’s been done before it’s not impossible, so yes, I will do it. Challenges will come my way, it’s expected but I’ve been able to adapt quickly when it comes to fighting them because now I know they are just checkpoints, hurdles, etc that comes once in a while to check on your progress and possibly test how passionate you are concerning the goal you are trying to achieve.</p><p>In all honesty, I’m thankful I didn’t break down at any point throughout last week, It was difficult at first but I picked up pace in between to meet up with the fast pace the Bootcamp required and although it’s still a bit tough for me I can say I am adapting well which is indeed a good thing.</p><p>I’m here now and the only thing I have to do is work harder and I sure will.</p><p>Thank you for reading.</p><p><a href="https://missating.github.io/">Vanessa (Nkoyo) Ating</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8813d4f63471" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience, as a great teacher]]></title>
            <link>https://medium.com/@atingenkay/experience-as-a-great-teacher-7382328e1c5a?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7382328e1c5a</guid>
            <category><![CDATA[girls-in-tech]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Thu, 26 Oct 2017 15:41:08 GMT</pubDate>
            <atom:updated>2020-03-26T15:34:37.836Z</atom:updated>
            <content:encoded><![CDATA[<p>I learn from experience like almost all the time, leaving my house daily I look forward to experiencing new things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hEDASII5u7vgqJ9NH4mYA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/TamMbr4okv4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Lately, my writing has been about my activities in the Andela Bootcamp and as you know it’s been one of a kind. I’ve been led through different phases of training, ranging from having soft skills as a developer to using the agile methodology in software development and ensuring to follow the git workflow when versioning project. It’s not been an easy ride for me, some concepts were entirely new to me and I got to learn them and apply them almost immediately which is a new method for me as I always tend to take my time to study and get to a certain level before I implement, But then again this method has made me realize that I can do anything I put my mind too.</p><p>I have indeed experienced a lot in these past few days, and as a learner, it’s been amazing to see myself catch on quickly in this fast-paced environment. Some of the things that I’ve experienced in this Bootcamp that was completely new to me are as follows:</p><ul><li>The importance of collaboration: I have been able to understand this concept as an essential part of software development. Often, a times software is not developed by a single person, people come together (Teams) to build things and it’s important you know how to collaborate among-st team members to enable better delivery of the end product.</li><li>When in doubt, ask questions: There is no such thing as a stupid question especially when you are learning.</li><li>Be willing to help others when they are stuck: Lighting another candle doesn’t quench the fire. Teaching also makes you become better, be willing to teach and explain to others when they have blockers.</li><li>Seek feedback, be open-minded, acknowledge feedback</li><li>Be flexible as possible in your learning, always be ready to embrace new concepts as Technology is always evolving, this is a very important part — Growth mindset</li></ul><p>And in conclusion, I’m glad I made it to this Bootcamp. A lot of things I didn’t know or was not entirely aware of, I know them now.</p><p>Thank you for reading.</p><p><a href="https://missating.github.io/">Vanessa (Nkoyo) Ating</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7382328e1c5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Journey to becoming — 2]]></title>
            <link>https://medium.com/@atingenkay/the-journey-to-becoming-2-552738419bd7?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/552738419bd7</guid>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[girls-in-tech]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Wed, 25 Oct 2017 14:42:37 GMT</pubDate>
            <atom:updated>2020-03-26T15:31:27.722Z</atom:updated>
            <content:encoded><![CDATA[<p>You rarely journey alone, right or wrong?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlxBhR9b_AbCLf-dnVi0iQ.jpeg" /><figcaption>photo — unsplash.com</figcaption></figure><p>Have you ever wondered how whenever you decide to travel from one point to another eg Lagos to Port-Harcourt either by road or air you never end up alone on the bus or plane? How, there are always other people who are embarking on this same journey, and how you might never know any of them or even made traveling plans with them yet you are all choosing to travel on that same day to the same location. Weird, right?</p><p>In my previous<a href="https://medium.com/@atingenkay/the-journey-to-becoming-86cd8a49247e"> post</a> which is more or less like a sequel to this one I spoke about the path am currently journeying on and the things I expect to get out of it, but here I’m going to talk about other people who are choosing to embark on this journey with me.</p><p>It’s day 3 of the Andela Bootcamp, challenges are still ongoing, we all are still waxing strong, learning and implementing while also bonding and building relationships amongst ourselves. In the spirit of relationship building, let me tell you about some of the interesting and like-minded people I’ve met on the journey so far.</p><ul><li><strong>Jogbojogbo, </strong>yes that’s the name of the first person I had a conversation with. He is a good listener who thinks his name is a fun fact about himself but I think it might be because it’s probably quite rare finding anyone with that name. He is a writer, whose stories so far I’ve come to enjoy. I like his inquisitive nature, he is not shy to ask for help from other people when needed. He struck me as an observer who is completely passionate about learning.</li><li><strong>Seun Daramola,</strong> I’m now certain that in every gathering I find myself there’s always going to be a Seun and they always turn out to be amazing. Seun is one of those reserved kinds of people, they don’t immediately break out of their comfort zone to relate with others but talking with him made me realize that this Bootcamp has made him a better person when it comes to relating with others. He enjoys football, you don’t need to guess because his OOP challenge was based on a football management system which I thought was a really good idea. We bantered a lot yesterday since we ended up taking the same route home and it was great bonding over things besides coding like how busy life in Lagos is compared to Abuja where he came from, for this Bootcamp.</li><li><strong>Micheal Ummah, “</strong>Abuja big boy<strong>” — </strong>That was my first thought when I saw him on the day of the interview, that was before the Bootcamp. We are actually from the same state. He is a free soul, completely down to earth and quite funny. He is passionate about Tech and he is concerned with doing more for the Tech Ecosystem. I hope his dreams and plans do come true because Africa does need people like him.</li></ul><p>I enjoy being in the midst of all the amazing people that I’ve met so far on this journey, everybody is completely different from the other with so much to offer. I hope to bond more and continue collaborating on here and beyond with people of the same like mind.</p><p>Thank you for reading.</p><p><a href="https://missating.github.io/">Vanessa (Nkoyo) Ating</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=552738419bd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Journey to becoming…]]></title>
            <link>https://medium.com/@atingenkay/the-journey-to-becoming-86cd8a49247e?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/86cd8a49247e</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[andela]]></category>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[journey]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Tue, 24 Oct 2017 15:37:00 GMT</pubDate>
            <atom:updated>2020-03-26T15:28:34.775Z</atom:updated>
            <content:encoded><![CDATA[<p>The stages we pass through to become…are filled with great expectations</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vA1izTahD1j5R7nlg3zzDA.jpeg" /><figcaption>Photo by Tegan Mierle</figcaption></figure><p>Life itself is a journey, a journey that has its fair share of expectations. Today you are a baby with everybody waiting on you and tomorrow it’s expected that you become an adult and begin to wait on yourself and even on others that will come after you.</p><p>Growing up to become what you expect might either break you or make you. Your expectations might not turn out the way you want them to, because having expectations on the journey to becoming is not as easy as one would think. On my quest to becoming a better developer I’ve lost sleep, I’ve cut down on a lot of social activities and I’m moving from a not so timely person to a timely person with the expectation that in the end, I do become better, but learning exactly has no end except you <em>“the become” </em>chooses to stop evolving.</p><p>On this particular journey of mine, I’m currently on the semi-phase of training to become a world-class developer through the Andela Bootcamp. Its day 2 and from everything that this Bootcamp training entails I expect to become not just a better developer, but to be honest as a person in all aspects of life, to communicate my questions and ideas effectively and learn to help other people like me with their challenges through this journey, so our expectations to all become world-class someday would not break us but rather make us the best versions of ourselves.</p><p>And as always, Thank you for reading.</p><p><a href="https://missating.github.io/">Vanessa (Nkoyo) Ating</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86cd8a49247e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges will come]]></title>
            <link>https://medium.com/@atingenkay/challenges-will-come-556bd590eea2?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/556bd590eea2</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[andela-bootcamp-nigeria]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[girlcode]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 15:13:32 GMT</pubDate>
            <atom:updated>2020-03-26T15:26:19.552Z</atom:updated>
            <content:encoded><![CDATA[<p>If am wrong, correct me, but I do not think that anything great ever comes without equally great challenges, struggles, and setbacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6tNwEKyFqvPGDV_wTMToQ.jpeg" /><figcaption>Photo by Igor Ovsyannykov (unsplash.com)</figcaption></figure><p>I think that for every rung on the ladder to greatness, there are unique challenges that everyone must overcome. These challenges should however never be a deterrent, they should rather inspire you to be successful. By definition, A challenge is a confrontation; a dare. A bid to overcome something, or my personal favorite -an attempt to take possession; a tackle. This just shows that challenges will always come at some point in life when you are setting out to do something worthy and because it is, you should accept the dare and tackle it, to take possession. It does not matter if you fail a couple of times because:</p><p>So, I recently got accepted into the very challenging and rigorous Andela Bootcamp on my journey to becoming a world-class developer. This is the very first day of the Bootcamp but the heat has been on right from the pre Bootcamp week exercises (challenges). The Bootcamp is everything I expect it to be and even more, but as always we must strive on. My most recent challenging experience was preparing for the ongoing Bootcamp, the exercises we were to complete before today. In all honestly, the instructions were quite straight forward because most of the tasks involved setting up the development environment for the upcoming week’s challenges.</p><p>On rounding up with the setup, while using git to clone and push the starter code for the Bootcamp project I got lost amid git workflow. I’m somewhat familiar with some of the git commands but the concept of branching was fairly new to me as I had never really incorporated it into any of my mini-projects. So, I quickly read up on it and started with the required task, at some point everything with the branching seemed to be going on fine until I had to host that branch on the gh-pages to show my work. I had no idea what command I used or what exactly I did but I lost everything, like everything I had spent the last 3 days working on and the green bars on my Github just went blank. I quickly ran to my local directory to check and nothing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*qh3AYEH8FaoiYXc-4WEFug.gif" /><figcaption>Me, Literally</figcaption></figure><p>I was exasperated, frustrated and so close to calling it quits but I forged on nonetheless, and like every other challenge that had come before now, and that will still come, I tackled and will tackle them all. Long story short, I completed 3 days worth of work in one night because well, I’m not going to give up.</p><p>Challenges will come my way, but the part ahead is too great <strong>not</strong> to overcome and take possession of beautiful results to be born.</p><p>Thank you for reading.</p><p><a href="https://missating.github.io/">Vanessa (Nkoyo) Ating</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=556bd590eea2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Version Control “Gist”]]></title>
            <link>https://medium.com/@atingenkay/the-version-control-gist-ffc1bb1167f4?source=rss-2d51aaaaf5d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffc1bb1167f4</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[version-control]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Vanessa Ating]]></dc:creator>
            <pubDate>Sun, 22 Oct 2017 06:59:16 GMT</pubDate>
            <atom:updated>2020-03-26T15:17:46.655Z</atom:updated>
            <content:encoded><![CDATA[<p>What is version control and how does it come into play?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3BZYZyK4cVHJanh-pHnZRg.jpeg" /><figcaption>Photo by Pawel Kadysz (unsplash.com)</figcaption></figure><p>Hey guys, So I finally made time to read a little and do some research and I picked the version control topic because I’ve never really gone deep to know what version control is, and how it works. I’m one of those people that just transitioned into using git (<a href="https://github.com/">Github</a>) but finally, I’ve caught up on the whole “gist” and am here to share what I learned.</p><p><strong>Getting Started:</strong></p><ul><li><strong>What is version control?</strong></li></ul><p>Version control is the management of changes to a document or set of documents over time. It helps you recall specific changes in specific later versions of your project and it does this by keeping track of every modification to the project in a special kind of database. Version Control System is a software<strong> </strong>that allows you to manage the revision of the same file or set of files by helping you keep track of changes you make in your code or design over time. As you edit your code, it takes snapshots of your file and saves them permanently so you can recall your changes later if you need them.</p><ul><li><strong>Where can I use version control?</strong></li></ul><p>Version Control can be used for every file on your computer. As a designer it can be used on your wire-frames or illustrations, as a developer, it can be used for changes in your project. It keeps track of every addition, modification, and deletion on all these files while also allowing you to revert these files to a previous date (if you need to) or compare changes over time. In a case where you lose your files, you can also recover them using version control.</p><ul><li><strong>What are the benefits of using version control?</strong></li></ul><p>Version control gives a lot of benefits, like — history on your project, saving your changes when you edit your code to help you recall why for later reference, it helps create different versions of your code to enable you to test out new features without tampering with your codebase, it saves all your code revisions to a database online, popularly known as a repository, and it supports collaboration — where other members of your team can be 10 miles away but still add to or make reviews concerning a project.</p><ul><li><strong>Types of version control?</strong></li></ul><p>There are two types of version control:</p><ol><li><strong>Distributed version control:</strong> Here every clone of the project is truly a full back up of the repository (project). During outages or while offline, developers can still consult the full project history, and should in case something happens to the server the project won’t be lost. eg of distributed version control — Git, Mercurial, Darcs, etc</li><li><strong>Centralized version control:</strong> The centralized is more or less like the opposite of the distributed. It has a single centralized repository, for eg If Jane is working on a project with John and she commits a file it goes directly from her working local directory to the central repository, the same thing happens with John. Here, both of their work (ie the project) is saved on the central server which is not entirely a good thing because if the server goes down both Jane and John won’t be able to collaborate at that time. And if at any point the storage system of the central database becomes corrupted and no proper backup of the project was kept you tend to lose everything. eg of centralized version control — CVS, Subversion, Perforce, etc.</li></ol><ul><li><strong>What is Github?</strong></li></ul><p>Github, as the name implies, is a hub where people (not just developers) store their projects and network with like-minded people. It uses Git (distributed VCS)- which is like the preferred VCS for most developers. Github allows you to host your code on a platform that enables you to work and collaborate from anywhere with others on a project.</p><p>Here is an interesting Twitter Poll that has Github ranking as the top open-source platform in use with 81% upvote</p><p><strong>The End :</strong></p><p>I hope you learned a thing or two from here. I did just by researching and writing this down.</p><p>As always, Thanks for reading.</p><p><em>For more articles like this, visit:</em></p><p><a href="https://www.mylifeasasoftwareengineer.com/">My Life As A Software Engineer Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffc1bb1167f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>