<?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 Tuyet Le on Medium]]></title>
        <description><![CDATA[Stories by Tuyet Le on Medium]]></description>
        <link>https://medium.com/@tuyet-le?source=rss-5488d6b287d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kaZPTN8VJf6PKRBIfUVy8g.jpeg</url>
            <title>Stories by Tuyet Le on Medium</title>
            <link>https://medium.com/@tuyet-le?source=rss-5488d6b287d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:40:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tuyet-le/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[Makers DevOps Bootcamp: Week 4 — Implementing Infrastructure as Code using Terraform to deploy an…]]></title>
            <link>https://tuyet-le.medium.com/makers-devops-bootcamp-week-4-implementing-infrastructure-as-code-using-terraform-to-deploy-an-82c7f9b4af1a?source=rss-5488d6b287d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/82c7f9b4af1a</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Tuyet Le]]></dc:creator>
            <pubDate>Wed, 07 Apr 2021 18:09:21 GMT</pubDate>
            <atom:updated>2021-04-07T19:59:13.125Z</atom:updated>
            <content:encoded><![CDATA[<h3>Makers DevOps Bootcamp: Week 4 — Implementing Infrastructure as Code using Terraform to deploy an application on Azure</h3><p><em>(My reflection of week three is </em><a href="https://tuyet-le.medium.com/makers-devops-bootcamp-week-3-learning-github-actions-with-a-focus-on-aws-262d2d4b3d3e"><em>here</em></a><em>.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GtiqbVfBh-g_MKfNDLW8EA.jpeg" /></figure><p>We’re over the halfway mark of the DevOps Bootcamp and I’m liking this DevOps thing so far!</p><h3>Overview</h3><p>In week four, the focus was to understand the concept of Infrastructure as Code (IaC) using Terraform and to deploy an application to Azure. The main goals to achieve by the end of the week were:</p><ul><li>to be able to explain what Infrastructure as Code (IaC) is;</li><li>to create a Github Actions automatic workflow to build and manage the project infrastructure using Terraform;</li><li>to set up a Github Actions CI/CD workflow to deploy an application to the infrastructure on Azure we created using Terraform;</li><li>to be a better DevOps engineer than the day before;</li><li>to have fun!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*BnLV95XCNQ6NDDOZEmL8tQ.gif" /></figure><h3>Infrastructure as Code</h3><h4>What is Infrastructure as Code?</h4><p>The name intimidated me at first but it’s exactly what the name suggests. IaC in the world of DevOps is writing multiple simple lines of code to provision and manage infrastructure i.e. servers, network interface, data storage, databases, etc., and automating the infrastructure deployment process. It’s essentially a programmable IT environment.</p><p>There are many benefits to implementing IaC especially when you compare it to the old manual process of how IT infrastructure is provisioned traditionally. Before the world of cloud services, humans would have to physically stack servers, manually configure the hardware to the requirements of the operating system and the application being hosted, and then finally deploy the application to the hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6BqmdNiOxPv9wNjNuhZDVg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ismailenesayhan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">İsmail Enes Ayhan</a> on <a href="https://unsplash.com/s/photos/servers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Thanks to IaC, these tasks can now be automated in one or more code files with the option to version control the infrastructure code.</p><h4>Terraform</h4><p>To grasp the concept of IaC, we got to learn one of IaC’s popular tools, <a href="https://www.terraform.io/">Terraform</a>, and build our own infrastructure configuration files. Terraform is an infrastructure automation tool created by HashiCorp. It can be used to define the initial setup of the infrastructure on any cloud provider (AWS, Azure, Google Cloud, etc), maintain the infrastructure and also the initial setup of the application.</p><p>I think of Terraform’s job as a tool that deploys a server, but not what’s on it.</p><h3>Building our first Infrastructure as Code on Azure using Terraform</h3><p>Azure is another popular cloud service provider by Microsoft so it was a good opportunity to see how it compares with AWS.</p><h4>Setting up Azure resources:</h4><ul><li><strong>Azure Resource Group</strong> — Before diving into using Terraform to set up an infrastructure for our application, we first needed to create an Azure Resource Group. An Azure Resource Group is a container that will hold all of the different Azure resources that we’ll later create as part of the Azure solution for our application.</li><li><strong>Azure Storage Account for Terraform State — </strong>We created an Azure Storage Account with a Blob container as the first resource to go under the resource group. The container will hold the Terraform state as a Blob, which is Microsoft’s object storage solution for the cloud. A Terraform state contains information about what infrastructure and related configuration are managed by Terraform. Every time the infrastructure is updated, Terraform will compare the current code (the current state) with its last known state (the file that’ll be saved in the Blob storage container).</li><li><strong>Azure Service Principal — </strong>The next Azure service we created was an Azure Service Principal. This creates an identity to enable Terraform to run on Github Actions and link it with Azure resources.</li></ul><h4>Getting started with Terraform</h4><p>Before Terraform can do anything useful, we first needed to create an initial Terraform configuration file in a separate project directory. This file specifies that we’d like to use the Azure Provider, which will give us access to the Microsoft Azure’s resources using the Azure Resource Manager’s (ARM) API. ARM is an Azure service that manages and deploys resources using IaC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XEPLVN6nLcsYf58R-07Jnw.png" /><figcaption>Our first Infrastructure as Code configuration file</figcaption></figure><p>A great thing about Terraform is that it’s written in declarative code, meaning all you do is simply define what infrastructure you want and Terraform will figure out how to get to that end state for you.</p><p>To initialise the Terraform configuration, we ran the ‘<strong>terraform init</strong>’ command in the terminal. After initialising, we were then able to run ‘<strong>terraform plan’</strong> which creates an execution plan to tell Terraform what the desired state is, and lastly <strong>‘terraform apply’</strong> to carry out the current execution plan.</p><p>And voila — after applying the changes, we could see that the Blob had been updated with the new Terraform state in our Blob container within the Blob storage account on Azure.</p><h4>Time for automation</h4><p>We wouldn’t be following DevOps best practices if we didn’t automate the manual process of creating our Terraform configuration! Applying what we learnt about Github Actions last week, we created two workflows that would automate our IaC.</p><ul><li><strong>terraform-plan.yml </strong>— this workflow triggers after every pull request to the main branch. The main jobs it will carry out are to check the formatting of the Terraform configuration file, followed by the initialisation and creation of the execution plan (just like before).</li><li><strong>terraform-apply.yml</strong> — this workflow will only run after the successful completion of the first workflow. This will apply the new Terraform changes to reach the desired state when merging into the main branch.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8YOfNbvdywjbD9Bis-Xmg.png" /><figcaption>A snippet of our team’s first workflow</figcaption></figure><p>The output that we got when creating our Azure Service Principal earlier came in handy here. Setting the ARM Client ID, ARM Client Secret, ARM Subscription ID and ARM Tenant ID as environment variables enabled our Terraform workflows to link with Azure.</p><h4>Adding more Azure resources to our infrastructure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MetqmGdGDmMnCLR8NDAIwA.png" /><figcaption>Application architecture</figcaption></figure><p>Like in previous weeks, our coach provided an application for our team to use. Our main task was to deploy that application to the infrastructure we just created on Azure using Terraform.</p><p>But first, as the above diagram shows, we first needed to create the additional Azure resources under our existing Azure Resource Group so that our application can deploy to Azure successfully. Continuing with Terraform, we could set this up by creating additional configuration files to our existing Terraform project directory.</p><p>The Azure resources to create were:</p><ul><li><strong>Azure Container Registry (ACR)</strong> — this will contain the dockerised application image</li><li><strong>Azure Web App Service</strong> — this is an HTTP-based hosting service where we will deploy the application</li><li><strong>Azure PostgreSQL server</strong> — a server for our PostgreSQL database</li><li><strong>Azure PostgreSQL database</strong> — an Azure Database for PostgreSQL</li></ul><p>We separated the Azure resources into separate Terraform configuration files in addition to the initial infrastructure setup file ‘<strong>main.tf</strong>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*A3gVrZ0LIzdu1FOAlFv_Hw.png" /><figcaption>Terraform IaC configuration files</figcaption></figure><p>The Terraform syntax to define new resources is pretty straight forward to understand. To create an Azure Container Registry, it is represented like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCj1UV5NhvnzCghB_jOTig.png" /><figcaption>Code snippet of acr-create.tf</figcaption></figure><ul><li><strong>resource </strong>— this keyword tells Terraform that we are about to define a resource.</li><li><strong>azurerm_container_registry</strong> — this defines the resource type that correlates to the infrastructure element to create on the cloud service provider. In this case, we created an Azure Container Registry.</li><li><strong>acr</strong> — this is the resource name that Terraform will use.</li><li><strong>name</strong>,<strong> resource_group_name</strong>, <strong>location</strong> and<strong> SKU</strong> — everything inside the curly braces are arguments we pass to let Terraform know what we want to create concerning that resource.</li></ul><p>We created two more configuration files <strong>‘pg-create.tf’</strong> and <strong>‘web-app-create.tf’</strong> to create our PostgreSQL and Azure Web App Service respectively.</p><p>Once we merged our updated IaC working directory to apply the changes, we could see that all of the new Azure resources under our Azure Resource Group on the Azure portal. 🎉</p><h3>Deploying the application to Azure</h3><p>Now that we have our infrastructure set up on Azure thanks to our Terraform configuration files, we were ready to deploy the application onto the infrastructure. We first needed to update the CI-CD pipeline in the application itself with our Azure credentials so that after every pull request and push made on the main branch, the application is containerised and deployed to Docker and our container registry on Azure.</p><p>After hours of debugging with further configurations on our Azure resources and the application code itself, we could finally see our application live on Azure, which was a task listing app! 🎉</p><h3>Reflections</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yWa1tLWcCgKJKw0RJKSn0Q.jpeg" /></figure><p>I wanted to go into week 4 being more kinder to myself by putting less pressure to understand new concepts immediately and set realistic learning goals for myself. It paid off because I had fun and developed a good high-level understanding of what IaC and Terraform are, which were my two main focus of the week. I’m excited to continue learning more about configuration management and Terraform specifically in the future.</p><p>It was also a good week of consolidating the method of CI/CD and automating manual processes using Github Actions. Being able to learn Azure and seeing how it compares with AWS was also interesting. To my surprise, its capabilities are similar and navigating on the Azure portal was relatively straight forward.</p><p>As a team, we went through many debugging sessions throughout the week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*jsHK6Phh44GoeXss1WaoMg.gif" /></figure><p>These sessions helped improve my confidence in reading error logs, get comfortable with shell scripting and researching for the right documentation to debug the errors.</p><p>We’re now on the final stretch of the DevOps Bootcamp with our final two-week project left to go. We’ll be working on solving common Site Reliability Engineering issues in a live application!</p><p>Thanks for reading 😁</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82c7f9b4af1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Makers DevOps Bootcamp: Week 3 — Learning Github Actions with a focus on AWS]]></title>
            <link>https://tuyet-le.medium.com/makers-devops-bootcamp-week-3-learning-github-actions-with-a-focus-on-aws-262d2d4b3d3e?source=rss-5488d6b287d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/262d2d4b3d3e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[makers]]></category>
            <dc:creator><![CDATA[Tuyet Le]]></dc:creator>
            <pubDate>Thu, 25 Mar 2021 08:33:24 GMT</pubDate>
            <atom:updated>2021-03-25T08:33:24.748Z</atom:updated>
            <content:encoded><![CDATA[<h3>Makers DevOps Bootcamp: Week 3 — Learning Github Actions with a focus on AWS</h3><p><em>(My reflection of week two is </em><a href="https://medium.com/codex/makers-devops-bootcamp-week-2-building-our-first-serverless-ci-cd-with-jenkins-and-aws-f2e9f8210031"><em>here</em></a><em>.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ZRJUFz0zm1eAoLhtE3chw.jpeg" /><figcaption>Github and AWS</figcaption></figure><p>It’s week three! I can’t believe we’re already halfway through the DevOps Bootcamp! 🤯</p><h3>Overview</h3><p>In week three, we continued to practise building our own CI/CD pipeline but this time using Github Actions instead of Jenkins. The main goals of the week:</p><ul><li>to build a CI/CD pipeline using Github Actions;</li><li>to deploy a containerised Node.js/Express application on AWS EC2 using our own CI/CD pipeline;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VKKy1fuN7fje_Fq6nzhDKQ.png" /><figcaption>This week’s project architecture</figcaption></figure><ul><li>to develop an understanding of IAM in AWS;</li><li>to be a better DevOps Engineer than the day before;</li><li>to have fun!</li></ul><p>ℹ️ It was also emphasised to learn and understand the concepts rather than to rush the tasks to finish the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/0*wbkagA1tZA_vRDpa.gif" /></figure><h3>Using Docker to containerise our app</h3><p>Similar to last week’s team project, we were given a Node.js web application to work with, enabling us to focus mainly on the pipeline and using AWS.</p><p>We kicked off the project by applying what we’d learnt about containers and Docker from <a href="https://medium.com/codex/makers-devops-bootcamp-week-1-devops-containers-and-aws-elastic-beanstalk-601ce285c616">week one</a> to dockerise our application using a Dockerfile and push the new image to Docker Hub. It was great to see that we could do this part with more ease after only being introduced to Docker two weeks ago!</p><p>We also pushed our application with the Dockerfile to a Github repository.</p><h3>Building a CI/CD pipeline with Github Actions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*4o_FM5OPnUhMkYSX.gif" /></figure><h4>What’s Github Actions?</h4><p>Like Jenkins, Github Actions is another popular CI/CD tool (but newer) that simplifies automation within the software development life cycle including running builds, executing tests, packaging an app and deploying. Github Actions is event-driven so the tasks will only trigger after a particular event takes place on the repository i.e. a pull request or a merge to the main branch.</p><p>To set up these tasks, a workflow file written in YAML needs to be created in the project repository inside the <em>.github/workflows</em> folder. A workflow has to contain one or more jobs consisting of steps that each run a command for a specific task. Each step can be defined using a shell command or an action — we can create our own action or use an action already created by the Github team or other companies in the <a href="https://github.com/marketplace">Github Marketplace</a>.</p><h4>Our workflow steps:</h4><ul><li>Setup a CI job to run the unit tests, Cypress test and Lint test after every push to the main branch</li><li>Generate a new image of the application after each successful build</li><li>Deploy the new image to Docker Hub</li><li>Add a CD workflow to deploy the containerised app to an AWS S3 Bucket to be then deployed on an AWS EC2 instance via AWS CodeDeploy</li></ul><p>In Github Actions, it’s possible to execute a workflow only after a separate workflow has completed. This is possible to set up by using <em>workflow_run</em> to configure the jobs (this <a href="https://stackoverflow.com/questions/62750603/github-actions-trigger-another-action-after-one-action-is-completed">StackOverflow page</a> explains how this is done well).</p><p>We created three Github Actions workflows: <em>test.yml</em>, <em>build.yml</em> and <em>deploy.yml</em>.</p><ul><li><strong>test.yml </strong>— this CI job executes first after every push to the main branch. All tests should pass before building a new image.</li><li><strong>build.yml </strong>— this next CI job executes after all the test in the previous build has successfully passed. It will build a new application image and upload it to Docker Hub.</li><li><strong>deploy.yml</strong> — this final CD workflow defines the deployment job to deploy the containerised app to AWS.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-MUdaTDKt15FGqThOBszw.png" /><figcaption>A snippet of our team’s test workflow</figcaption></figure><p>A cool thing with Github Actions is that it provides you real-time feedback into the progress of the steps in a sequential order with clear error messages if any, and green ticks for each passed step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y8VTUz8EjlG-z2MEkN7wfA.png" /><figcaption>Real-time feedback of a build</figcaption></figure><h3>Learning new AWS Services — IAM and CodeDeploy</h3><p>Once we completed building our CI workflows, it was time to move on to setting up several AWS services to complete the CD workflow and get our containerised app deployed to EC2.</p><p>So far in the Bootcamp, the AWS services we’ve covered are S3 Buckets, EC2, Elastic Beanstalk, Lambda and Amazon API Gateway. It was time to add AWS IAM and AWS CodeDeploy into the mix as part of the last two sections of the project architecture. A summary of what both services do:</p><h4>AWS IAM</h4><ul><li>IAM stands for Identity and Access Management</li><li>It’s a feature that allows you to manage access to AWS services and resources securely</li><li>You can create users and groups, and set permissions to allow or deny their access to specific AWS services</li></ul><h4>AWS CodeDeploy</h4><ul><li>A deployment service that automates software application deployments to various compute services including EC2 instances</li><li>It can deploy applications that are stored in S3 buckets or Github repositories</li><li>It eliminates the need for error-prone manual operations</li></ul><p>The remaining steps to do on AWS to automate the deployment job were:</p><ul><li>Create an EC2 instance with the correct IAM roles assigned to it so it can communicate with CodeDeploy and the S3 bucket</li><li>Setup CodeDeploy to deploy the application from the S3 bucket to EC2</li><li>Retrieve our team’s IAM Group’s Access Key and Secret Key with permission to read and write to S3 to enable us to add them to our Github Action deployment workflow so it can push the containerised app to S3 accordingly</li><li>Configure AWS Credentials Action for Github Actions</li></ul><h3>Reflection</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZfRP-47wuVJgtrr4XyHlgg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@matreding?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mathias P.R. Reding</a> on <a href="https://unsplash.com/s/photos/rainbow?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Learning Github Actions and understanding the YAML syntax to create workflows took some time meaning we didn’t have enough time to complete the last step of getting our CD workflow to deploy the containerised app to the EC2 instance.</p><p>Nonetheless, I have a better understanding of how different AWS services can connect together with CI/CD tools such as Github Actions to create an automated software development life cycle.</p><p>It was also a good week of consolidating what we’ve learnt so far over the last three weeks where I now feel more confident in navigating the AWS management console (which is by the way a beast!), using Docker and transferring my knowledge of CI/CD into a new tool— Github Actions. The ability to automate software builds, tests and deployments right from Github makes it, <em>in my opinion</em>, more appealing than Jenkins.</p><p>We’re moving away from AWS in week four to learn about another cloud computing service — Azure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=262d2d4b3d3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Makers DevOps Bootcamp: Week 2 — Building our first serverless CI/CD with Jenkins and AWS]]></title>
            <link>https://medium.com/codex/makers-devops-bootcamp-week-2-building-our-first-serverless-ci-cd-with-jenkins-and-aws-f2e9f8210031?source=rss-5488d6b287d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e9f8210031</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Tuyet Le]]></dc:creator>
            <pubDate>Tue, 16 Mar 2021 23:09:17 GMT</pubDate>
            <atom:updated>2021-03-19T01:12:33.945Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://medium.com/codex">CODEX</a></h4><h3>Makers DevOps Bootcamp: Week 2 — CI/CD, Serverless and more AWS</h3><p><em>(My reflection of week one </em><a href="https://tuyet-le.medium.com/makers-devops-bootcamp-week-1-devops-containers-and-aws-elastic-beanstalk-601ce285c616"><em>here</em></a><em>.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WI0s5fI_sU0_65j6hfHDbg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@billy_huy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Billy Huynh</a> on <a href="https://medium.com/s/photos/clouds?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We kicked off week two by diving straight into our new weekly team project and the goals were:</p><ul><li>to use AWS S3 Buckets to host a static website app;</li><li>to build our first CI/CD pipeline using Jenkins;</li><li>to deploy a static website with AWS Lambda and Amazon API Gateway;</li><li>to be a better DevOps engineer than the day before;</li><li>to have fun!</li></ul><p>By the end of the week, we should have a simple serverless website that’s deployed on AWS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHq58gHoGqUzg0j-32VM1A.jpeg" /></figure><p>The AWS ecosystem is HUGE so I was excited to learn more about other AWS services and continuous integration (CI) and continuous delivery/deployment (CD), which you often hear about in DevOps and modern software development practices.</p><h3>A summary of CI/CD</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*apeKCozAPxQl3TP9QqMSBA.gif" /></figure><p>CI/CD are practices that make up the fundamental architecture of DevOps enabling engineers to deliver software and better quality code faster.</p><h4>CI</h4><p>CI is a major step in the DevOps lifecycle. It’s the process of frequently merging developers’ code changes into a shared repository thanks to the help of automated testing. When developers make a merge pull request, it triggers a pipeline that automatically builds, tests and validates the code changes before merging into the repository. Adding test automation as part of the CI solution helps with identifying errors faster and ensures better quality builds.</p><h4>CD</h4><p>CD deploys that CI-validated code to the application. Continuous delivery is often used interchangeably with continuous deployment. The subtle difference between the two is that continuous delivery deploys the code into a staging environment where team members can play around with the application before it goes live to customers. Continuous deployment on the other hand automatically deploys the code straight to production.</p><h3>Creating an Amazon S3 Bucket</h3><p>Project time!</p><p>Before creating our first CI/CD pipeline solution, we first needed to create an S3 bucket on AWS and configure it to host our static website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*cDHe5Q_RDkNt_g-KKxZVcw.png" /><figcaption>AWS S3 Bucket</figcaption></figure><h4>What’s an Amazon S3 Bucket exactly?</h4><p>It’s a simple object storage service by Amazon that’s used to store and protect data for different use cases, such as images, text files, websites, mobile applications and more. It’s most commonly used to host static websites and often included in the automation pipeline where the app is deployed and directly hosted on the S3 bucket.</p><p>Our coach thankfully provided a simple app with a simple HTML file for us to work with so we didn’t need to spend time building a website, allowing us to focus on the main goals of the week.</p><h3>Setting up Jenkins on AWS</h3><p>Once we created our S3 bucket, it was time to learn about the popular CI tool, Jenkins, to build our CI/CD pipeline with and get it set up on an AWS remote server.</p><h4>What is Jenkins?</h4><p>Jenkins manages all types of automation including software building, application testing and deployment. To help visualise how Jenkins comes into play in CI/CD, I doodled the flow (apologies for the stickmen drawing 😅).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xahdcQd6_F3_j3XFeQmOAg.jpeg" /><figcaption>CI/CD pipeline with Jenkins</figcaption></figure><h3>Creating an Amazon EC2 instance and installing Jenkins on it</h3><p>Setting up Jenkins onto an AWS remote server, otherwise known as an EC2 instance, took a fair amount of time and research to understand and achieve. The Jenkins documentation on how to install <a href="https://www.jenkins.io/doc/tutorials/tutorial-for-installing-jenkins-on-AWS/">Jenkins on AWS</a> was a great resource we used that breaks down the steps clearly.</p><p>Here’s an overview of the steps we did on the AWS Management Console to set up an EC2 instance with Jenkins:</p><ol><li>Create a key pair —<em> this creates a set of security credentials consisting of a public and private key used for you to prove your identity when connecting to an EC2 instance</em></li><li>Create a security group —<em> this creates a virtual firewall for the EC2 instance to control incoming and outgoing traffic</em></li><li>Launch the EC2 instance</li><li>Connect to the EC2 instance using SSH from the command line</li><li>Download and install Jenkins onto the EC2 instance</li><li>Configure Jenkins that’s now installed on the EC2 instance by installing the recommended plugins, connecting it to our Github repository and setting up user access for all team members to access Jenkins <em>(note: we used the same key pair credentials for all team members)</em></li></ol><p>After completing these steps, we were able to get Jenkins working on our EC2 instance!</p><h3>Building our CI/CD pipeline (Jenkinsfile and Webhooks)</h3><p>You may be wondering now, how does our Jenkins instance know when a developer has updated the repository? Enter… Webhooks!</p><p>Webhooks allow you to set up integrations to provide other applications with real-time information when certain events are triggered. So in our case, when one of our team members makes a push or a merge pull request to the repository, webhook will send an HTTP POST request to our Jenkins instance. This then automatically triggers the CI build job on our Jenkins instance.</p><h4>Jenkinsfile</h4><p>We defined our pipeline by writing scripts in a Jenkinsfile. A Jenkinsfile is a text file written in <em>groovy</em> (what a fun name!) that’s created in the root directory of the project.</p><p>We implemented a very basic three-stage continuous delivery pipeline— build, test and deploy — with a script to print the ID of the build, to run the unit tests and to deploy the HTML files to our S3 Bucket respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rDOrlyH-jlTKTLOkDFRt_w.png" /><figcaption>Our very simple pipeline written in grooovy</figcaption></figure><p>The stages are executed sequentially so if our unit tests fail, the pipeline will not move on to the deploy stage.</p><p>After lots of configuration, and testing different scripts in the pipeline, our HTML files successfully deployed! 🎉</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q95LkkyI4ufv4uuvEfDR3w.png" /><figcaption>Home page</figcaption></figure><h3>Going serverless with AWS Lambda</h3><p>The last step was to get the button to change the monkey image as well as the text. Currently, the button doesn’t do anything when clicked.</p><p>We learnt that we could set up this functionality with AWS Lambda, which is a serverless service that allows you to run code based on the incoming request or event. A huge advantage of many serverless solutions including AWS Lambda is that it supports event triggers, making it great for pipelines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3dvVhsRPgrwlTPwPaTQwBw.jpeg" /><figcaption>We had a workshop to diagram what a serverless architecture looks like and how Amazon S3 can work with Amazon API Gateway and Amazon Lambda to achieve this</figcaption></figure><p>Minus the user authentication part of the diagram above, setting up the Amazon API Gateway and Amazon Lambda were the last pieces to add to create a serverless website.</p><p>We created a Lambda function to change the text of the HTML body when the user clicks on the button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwrzKJRof0-6OPMDRb5gFw.png" /><figcaption>Our Lambda function written in Python</figcaption></figure><p>To enable the S3 bucket to invoke the Lambda function when the user clicks the button, we first configured the S3 trigger in the Lambda console on AWS to enable it to send an event notification via an API Gateway. Next was to set up an HTTP API in the Amazon API Gateway and add the endpoint URL in our HTML file so that the request is properly sent to the Lambda function and returns the function’s response to the client.</p><p>Voila! Our button now works — it displays the new text and monkey photo!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_n5Bap10gknFMIkzhtIkCQ.png" /></figure><h3>Reflection</h3><p>The AWS ecosystem is huge and learning about how pipelines actually work was all mind-blowing 🤯</p><p>I enjoyed learning more about other popular AWS services including Lambda, EC2 and S3 bucket, and seeing how they all work together to host a simple website on a virtual server.</p><p>There were a lot of steps and time spent on setting up and configuring Jenkins before we could even start building our pipeline so it will be interesting to see how working with Github Actions, another popular CI tool, differs from working with Jenkins in the coming week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2e9f8210031" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/makers-devops-bootcamp-week-2-building-our-first-serverless-ci-cd-with-jenkins-and-aws-f2e9f8210031">Makers DevOps Bootcamp: Week 2 — Building our first serverless CI/CD with Jenkins and AWS</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Makers DevOps Bootcamp: Week 1 — DevOps, Containers and AWS Elastic Beanstalk]]></title>
            <link>https://medium.com/codex/makers-devops-bootcamp-week-1-devops-containers-and-aws-elastic-beanstalk-601ce285c616?source=rss-5488d6b287d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/601ce285c616</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[makers]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[Tuyet Le]]></dc:creator>
            <pubDate>Sun, 07 Mar 2021 19:39:41 GMT</pubDate>
            <atom:updated>2021-03-19T01:12:27.917Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="http://medium.com/codex">CODEX</a></h4><h3>Makers DevOps Bootcamp: Week 1 — DevOps, Containers and AWS Elastic Beanstalk</h3><p>Last week, we wrapped up the final week of the Makers software development apprenticeship bootcamp and presented our final group project to our peers and employers. The last 12 weeks have been intense but an incredibly rewarding experience learning to code with an amazing cohort who I now call friends. We’ve grown with newfound confidence, presenting like a boss and with new technical skills under our belt.</p><p>Although it’s not all over yet! For some of us, we still have another six weeks to go where we will complete Makers’ very first DevOps course and I couldn’t be more excited to be a part of it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ax0CXpmKtDYzoC-mhOitsQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@synkevych?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Roman Synkevych</a> on <a href="https://unsplash.com/s/photos/code?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Makers is all about self-directed learning and the structure of the DevOps bootcamp is no different. The course is six weeks of self-led learning, workshops and team projects with a curriculum that cover topics on DevOps best practices, containerisation, serverless, CI/CD, AWS, Azure, Infrastructure as Code and common issues in Site Reliability Engineering.</p><p>We kick off the first week by learning what DevOps is, why it matters in the software development world, how it works, how to use Docker to containerise a web application and an introduction to AWS.</p><h3>What’s DevOps exactly?</h3><p>It’s been a recent buzzword for many people but not everyone really knows what it is, including me so I was super excited to spend the first day learning about what it is exactly.</p><p>DevOps is not tied to a particular technology in software development. At a high-level, it’s a culture that combines new practices, new tools and new ways of thinking to bridge the gap between IT operations, software development and quality assurance. It combines agile software development practices and automation to the world of IT operations. With this approach, DevOps helps to reduce the software development life cycle (SDLC) enabling organisations to roll out new products and services more quickly in a secure and reliable way while also improving operations performance.</p><p>Traditionally, IT operations and software developers work separately but by combining the two teams together, DevOps engineers get exposure to the application’s entire lifecycle, from the planning stage to development and testing, to releasing the product, to customer feedback and to application enhancements based on that feedback.</p><p>Some of the main benefits of adopting the DevOps model:</p><ul><li><strong>Speed</strong> — automation is one of the pillars of DevOps meaning new features and updates are released faster enabling businesses to adapt to market changes more quickly.</li><li><strong>Rapid software delivery</strong> — with the increase in frequency of releasing new software, businesses are able to iterate on customer feedback more often, allowing for innovation and improved product releases.</li><li><strong>Reliability</strong> — automated tests run before the release of an application, which increases the likelihood of things not going wrong hence improving its reliability. Businesses are able to stay informed of the application’s performance in real-time using monitoring and logging practices.</li><li><strong>Scale</strong> — applications can easily be scaled up or down as and when needed and according to changes in user traffic overtime.</li><li><strong>Improved</strong> <strong>collaboration and communication</strong> — teamwork is improved thanks to the combined practices and workflow of operations and development. With team members collaborating on the whole SDLC, there is a greater sense of ownership and sharing of tasks across the team, resulting in the improvement of the quality of services they provide to customers.</li><li><strong>Security</strong> — this is a crucial part of the SDLC. With everyone now working on the entire SLDC and automated security testing replacing manual tests, it’s easier to stay compliant even at a large scale.</li></ul><h3>Containers — the foundation of DevOps collaboration</h3><p>When I first heard we were learning about containers, I immediately thought of shipping containers. By its very nature, it’s purpose is not too far off in comparison to the use of containers in DevOps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-UWMflOn9_TJnGYuvjHXw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@hooverpaul55?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paul Teysen</a> on <a href="https://unsplash.com/s/photos/containers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>What are Containers?</h3><p>Containers are isolated executable packages that contain everything that’s needed to run an application including its associated dependencies, libraries and configuration files.</p><p>So what does DevOps have to do with containers? Containerising an application offers significant benefits to DevOps including the flexibility to manage and deploy applications through portable and lightweight containers (maybe not so lightweight for the actual containers in the above photo).</p><p>It also enables developers to share their application more easily with operations and production environments while solving the typical day-to-day “it doesn’t work on my computer” problem as the container will always run the same from one computing environment to another.</p><h3>Docker</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUOITpaBdlrMP9D__-K5Fw.png" /></figure><p>Docker is a big player in the container technology world. It’s a popular software platform used in DevOps that allows you to easily share, manage and deploy applications consistently through containers.</p><p>The computer that Docker is installed and running on is referred to as a Docker Host or Host for simplicity.</p><p>Docker Containers and Docker Images are two additional essential concepts to know when working with Docker.</p><p>When deploying an application on the host, it creates a Docker Container. Docker Images are blueprints with instructions for building a container, which includes the application and its associated dependencies. As such, a Docker Container is a running snapshot of a Docker Image</p><h3>Containerising our first application to deploy to the cloud</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ZD2w0QBo-znkKKtbid8Kg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kristimartin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kristi Martin</a> on <a href="https://unsplash.com/s/photos/cloud-computer?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>To understand the benefits of containers using Docker, we were tasked with our first group project of week one, which was to build a simple Node.js/Express application on anything of our choice and then to containerise it using Docker ready for deployment on to the cloud — AWS Elastic Beanstalk. We had four days to work on this in readiness to demo to the rest of our cohort on Friday.</p><p>My first thoughts were “holy crap we’re really diving right into it on day two!”. However, this gave us a real opportunity to apply all of day one’s workshops and reading that we did on containers to an actual project immediately.</p><p>Our team of four decided to build a simple one-page app as we wanted to prioritise our time to learn Docker, its commands to manage containers and how to deploy our containerised app on to AWS Elastic Beanstalk.</p><p>Here’s how our project went over the next four days as a team:</p><p><strong>Day 1 of the project (research and app-building):</strong></p><ul><li>Group brainstorming session of what we wanted to build; decided on an interactive drawing app with a chatbox.</li><li>Created a diagram of our team’s workflow for the week.</li><li>Learnt how to set up a basic Express file structure for our app.</li><li>Researched JavaScript libraries for creating an interative drawing board and a chatbox. We decided to use <a href="https://re.trotoys.com/article/rocanvas/">RoCanvas</a> for the drawing tool and <a href="http://socket.io/">socket.io</a> for the chatbox.</li><li>Set up our back-end server and created the HTML of our front-end.</li></ul><p><strong>Day 2 of the project (containerising our app):</strong></p><ul><li>Built a Docker Image of our web application by using a Dockerfile. A Dockerfile is also used by AWS Elastic Beanstalk to deploy the app.</li><li>Learnt how to run our Docker Image on our local machine as a Docker Container using Docker.</li><li>Committed and published our dockerised Node.js application to Docker Hub (Docker Hub is a repository registry where you can publish and download Container Images — similar to GitHub for source code).</li></ul><p><strong>Day 3 of the project (deploying app to AWS Elastic Beanstalk):</strong></p><ul><li>Explored the AWS Console Interface and the Elastic Beanstalk documentation to understand how to deploy our containerised app.</li><li>We realised that there are different ways of configuring our Docker app to deploy onto AWS Elastic Beanstalk — you can either use a Dockerfile, a dockerrun.aws.json file, or both!</li><li>Successfully deployed our first containerised app by using both a Dockerfile and a dockerrun.aws.json file.</li></ul><p><strong>Day 4 of the project (final touches and presentation):</strong></p><ul><li>Final styling of the front-end.</li><li>Re-build our Docker Image with our updated code to re-deploy to AWS Elastic Beanstalk</li><li>Presentation time and retro!</li></ul><p>You can read more about our team project <a href="https://github.com/cgloker/Hello-Cloud-World">here</a>.</p><h3>Reflection</h3><p>Our first week of introductions to DevOps, containers and AWS was a steep learning curve but I’ve thoroughly enjoyed learning more about this exciting part of engineering after being immersed with the development side of things for the last 12 weeks.</p><p>During our retro, we learnt that the way we were tasked to complete week one’s project was intentionally manual in order for us to get a feel for working with containers and using AWS for the first time.</p><p>I’m looking forward to moving on to Continuous Integration/Continuous Delivery/Deployment (CI/CD) next week to see how we can automate some of the repetitive steps we had to do during the integration and deployment phases of our first app this week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601ce285c616" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/makers-devops-bootcamp-week-1-devops-containers-and-aws-elastic-beanstalk-601ce285c616">Makers DevOps Bootcamp: Week 1 — DevOps, Containers and AWS Elastic Beanstalk</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My career change journey from charity administrator to software development]]></title>
            <link>https://tuyet-le.medium.com/my-career-change-journey-from-charity-administrator-to-software-development-f2fc89df23ed?source=rss-5488d6b287d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2fc89df23ed</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Tuyet Le]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 12:01:34 GMT</pubDate>
            <atom:updated>2023-01-24T21:41:23.903Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In 2019, I decided to learn to code in the hopes of changing careers into software development and after a year, I did it!</strong></p><p>I wasn’t in a position to leave my 9–5 job to do a computer science degree or a bootcamp so instead, I learned everything online, went to programming meetups and events after work, and took part in the Twitter <a href="https://www.100daysofcode.com/">#100DaysOfCode</a> challenge. Not long after setting myself this challenge, I was furloughed from my job as a result of the pandemic. The uncertainty only drove me further to use the extra time to work towards achieving my next career goal. Now after a year of self-studying, I feel grateful to be doing an apprenticeship programme with Makers and Expedia Group as a DevOps Engineer.</p><h3>A bit about my background</h3><p>I’ve always been fascinated by the digital world. As a kid, I’d mess around with basic HTML and CSS on sites such as Piczo and MySpace for hours. I never really understood the code but I loved changing it until I could make the page look good.</p><p>Coming from a first-immigrant generation family and as the eldest child, there was pressure to study particular subjects to meet family expectations. Studying a creative subject or IT wasn’t one of them. I was actually set on doing a degree in photography until my parents convinced me otherwise. The next best thing as a compromise was a joint degree in psychology and sociology, which I did really enjoy! However, after graduating I still wasn’t sure what I wanted to do. I loved psychology but it wasn’t something I was passionate enough to pursue as a career. For the next six years, I worked within the education and charity sectors as a researcher ad administrator while still figuring out what my “passion” was. Coding was a distant memory until I accidentally rediscovered my love for it when I helped with redesigning the charity’s website!</p><h3><strong>My coding journey</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6v1lw7W34IYp6XtQoDaAg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@impatrickt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Patrick Tomasso</a> on <a href="https://unsplash.com/s/photos/journey?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>“Change happens when the pain of staying the same is greater than the pain of change.” — Tony Robbins</blockquote><p>My coding journey started off with watching heaps of YouTube videos and doing online courses most evenings and eventually every day after being furloughed. The first programming languages I learned were HTML, CSS and JavaScript. The creative part of front-end development appealed to me so this was perfect. To build a habit of coding daily, I took part in the <a href="https://www.100daysofcode.com/">#100DaysOfCode</a> challenge, which I highly recommend to anyone as you learn with a great supportive community of coders and get to see what cool stuff others have built! (Fun fact: it takes roughly 66 days to build a new habit according to <a href="https://jamesclear.com/new-habit">James Clear</a>!)</p><h4><strong>Online courses</strong></h4><h4><strong>FreeCodecamp &amp; Codecademy</strong></h4><p>I started using <a href="https://www.freecodecamp.org/">freeCodeCamp</a> and <a href="https://www.codecademy.com/">Codecademy</a>. My personal preference is freeCodeCamp — there’s less hand-holding and it encourages you to do a lot of ‘googling’ to find your answers. The curriculum also provides a great learning structure with five projects at the end of each section to test your knowledge. If you’re more interested in back-end programming, they’ve recently added Python and Machine Learning to the curriculum. I worked through the Responsive Web Design, JavaScript Algorithms and Data Structures and Front End Libraries Certifications. By this point, I was hooked with the problem-solving aspect of coding and wanted to keep writing code to make my laptop do things!</p><h4><strong>Udacity</strong></h4><p>I wanted to try other resources to learn web development and had heard lots about Udacity. There are free and paid courses depending on what you want to learn. One of my favourite free courses is the <a href="https://www.udacity.com/course/version-control-with-git--ud123">Version Control with Git</a>. It’s a great beginner’s course and an essential skill for all developers to know and be comfortable in using. Employers will often look on Github to see your work so I started using version control very early on to save my projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4ms_KKC0spU9HrA2mNBCQ.png" /><figcaption>Github contributions between Feb — Nov 2020</figcaption></figure><p>I decided to give the <a href="https://www.udacity.com/course/front-end-web-developer-nanodegree--nd0011">Front End Web Developer Nanodegree</a> a try since they were doing 50% off their paid courses during the pandemic. The course was challenging and it was a natural progression after learning HTML, CSS and JavaScript on freeCodeCamp. I learnt how to set up a server using Node.js and Express, use build tools to manage asset files, interact with APIs, simplify CSS stylesheets with Sass and write meaningful README files. One of my favourite projects from the nanodegree was building a Node.js/Express web app that uses a Natural Language Processing API to analyse blog articles to determine the author’s emotions — you can check it out <a href="https://news-article-nlp.herokuapp.com/">here</a>.</p><h4><strong>YouTube</strong></h4><p>I supplemented my learning with many YouTube videos and still refer back to them today. Whether it’s to follow a tutorial on how to create a full website, build a candy crush game in JavaScript, learn how to use a code editor, how to use git or to understand a programming concept, I owe it to these channels for their straight-to-the-point content.</p><ul><li><a href="https://www.youtube.com/channel/UC29ju8bIPH5as8OGnQzwJyA">Traversy Media</a></li><li><a href="https://www.youtube.com/channel/UCW5YeuERMmlnqo4oq8vwUpg">The Net Ninja</a></li><li><a href="https://www.youtube.com/user/shiffman">The Coding Train</a></li><li><a href="https://www.youtube.com/user/KepowOb">Kevin Powell</a></li><li><a href="https://www.youtube.com/channel/UCFbNIlppjAuEX4znoulh0Cw">Web Dev Simplified</a></li><li><a href="https://www.youtube.com/channel/UC5DNytAJ6_FISueUfzZCVsw">Code with Ania Kubów</a></li><li><a href="https://www.youtube.com/channel/UClb90NQQcskPUGDIXsQEz5Q">Dev Ed</a></li></ul><h4><strong>Code First Girls and Codebar</strong></h4><p>I love being part of a community as learning every day in your room by yourself can get isolating, especially when you’re stuck on a problem. I reached out to a friend working in the industry in September 2019 who shared valuable guidance, which set me on a path to supplement my self-learning by attending coding workshops and courses run by non-profit organisations such as <a href="https://codefirstgirls.org.uk/">Code First Girls</a> and <a href="https://codebar.io/">codebar</a>.</p><p>I joined the <a href="https://codefirstgirls.org.uk/">Code First Girls</a> community and completed both 8-week courses in Web Development and Python in the evenings. I thoroughly enjoyed learning with other women also learning to code and have made some great connections as a result. Learning Python also helped consolidate some of the programming concepts I was learning in JavaScript such as variables, methods and data structures. You begin to see similarities between languages.</p><p><a href="https://codebar.io/">Codebar</a> is another great community that aims to make coding accessible to people from all walks of life. They regularly hold free workshops (currently virtual) where you can work with a coach to go through their tutorials or attend with a project of your own to get help on.</p><h4><strong>Tech events</strong></h4><p>These are great opportunities to learn about what’s happening in tech, learn new skills, pick up heaps of free stickers, learn about job opportunities, and most importantly to speak with other developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hd_-Wu1Sq0E__Nww_WuNDw.jpeg" /><figcaption>I love free stickers!</figcaption></figure><p>Early on in my coding journey, I travelled at 6 am for 2.5 hours from London to Birmingham to attend the ‘<a href="https://yougotthis.io/">You Got This Conference</a>’ by myself, aimed for junior developers and it was one of the best decisions I’ve ever made. I wasn’t sure if I was smart enough to go as well as not knowing anyone but I left that day feeling super inspired by all the speakers, the connections I made and the overall welcoming atmosphere. I was more motivated after hearing different stories of those that also career-changed into tech. It quietened my doubts and reminded me of why I was pursuing this path.</p><p>If there’s one advice that I could give, it’s to attend tech events and network as much as possible! I originally heard about my apprenticeship programme at a Code First Girls careers event before it advertised publicly so it’s definitely worth checking these out to learn about potential job opportunities for aspiring developers. Most events are currently remote and are often free so keep an eye out on Twitter and the events page of these organisations in particular:</p><ul><li><a href="https://codefirstgirls.org.uk/">Code First Girls</a></li><li><a href="https://codebar.io/">Codebar</a></li><li><a href="https://yougotthis.io/">You Got This Conference</a></li><li><a href="https://www.eventbrite.co.uk/o/makers-4400073409">Makers</a></li><li><a href="https://www.womenwhocode.com/">Women Who Code</a></li><li><a href="https://generalassemb.ly/education">General Assembly</a></li></ul><h3><strong>Finding a job</strong></h3><p>I don’t think I ever felt “ready” to apply for jobs. The lengthy requirements in job descriptions intimidated me, which fed into my thoughts that I wasn’t ready. I eventually realised that you’re never really ready <em>technically</em> until you start working as a developer professionally. As long as you’re passionate about coding, love problem-solving, enjoy working in a team, have a curious mindset and have empathy, then I’d say you’re ready.</p><p>I took the selective approach and applied for Front-End Developer roles and software development paid training programmes that accepted career changers. I also looked for companies that valued mentorship and investing in their junior developers’ growth.</p><p>I kept track of my applications using a table on Notion and applied for 23 openings over three months. Three companies took a chance on me and I made it through to the interview stages. The first was for a Junior Front-End Developer role; the second was an academy programme involving a 12-weeks software engineering training to join a project team after; lastly, a paid apprenticeship programme for an international company with 12-weeks training at a bootcamp. Third time lucky, I accepted the latter and it was the best possible outcome for me so I’m grateful to my current employer for giving me this amazing opportunity to start a new career.</p><p>All three interview processes were different. It varied from an informal ‘get-to-know’ cultural fit chat to multiple stages with take-home coding tests, pair-programming sessions with other candidates and behavioural-based interviews.</p><h4><strong>My learnings from interviews</strong></h4><p>I absolutely hate interviews. I’m a ball of anxiety under the spotlight but the thing that helped me manage the nerves was to over-prepare and remember my reasons for making this change. Queue Eminem…</p><p><em>If you had one shot<br>Or one opportunity<br>To seize everything you ever wanted<br>In one moment<br>Would you capture it<br>Or just let it slip?”</em></p><p>In addition to preparing for technical questions, there are five main things that I learnt from my interview experience:</p><ol><li><strong>Know your why! </strong>Why do you want to be a software developer? What is it about technology that excites you? Why do you want to change careers?</li><li>Prepare for common behavioural interview questions following the <a href="https://www.thebalancecareers.com/what-is-the-star-interview-response-technique-2061629">STAR method</a>. If you’re changing careers into a completely new field like tech, <strong>you have transferable soft skills</strong>! Think about evidence of good communication, taking the initiative to solve a problem, managing projects/tasks through to completion, and dealing with challenges of working in teams and how you dealt with it with compassion.</li><li><strong>Practice, practice, practice</strong>! I asked my partner to fire common interview questions at me and this was incredibly helpful. Remember to highlight how you can bring value to the team.</li><li><strong>Research the company </strong>and explore their website. Understand their core values, what sets them out from their competitors and what goals they are working on. When the interviewer asks whether you have any questions for them, this is a good time to show you’ve done your research by asking them questions based on company articles you might have found interesting. It shows you’re also thinking about the bigger picture and it’s not just a job for you.</li><li>The company has given you a chance for a reason so don’t underestimate your abilities. I struggle with being confident at the best of times and it shows through in my response. <strong>Stay positive and trust the process.</strong></li></ol><h3><strong>Upon reflection of changing careers into tech…</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ktG9JJjLVTZKzLH3P8mhQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ben_neale?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ben Neale</a> on <a href="https://unsplash.com/s/photos/rainbow?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It’s been a crazy journey so far and I’m so excited to continue taking my learning to the next stage in 2021. These are some things that helped me stay motivated during the process of a career change in a pandemic:</p><ul><li>Do the <a href="https://www.100daysofcode.com/">#100DaysOfCode</a> challenge! It’s a great way to get started with learning with other coders online so you’re not alone. The public accountability helps you stay on track to code a little bit each day, even if it’s just for 15 minutes (but it’s also ok to miss days because of life so don’t be too hard on yourself if you miss a day 😊)</li><li>Join tech communities and attend events to talk to others already in the field. This will help you see whether this is a path you want to explore. You may also hear about job opportunities suitable for career-changers.</li><li>Take advantage of the free coding workshops out there. I find learning with others more enjoyable and you learn topics faster through discussion.</li><li>Don’t try to learn everything! I wish I learnt this early on. You don’t have to be an expert in multiple languages before applying for your first job.</li><li>Regularly look at job descriptions on LinkedIn and Indeed to get an idea of the skills in demand in your area. Don’t wait until you meet all the requirements to apply — start applying as soon as you can so you can get a feel of the interview process early on.</li><li>Apply your skills by offering to build someone a website for free. This really helped consolidate the things I learnt from the various online courses. A friend launched a small business during the pandemic and I offered to build her a website with plain old HTML, CSS, JavaScript and Node.js (it’s live <a href="http://www.mamali.co.uk/">here</a> if you’re curious).</li><li>Practice your problem-solving skills by solving small coding challenges (also known as kata) on <a href="https://www.codewars.com/">Codewars</a>.</li><li><strong>Be persistent. </strong>You will have frequent moments of doubt but all progress is linear. Everyone’s situation and learning style are different but it is certainly not impossible no matter your background or whatever life throws at you!</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2fc89df23ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>