<?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 Temi Olukoko on Medium]]></title>
        <description><![CDATA[Stories by Temi Olukoko on Medium]]></description>
        <link>https://medium.com/@temiolukoko?source=rss-8d863a33acca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f9PJjynhH2m0p442WkR1bg.png</url>
            <title>Stories by Temi Olukoko on Medium</title>
            <link>https://medium.com/@temiolukoko?source=rss-8d863a33acca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:11:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@temiolukoko/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[How I Passed the AWS Cloud Practitioner Exam in 3 Months]]></title>
            <link>https://temiolukoko.medium.com/how-i-passed-the-aws-cloud-practitioner-exam-in-3-months-5de6030ec54d?source=rss-8d863a33acca------2</link>
            <guid isPermaLink="false">https://medium.com/p/5de6030ec54d</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-cloud-practitioner]]></category>
            <dc:creator><![CDATA[Temi Olukoko]]></dc:creator>
            <pubDate>Thu, 26 May 2022 17:20:24 GMT</pubDate>
            <atom:updated>2022-05-26T17:26:41.806Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*bLHR9heHzhEY3u-qc75RHA.jpeg" /></figure><p>I passed the AWS Cloud Practitioner (CP) exam in 3 months without any formal knowledge of the cloud. To provide some context to my technical background and abilities, I currently work as a DevOps Engineer, although previously worked as a software engineer for 2 years. During my time as a software engineer, I was involved in a project that used AWS extensively. With this being my first time using that particular ecosystem, it made sense to use the opportunity to gain the AWS CP certificate.</p><h4><strong>Tips toward exam preparation</strong></h4><p>How you prepare for any exam is completely up to you, and there is no right way to do it. Although generally for most people, studying for exams on complex technical subjects doesn’t come easy, therefore I’ve shared some of the things that helped me get to a position to pass the exam</p><ol><li><strong>Book the exam early. </strong>The first thing I would advise you to do is book the exam before you start studying so you have a deadline and a goal to work towards. After you book the exam, you can only reschedule twice. If you’re looking to reschedule for a third time around without getting charged, you’ll have to cancel and book a new appointment.</li><li><strong>Set up an AWS account and get hands on experience with AWS </strong>to understand how the services work. It’s very easy to follow tutorials blindly and not retain much so if you can work on a mini project whilst preparing for the exam, you’ll get a much better understanding of each service. Tip: AWS offers a free tier account that gives you the ability to explore and try out AWS services free of charge up to specified limits for each service.</li><li><strong>Follow a course </strong>to help you structure and stay on track with your learning. Learning a new technology can be overwhelming so following a course will provide you with a structured plan to follow.</li><li><strong>Shut down services you’re no longer using.</strong> After you configure a service and no longer need it shut it down! Tip: Use AWS Budgets (a service that monitors your AWS spend) after you set up a service, to set personalised budgets and obtain alerts when you’re close to going over your budget. Although you can use the AWS free trial, if you leave services running, it’s easy to incur unwanted costs.</li><li><strong>Do practice questions and papers. </strong>AWS has an official course you can follow that includes practice questions after every unit. It’s a good idea to do the questions as you’ll find out what information you’ve retained and be able to identify any gaps in your knowledge. There are also practice exam papers you can do (linked below) to get used to the official exam layout and question style. The practice exams have a very similar format to the real AWS CP exam. My advice is to do practice papers before you take the exam and aim to get at least 75% before sitting the real thing. Whilst doing practice papers, pay attention to the questions you consistently trip-up on and go back to study that content until you’ve understood what a certain service is responsible for. Make sure you also review answers you get right to gain a deeper understanding of what specific services do.</li></ol><h4>Resources</h4><p>There are a lot of resources you can use to become familiar with AWS, below is a list of resources that I’ve personally found useful when studying for the AWS CP exam. I’ve split the resources list into courses, blogs, AWS Whitepapers and practice papers.</p><p><strong>Courses<br></strong>AWS Cloud Practitioner Essentials Course: <a href="https://www.aws.training/">https://www.aws.training/</a></p><p>AWS Certified Cloud Practitioner Training 2020: <a href="https://www.youtube.com/watch?v=3hLmDS179YE">https://www.youtube.com/watch?v=3hLmDS179YE</a></p><p><strong>Blogs &amp; Whitepapers<br></strong>How I passed my AWS CCP Exam by <a href="https://twitter.com/paulienuh">Pauline Narvas</a>: <a href="https://pawlean.com/2019/12/07/how-i-passed-my-aws-ccp-exam">https://pawlean.com/2019/12/07/how-i-passed-my-aws-ccp-exam</a></p><p><strong>Practice Papers<br></strong>AWS Certified Cloud Practitioner: 6 Full Practice Exams 2022: <a href="https://www.udemy.com/course/aws-certified-cloud-practitioner-practice-test/">https://www.udemy.com/course/aws-certified-cloud-practitioner-practice-test/</a></p><p>I wanted to keep this blog short, sweet and to the point so if you have any questions, don’t hesitate to reach out to me on Twitter or Instagram. Good luck with your exam!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5de6030ec54d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[100 Days Of Code: Challenge Accepted And Completed!]]></title>
            <link>https://temiolukoko.medium.com/100-days-of-code-challenge-accepted-and-completed-3114a1d56614?source=rss-8d863a33acca------2</link>
            <guid isPermaLink="false">https://medium.com/p/3114a1d56614</guid>
            <category><![CDATA[100daysofcode]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[100daychallenge]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Temi Olukoko]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 19:00:39 GMT</pubDate>
            <atom:updated>2020-07-23T19:08:34.991Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9R6yjojj8zGjVPJSafLGoQ.png" /></figure><p>I completed the 100 Days of Code Challenge, where I coded for (almost) 100 days in a row. Prior to this, I‘d tried learning how to code several times but wasn’t consistent so I would often find myself re-learning concepts like variables, loops and functions. I am currently a Software Developer on a technology graduate scheme where I rotate across 3 different sectors in technology and spend 8 months in each team. I knew I was moving into the development team early on and wanted to prepare for the role, so after coming across the 100 days of code challenge on my twitter timeline, I decided to give it a go!</p><p>You can find my 100 days of code twitter thread <a href="https://twitter.com/TemiOlukoko/status/1241035251507433472">here</a></p><h3><strong>Non-technical Things I Learnt</strong></h3><p>Before I jump into the technical things I learnt, these are some of the non-technical things I learnt along the way:</p><ol><li><strong>Be aware of your learning style.</strong> Having spent nearly all of my years in education I’m very aware of my learning style and I’ve discovered that I retain information best through visual learning, i.e. video tutorials and lectures. I structured my day-to-day learning around the <a href="https://www.udemy.com/">Udemy courses</a> I had bought. Besides Udemy, there are other websites that have great courses/paths to follow such as; YouTube, Udacity, online Harvard courses, freecodecamp and ww3schools. There were points when certain topics weren’t clear so I occasionally watched YouTube tutorials or read blogs to get different perspectives. Knowing your learning style before committing to this challenge is important as you’re more likely to stick to it if you’re working in a way that suits you best!</li><li><strong>Prioritise time.</strong> Setting aside a realistic amount of hour(s) every day at the same time of the day helped me stay consistent. For me the best time to code was straight after work and due to current circumstances (COVID-19) I could do this quite easily. Once I got used to coding at a specific time each day, I rarely missed any days as it became part of my routine. Being consistent and persistent is the key to progressing during this challenge!</li><li><strong>Structure your learning.</strong> Make sure you have a plan before you sit down every morning/evening and start to code. This helped me as it gave me a set of micro-goals to work towards, which made me more determined to get it all done. The key is making sure the goals are achievable so that you aren’t derailed or tempted to give up.</li><li><strong>Make notes.</strong> Taking notes as you go makes it easier for you to retain information as you’re putting the information you’ve learnt into your own words so you’re more likely to understand and remember that information. This has been extremely useful to me as I could quickly recap certain concepts without wasting time looking for tutorials.</li><li><strong>Join a supportive platform.</strong> I discovered the challenge from Twitter, so it didn’t take long for me to find supportive groups on there, and I later made a developer instagram to showcase certain projects I was working on, which you can find <a href="https://www.instagram.com/temilola.dev/">here.</a> I also joined a few developer slack groups which meant I could easily ask for help or advice when I didn’t feel like spending hours on <a href="https://stackoverflow.com/">stackoverflow</a>! Through these platforms I also discovered certain groups and organisations that put on regular events (albeit remote due to COVID-19) which meant I could network with like-minded individuals (list of meet-ups I attended below).</li><li><strong>Take breaks!</strong> I’m aware that this statement is a bit controversial given the rules of the challenge state you need to code every day but many people may be balancing full time jobs, families or hobbies — so it might not be possible for some to code every single day. In my opinion the main reason you should participate in this challenge is to incorporate coding into your daily routine and make it a long lasting habit. Coding every other day consistently is better than doing it every once in a while and never making any progress, so don’t be too strict with yourself!</li><li><strong>Be patient.</strong> Learning to code can be hard and doesn’t come easy to everybody (I know for me it doesn’t) so be kind to yourself if certain concepts aren’t clicking. Make sure to take time to appreciate how much you’ve learnt every so often. I personally felt a bit of joy every time I understood a coding meme, technical conversations between developers on my twitter timeline or when I used technical language without even thinking about it.</li></ol><h3>Technical Things I Learnt</h3><p>Prior to starting the challenge I had a very basic understanding of python and MATLAB as I used these languages throughout my undergraduate and postgraduate degrees. Throughout this challenge, I gained the the following technical knowledge:</p><ul><li><strong>HTML </strong>— HTML basics; lists, Divs and Spans, Attributes, Tables and Forms.</li><li><strong>CSS </strong>— CSS basics; Stylesheets, Selectors, Specificity and the Cascade and The Box Model.</li><li><strong>JavaScript </strong>— JavaScript basics, DOM Manipulation, jQuery &amp; Node.js</li><li><strong>Frameworks </strong>— Bootstrap 3, React Native, Express and Semantic UI</li><li><strong>Backend </strong>— The Command line, API’s &amp; RESTful API’s, MongoDB &amp; Mongoose, Authentication and Authorization.</li><li><strong>Git &amp; GitHub </strong>— I have learnt how to create my own repositories, set up my own projects and deploy these projects to GitHub.</li><li><strong>Postman </strong>— I have become familiar with using Postman to test and debug HTTP APIs.</li></ul><h3>What I Created</h3><p><strong>React Native App</strong> — throughout May I participated in a remote month-long Code First Girls Hackathon and in a team of 5 created a prototype app. The prototype updates a designated emergency contact with the developments of a patient in quarantine and was developed using only frontend technologies. You can find out more about the process <a href="https://medium.com/codingblackfemales/how-i-built-a-react-native-app-for-a-hackathon-in-response-to-the-covid-19-pandemic-as-a-2c3f7ff306f3">here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*7EUsVP0ubvIy4L4xddvhjQ.gif" /><figcaption>Short demo of the prototype shown on an Android emulator</figcaption></figure><p><strong>Static webpage</strong> — Natural hair care landing page created in Bootstrap 3 using HTML, CSS and JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8jWefFoFMOVWmHghIzpj4g.gif" /><figcaption>Static responsive landing webpage</figcaption></figure><p><strong>Colour game project</strong> — RGB colour guessing game, which is useful for practising RGB colours. This was made using HTML, CSS &amp; JavaScript in Bootstrap 3!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dpeJ87-UaioLQVV8CS5-Dw.gif" /><figcaption>RGB colour guessing game demo</figcaption></figure><p><strong>RESTful API blog</strong> — Blog application that lists books written by black authors. The application was developed using Node JS, HTML, CSS in the Semantic UI framework. The user has the option to add new posts, edit existing posts or delete posts entirely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dKss1wnTjl4GHaxHpRhhyw.gif" /><figcaption>Blog application built using REST APIs</figcaption></figure><p><strong>Yelp Clone </strong>— Yelp clone that allows users to review Black owned restaurants in the UK. The user has the option to sign up, create an account/user profile and add their reviews. As seen in the demo, the user can add the location of the restaurant and this featured was enabled by using the Google Maps API. This full-stack application built using Node.js, Express, MongoDB, Google Map APIs, HTML, CSS &amp; JavaScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4a_pC_mLEo8WW349sLsjlg.gif" /><figcaption>Yelp Clone demo</figcaption></figure><h3>Virtual Events &amp; Meet-ups</h3><p><strong>Black women in tech event</strong> — (I actually spoke at this event!)</p><p><strong>A spotlight on Data Science, DevOps, Product Management and UX/UI Design</strong></p><p><strong>Women-in-tech event</strong>— (I spoke at one of these events too!)</p><p><strong>Get into web development</strong></p><p><strong>Remote Developer Conference</strong></p><p><strong>Tech-ish Live Event</strong> (remote)</p><p><strong>Women in IT event</strong></p><p><strong>Rise of Black Communities in Tech</strong></p><p><strong>Remote month-long Hackathon</strong> (my team won 3rd place! Read my blog post <a href="https://medium.com/codingblackfemales/how-i-built-a-react-native-app-for-a-hackathon-in-response-to-the-covid-19-pandemic-as-a-2c3f7ff306f3">here </a>)</p><h3>Favourite resources</h3><p><a href="https://www.youtube.com/channel/UCLBhrKXc9CQczo1vBA6w_mA/videos">Coding with Curry (YouTube)</a></p><p><a href="https://www.youtube.com/c/TheNetNinja/videos">The Net Ninja (YouTube)</a></p><p><a href="https://www.youtube.com/c/programmingwithmosh/videos">Programming with Mosh (YouTube)</a></p><p><a href="https://www.udemy.com/course/the-web-developer-bootcamp/">Web developer bootcamp course by Colt Steele (Udemy)</a></p><p><a href="https://www.udemy.com/course/javascript-the-basics-for-beginners/">JavaScript Beginner Bootcamp by Rob Merrill (Udemy)</a></p><p><a href="https://www.youtube.com/c/TraversyMedia/videos">Traversy Media(YouTube)</a></p><p><a href="https://www.youtube.com/c/funfunfunction/videos">Fun Fun Functions (YouTube)</a></p><p><a href="https://www.freecodecamp.org/">FreeCodeCamp (website)</a></p><p>Thank you for reading!</p><p>To see more of my progress, <strong>follow me</strong> on:<br><strong>Twitter: temiolukoko<br>Instagram: temilola.dev</strong><br>&amp; <strong>subscribe to my YouTube channel: Temi Olukoko</strong>, where I discuss all things tech, careers and adulthood!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3114a1d56614" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I built a React Native App for a hackathon in response to the COVID-19 pandemic as a…]]></title>
            <link>https://medium.com/codingblackfemales/how-i-built-a-react-native-app-for-a-hackathon-in-response-to-the-covid-19-pandemic-as-a-2c3f7ff306f3?source=rss-8d863a33acca------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c3f7ff306f3</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Temi Olukoko]]></dc:creator>
            <pubDate>Wed, 13 May 2020 18:26:31 GMT</pubDate>
            <atom:updated>2020-05-15T07:11:53.966Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I built a React Native App for a hackathon in response to the COVID-19 pandemic as a JavaScript beginner</h3><h4>I entered a month-long remote hackathon in a team of 5 and together we created a prototype mobile app!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ysZBDw0u_KG_1NQdluAIjA.png" /></figure><h3><strong>A quick overview of my coding journey/background</strong></h3><h4>No computer science degree ? — No problem!</h4><p>Before I jump into the fun stuff, i’m going to give a swift introduction and overview into my tech background. First of all I’d like to address that <strong>I don’t have a computer science/IT/coding degree!</strong> I obtained an undergraduate degree in geology and physics followed by a postgraduate degree in geophysics. I was first introduced to python in my second year of my undergraduate studies, where my lecturer more or less threw a coding manual at the class and told us that our first assignment was due in four weeks! At the time, I never understood python and from that first encounter I was reluctant to dive any further into coding all together.</p><p>The summer before my postgrad degree started, I occasionally practiced coding in MATLAB in preparation for a computational module I’d be taking. I discovered I enjoyed creating programs that allowed me to visualise data. This is where my interest in tech first stemmed from and throughout the duration of my masters, I applied for different technology graduate schemes. Fast forward to almost a year later and I’m finishing up my first rotation in the Network Design team at one of the biggest telecom companies in the UK!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*80fXIRpQsmjemtXvPKTPbg.png" /></figure><h3><strong>The reason behind entering the hackathon</strong></h3><p>As a result of the COVID-19 outbreak and global pandemic, I’ve been working from home and have found that I’ve had more free time outside of my 9–5 job. At the time <strong>I had recently finished a JavaScript </strong><a href="https://www.udemy.com/"><strong>Udemy</strong></a><strong> course</strong> and wanted to use the time effectively so I signed up for the Code First Girls — Hack From Home month-long remote hackathon. The <strong><em>aim</em></strong> <strong><em>of the hackathon </em></strong>was to <strong><em>create a tool </em></strong>in teams that assists people in their new daily routines that have developed due to the outbreak.</p><p>I felt slightly apprehensive before starting the hackathon and did not think I’d see it through as I had the notion that I didn’t have enough coding experience and anticipated everyone else involved being more skilled than I was. But after signing up I quickly found myself in a team with 5 really friendly girls, we had some brief introductions and assigned ourselves roles fairly quickly.</p><p>Within this project I took on the role as one of the Lead React Native programmers as being new to JavaScript, I wanted to take on a role that would place me outside of my comfort zone in challenging ways! Therefore <strong>my main focus in this blog post will be on the development (coding) side of this project</strong> and less so on the UX/UI design!</p><h3><strong>How we did it</strong></h3><h4><strong>Step 1 — Understanding the problem and identifying the solution</strong></h4><blockquote><strong>Tip: You don’t need to be a coding expert to build an app — you just need patience and resilience!</strong></blockquote><p>Whilst researching potential avenues to pursue stemming from the aim of the hackathon, we found that there was a lack of communication between family/emergency contacts of patients and healthcare workers. Therefore, the product manager of the team outlined <strong>the solution</strong> which was to <strong><em>create an app that updates the designated emergency contact with the developments of a patient in quarantine. </em></strong>We decided that the prototype would be made from the emergency contacts perspective and would be developed using only front-end technologies due to the short time frames. Additionally, due to security/privacy guidelines and not being affiliated with the NHS, we weren’t able to use any data from their existing databases.</p><p>Having only recently finished an introduction to JavaScript course on <a href="https://www.udemy.com/">Udemy</a>, I was filled with worry and not sure if I was capable of coding an app from scratch. I assumed that to develop an app, you had to be a coding genius. Despite my apprehensions I carried on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*ueKfDid3pEaKrFZ4GmeNvQ.png" /></figure><h4><strong>Step 2 -Timeline production</strong></h4><p>Secondly, we created an approximate timeline consisting of ‘micro-goals’ leading up to the main goal of completing the prototype by the established deadline in a month’s time. Over the duration of the development process, we had to make adjustments according to our position along the project lifespan as there were times we were behind and ahead of schedule, as well as times when we decided specific tasks were no longer a top priority.</p><h4><strong>Step 3 — Created a product canvas</strong></h4><p>We created a product canvas to identify; alternative products/services on the market, competitors and value propositions, as well as develop our approach to the problem and the solution. This allowed us to put all of our ideas onto paper and decide what should be included in the final prototype.</p><h4><strong>Step 4 — Using Figma to create UX/UI designs</strong></h4><blockquote><strong>Tip: UX — The user experience, which is how something works and how the user interacts with it. UI — The user interface, which focuses on the look and layout.</strong></blockquote><p>Three of the UX/UI leads created profiles for the two main potential users of the prototype which are (1) emergency contacts and (2) healthcare workers. As it was decided that the app would be created from the emergency contacts perspective, the UX/UI leads then created user scenarios to determine what features the app would need.</p><p>The UX/UI leads began with producing sketches of the pages we wanted to produce and following this they were quick to get to grips with basic wireframing. The final step was to bring the sketches and wireframes to life by creating the visual designs in Figma. As a team it was decided that we wanted the app to include the following pages which were designed in Figma and coded in React Native:</p><ul><li><strong><em>Landing page</em></strong></li><li><strong><em>Sign in page</em></strong></li><li><strong><em>Sign up pages</em></strong></li><li><strong><em>Onboarding (welcome ) pages</em></strong></li><li><strong><em>Proof of identity pages</em></strong></li><li><strong><em>Home screen for emergency contact</em></strong></li><li><strong><em>Support page</em></strong> — includes mental health tips and links to charities/support groups</li><li><strong><em>FAQ page</em></strong></li><li><strong><em>Feed </em></strong>— including the patients profile with updates in the form of a timeline</li><li><strong><em>Call nurse page — </em></strong>includes the nurses availability and allows emergency contact to call if family member is in critical condition</li><li><strong><em>Settings page</em></strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*LSlddMi4n-xV096YiHzekg.png" /><figcaption>Example of the about, feed, call nurse, FAQ and setting pages designed by the UX/UI leads in Figma.</figcaption></figure><h4><strong>Step 5: Developing the app</strong></h4><blockquote><strong>Tip: Try to have two versions of one ‘.js’ file saved at all times and never have two different files saved under the same name!</strong></blockquote><p>As one of the lead programmers, <strong>I decided to use Expo</strong> (a toolchain built around React Native) for <strong>React Native</strong> (JavaScript framework created by Facebook) to code the app as it was highly recommended for beginner app developers. I used Visual Studio Code as a code editor and its embedded Git feature to push and pull updates to the GitHub repository. The <strong>c<em>ode logic is in JavaScript</em></strong> and the<strong> <em>styling components are created using CSS syntax</em></strong> (<em>i’d never used CSS before</em> and didn’t realise I was doing it until I’d almost finished coding my pages..).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*l7COJqGkXQYouKQoPbkLrg.png" /><figcaption>Example of CSS styling from the App.js file</figcaption></figure><p>We decided as a team to set up a GitHub repository (repo) to be able to collaborate on the project together at the same time. Setting up the repo is where <strong>I started running into problems</strong> as I’d never collaborated using GitHub before so overnight I had to become very familiar with using git commands such as ‘git innit’, ‘git pull’ and ‘git push’ etc.</p><blockquote><strong>Tip: Utilise YouTube! Some channels I used a lot were </strong><a href="https://www.youtube.com/channel/UCW5YeuERMmlnqo4oq8vwUpg"><strong>The Net Ninja</strong></a><strong> and </strong><a href="https://www.youtube.com/channel/UCLBhrKXc9CQczo1vBA6w_mA"><strong>Coding with Curry.</strong></a></blockquote><p><strong><em>The first step</em></strong> was to decide which pages from the Figma project were the most important to code and then allocate specific pages to different team members. Initially I took on the landing, sign in and feed page. As I had no prior knowledge of using JavaScript or CSS styling to build app pages, I of course <strong>I immediately turned to YouTube!</strong></p><p>The project had the following structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*pInWhTsNGX7yWW52egtf7Q.png" /><figcaption>Section from the project folder.</figcaption></figure><p>I discovered that styling and programming the pages to fit our agreed aesthetic wasn’t difficult but instead <strong><em>I struggled with </em></strong>linking the landing page to the sign in page and then the sign in page to the onboarding pages. It took me a while to discover the <a href="https://reactnavigation.org/docs/hello-react-navigation/"><strong>stack navigator</strong></a><strong> </strong>function and then<strong> </strong>a few days to discover how to use it in the newer version (version 5) of React Native. <strong><em>I spent a lot of time</em></strong> emerged in <a href="https://reactnative.dev/docs/getting-started">React Native documentation</a> and trying a lot of different YouTube tutorials until a certain combination finally worked but also never shied away from asking my teammates for help!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5sicwku_386I2qDzj7ODpg.png" /><figcaption>Onboarding pages made by one of the the lead UX/UI Leads. My task here was to link these pages together via the next button.</figcaption></figure><p>The easy part was importing the different navigation components and screens but it was harder to figure out how to use <strong><em>‘onPress={( )=&gt; navigation.navigate(“example page”}’</em> </strong>on certain buttons to link the pages. Following this, I discovered how to develop a simple drawer navigator that included the ‘Home, Feed and About’ screens. The code to make the drawer navigator was more or less the same but with minor differences. For the final prototype a more practical version of the navigator was produced by one of the other developers, along with code for the tab navigator and hence used in the final prototype.</p><blockquote><strong>Tip: Errors messages in React Native are fairly comprehensive, so if you’re ever struggling to debug, copy and paste the message into Google (9/10 times the answer is on </strong><a href="https://stackoverflow.com/"><strong>StackOverflow</strong></a><strong>)!</strong></blockquote><p><strong>I took control</strong> of coding the feed page and whilst doing so, <strong>I ran into some issues</strong> with styling and using the &lt;ScrollView&gt; function. For the timeline styling I used code from stack overflow as a starting point and continued to build on that! <strong>I battled with the &lt;ScrollView&gt; function </strong>for a little while as the page I was coding had the tendency to glitch upon scrolling up and down, producing several errors along the way.</p><p>Completed feed page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*OfHGpInDPxzZ93HuxVqPSQ.gif" /><figcaption>Feed page scrolling feature shown on an Android emulator.</figcaption></figure><h3><strong>The outcome</strong></h3><p>At the beginning of the hackathon my team and I were more or less JavaScript beginners and a few had some experience with HTML and CSS. Despite having limited programming knowledge, we developed a functioning prototype app and were also 1 of 5 teams selected (out of 17) to present to the judges at the finals! The process taught me that you don’t need to be a coding expert to build an app, you just need to be determined!</p><p>Short demo of the app:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*7EUsVP0ubvIy4L4xddvhjQ.gif" /><figcaption>Short demo of the app shown on an Android emulator.</figcaption></figure><p><strong>Thanks for reading! </strong>Follow me on here to keep up with my incoming tech-related articles where I’ll be writing about my tech journey so far, tips on how to get into tech as a graduate (without a computer science degree) and much more! To connect or continue the conversation, <a href="https://twitter.com/TemiOlukoko">follow me on twitter. </a>Follow <a href="https://www.instagram.com/temilola.dev/">my developer page</a> for similar content and to see what I get up to. V<a href="https://github.com/TemiOlukoko/patient-progress-app">iew the GitHub repo here</a> and test the prototype out for yourself either in the web browser or using the expo app if you have an android mobile device!</p><p>Let me know if you have any questions or comments — this is my first blog post so feedback is most welcomed!</p><p><strong><em>Tools credit: </em></strong><a href="https://www.figma.com/"><strong><em>Figma</em></strong></a><strong><em>, </em></strong><a href="https://reactnative.dev/"><strong><em>React Native</em></strong></a><strong><em> and </em></strong><a href="https://expo.io/"><strong><em>Expo</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c3f7ff306f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codingblackfemales/how-i-built-a-react-native-app-for-a-hackathon-in-response-to-the-covid-19-pandemic-as-a-2c3f7ff306f3">How I built a React Native App for a hackathon in response to the COVID-19 pandemic as a…</a> was originally published in <a href="https://medium.com/codingblackfemales">CodingBlackFemales</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>