<?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 Elle Townsend on Medium]]></title>
        <description><![CDATA[Stories by Elle Townsend on Medium]]></description>
        <link>https://medium.com/@elletownsend?source=rss-59cd7a0d5caf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N2vtNIgLpcnfUNxwRaRVmA@2x.jpeg</url>
            <title>Stories by Elle Townsend on Medium</title>
            <link>https://medium.com/@elletownsend?source=rss-59cd7a0d5caf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:36:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elletownsend/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[처음부터 지금까지— Learning Korean From Scratch]]></title>
            <link>https://elletownsend.medium.com/%EC%B2%98%EC%9D%8C%EB%B6%80%ED%84%B0-%EC%A7%80%EA%B8%88%EA%B9%8C%EC%A7%80-learning-korean-from-scratch-becfbb3ce587?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/becfbb3ce587</guid>
            <category><![CDATA[korean]]></category>
            <category><![CDATA[korean-language]]></category>
            <category><![CDATA[learning-language-tips]]></category>
            <category><![CDATA[language-learning]]></category>
            <category><![CDATA[learning-korean]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Tue, 03 Aug 2021 15:59:57 GMT</pubDate>
            <atom:updated>2021-08-03T16:00:58.153Z</atom:updated>
            <content:encoded><![CDATA[<h4>I’ve been self-studying Korean for 5 years, here’s what I’ve learnt.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WMowGektGDRsdyeg" /><figcaption>Photo by <a href="https://unsplash.com/@caitellis?utm_source=medium&amp;utm_medium=referral">Cait Ellis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Learning a new language is something we are always told is good for our brains. As children, we are encouraged to learn a modern foreign language to expand our world view and even help us with language development in our native language.</p><p>For me, language learning started from a young age, studying French as a child at a language club. At school we were taught French and German for a few years, but after taking my further education down the path of the sciences, I lost touch with language learning.</p><p>As I got older and times changed, I fell in love with Korean music, television and culture, and was fascinated by the beautiful language with an entire writing system I had never seen before in my life. It was something so new and so unlike any other language I had learnt before, but I decided to have a go at learning it myself.</p><p>That was 5 years ago now, and I’m still here, 5 years later, engrossed in studying the writing system, vocabulary and grammar principles of the Korean language. If, like me, you are interested in learning Korean for yourself, here’s all the advice I would give to my past self.</p><h3>Learning Resources</h3><p>There are 2 main learning resources I recommend for self-studying Korean, Talk To Me In Korean, and HowToStudyKorean. Both are great resources for learning, and over the years I have heavily relied on both to get a full understanding of many grammatical principles. Here’s a rundown of the two:</p><h4><a href="https://talktomeinkorean.com/"><strong>Talk To Me In Korean (TTMIK)</strong></a></h4><p><strong>Pros</strong></p><ul><li>Completely free online courses (They also have a paid membership with extra content, and lots of physical textbooks you can buy— I never bothered because the shipping is pretty pricey depending on where you live).</li><li>All of the content covered in their text books is available for free on their website (but they do have a lot of other books that aren’t).</li><li>Very beginner friendly (especially if you are new to learning languages in general).</li><li>Lots of audio material, YouTube videos, podcasts &amp; all the lessons have recordings.</li><li>Easy to track progress with the online courses.</li><li>Very concise lesson notes.</li></ul><p><strong>Cons</strong></p><ul><li>Some of the explanations of grammatical concepts or applications are very simplified for ease of learning (a great thing if you’re a beginner though!).</li></ul><h4><a href="https://www.howtostudykorean.com/"><strong>HowToStudyKorean</strong></a></h4><p><strong>Pros</strong></p><ul><li>LOADS of vocabulary (every lesson has a list of new words to learn).</li><li>Very detailed explanations of all concepts covered.</li><li>Tons of lessons (all free) — including some on hanja, and extra (paid) content including pdf workbooks and short stories.</li></ul><p><strong>Cons</strong></p><ul><li>Very verbose and detailed explanations, which can be overwhelming for beginners.</li></ul><h4><strong>Learning Apps I Recommend</strong></h4><ul><li><a href="https://www.memrise.com/">Memrise</a> is perfect for vocabulary.</li><li><a href="https://papago.naver.com/">Papago</a> for translating to &amp; from Korean (trust me it’s better than Google Translate).</li></ul><h3>How To Get Started</h3><p>The first step is always the hardest, but my best advice would be to start small. Without a doubt before you learn anything else, learn 한글 (Hangul), the writing system for the Korean language. Make sure you learn how to recognise each individual letter, and letter combinations, how to pronounce them and the syllabic structure of how words are written. This is the most important step. After this, I recommend choosing either TTMIK or How To Study Korean and getting started with their first lesson.</p><p>In terms of time commitment, in an ideal world it’s good to set some time out of your day every day to study a little, but that’s not set in stone. I like to do a few minutes of vocabulary practice (Recalling or learning new words with Memrise) every day, and competing / reviewing a lesson to learn some new grammar when I have the time.</p><h3>Supporting Your Learning</h3><p>While you’re learning a new language, it’s important to supplement your learning with lots of exposure to your target language. Listening to native speakers and getting lots of experience listening and trying to comprehend conversations helps with learning and retention.</p><p>If you aren’t fortunate enough to have been able to visit South Korea yourself yet to get the fully immersive experience, that’s ok (I haven’t either — yet!). There are definitely lots of other ways to support your Korean learning.</p><p>The clichés are absolutely true in this case, watching K-dramas &amp; listening to K-pop counts as studying! However, I do recommend trying to watch Korean reality TV / talk shows with subtitles, as in my experience they are better for hearing everyday conversations (My recommendations are: <a href="https://youtube.com/playlist?list=PLMf7VY8La5RFIeOyIZ5IOm68WVb7c2dyT">The Return of Superman</a>, <a href="https://youtube.com/playlist?list=PLMf7VY8La5RHYWE9mgF7x6duuCEuA5Fpq">Matching Survival 1+1</a>, and <a href="https://youtube.com/playlist?list=PLMf7VY8La5RHqhKKy9aOGtDBL8vUXaQME">Hello Counsellor</a>).</p><p>Youtubers are another great language learning resource. I like to watch Youtubers who speak exclusively Korean in their videos, but also provide subtitles in English. This is again another way of hearing the language spoken by native speakers to aid with pronunciation, as well as exposure to natural speaking and new vocabulary (My recommendations are: <a href="https://www.youtube.com/channel/UCSn90DAxCF3yRs6mFK0-8TA">ondo온도</a>, <a href="https://www.youtube.com/channel/UCC7CrJilMc-MIaAeEqjO-Lg">수린 suzlnne</a>, and <a href="https://www.youtube.com/channel/UC2tfQfxl_wmAosF4ES_zULw">혜리</a>).</p><p>Having a go at translating Korean is also a great way to gain a better understanding and experience of how the language is used and written by the native speakers. I like to find books that are not too complex (maybe short stories written for children / teens) and try to read and understand them, making a note of any new words I come across or any grammatical principles I’m not familiar with — the best one I can recommend so far is <a href="https://g.co/kgs/cFETfM">‘Intermediate Short Stories In Korean’ by Olly Richards</a>. You can also do this for song lyrics too!</p><p>If you’re a little further ahead with your leaning and want to be exposed to an ever broader range of vocabulary, tailored specifically to your interests , try looking up articles or blog posts written in Korean on topics you’re interested in (I like reading articles on the nature of coding &amp; web development in Korea). It can definitely be challenging at first, as there will be a lot of new vocabulary, but that’s the best part!</p><h3>Test Yourself</h3><p><a href="https://www.topikguide.com/">TOPIK</a> is the “Test of Proficiency in Korean”, a written test (comprised of listening, reading and writing tests) designed to measure the ability of non-native speakers for expression and comprehension in the Korean language.</p><p>TOPIK has lots of past papers you can download (with audio files, question papers &amp; marking criteria) that you can use to effectively test your current comprehension level. If you’d like to take it a step further, you can register to take the official test, and there are guides on how to do this from your home country, but it’s not a requirement if you are just learning for fun. You can instead just take the past papers and mark your own tests to check your progress.</p><p>The tests themselves are split into fluency levels depending on what you score and all is explained in the <a href="https://www.topikguide.com/topik-overview/">TOPIK guide</a>. The guide website also has instructions on how to apply for the tests, where the testing centers are located, and when results are announced. If you are based in the UK, you can also find more information on cost and testing centers through the <a href="http://www.koreaneducentreinuk.org/en/topik-test-of-proficiency-in-korea/">Korean Education Centre in the UK</a>.</p><h3>General Advice</h3><ul><li>Learning vocabulary is just as important as learning grammar!</li><li>It’s ok to be self-conscious of your pronunciation, just keep practicing (the same goes for handwriting — It will come with practice and time).</li><li>There is a LOT of grammar to learn, but as you progress, you become used to it and I promise it won’t be impossible to remember it all.</li><li>People will always question why you’re learning any language, but you have your own motivations and that’s absolutely fine! You got this and I’m rooting for you!</li><li>Keep at it! I took a lot of breaks from learning over the years that slowed my progress but all these years later I’m still learning and still loving it.</li></ul><p>If you’ve ever considered learning a new language, but you’re put off by the different writing system, the initial confusion, or the scary amount of grammatical principles it seems like you need to learn, my words to you are these: <em>Take your time.</em> It’s not a race to see who can learn the most the quickest and become fluent first, it’s a life-long learning process, and it’s about the enjoyment and appreciation of learning a new language, and learning all about the culture and history that comes with it.</p><p>[This post was originally written here: <a href="https://www.elletownsend.co.uk/blog/posts/learning-korean/">https://www.elletownsend.co.uk/blog/posts/learning-korean/</a>]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=becfbb3ce587" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Your Websites More Accessible]]></title>
            <link>https://elletownsend.medium.com/making-your-websites-more-accessible-f2cdd2f42fcf?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2cdd2f42fcf</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Mon, 17 May 2021 17:03:24 GMT</pubDate>
            <atom:updated>2021-05-19T06:04:04.473Z</atom:updated>
            <content:encoded><![CDATA[<h4>My 6 Accessibility Tips To Make Your Websites More Accessible</h4><figure><img alt="Man in black long sleeve shirt wearing black headphones, sitting on a chair, looking at a computer screen with code editor open" src="https://cdn-images-1.medium.com/max/1024/0*TZw5IWMmXhyTY_vz" /><figcaption>Photo by <a href="https://unsplash.com/@nubelsondev?utm_source=medium&amp;utm_medium=referral">Nubelson Fernandes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What Is Accessibility and Why Is It Important?</h3><p>Web accessibility in its purest form relates to the usability of a website for all people. Can a website be used by everyone? Can everyone perceive, understand, navigate, and interact with the functionality of your website / digital product?</p><p>Unfortunately, this can’t be said for every website you may stumble across, but making websites usable for everyone should be the standard. Accessibility should be at the forefront of your mind when you create any product, especially for the web. Accessibility should be part of the design, user experience, coding, and testing of everything created to be used by the masses.</p><h3>How Can I Check The Accessibility Of My Website?</h3><p>You should try to keep accessibility as an essential, high priority part of any work you do. However, you might be thinking about how potentially unaccessible sites you have made previously may be.</p><p>Accessibility can be retro-fitted in situations like this, but this should be the exception not the norm. There are many accessibility tools that will tell you how accessible a website is, and may also provide tips on how it can be improved, two that I recommend are:</p><ul><li>WAVE Web Accessibility Evaluation Tool — <a href="https://wave.webaim.org/">https://wave.webaim.org</a></li><li>Google Lighthouse Accessibility Audit Tool — <a href="https://medium.com/accessibility-a11y/do-an-accessibility-audit-using-google-chrome-lighthouse-30ff7887901c">https://medium.com/accessibility-a11y/do-an-accessibility-audit-using-google-chrome-lighthouse-30ff7887901c</a></li></ul><h3>I Want To Make All My Websites Accessible! Where Can I Start?</h3><p>Here are 6 things you can do right now to make all your sites more accessible…</p><h4>1. Use Semantic HTML.</h4><p>Using correct semantic HTML is a great foundational step towards an accessible website. Semantic HTML gives us a built-in way to represent logical sections of our web apps, and while they don’t perform any real functional differences, they work well with assistive technologies to provide alternative ways of viewing / navigating a web page.</p><p>My biggest take-away for you for this point is that div &amp; span elements are for layout only. Try to find other elements that are more appropriate semantically if you can (like nav, footer, button, etc.). To skill up on semantic HTML elements, have a read of the <a href="https://www.w3schools.com/html/html5_semantic_elements.asp">W3Schools page</a> on it!</p><h4>2. Correct Heading Structure.</h4><p>Along the same vein, let’s talk about headings. We all know the correct usages of H1, H2, H3 etc. elements, but using them in the appropriate hierarchy on your web page is really important. Headings should be nested by their ‘level’ — so the top-most heading should always be a H1 element and so on. W3C has great <a href="https://www.w3.org/WAI/tutorials/page-structure/headings/">documentation explaining this</a> in detail.</p><h4>3. Add Alt Text To Your Images.</h4><p>Using visual elements on your website is great, as long as they are supported by alt text to allow all users to perceive them. Alt text should be understandable and describe the picture as clearly as possible as it will be read out to those using a screen reader to access your website. This allows us to give necessary context that users may otherwise miss out on if they cannot see the image on the site.</p><h4>4. Contrast!</h4><p>Choose your colours wisely! Make sure the colours that you select to use in your site design have adequate contrast so that all users can distinguish between elements and comfortably read text on your website. Ensure that text stands out well against the background so it can be read easily.</p><p>If you’re unsure how to make sure your colour palette is cute and accessible, choose your colours and then pop them into a <a href="https://webaim.org/resources/contrastchecker/">contrast checker</a> to ensure everyone can enjoy them!</p><h4>5. Keyboard Navigation Is A Must.</h4><p>Accessible websites should be navigable without the use of a mouse. In general, it should be possible to use all of your website’s important features &amp; functionality using just the keyboard alone. Using focus indicators correctly and making sure the navigation order of your website is logical and intuitive makes your website a whole lot easier to use for lots of people.</p><p>WebAIM have a great <a href="https://webaim.org/techniques/keyboard/">guide</a> you can follow to work on improving your site’s keyboard accessibility.</p><h4>6. Always Have Accessibility In Mind.</h4><p>With all that being said, remember to always have accessibility principles at the forefront of your mind when you are doing any sort of work. Not everyone experiences the web in the same way that you do, and it’s good to be mindful of that so that we can create a fun and accessible web for everyone. Accessibility is a priority, not an afterthought.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2cdd2f42fcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integration & Unit Testing For Node.js]]></title>
            <link>https://javascript.plainenglish.io/integration-unit-testing-for-node-js-5d44b588cd17?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d44b588cd17</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 10 Apr 2021 09:11:21 GMT</pubDate>
            <atom:updated>2021-04-12T12:06:14.440Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Beginner’s guide to testing Node &amp; Express projects using Mocha &amp; Chai ☕️</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5_pqCzTrn6e0ERbk" /><figcaption>Photo by <a href="https://unsplash.com/@sincerelymedia?utm_source=medium&amp;utm_medium=referral">Sincerely Media</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Software testing verifies that our code works as intended and meets the technical, functional, and user requirements that it needs to. Testing is a vital part of developing any software, but is so often overlooked by new engineers as an area to learn and develop their skills. It doesn’t help that more often than not, it’s hard to find good tutorials, guides or blog posts explaining the different kinds of tests for a code project, and how to actually write these tests.</p><p>To begin with, I wanted to go over some important words that pop up all the time around software testing, and what they mean:</p><h4><strong>Unit Testing</strong></h4><p>Unit testing is the testing of the smallest ‘units’ or components of a program. In most cases, the smallest unit under test would be a function. Therefore, in these situations, we are testing to make sure our individual functions work as expected.</p><p>Unit testing is performed before any other type of software testing, and it is usually the responsibility of the developer to conduct &amp; write these tests.</p><h4><strong>Integration Testing</strong></h4><p>Integration testing is the testing of a combination of a related group of units of code that provide a given functionality. In this case, we are testing for bugs that can occur within the interactions between units.</p><p>Integration testing can also be the responsibility of a developer, but it’s not uncommon to have independent testers to also get involved with integration testing.</p><p>In this example, we will go over unit and integration tests for a Node.Js &amp; Express API project. The main functionality of our example project will be responding to GET HTTP requests with a random number, this isn’t too important, as the main focus will be on the tests.</p><h3>Tools</h3><h4>Node.js &amp; Express 🔥</h4><p>We are going to be creating a simple Node.js application that uses the <a href="https://expressjs.com/">Express.js</a> framework to create a mini-API. This is just for example purposes, and will act as the code under test.</p><p>For more information on both of these, please have a look at the <a href="https://nodejs.org/en/">Node.js</a> and <a href="https://expressjs.com/">Express.js</a> documentation.</p><h4>Mocha ☕️</h4><p>Mocha is a flexible, open-source JavaScript testing framework that runs on Node.js. It works for testing synchronous and asynchronous code, and nicely logs the test results to the console. Mocha can be used for both unit &amp; integration testing.</p><p>Mocha can be used alongside most <a href="https://stackoverflow.com/questions/25678063/whats-the-difference-between-assertion-library-testing-framework-and-testing-e/25678226#25678226">assertion libraries</a> (a tool that is in charge of the verification of your test results), but the most popular Node.js assertion library used with Mocha is called Chai.</p><h4>Chai &amp; Chai-http 🫖</h4><p>Chai is a Behaviour / Test driven design assertion library used frequently with Mocha in Node.js testing. Chai-http is a plugin for Chai that allows us to write HTTP integration tests with Chai.</p><p>The hot-beverage themed pair work together to create a great way to get started with testing our Node.js &amp; Express projects.</p><h3>The Set Up</h3><p>Requirements: <a href="https://nodejs.org/en/">Node.js installed</a>.</p><p>In order to best demonstrate testing, we are going to need some code to test.</p><p><em>(If you’re using this tutorial as a guide to testing an existing project — great! You don’t need to create this project, but the testing should follow the same principles.)</em></p><p>First things first, create a new Node.js project (create a new folder and run npm init from there). After this, go ahead and install express using npm install express.</p><p>Next, we will create our server.js file, which is going to hold all the logic for our example app:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/54858014655b0ef055284067ae1c3ebe/href">https://medium.com/media/54858014655b0ef055284067ae1c3ebe/href</a></iframe><p>Our Node app listens at localhost:3000 and exposes an endpoint /random that returns a random number. You can give it a try by running your app (npm start), and navigating to localhost:3000 in your browser.</p><h3>The Tests</h3><p>Now its time to test!</p><p>To set this up correctly, I’d advise that you create a test sub-folder to keep all your testing files for this app together.</p><p>Next up, we need to install our testing libraries by running:</p><pre>npm install mocha chai chai-http</pre><p>And making sure that in our package.json we have added Mocha to our test script like so:</p><pre>...<br>  &quot;main&quot;: &quot;server.js&quot;,   <br>  &quot;scripts&quot;: { <br>    &quot;start&quot;: &quot;node server.js&quot;,<br>    &quot;test&quot;: &quot;mocha&quot;<br>  },   <br>  &quot;author&quot;: &quot;&quot;,<br>...</pre><p>This means that now we only need to run npm test when we want to run our tests. We are now all set up and ready to write our first unit test.</p><h4>Unit Tests</h4><p>As mentioned earlier, unit testing is all about testing single, individual functions. In the case of our example code, we are going to write a unit test that checks that our getRandom function does what it’s supposed to and generates a random whole number between 0 and 100.</p><p>We first have to require chai and chai.assert to get our assertion library. Then we describe the function under test, call that function, and make assertions on the result.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab69d6cde424715eaf9537bf18310c36/href">https://medium.com/media/ab69d6cde424715eaf9537bf18310c36/href</a></iframe><p>Here, the describe function encapsulates our test. The first argument is a string that describes what we are testing (for the sake of example, I have called it ‘Unit Test’, but it would be more descriptive to pass something like ‘GetRandom random number generation’).</p><p>The second argument passed is a function that acts as the body of the test. It starts with an it function, which similar to the describe function, describes the test. Here, we give a small description of the functionality we are testing, or what the expected functionality is. The second argument is another function, and in this function we can actually write our test code.</p><p>In this example, we are using the assert assertion style, but Chai offers other styles of assertion, such as should or expect. You can find out the differences between them in the <a href="https://www.chaijs.com/guide/styles/">Chai Assertion Styles Guide</a>.</p><p>When this test is run, our getRandom function is called, and the test makes assertions on the result. We assert (verify) that the returned result (random) is not null, is a number, and is at least 0, but no more than 100. If all these assertions pass, that means our code is functioning as it is supposed to, and our unit passed it’s unit test.</p><h4>Integration Tests</h4><p>Testing the functionality of our API endpoint constitutes an integration test as we are testing how all the individual parts of our program work together to send a response back when our /random endpoint is hit. In order to do this, we need to use chai-http. This package allows us to make HTTP requests to our server during tests.</p><p>Because of the use of asynchronous code and promises in the implementation of this functionality, we have to approach the integration test for this code slightly differently. We pass a callback inside the it function that calls and tests our asynchronous code (same as before).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c78b6a3873ea282be1bee3d15a335fc/href">https://medium.com/media/2c78b6a3873ea282be1bee3d15a335fc/href</a></iframe><p>chai-http allows us to construct a request to our application by passing in our app. This automatically opens our server for incoming requests. We can then use .get() to call our /random endpoint. The end method is then used to make the request and assert on the response.</p><p>Because the end functions is a callback, we have to use the done callback in order to indicate to Mocha that our callback has completed and the assertions are ready to be verified. If we don’t do this, the test will pass before the assertions are checked.</p><p>We check that our response contains a successful status code, and that the number that the response returns is not null, is a number, and is at least 0 but no bigger than 100 (no change there).</p><p>In this integration test, we are making sure that not only are we provided with the response from the API endpoint that we are expecting, but we are also making sure that our API as a whole behaves as expected when responding to a GET request. This is testing how multiple ‘units’ of our application come together to provide this functionality.</p><p>And that’s it! We have completed a unit and an integration test for our mini-API.</p><p>While this is a simplified example, you can use these as a template to go on and test your own, more in-depth Node &amp; Express projects. The implementation remains the same, but you can develop these example tests further and duplicate them in order to test larger and more complex programs.</p><p>Below I have linked to some other great guides on unit &amp; integration testing in Node.js, as well as the official documentation for Mocha &amp; Chai. Happy testing!</p><h4>Resources</h4><ul><li>Unit Testing in Node.js with Mocha &amp; Chai — <a href="https://livecodestream.dev/post/testing-in-nodejs-using-mocha-and-chai-part-1/">https://livecodestream.dev/post/testing-in-nodejs-using-mocha-and-chai-part-1/</a></li><li>Integration Testing in Node.js with Mocha &amp; Chai — <a href="https://livecodestream.dev/post/testing-in-nodejs-using-mocha-and-chai-part-2/">https://livecodestream.dev/post/testing-in-nodejs-using-mocha-and-chai-part-2/</a></li><li>JavaScript Testing with Mocha &amp; Chai — <a href="https://codeburst.io/javascript-unit-testing-using-mocha-and-chai-1d97d9f18e71">https://codeburst.io/javascript-unit-testing-using-mocha-and-chai-1d97d9f18e71</a></li><li>Unit &amp; Integration Testing for Node.js — <a href="https://blog.logrocket.com/unit-and-integration-testing-for-node-js-apps/">https://blog.logrocket.com/unit-and-integration-testing-for-node-js-apps/</a></li><li>Mocha — <a href="https://mochajs.org/">https://mochajs.org</a></li><li>Chai — <a href="https://www.chaijs.com/">https://www.chaijs.com</a></li><li>Chai-http — <a href="https://www.chaijs.com/plugins/chai-http/">https://www.chaijs.com/plugins/chai-http/</a></li></ul><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d44b588cd17" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/integration-unit-testing-for-node-js-5d44b588cd17">Integration &amp; Unit Testing For Node.js</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tackling Impostor Syndrome]]></title>
            <link>https://elletownsend.medium.com/tackling-impostor-syndrome-8e2f9f433a96?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e2f9f433a96</guid>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[impostor-syndrome]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 13 Mar 2021 11:34:56 GMT</pubDate>
            <atom:updated>2021-03-13T15:34:12.322Z</atom:updated>
            <content:encoded><![CDATA[<h4>Impostor Syndrome is very real, but it doesn&#39;t define you.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c4d31ZBxg9_Eeku2" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We have all seen these words popping up more and more frequently recently, but what does it really mean? and how can we recognise when impostor syndrome begins to manifest itself in our own lives?</p><p>Impostor syndrome refers to the state of feeling or believing that you are not as competent as others perceive you to be. You may feel like you are a “fake” and that at any moment, the people around you are going to figure it out, or that you don’t deserve to be where you are, that you only got to where you are through luck.</p><p>Impostor syndrome can affect anyone, at any skill level or degree of expertise at any time, and I can say I have personally experienced it throughout my degree, my job and even through writing for my blog.</p><p>Some huge impostor syndrome red flags to look out for include:</p><ul><li>Self-doubt &amp; doubting your own competence</li><li>Self-sabotage &amp; limiting your own success</li><li>Holding yourself back from good opportunities</li><li>Fear you don’t live up to expectations put onto you by yourself or others</li><li>Belittling your performance</li></ul><p>Even highly successful people can suffer from this as doing well or achieving a goal doesn’t change how you feel, it only perpetuates the feeling that it was just a fluke. You begin to ask yourself “What gives me the right to be here?” “Who am I to do this?”, and the more you accomplish, the more “fake” you feel. It’s unfortunately a pretty self-perpetuating problem.</p><p>For me, impostor syndrome has manifested itself in the form of unbearable levels of self-doubt, questioning “Who am I to deserve to do this?”, questioning writing or speaking about topics as “who am I to write / speak about this?” and feeling inadequate in my abilities as a developer. Feeling like one day everyone is going to turn around and realise I don’t know what I’m doing and I spend a lot of my time googling things to try to work out how to code something (as if they don’t do that too 😅).</p><p>However, when it comes to combatting impostor syndrome, the answer is not yet clear. It’s important that when you feel like you aren’t very good at something, it is not a fact that you are actually bad at it. Distinguishing between how you feel and facts, when you start to doubt your abilities is a great way to shift your mindset. Another thing that we all need to work on is developing a healthy response to failure. Instead of feeling like a failure for getting something wrong or making a mistake, forgive yourself, learn from it and succeed next time!</p><p>Start celebrating the little wins too. Reward yourself for all the positive things you have done, no matter how small. You are worthy, you are not a failure, and you got this 💪.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e2f9f433a96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Essential Tech Tools for New Developers]]></title>
            <link>https://elletownsend.medium.com/5-essential-tech-tools-for-new-developers-f13df17bdfc4?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f13df17bdfc4</guid>
            <category><![CDATA[tech-tools]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 09:30:36 GMT</pubDate>
            <atom:updated>2021-03-01T09:30:36.312Z</atom:updated>
            <content:encoded><![CDATA[<h4>Free tools every developer should know about.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w7WhusHKoXdpcvds" /><figcaption>Photo by <a href="https://unsplash.com/@jmckinven?utm_source=medium&amp;utm_medium=referral">James McKinven</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Tools can make your life as a developer a whole lot easier, but as a new developer, knowing which tools to use can be confusing. Until now, you’ve probably ended up sticking with tools you were introduced to early on in your coding journey, or ones recommended to you by other devs.</p><p>I want to tell you about 5 developer tools I use to improve my workflow, and the main tools I recommend all new developers try out.</p><h3>Visual Studio Code</h3><p>When you first start out, it’s really important to set yourself up with a good code editor to write your projects in. Visual Studio code is free to download and use, and supports a vide variety of programming languages. It also has thousands of community plugins for additional functionality, as well as integrated source control management, syntax highlighting, IntelliSense code completion, bracket-matching, auto-indentation and more. VS Code is incredibly customisable, completely open-source, and one of the most popular code editors around at the moment. I’m sure you’d struggle to find a developer who hasn’t heard of it or used it before.</p><p><a href="https://code.visualstudio.com/">Download Visual Studio Code</a></p><h3>Browser Dev Tools</h3><p>If you’re developing things for the web, the built-in browser dev tools are going to become your best friend. No matter what browser you’re using (yes, even Internet Explorer), there will be built-in developer tooling to help with website development, all you have to do is find them. With these tools, you can visibly edit the page you are viewing, access source files, utilise the JavaScript console, and browse the entire HTML DOM for that page. This can also be really useful when you’re trying to debug CSS issues, as you can make non-persistent changes to the CSS code to work out what’s going wrong.</p><p><a href="https://support.apple.com/en-hk/guide/safari/sfri20948/mac">Safari Dev Tools</a> | <a href="https://developers.google.com/web/tools/chrome-devtools">Chrome Dev Tools</a> | <a href="https://developer.mozilla.org/en-US/docs/Tools">Firefox Dev Tools</a> | <a href="https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/open/?tabs=cmd-Windows">Edge Dev Tools</a></p><h3>Oh My Zsh</h3><p>Oh My Zsh is an open-source framework for customising your terminal. Not only are there hundreds of cool looking themes to make you feel cooler every time you use your terminal, there are also a bunch of plugins and helpers to boost your productivity.</p><p>You can streamline your workflows and even keep track of your git status all from the terminal, to help you go from terrified of the terminal to a command prompt master in no time! I find the git integration to be a life-saver when I’m working on coding projects, as I can always keep track visually of what branch I’m on and if I have any non-committed changes.</p><p><a href="https://ohmyz.sh/">Download Oh My Zsh!</a></p><h3>Postman</h3><p>If you do any development work with APIs, Postman will improve your productivity tenfold! Quickly and easily send REST, SOAP, and GraphQL requests directly within Postman’s API client with next-to no set up time.</p><p>Whether you’re creating your own API and need to test it, or learning how API requests work, Postman’s free tier provides everything you need for trying out APIs and API development, with no limit on the number of API calls you can make from the client.</p><p><a href="https://www.postman.com/downloads/">Download Postman</a></p><h3>Figma</h3><p>This might not be for everyone, but I love creating my own designs before I start coding. If you’re like me, and you’re looking for a design tool to level up your digital designs, give Figma a try.</p><p>With Figma, you can quickly and easily design and prototype your projects before you write any code. Figma is also a cloud software that saves and stores all of your designs for you, so all you need to think about is making cool stuff! I love how much creativity Figma has brought into my development projects, and I recommend it to all fellow creative coders with an eye for design.</p><p><a href="https://www.figma.com/">Download Figma (or use it in your browser)</a></p><p>There are so many different tools for developers looking to improve their development workflow, I can’t possibly include them all in one list, but I think I’ve done a good job covering my favourites.</p><p>What are your favourite dev tools? are there any tools you use that you couldn’t code without?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f13df17bdfc4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Ways To Create Your Own API]]></title>
            <link>https://medium.com/better-programming/3-ways-to-create-your-own-api-f99f7fb739b1?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f99f7fb739b1</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 11:02:14 GMT</pubDate>
            <atom:updated>2021-02-15T18:37:08.835Z</atom:updated>
            <content:encoded><![CDATA[<h4>Three beginner-friendly methods for creating an API from scratch</h4><figure><img alt="Outdated tech" src="https://cdn-images-1.medium.com/max/1024/0*7ZuKANl9b0DuDdvL" /><figcaption>Photo by <a href="https://unsplash.com/@lorenzoherrera?utm_source=medium&amp;utm_medium=referral">Lorenzo Herrera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><p>APIs are everywhere, and they play a vital role in modern-day technology. From payment platforms to stock market updates, everything is an API nowadays, and learning to create one yourself is a fundamental step in the path to becoming a full-stack developer.</p><p><em>Note: If you aren’t sure what an API is, I have </em><a href="https://www.elletownsend.co.uk/blog/posts/top-5-apis/"><em>a handy introduction for you</em></a><em>.</em></p><p>In this article, I will discuss three beginner-friendly ways you can create an API:</p><ol><li>JSON Server</li><li>Node.js and Express</li><li>Python and Flask RESTful</li></ol><p>Each of these methods has different use cases and uses different tech stacks. It is up to you which one you’d like to go with.</p><h3>JSON Server</h3><p><em>Requirements: </em><a href="https://nodejs.org/"><em>Node installed</em></a></p><p>JSON Server is a package available through NPM that allows us to create a REST API with CRUD (Create, Read, Update, Delete) operations out of the box super quickly using only a single JSON file.</p><p>First, we need to install the package (globally) by running this in the terminal:</p><pre>npm install -g json-server</pre><p>Now we need some data to serve. Create a db.json file with some data (this can be whatever you’d like your API to serve):</p><pre>{ <br>  &quot;dogs&quot;: [<br>    { &quot;id&quot;: 1,<br>      &quot;breed&quot;: &quot;pembroke-welsh-corgi&quot;,<br>      &quot;name&quot;: &quot;Charles&quot;<br>    },<br>    { &quot;id&quot;: 2,<br>      &quot;breed&quot;: &quot;pug&quot;,<br>      &quot;name&quot;: &quot;cheese&quot;<br>    },<br>    { &quot;id&quot;: 3,<br>      &quot;breed&quot;: &quot;dachshund&quot;,<br>      &quot;name&quot;: &quot;ralph&quot;<br>    }<br>  ],<br>  &quot;cats&quot;: [<br>    { &quot;id&quot;: 1,<br>      &quot;breed&quot;: &quot;ragdoll&quot;,<br>      &quot;name&quot;: &quot;mimi&quot;<br>    },<br>    { &quot;id&quot;: 2,<br>      &quot;breed&quot;: &quot;siamese&quot;,<br>      &quot;name&quot;: &quot;mocha&quot;<br>    },<br>    { &quot;id&quot;: 3,<br>      &quot;breed&quot;: &quot;russian-blue&quot;,<br>      &quot;name&quot;: &quot;bean&quot;<br>    }<br>  ]<br>}</pre><p>In order to get our server up and running, run:</p><pre>json-server --watch db.json --port 8080</pre><p>If we now make a request to <a href="http://localhost:8080/dogs/1">http://localhost:8080/dogs/1</a>, we should get back:</p><pre>{ &quot;id&quot;: 1, &quot;breed&quot;: &quot;pembroke-welsh-corgi&quot;, &quot;name&quot;: &quot;charles&quot; }</pre><p>The following HTTP endpoints will be created automatically by JSON server too:</p><pre>GET /dogs <br>GET /dogs/{id} <br>GET /cats <br>GET /cats/{id} </pre><pre>POST /dogs <br>POST /cats </pre><pre>PUT /dogs/{id} <br>PUT /cats/{id} </pre><pre>PATCH /dogs/{id} <br>PATCH /cats/{id} </pre><pre>DELETE /dogs/{id} <br>DELETE /cats/{id}</pre><p>With JSON Server, we can filter results by adding query parameters to our requests. If we hit <a href="http://localhost:8080/cats?breed=siamese">http://localhost:8080/cats?breed=siamese</a>, it should return an array of all the cat objects in the data that match the given criteria.</p><p>We can also do a full-text search with the p parameter: <a href="http://localhost:8080/cats?q=m">http://localhost:8080/cats?q=m</a>.</p><p>All of this information and more can be found in much greater detail in the <a href="https://github.com/typicode/json-server">JSON Server GitHub repo</a>.</p><p>If you’d like to look into this a little further and find out how to deploy your JSON Server API, I recommend <a href="https://www.youtube.com/watch?v=FLnxgSZ0DG4&amp;feature=youtu.be">Ania Kubow’s YouTube tutorial</a> on how to create and deploy a mock API.</p><h3>Node.js and Express.js</h3><p><em>Requirements: </em><a href="https://nodejs.org/"><em>Node installed</em></a></p><p>For this method, we will be creating a new Express app. To do this, create a project folder called node-api and a server.js file inside it. After this is done, open a new terminal inside our node-api folder and run:</p><pre>npm init</pre><p>This will initialise our project and create a package.json file (for setup questions, it’s OK to just press enter and leave everything blank/default).</p><p>Now we need to install Express! We can do this with NPM by running:</p><pre>npm install express</pre><p>And in our server.js file, we can now create our server as follows:</p><pre>var express = require(&quot;express&quot;);</pre><pre>var app = express();</pre><pre>app.listen(8080, () =&gt; {<br> console.log(&quot;Server running on port 8080!&quot;);<br>});</pre><p>We have everything we need all set up with Express. Now we are going to create the endpoints for our requests. In this tutorial, we will be creating endpoints for GET requests only.</p><p>We can add the data to our file by using two constant variables containing the objects for our data like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d364aa0ffbf3f40e26c1abee137adad/href">https://medium.com/media/9d364aa0ffbf3f40e26c1abee137adad/href</a></iframe><p>Right after var app = express();, let’s add some functions to handle GET requests to send back all the data on the requested resource with a “200 OK” status code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d938228d032137dd93f18b3f98333bc/href">https://medium.com/media/2d938228d032137dd93f18b3f98333bc/href</a></iframe><p>In order to GET specific entries by ID, we have to use the :id URL parameter to search our arrays to find an entry that matches the given ID. Underneath our standard GET requests, add these in:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e918abfa65c3f298efb86e4869d3ca9/href">https://medium.com/media/3e918abfa65c3f298efb86e4869d3ca9/href</a></iframe><p>We can now visit <a href="http://localhost:3000/posts/1">http://localhost:8080/dogs/</a> and <a href="http://localhost:3000/posts/1">http://localhost:8080/dogs/1</a> or <a href="http://localhost:3000/posts/1">http://localhost:8080/cats/</a> (etc.) and see our API working properly. We have created a very simple Node API!</p><p>If you want to develop this further and add more endpoints and functionality to your Node API, I recommend <a href="https://medium.com/javascript-in-plain-english/create-rest-api-web-services-using-node-js-and-express-js-with-crud-operations-ff790d6ae030">Ankit Maheshwari’s CRUD Rest API tutorial</a> from JavaScript In Plain English.</p><h3>Python and Flask RESTful</h3><p><em>Requirements: </em><a href="https://www.python.org/downloads/"><em>Python 3</em></a><em> and PIP installed</em></p><p>For starters, we are going to need to install <a href="https://flask-restful.readthedocs.io/en/latest/">Flask-RESTful</a> by running:</p><pre>pip install flask-restful</pre><p><a href="https://flask-restful.readthedocs.io/en/latest/">Flask RESTful</a> is a Python module that extends the functionality of the Python Flask module to help us build REST APIs quickly.</p><p>To get started, in a new Python project file, create an api.py file and import the following at the top:</p><pre>from flask import Flask<br>from flask_restful import Api, Resource</pre><p>We then have to create an instance of the Flask class and pass that to an instance of a Flask RESTful API:</p><pre>app = Flask(__name__)<br>api = Api(app)</pre><p>Next up, let’s create some lists to store our data:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/462cb9261f01d6fcec9efb0170251d03/href">https://medium.com/media/462cb9261f01d6fcec9efb0170251d03/href</a></iframe><p>Now on to the more complicated stuff. According to the <a href="https://flask-restful.readthedocs.io/en/latest/">Flask RESTful documentation</a>, we need to create resource classes to define our HTTP methods. We have to create one resource for the list of cats/dogs and one for the individual ones (by ID):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc4c748e01ac88db918bce883cace27b/href">https://medium.com/media/cc4c748e01ac88db918bce883cace27b/href</a></iframe><p>To actually add these resources to be endpoints for our API, we are going to use the add_resource() method and pass in our resources and the respective endpoints we want those resources to be accessed from:</p><pre>api.add_resource(DogList, &#39;/dogs&#39;)<br>api.add_resource(Dog, &#39;/dogs/&lt;int:dog_id&gt;&#39;)<br><br>api.add_resource(CatList, &#39;/cats&#39;)<br>api.add_resource(Cat, &#39;/cats/&lt;int:cat_id&gt;&#39;)</pre><p>And finally, we add this line at the end of the file:</p><pre>if __name__ == &#39;__main__&#39;:<br>    app.run(debug=True)</pre><p>Here, we are enabling Flask debugging mode when we run our code so it reloads when changes are made (like nodemon) and gives us more verbose error messages when things go wrong.</p><p>Now, if you try <a href="http://localhost:5000/dogs">http://localhost:5000/dogs</a>, <a href="http://localhost:5000/dogs">http://localhost:5000/</a>cats, <a href="http://localhost:5000/dogs">http://localhost:5000/dogs/1</a>, etc., you will see your API working perfectly!</p><p>If you’d like to develop your Python Flask API project further, I recommend <a href="https://rapidapi.com/blog/how-to-build-an-api-in-python/">RapidAPI’s guide on Python APIs</a>.</p><h3>Conclusion</h3><p>And there you have it: REST APIs three different ways! I hope this article helps you get started in developing your own API.</p><p>All the example files for these three methods can be found <a href="https://github.com/elletownsend/create-an-api">on GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f99f7fb739b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/3-ways-to-create-your-own-api-f99f7fb739b1">3 Ways To Create Your Own API</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Beginner Blogging Mistakes]]></title>
            <link>https://elletownsend.medium.com/5-beginner-blogging-mistakes-334d6fbb1e34?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/334d6fbb1e34</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[blogging-tips]]></category>
            <category><![CDATA[blogging-mistakes]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[tech-blogging]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 23 Jan 2021 11:03:37 GMT</pubDate>
            <atom:updated>2021-01-23T11:03:37.570Z</atom:updated>
            <content:encoded><![CDATA[<h4>Mistakes I made when starting my blog, and the things you can do to avoid them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EjQa0l0EHXbCv-39" /><figcaption>Photo by <a href="https://unsplash.com/@domenicoloia?utm_source=medium&amp;utm_medium=referral">Domenico Loia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are so many things I wish I knew when I started blogging, and I definitely made a fair few mistakes starting out. Looking back after a whole year of consistent blogging, I wanted to give some insight into 5 mistakes I made when I first started my blog (and tips on how to avoid them).</p><h3>Be Original &amp; Be Yourself</h3><p>It’s easy when you first start out to slip into creating content that imitates popular trends or writers with thousands of reads.</p><p>Reading the work of others is a great way to pick up new writing techniques and popular blog formatting styles. However, there is a huge difference between writing about similar content or topics and outright copying, and you should be aware of the difference and make sure to keep yourself in check.</p><p>Exploring and finding your own writing style has a much higher pay off than copying those of popular bloggers, so it’s important to give yourself the time and space to practice your own writing style (which is something I regret not giving myself the time to practice).</p><h4>Try:</h4><ul><li>Read 5 articles / blog posts and make notes on what you enjoy about the post or the writer’s style or formatting.</li><li>When writing your next post, have these points in mind, but don’t let yourself copy them exactly, use them to add to your own style and enhance how you would normally write a new post.</li></ul><h3>Be Prepared</h3><p>Hands down the one thing that allowed me to write two blog posts (almost) every month last year was adequate preparation. Planning consistent content uploads is key to keep readers interested. It also helps in the long run, allowing you to write your posts and proof-read them way in advance of posting, giving you lots of time to tweak and perfect them.</p><h4>Try:</h4><ul><li>Create an upload schedule for when you are going to post, be sure to put it in your calendar so you don’t forget.</li><li>Brainstorm some topic ideas for upcoming blog posts.</li></ul><h3>Don’t Be Afraid To Shout About Your Work &amp; What You’re Doing</h3><p>When I started my blog, I was <strong>so</strong> shy to share my work. I think the feeling that people would “make fun of me” for it (as if we were back in school) got the better of me for quite a while.</p><p>In order to banish these feelings of inadequacy, find a community or a group you can join where you can share your work to people you think might like to read it. If you write a tech blog, find a supportive tech community that has the space for members to share created content.</p><h4>Try:</h4><ul><li>Every time you publish a new post, share it out on social media with a little introduction to the post as a call to action for people to read more.</li><li>At the same time, share a link to your new post in a tech community slack or discord (in either a blog sharing channel, or a space where self-promotion is acceptable).</li></ul><h3>Don’t Try To Be Trendy For The Sake Of Popularity</h3><p>You will burn out trying to copy &amp; stay up to date with the fleeting trends that fly through the tech scene.</p><p>Instead, invest time into writing about topics you enjoy or find interesting, and if it so happens that those topics align with those that are trending, it’s a happy coincidence. Don’t force yourself to write about a topic just because it is trending, write about things that you would actually want to read about.</p><h4>Try:</h4><ul><li>Write a list of 5 topics you want to write about.</li><li>Take a look at the front-page of Medium or Hackernoon, what topics can you see? Do any overlap with your starting 5?</li></ul><h3>Have Fun, Don’t Take Yourself Too Seriously</h3><p>Creating your blog should be a fun project in which you can really explore and experiment. If you’re thinking about starting a blog, the most important thing is to enjoy what you’re doing. With blogging, you have the opportunity to explore new topics, learn new things and share your thoughts with the world. Make the most of it and don’t take it too seriously.</p><p>I hope these tips will help you if you’ve just started blogging, or maybe even encourage you to start if you haven’t already! Hopefully you can learn from my mistakes and avoid these blogging pitfalls.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=334d6fbb1e34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Celebrate The Little Wins ]]></title>
            <link>https://elletownsend.medium.com/celebrate-the-little-wins-dbec573303d5?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbec573303d5</guid>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[new-years-resolutions]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 09 Jan 2021 11:03:11 GMT</pubDate>
            <atom:updated>2021-01-09T11:03:11.209Z</atom:updated>
            <content:encoded><![CDATA[<h4>When Setting Goals, Bigger Isn’t Always Better</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bKWko4-vK8Tnd7Bh" /><figcaption>Photo by <a href="https://unsplash.com/@socialcut?utm_source=medium&amp;utm_medium=referral">S O C I A L . C U T</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As we make a start to the new year, many people will begin with setting goals for the year ahead. While I am all for dreaming big and laying foundations for what you want to achieve in the next 365 days, putting big expectations on yourself and holding yourself to big picture goals can actually be holding you back.</p><p>When it comes to outlining what you want to accomplish, having big goals is a great motivator, and they can help you stay focused and guide you towards where you want to be. However, if we only work towards one singular north star, this can sometimes hinder progress.</p><p>Instead of setting a small number of large goals (Get promoted, get a new job, write a book, big picture things), try splitting your goals into bite-size mini-goals (Pass a progress review, ace a practice interview, write 500 words a day, etc). ‘<em>Microproductivity</em>’ is the way in which we can break a large goal into small, approachable tasks, make mountains feel a lot more like mole-hills, and unlock more potential for regular feedback. And regular feedback boosts motivation 🚀</p><p>One of the biggest reasons why we lose motivation is because we aren’t seeing results. We aren’t seeing progress fast enough or often enough. This is where your mini-goals shine. Smaller, short-term goals that can be achieved on a more frequent basis mean there is so much more to celebrate. Instead of the delayed gratification of working for an entire year or more to accomplish one mega goal, celebrate the little wins and everything you have achieved in the process of accomplishing each mini goal on the path to the major goal you set yourself.</p><p>Write down and make a note of each goal you complete and each new feat you achieve. Document all your achievements, no matter how small they may seem. Then, if at any point you start feeling like your aren’t getting anywhere, or that you don’t feel good enough, bring out that good old Book of Wins (yes, we’re calling it that) and celebrate yourself and just how far you really have come to achieving your goals, and all the brag-worthy things you have accomplished! With a whole bunch of mini goals on your completed list, you are bound to feel so much more productive and a whole lot better about your progress.</p><p>Now, go! Set those goals and start celebrating all of your little wins!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbec573303d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Things I Learned In My First 100 Days as a Developer]]></title>
            <link>https://medium.com/swlh/5-things-i-learned-in-my-first-100-days-as-a-developer-6ed4849c86?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ed4849c86</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[5-things-i-learned]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Sat, 19 Dec 2020 10:47:48 GMT</pubDate>
            <atom:updated>2020-12-21T18:00:27.895Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 Things I Learnt in My First 100 Days in Tech</h3><h4>Stay curious, stay focused, stay true to yourself. 5 Important learnings from my first 100 days in tech.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HTiIjBKtRv9Gi0Id" /><figcaption>Photo by <a href="https://unsplash.com/@silvawebdesigns?utm_source=medium&amp;utm_medium=referral">Nathan da Silva</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In September, I took my next step and started my first job in tech. As of this December, I will have officially been “in” the tech industry for 100 days. Here are the 5 most important things I learnt in my first 100 days in tech.</p><h4>There Is Always Something More To Learn</h4><p>I can be quite a shy person at times, but this is usually only to my own detriment. Starting out in your first job in tech, don’t be afraid to speak to people, be curious and ask questions. If you’re starting as a junior, nobody should expect you to be an expert, so being shy and not asking questions won’t get you anywhere. Ask why does it work like that? Why do we do that in this way? You are new to the team and how they work, so ask the other experienced developers. They are a great source of information, and it’s a perfect way to get to know the people on your new team.</p><h4>Make A Note Of Everything</h4><p>In my first 100 days, I wrote down practically everything new I found out, whether that be a new principle or use of technology, or new information about the business, I wrote down just about everything I could and kept it in a notebook dedicated to work related things. This way, I have a huge knowledge base I can refer back to at any point, which can be a great resource, especially for manager meetings or performance reviews. I also keep a note of people I’ve met with and information about them and what we have talked about, just in case I need to refer back to anything.</p><h4>Make The Most Of Opportunities (But Don’t Spread Yourself Too Thin)</h4><p>A great way to open up new doors in your new jobs is to get stuck in and involved with new opportunities. If you’re starting as part of a programme or graduate scheme, there is bound to be oodles of activities that you could get involved with, and hopefully you will get to know exactly what is going on in your organisation and what you can partake in. I’ve been very lucky to have so many opportunities to get involved with activities outside of my day-job within work. However, please keep your wellbeing in mind, and stay within your capacity. You don’t want to burn yourself out by spreading yourself too thin by committing to too many things inside &amp; outside of work.</p><h4>Get Out Of Your Comfort Zone</h4><p>When you’re starting your first job, or starting a new job at a new company, nerves are bound to be at an all time high. There will be so many opportunities to try new things, meet new people, and learn a lot about your business area and technology stack. It’s easy to stay within your comfort zone and shy away from new things or situations. But you can’t grow if you confine yourself to your comfort zone. I’ve found it so rewarding to jump on new opportunities to learn and grow, even if it might be a bit of a nerve wracking experience, like giving a presentation to a large meeting of people. Try it, you never know what might come of it.</p><h4>There Is So Much Out There, You Will Find Where You Shine One Day</h4><p>In my first 100 days in tech, I have gotten a glimpse into so many new concepts and topics, I’ve had a go at everything from DevOps, to project management, to unit testing and new coding languages. All in the space of 3 months. What I’ve learnt from this is that it’s completely okay if you aren’t quite sure what specific area within tech you want to work in. There are so many different job roles, areas of technology and skills you can learn that you don’t have to find your dream job straight away and stick to it for the rest of your career. Explore, try new things, take opportunities to learn new tech and honestly explore what <strong>you </strong>enjoy and what motivates <strong>you</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ed4849c86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/5-things-i-learned-in-my-first-100-days-as-a-developer-6ed4849c86">5 Things I Learned In My First 100 Days as a Developer</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Accessing APIs]]></title>
            <link>https://codeburst.io/the-art-of-accessing-apis-bf1a25338fac?source=rss-59cd7a0d5caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf1a25338fac</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Elle Townsend]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 20:45:40 GMT</pubDate>
            <atom:updated>2020-12-04T21:29:02.911Z</atom:updated>
            <content:encoded><![CDATA[<h4>Everything you need to know to become a master of APIs.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7W5QT3FO0y_kpcBJ0rbsA.png" /></figure><p>APIs are incredibly powerful and exciting tools that make up a large part of modern technology. Knowing what they are and how to use them is a vital skill that every developer should have in their arsenal.</p><h4>What is an API?</h4><p>Put plainly, an <strong>API</strong> (or <strong>‘<em>Application Programming Interface’</em></strong><em>) </em>is an intermediary software that allows for communication between two applications. Think of them like a waiter; you sit down at a restaurant and order some food from the menu (you are an application), you convey your order request to the waiter (the API), who then communicates your request for food (data) to the kitchen (the second application). When your food (data) is ready, the waiter (the API) brings it straight to your table. That’s exactly what an API does — manages requests for data and responses between two applications.</p><p>There are a bunch of APIs out there (I listed <a href="https://www.elletownsend.co.uk/blog/posts/top-5-apis/">my favorites here</a>, and there is a great <a href="https://github.com/public-apis/public-apis">list of free public APIs here</a>). While there is no end to the streams of ideas and projects that could stem from utilizing these APIs, if you want to start getting into the wonders of consuming data from APIs then you should read on to learn how to use them.</p><p>In this blog post, I set out to share my love of APIs with you and cover how to use them.</p><h3>Some Things To Note</h3><p>There are a few nuances to explore when it comes to approaching APIs for the first time. When APIs are created, they can be secured using forms of authentication and unique codes that identify who is calling the API. These are put in place so that the owners of the API can keep track of who is using and/or consuming from the API, thereby preventing malicious use and abuse. The API that you plan to use will determine what you will need to do in order to get access. Most APIs will require you to register for an API key and use this as an identifier for every call that you make to the API. <strong>Note: see below for a brief on API keys.</strong></p><p>Secondly, API owners sometimes enforce a limit on the number of requests that can be made to the API in a given time-frame in order to prevent users from overwhelming the service. This is called a ‘rate-limit’, and it varies from API to API.</p><h3>Documentation is a Dev’s Best Friend</h3><p>You might be thinking, Elle, this is quite a lot of information I need to gather before I access an API. Where am I supposed to find it all? Well, I would advise you to get familiar with the API’s <strong>documentation</strong>. In the documentation of any API, the developers should detail how to get an API key, what the rate limit is (if there is one), and information on the API’s <strong>endpoints</strong>.</p><p>When accessing an API, the place that your request is sent to (and where the response is received) is called an ‘endpoint’. API endpoints come in the form of URLs and, depending on what kind of request you are trying to make or what data you want back, the API documentation should point you to the endpoint that you are looking for.</p><p>For example, the endpoint of the <a href="https://swapi.dev/">Star Wars API</a> that has all the data on films is:</p><p>https://swapi.dev/api/films/</p><p>and making a request to this endpoint returns information on all Star Wars films.</p><h3>Know What You’re Asking For</h3><p>The most important thing to consider when writing and debugging your API requests (“Why is this not working?” “I know it’s there, why is it undefined?”) is what the response you are expecting <strong>looks like</strong>. The best places to find this out are the API documentation or good old console.log the response and take a look yourself. As you will see in the following code examples, no two APIs are exactly the same and so the way you access the data from their respective responses will be different too. These little nuances will be the root of lots of your API problems and debugging but now you know where to look, you should be able to find out how to access that data and use it in your applications.</p><p>Now, onto the good stuff…</p><h3>Making Requests</h3><h4><strong>Search for a Star Wars character by name — (API without an API Key)</strong></h4><p>Endpoint: https://www.swapi.tech/api/people/ , Query Parameters: name = &quot;r2-d2&quot;.</p><p><strong>Example (JavaScript &amp; Axios):</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/00cd31a1ea6783f4c26998077fa55782/href">https://medium.com/media/00cd31a1ea6783f4c26998077fa55782/href</a></iframe><p><strong>Example (Python):</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b53b9e4ac8d1e7db253c57f71660254a/href">https://medium.com/media/b53b9e4ac8d1e7db253c57f71660254a/href</a></iframe><h4><strong>Search for a Movie by title — (API with an API Key)</strong></h4><p>Endpoint: https://api.themoviedb.org/3/search/movie, Query Parameters: query = &quot;Harry Potter&quot;.</p><p><strong>Example (JavaScript &amp; Axios):</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f399b7ec779c7f02bdf46a7eedd850e2/href">https://medium.com/media/f399b7ec779c7f02bdf46a7eedd850e2/href</a></iframe><p><strong>Example (Python):</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/709a4a9eed19688e1cf05404902ba72b/href">https://medium.com/media/709a4a9eed19688e1cf05404902ba72b/href</a></iframe><h3>A Note on API Keys</h3><p>If you’re using an API that requires an API key, <strong>please </strong>keep that key a secret. If you’re not planning on uploading your code or hosting your project publicly, you should be fine, but if you are going to upload it to GitHub or host it live then take these steps to keep your API key secret.</p><h4><strong>In JavaScript (React)</strong></h4><p>In your project folder, create a file called .env (a file where we can store environment variables). In this file on the first line, you’re going to want to type REACT_APP_API_KEY= and then paste your API key. No quotes, no ;</p><p>Then when you want to use this environment variable in your code, refer to it using process.env.REACT_APP_API_KEY instead of a string containing your API key. Don’t forget to also add your .env file to your .gitignore.</p><h4><strong>In Python</strong></h4><p><a href="https://medium.com/dataseries/hiding-secret-info-in-python-using-environment-variables-a2bab182eea">https://medium.com/dataseries/hiding-secret-info-in-python-using-environment-variables-a2bab182eea</a> — This is a great tutorial blog post on using environment variables in Python.</p><h3>Conclusion</h3><p>As covered earlier, APIs are a great tool to understand and implement. This article has set out to provide an overview of what APIs are, examples of popular APIs, and a brief tutorial on how to make requests. I hope that this article has been helpful, thanks for reading!</p><h4>Resources</h4><ul><li>Using Axios — <a href="https://blog.logrocket.com/how-to-make-http-requests-like-a-pro-with-axios/">https://blog.logrocket.com/how-to-make-http-requests-like-a-pro-with-axios/</a></li><li>List of lots of APIs — <a href="https://github.com/public-apis/public-apis">https://github.com/public-apis/public-apis</a></li><li>The Movie DB API — <a href="https://www.themoviedb.org/documentation/api">https://www.themoviedb.org/documentation/api</a></li><li>Star Wars API — <a href="https://www.swapi.tech/">https://www.swapi.tech/</a></li><li>Using environment variables in React — <a href="https://medium.com/better-programming/using-environment-variables-in-reactjs-9ad9c5322408">https://medium.com/better-programming/using-environment-variables-in-reactjs-9ad9c5322408</a></li><li>Using environment variables in Python — <a href="https://medium.com/dataseries/hiding-secret-info-in-python-using-environment-variables-a2bab182eea">https://medium.com/dataseries/hiding-secret-info-in-python-using-environment-variables-a2bab182eea</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf1a25338fac" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/the-art-of-accessing-apis-bf1a25338fac">The Art of Accessing APIs</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>