<?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 Azeezat Raheem on Medium]]></title>
        <description><![CDATA[Stories by Azeezat Raheem on Medium]]></description>
        <link>https://medium.com/@azeezatraheem?source=rss-a349767e884------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LMAXZvIXEp0wZ9GtbnhNCw.jpeg</url>
            <title>Stories by Azeezat Raheem on Medium</title>
            <link>https://medium.com/@azeezatraheem?source=rss-a349767e884------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:53:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azeezatraheem/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[IMPLEMENTING AUTHENTICATION REDIRECTS IN NEXT.JS]]></title>
            <link>https://azeezatraheem.medium.com/implementing-authentication-redirects-in-next-js-c15907ec82b7?source=rss-a349767e884------2</link>
            <guid isPermaLink="false">https://medium.com/p/c15907ec82b7</guid>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[login]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[redirect]]></category>
            <dc:creator><![CDATA[Azeezat Raheem]]></dc:creator>
            <pubDate>Tue, 06 Apr 2021 16:24:13 GMT</pubDate>
            <atom:updated>2021-05-05T21:08:26.917Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XjLwKES-iJ31O8wfaGL9gA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mr_williams_photography?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Micah Williams</a> on <a href="https://unsplash.com/s/photos/login?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In the last few months, I have been working on Next.js applications. Although, there are many methods of implementing authentication workflows in next.js, but I didn’t find any tutorial that described implementing client side authentication logic in detail. But, with bits of information I gathered here and there and so many tries, I was able to figure it out. I have written this article to guide anyone who is interested in implementing something like this.</p><h3><strong>Implemetation</strong></h3><p>Below are the steps I took to achieve this using a higher order component, Context API and React hooks.</p><h4><strong>STEP 1: STORE AUTHENTICATION STATE</strong></h4><p>The first step is to use whatever method you are comfortable with to store authenticated user state. In my case, I used the React context API to store my authenticated user state, which I persisted in the local storage. There are many tutorials that detail how to use context API. But here, our focus is to redirect the user to another page if user is not logged in.</p><h4><strong>STEP 2: CREATE A NEW COMPONENT</strong></h4><p>Create a new file called <strong>ProtectedRoute.js</strong> and initialize it with the following lines of code. Notice there are two props — <strong>router and children</strong>. The <strong>router </strong>prop would be passed in from the <strong>_app.js </strong>file that would be created in the <strong>pages </strong>folder. The <strong>children </strong>is one of the commonly used props in react that refers to any child of the parent component. I would discuss this in the later part of this article, but for now, lets focus on creating a new component.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/304c06ef2fdc9c1f363f3fd82100b6c7/href">https://medium.com/media/304c06ef2fdc9c1f363f3fd82100b6c7/href</a></iframe><p>In my case, I had more routes that required the user to be logged in before they can access them than the ones that do not. Owing to this reason, I chose to keep a list of routes that <strong>do not need authentication</strong> which I have stored in a variable named <strong>unprotectedRoutes</strong>. If reverse is the case, you can choose to do the opposite of what I have done here.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/585ebdc31a3f03b163f6de7f934446a2/href">https://medium.com/media/585ebdc31a3f03b163f6de7f934446a2/href</a></iframe><h4><strong>STEP 4: WRITE LOGIC FOR REROUTING UNAUTHENTICATED USER</strong></h4><p>If the user is trying to access a route that needs authentication, the user should be redirected to the login page (or whatever page you deem fit as your project may require).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d12b8d38fe3de171d7314b763c0f48e/href">https://medium.com/media/4d12b8d38fe3de171d7314b763c0f48e/href</a></iframe><p>Notice the <strong>isBrowser </strong>function, it is used to distinguish between when you are on the server environment (NodeJS) and client environment (browser), because <strong>router.push</strong> only works on the browser.</p><h4>STEP 5: CREATE/MODIFY _app.js</h4><p>if you have an _app.js file in your pages folder already, all you need to do it modify appropriately, but if you don’t, create a file called <strong>_app.js</strong> in the pages directory. <strong>Do not attempt to call this file any other name</strong> as it is used by Next.js to initialize pages. Click <a href="https://nextjs.org/docs/advanced-features/custom-app">here</a> to read more. If you are using context API, here is a good place to wrap your context provider.</p><p>Import the<strong> ProtectedRoutes.js </strong>component we created in step 2 into the _app.js file. See output below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bca2f590c3145c90eb4e57787fefd200/href">https://medium.com/media/bca2f590c3145c90eb4e57787fefd200/href</a></iframe><h3>Finally…</h3><p>To ascertain that everything works as expected, visit any route that is not on the <strong>unprotectedRoutes </strong>list and you should be redirected to the login page. Visiting any unprotected route should also direct you to the right pages.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c15907ec82b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[8 ONLINE TOOLS THAT CAN SPEED UP YOUR CSS DELIVERY]]></title>
            <link>https://azeezatraheem.medium.com/8-online-tools-that-can-speed-up-your-css-delivery-e0c1562eda73?source=rss-a349767e884------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0c1562eda73</guid>
            <category><![CDATA[svg]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[css-gradient]]></category>
            <dc:creator><![CDATA[Azeezat Raheem]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 07:01:01 GMT</pubDate>
            <atom:updated>2020-09-15T22:42:41.053Z</atom:updated>
            <content:encoded><![CDATA[<h3>8 online tools that can speed up your css delivery</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pAJ0dPkq_t6q11WLcZ7alg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@picjumbo-com-55570?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">picjumbo.com</a> from <a href="https://www.pexels.com/photo/notebook-beside-the-iphone-on-table-196644/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>It can be very tasking developing UI effects for your website. Especially when you have complex shapes, animations, and numerous images to deal with. Thankfully, some thoughtful people on the internet have built a number of tools that generate CSS codes hence, easing some of these exhausting tasks. As always, I advocate that you take some time to understand the underlying principles behind the CSS attributes used by these tools, as it would help you manipulate the generated codes easily. Here are some tools that can make writing CSS seamless.</p><p><strong>1. CLIP PATH MAKER</strong></p><p><a href="https://bennettfeely.com/clippy/"><strong>Clippy</strong></a><strong> </strong>is an online tool that helps generate CSS clip-paths. Clippy offers a wide range of clip-path shapes you can select from. You can also manipulate selected shapes directly from the clippy website UI. Once you are done, you can copy the codes generated by clippy and paste them in your project. Other alternatives include solutions from <a href="http://www.cssplant.com/clip-path-generator">cssplant</a>, <a href="https://www.uplabs.com/posts/clip-path-generator">uplabs</a> e.t.c.</p><p><strong>2. THEME AND COLOUR SELECTION</strong></p><p>Whenever I run into confusion as to what colour combinations I want to use on an application, I use <a href="https://coolors.co/"><strong>coolors</strong></a>. Coloors offers a wide range of exciting features like colour scheme generation, gradient generator. Another interesting feature on Coolors is the <a href="https://coolors.co/contrast-checker/112a46-acc8e5">contrast checking feature</a>. It tells you the contrast levels between your background and foreground colours. With that, one is able to quickly decide if two colors sit well on each other. <a href="https://coolors.co/">Coloors </a>also offers the <a href="https://coolors.co/image-picker">select colour from image</a> feature where you can get all the colours present in an uploaded image.</p><p><strong>3. IMAGE RESIZERS</strong></p><p>Building responsive websites can be very stressful, especially when you have lots of images to deal with. A standard principle of responsive web design is that you use image resolutions that align with target devices. <a href="https://cloudinary.com/documentation/image_transformations"><strong>Cloudinary</strong></a><strong> </strong>uses one image to generate several other images based on the selected height, width, device resolution and image format. It also allows you upload multiple images and download them when the resize is complete, saving you time and stress. Some alternatives are <a href="https://picresize.com/">picresize</a>, <a href="https://www.canva.com/">canva</a> e.t.c</p><p><strong>4. SVG MAKER</strong></p><p>SVGs are fast making web design appealing. There are a number of ways to use SVGs in your application. If you need to generate SVG backrounds on the fly, <a href="http://www.svgbackgrounds.com/"><strong>svgbackgrounds</strong></a><strong>, </strong><a href="https://svgeneration.netlify.app/">svgeneration</a>, <a href="https://www.heropatterns.com/">heropatterns<strong> </strong></a>offers lots of them. With tools like <a href="https://editor.method.ac/">methoddraw</a>, you can draw anything and convert them to SVGs instantly. <a href="https://svgartista.net/">Svgartista</a> also makes manipulating existing SVGs very easy.</p><p><strong>5. ANIMATION AND TRANSITIONS MAKER</strong></p><p><a href="https://animista.net/"><strong>Animsta </strong></a>has a wide range of free and paid animations and transitions. <a href="https://animista.net/">Animsta </a>auto generates CSS animation key-frames for you based on certain selected criteria. With <a href="https://animista.net/">Animsta</a>, you can create CSS animations of the fly. <a href="http://cssanimate.com/">CSS animate</a> also offers cutomizable CSS animations.</p><p><strong>6. LAYOUT GENERATOR</strong></p><p><a href="http://www.cssplant.com/layout-generator/"><strong>Cssplant </strong></a>Generates layout for you based on CSS techniques like Flexbox, CSS Grids, tables and blocks. There are also a couple of other tools like <a href="https://cssgrid-generator.netlify.app/">gridgenerator</a>, <a href="https://grid.layoutit.com/">layoutit</a>, <a href="https://griddy.io/">griddy</a> which uses CSS Grids only.</p><p><strong>7. GRADIENT GENERATOR</strong></p><p><a href="https://cssgradient.io/"><strong>Cssgradient.io</strong></a> can help you generate any type of gradient. All you need do is position the colors appropriately and review till its perfect. It also has a huge collection of gradients with support for gradient text, linear and radial css gradients. Go ahead and manipulate as you wish.</p><p><strong>8. RESPONSIVENESS CHECK</strong></p><p>If you need to do an overall check of how responsive your web app or website is, <a href="https://responsivedesignchecker.com/"><strong>responsivedesignchecker</strong></a><strong> </strong>is your go to tool. <a href="http://ami.responsivedesign.is/"><strong>AmIResponsive</strong></a><strong> </strong>is the only solution I have seen that supports localhost urls although it supports limited number of devices. Other alternatives are <a href="https://www.responsinator.com/">responsinator</a>, <a href="http://responsivetesttool.com/">responsivetesttool</a> e.t.c.</p><p><strong>Feel free to share other tools you have used in the comments section.</strong></p><p>Stay coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0c1562eda73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Counter Animation in React]]></title>
            <link>https://azeezatraheem.medium.com/implementing-counter-animation-in-react-81f09bff0445?source=rss-a349767e884------2</link>
            <guid isPermaLink="false">https://medium.com/p/81f09bff0445</guid>
            <category><![CDATA[algorithms]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[counter]]></category>
            <dc:creator><![CDATA[Azeezat Raheem]]></dc:creator>
            <pubDate>Mon, 02 Sep 2019 16:26:40 GMT</pubDate>
            <atom:updated>2020-02-04T14:32:09.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Packages can be of great help but overuse should be avoided. For one obvious reason — Maintainability. The more packages you use, the more difficult it is to maintain your code base. A package update could be a huge disaster. Like I always say, If you can write the logic, you do not need a package.</p><p>Some days ago, I needed to create a counter animation effect on a website. The product owner wanted a portion of the page which had statistics to appear as if it is counting the database records in real-time.</p><p>I came across so many packages that could do this. But I just wanted to do it without using a package. After a while, something occurred to me… <strong>a for loop </strong>that<strong> s</strong>tarts counting from 0 and ends at the length of items that is pulled from the API. View the full code <a href="https://gist.github.com/azeezat/5851d5e4fecf93b41026928d27b1e810">here</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Faziziraheem%2Fembed%2Fpreview%2FeYOGByQ%3Fheight%3D600%26slug-hash%3DeYOGByQ%26default-tabs%3Djs%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io&amp;url=https%3A%2F%2Fcodepen.io%2Faziziraheem%2Fpen%2FeYOGByQ&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fm.cdpn.io%2Fscreenshot-coming-soon-small.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ebd778a059e4bacbccc6a2b1a4c478e/href">https://medium.com/media/3ebd778a059e4bacbccc6a2b1a4c478e/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8fd254f660292e39a0b728bec8bf42dd/href">https://medium.com/media/8fd254f660292e39a0b728bec8bf42dd/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81f09bff0445" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using SonarQube and Jenkins for Unit Test Coverage Reporting]]></title>
            <link>https://azeezatraheem.medium.com/using-sonarqube-and-jenkins-for-unit-test-coverage-reporting-64ed4d5271ea?source=rss-a349767e884------2</link>
            <guid isPermaLink="false">https://medium.com/p/64ed4d5271ea</guid>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[sonarqube]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Azeezat Raheem]]></dc:creator>
            <pubDate>Sun, 07 Jul 2019 01:52:15 GMT</pubDate>
            <atom:updated>2020-02-04T14:42:24.575Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r6ZN0qLguJBLXVkXavMsEw.jpeg" /></figure><h3><strong>Using Jenkins and SonarQube for Unit</strong> Test Coverage Reporting</h3><p>Lastweek was a great week for me. I finally got SonarQube to pick up my test coverage report. I would give you a step by step guide to how I achieved this. I do hope you will find this tutorial helpful.</p><p>I am making the assumption that you already use React and Jenkins but, you just want SonarQube to be able to read your test coverage reports. I have also assumed that you have already written your unit tests.</p><h3>Step 1: Configure your Package.json File</h3><p>The first step is to configure your package.json file. Create-React-App already comes with a package.json file and jest as the default testing tool. All you need to do is to configure other parameters for jest such as test coverage report format or coverage path as the case may be. Below is a sample config:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/586b9edc2c7769c0e8ff7d74c4f1b009/href">https://medium.com/media/586b9edc2c7769c0e8ff7d74c4f1b009/href</a></iframe><p>Notice that I have written a script called coverage:prodfor modularity. This helps us to be able to use one command to run our tests in different environments. Notice that it contains the same commands <strong>without </strong>the --watchAll<strong>. </strong>The --watchAll command watches files for changes and reruns all tests when something changes. In production or CI environment this option is not required. You can learn more about the package.json file <a href="https://www.tutorialdocs.com/article/npm-scripts-tutorial.html">here</a></p><h3><strong>Step 2: Running Test and Test Coverage Commands locally</strong></h3><p>In your terminal, type command below to run test:</p><pre>npm test or npm run test</pre><p>After the test is complete, you should see something like the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*urcJbyzQEq2kl9CUIphxFA.png" /></figure><p>Also, type the command below in your terminal to generate coverage report:</p><pre><strong>npm run test --coverage --watchAll</strong></pre><p>you should see a new folder called <strong>coverage</strong> in your project root directory. When you open up the <strong>coverage </strong>folder, you should see something like the below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*fe3DZuq1KAsRDVd7q0ds6A.png" /></figure><p>When you navigate to <strong>lcov-report &gt; index.js, </strong>you should see an html report that looks like the image below. If you have these two, it means we are on the same page. Great! Let’s proceed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zCGH_xK8EQQ5upaEXeKxBg.png" /></figure><h3><strong>Step 3: Configure Package.json for CI environment</strong></h3><p>You’ll need to do a bit of configuration in your <strong>package.json</strong> file. There are many test report formats supported by different CI tools. What I showed above is the html report format. The focus of this tutorial is on React, Jenkins and SonarQube, so I will focus more on the cobertura and the lcov report formats. Sonar cube supports many report formats but because this is a React project, our focus would be on the lcov report format.</p><p>On your local machine if you try to run your test using <strong>npm run test</strong>, you will notice that when all the tests have finished running, the terminal doesn’t exit the process. If you are in a CI environment, the same thing will happen, hence blocking other commands from executing. To solve this problem, you will need to tell your terminal that you are in a CI environment using any of the commands below. <strong>Notice that the commands vary depending on the terminal you are using. </strong>You could test this locally as well and you will see that your tests now exit after running. Cool right?</p><h4>Windows (cmd.exe)</h4><pre>set CI=true&amp;&amp;npm test</pre><pre>set CI=true&amp;&amp;npm run build</pre><p>(Note: the lack of whitespace is intentional.)</p><h4>Windows (Powershell)</h4><pre>($env:CI = &quot;true&quot;) -and (npm test)</pre><pre>($env:CI = &quot;true&quot;) -and (npm run build)</pre><h4>Linux, macOS (Bash)</h4><pre>CI=true npm test</pre><pre>CI=true npm run build</pre><p>To run the test coverage, you will need to run the following commands</p><pre><strong>npm run test --coverage --watchAll</strong></pre><h3>Step 4: Run Tests in jenkins</h3><p>Once you are ready to run my tests and coverage report on the Jenkins CI environment, I will use the following commands (assuming I am using Windows powershell)</p><pre>($env:CI = &quot;true&quot;) -and (npm run coverage:prod -u)</pre><p>After the test run is complete, I should be able to see a folder called <strong>coverage</strong> (or whatever folder name you specified for coverage report path in your package.json) in your Jenkins workspace folder. You will see the test reports generated in different formats inside that folder. The file lcov.info is exactly what you need to be able to communicate with SonarQube.</p><h3><strong>Step 5: Configure SonarQube properties on Jenkins</strong></h3><p>In your SonarQube analysis properties file, include the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/27a9557b3e13720af1edc963a4c2c494/href">https://medium.com/media/27a9557b3e13720af1edc963a4c2c494/href</a></iframe><p>Once setup is complete, you should save your Jenkins config and rerun your build. You should see your coverage reports analysis in SonarQube</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AnFZL9hXQ2bG79yXvFgeXA.png" /><figcaption>Test coverage report from SonarQube</figcaption></figure><h3>Step 6: Configure Cobertura Report on Jenkins</h3><p>In the package.json file above, notice that <strong>cobertura report</strong> format is one of the coverage reporters.This report format can be used to display your test reports on Jenkins if you do not want to use SonarQube. In Jenkins, add a post build action called <strong>publish corbertura coverage report. </strong>Include the path to the <strong>corbertura coverage </strong>file as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*g-LF4Df8Q_ne-_2P-EDevQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*XH1OeRmPUxnGtM6ZeyGoFQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64ed4d5271ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The journey to coding]]></title>
            <link>https://azeezatraheem.medium.com/the-journey-to-coding-bf81a9b34211?source=rss-a349767e884------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf81a9b34211</guid>
            <dc:creator><![CDATA[Azeezat Raheem]]></dc:creator>
            <pubDate>Sat, 11 May 2019 20:27:29 GMT</pubDate>
            <atom:updated>2020-07-31T05:38:19.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDJHtJfwsyOxm6ErS1bhSA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@clemensvanlay?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clemens van Lay</a> on <a href="https://unsplash.com/s/photos/journey?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>I hated Tuesdays four years ago</h3><p>I used to wish the day after Monday could be Wednesday. Tuesday was that day of the week when I faced one of my biggest fears — programming classes. I was in second year and it was my first time of taking a course in programming. Before then, I had never written a line of code. The first few classes I attended sent a scary signal. I knew I had to put in extra work to be able to pull through the course. Many of the concepts seemed very abstract and by the time we got to object oriented programming, inheritance and encapsulation, I was lost already. The more lectures I attended, the more confused I got. In fact, many of my classmates also shared this frustration. We had a meeting and decided we had to look for a collective solution to this problem. We hired a student in year four who took us every Friday and who hinted that the lecturer often repeats exam questions. It got better. At least I could define a variable and assign it then perform simple arithmetic. But because we already had it in our subconscious that programming was hard, many of us didn’t make much progress.</p><p>The exams would require me to write code and I didn’t have a good grasp of it. For me, failure wasn’t an option! I decided I was going to cram since my efforts weren’t yielding any positive results. Before the exams, I got solutions to past questions and crammed all the answers. Yes! I crammed. I crammed all classes, functions, constructors, properties, down to variable names. Eventually, I managed to get a C in this course.</p><p>Some months later, there was a strike action that lasted six months. During this period, I came across an opening for the position of a student research assistant and I applied. Luckily, I was selected. I had the opportunity of working with someone who understood the rudiments of programming. This was what changed the game. I went back to my course textbook (Illustrated C# by Daniel Solis) and read it from cover to cover. I could then relate easily with concepts I found very difficult to understand. Programming is logic. The first step is always brainstorming. You need to think about how you want to solve a problem before writing the code. Deep thinking is a successful ingredient in coding.</p><p>Today, I can write proficiently in four stacks and teach others. It’s been an exciting and challenging journey. There’s no greater feeling than getting to your workstation everyday and knowing that your work contributes to solving a problem in the society.</p><p>This experience has shaped me in many ways. If you’re interested in learning how to code, I have the following tips for you:</p><p>1. Never miss the basics: Always start from scratch if you are just starting. The initial phase is as important as the end.</p><p>2. Get your hands dirty: Tutorials would teach you a great deal. But the real challenge comes when you work on projects. Invent challenges, ask questions, read other people’s code and write algorithms. There are so many ways to write code. You’ll be amazed that people have come up with simpler and faster solutions to the problem you’re trying to solve. Never stop learning!</p><p>3. Pick one language and learn it well. It’s very easy to get overwhelmed by the numerous technology stacks we have today. As a beginner, focus on learning one language at a time. If you understand one programming language in depth, it would be easier to pick up new ones.</p><p>4. Join communities. Communities are supposed to connect you with people with like interests. I got free access to the MSDN and many other resources after attending a Microsoft boot camp. This helped me to build my first mobile app.</p><p>5. Teach others. Teaching is the easiest way to learn. As a principle, once I crack a problem, I tell other people about it. That way, I don’t forget how I solved it and they also know what to do when they encounter the same issue.</p><p>Stay coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf81a9b34211" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>