<?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 Angelyn A. Liem on Medium]]></title>
        <description><![CDATA[Stories by Angelyn A. Liem on Medium]]></description>
        <link>https://medium.com/@angelynliem?source=rss-f25e0a66e387------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3whvnanwXzTxJpGuzwCEmg.jpeg</url>
            <title>Stories by Angelyn A. Liem on Medium</title>
            <link>https://medium.com/@angelynliem?source=rss-f25e0a66e387------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:43:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@angelynliem/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[A background section]]></title>
            <link>https://angelynliem.medium.com/a-background-section-bf04de800857?source=rss-f25e0a66e387------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf04de800857</guid>
            <dc:creator><![CDATA[Angelyn A. Liem]]></dc:creator>
            <pubDate>Fri, 23 Apr 2021 03:36:22 GMT</pubDate>
            <atom:updated>2021-04-27T03:22:34.485Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Learning to Run Data Science API on Local Host</strong></h3><p><em>Sharing some of my experiences in Labs, the final project at Lambda School. The story mainly touches on how I learned to run Data Science API on local host from a full stack web developer’s perspective.</em></p><p><strong><em>Overview of Lambda School Labs</em></strong></p><p>As a Full Stack Web Development part-time student at Lambda School, I am required to complete a two-month “capstone” group project known as Labs.</p><p>The following is more or less how Labs works:</p><ul><li>You are placed on a team of about 10 students across Web, Data Science, and iOS tracks.</li><li>You are given a project passed down from the previous Labs group, and therefore, you need to work with an existing code base.</li><li>You receive Guided Projects via Zoom to help you with various aspects of the project, and your team gets a Team Lead who has gone through Labs and is able to help you navigate your way through Labs.</li><li>To pass Labs, you need to be an active participant in your team, pass all bi-weekly Sprint Challenges and a Labs Interview that cover both your career-related and technical-related skills.</li></ul><p><strong><em>Overview of my team’s Labs project</em></strong></p><p>Since I am part of the Web team, and two of the students on the Web team mentioned that they are more comfortable working on the backend, I decided I’d be the frontend developer for the Labs project. As one of the two students working on the frontend, I was assigned the task of connecting our frontend Web application to the Web and Data Science API.</p><p>A brief overview of our project:</p><ul><li>Our project is called CitySpire, a Web and iOS application that allows users to search for a city in the United States in order to make the best informed decision on where they should live.</li><li>When a user types in or selects a city and state, it directs them to a dashboard to view that city information, such as weather, traffic, pollution, walkability, livability, crime, and so on. It also shows the map of that city’s location within the United States.</li></ul><p>As the person responsible for the Search functionality on the frontend, I had to figure out how to connect the frontend to the backend of Web and Data Science.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*sMZabyiXRiezGvi2EZrW2g.png" /><figcaption>Mobile Web version</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*d-xg8Bss1I0HHSQlkav-hQ.png" /><figcaption>Tablet version</figcaption></figure><p><strong><em>Getting familiar with existing code</em></strong></p><p>The first two weeks of Labs was mainly spent on planning and getting to know the other students on the team. Part of the planning stage is creating user stories, working on wireframes, agreeing on our tech stack, and our engineering diagram. For the planning stage, we mainly used Whimsical and Trello. I contributed to this initial stage by coming up with the Web version of the wireframe and taking the lead on the group discussion for our Web-related tech stack.</p><p>Soon after the initial stage is over, we were given the existing code base from the previous Labs group via Github/Git, and we started immersing ourselves with the code to familiarize ourselves with it. It took me a number of days to get a more solid understanding of the code and how it works. Since my main task is to connect the Search bar to the Web and Data Science API, I focused first on the state management which used Redux. I also had to familiarize myself more on some of the new languages and libraries that the past Labs group was using such as <a href="https://ant.design/">Ant Design</a> and <a href="https://www.mapbox.com/">Map Box</a>. Moreover, I had to update their Redux dependencies as it didn’t include the toolkit, which I love using, as it allows me to see more easily what is in the store and how the state is managed more clearly with the <a href="https://redux-toolkit.js.org/introduction/getting-started">Redux toolkit</a> dependency.</p><p><strong><em>Learning to run Data Science API locally</em></strong></p><p>A key challenge I faced after I became more familiar with the existing code is to connect and view the Web and Data Science API. I focused more on the Data Science API since the previous Labs group had created one, whereas they didn’t have a Web API so our team had to start that from scratch. A major downside of the Data Science API, however, is that our current team has to update the API and re-deploy it via AWS. This took the current Data Science team a while to work on, whereas I wanted to connect to the API right away to get a better idea what the data entails and if the existing code needs to be updated. Since the previous Data Science API is not deployed, I had to learn to run it locally. The following is some of the steps I took, the challenges I overcame, and the help I received to successfully run it on local host:</p><ul><li>I went to the Data Science repository on Github and read the documentation in the README file.</li><li>I cloned the repository, ran an npm install to install all the dependencies locally then tried to run it. However, I got an error back and couldn’t get the API up and running locally, so I reached out to the Labs channels on Slack to see if anyone could help. The Data Science Team Lead for our Labs cohort is awesome and he responded to me promptly. It turned out that my laptop does not have some Python-related dependencies installed and that’s needed to run the Data Science API. I only knew Python at large, because we used the language in the Computer Science Unit right before Labs where we learned Data Structure and Algorithms and coded using Python. Apparently there was more to Python and this is where I learned about <a href="https://pip.pypa.io/en/stable/installing/">Pip</a>, <a href="http://How to Use Python Pipenv in Mac and Windows">Pipenv</a>, <a href="https://plotly.com/">Plotly</a>, and <a href="https://www.uvicorn.org/">Uvicorn</a>.</li><li>After a successful installation of the above-mentioned Python and Data Science-related dependencies, and adding a Postgres link in the Data Science repository’s env file, I was able to get the API running on my local host. I followed the instructions and touched base with the current Data Science team to help me navigate the displayed data and how to test and use it. I was also able to test it on Postman which was great because I am already familiar with the testing tool from Unit 4 where we learned Web backend development using Node and Sqlite3.</li><li>Despite being able to run it locally, however, I still wasn’t able to connect to it with the existing code from the frontend. I ended up waiting for the current Data Science team to deploy their updated Data Science API, and the other student who is working on the frontend with me helped me out and got our frontend connected to the deployed Data Science API.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*VOKtK4D73CspIipNelVz_A.png" /><figcaption>Steps to install Pip on local device</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*KOK0hDurbLE76RNR2GE94w.png" /><figcaption>Steps to install Pipenv on local device</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*ZZS7N6_Atrnvuv5TvRvduQ.png" /><figcaption>Steps to run the Data Science API on local host after completing above two steps</figcaption></figure><p><strong><em>The power of teamwork and collaboration</em></strong></p><p>I am currently approaching the last week of Labs, which also marks my completion of about a year of part-time study at Lambda School Full Stack Web Development program.</p><p>In the end, I am thankful of my Labs team who complements my weaknesses so that we can achieve more together. Together with my Web team, we were able to update the User Interface of the project to make it look more modern and cleaner. We were able to get all our tests to pass using Lint which is something new we learned in Labs. We learned to work together using Github/Git, followed Lambda School’s pull requests and code review standards, and developed lasting friendships.</p><p>I am excited to see where this project will go with the next team that gets it! Since we still had difficulty getting the deployed frontend to connect to the backend by the time we had to do our final presentation to the stakeholders, I hope that the next team that gets this project will be able to debug and fix that. Additionally, getting an endpoint for the Top Cities and Learn More About U.S. Cities sections so that they are not using external links would be impressive.</p><p>Last but not least, I am deeply grateful for Lambda School for the amazing opportunity and the adventure I was able to experience in my quest to become a full stack web developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf04de800857" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cheat Sheet For Grow with Google Scholarship Android Basics Recipients]]></title>
            <link>https://angelynliem.medium.com/cheat-sheet-for-grow-with-google-scholarship-android-basics-recipients-db2380f03a36?source=rss-f25e0a66e387------2</link>
            <guid isPermaLink="false">https://medium.com/p/db2380f03a36</guid>
            <category><![CDATA[udacity]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[cheatsheet]]></category>
            <category><![CDATA[android-basic]]></category>
            <category><![CDATA[grow-with-google]]></category>
            <dc:creator><![CDATA[Angelyn A. Liem]]></dc:creator>
            <pubDate>Fri, 09 Feb 2018 03:44:29 GMT</pubDate>
            <atom:updated>2018-02-11T04:23:40.452Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*XBYnfzMaoG7g_Rl4IwXoTg.png" /><figcaption>My First Project</figcaption></figure><p>Hello — I am one of the recipients of the Grow with Google Scholarship — Android Basics this year. I am new at coding and have been an active member of the Grow with Google Android Basics forum and Slack communities for only a month. During the one-month period, I was able to complete my course and read through some of the mentors feedback for myself and other students. Some students started late — They either missed their email of acceptance from Udacity, the email got into their Spam, or they’ve been really busy. If you are one of those students who are starting late, I have summarized a list of things the mentors generally suggest when you submit your first project. Hopefully this saves you some time from reading through the forum threads. Also, I think the mentors will be impressed if you get to implement them! Here they are:</p><ol><li>Use the String, color, dimension, and style resource files. Hard coding the strings, colors, and dimensions in the layout is not good practice. For String, you can click alt and enter on the text to extract the string resource. For more information, read this<a href="https://developer.android.com/guide/topics/resources/more-resources.html2"> article</a>.</li><li>Your first project should be to create an informative single screen app about Udacity or local business. You can remove the action bar so that the app will look full screen and you have more screen estate to play with. To remove the action bar, you can change the parent of app theme to &quot;Theme.AppCompat.Light.NoActionBar&quot; in styles.xml file.</li><li>Wrap your whole layout inside ScrollView so that it will be scrollable on small screen devices and in landscape mode.</li><li>Use android:drawableLeft to add icons next to the address, phone, and/or website.</li><li>Use autoLink so that the address, phone, and website are clickable.</li><li>Use <a href="https://developer.android.com/training/accessibility/accessible-app.html">contentDescription</a> for better accessibility of your app.</li><li>TextSize should be in sp, not dp or pt.</li><li>Nested layouts are bad for performance and should be avoided.</li><li>General guideline so that your texts/images are not too close to the edge of the screen is to give them 16 dp of margin/padding.</li><li>Make sure your texts are distinguishable from the background color. Make use of the color palette from <a href="http://material.io/">material design</a>.</li></ol><p>And when you’re done with these five things and ready to tackle the second project, the mentors will likely suggest you do these two things for your score keeping app:</p><ol><li>Make sure the score doesn’t reset to zero when a user rotates the screen. Use the onSaveInstanceState() and onRestoreInstanceState() callback methods to resolve this issue.</li><li>Create global variables for all the views by initializing them in onCreate() method, and use it in your own methods. The purpose of doing this is to reduce the number of calls to findViewById() method which is resource intensive and expensive work.</li></ol><p>And for the third and final project which is a quiz app:</p><ol><li>Allow users to share their scores with others using a share intent. Here’s the corresponding <a href="https://developer.android.com/training/sharing/send.html">article</a>.</li></ol><p>In general, these are just some of the things the mentors will suggest. I would love if other students could add to this list as I am only a small part of the +/-15,000 member community. Plus, together we can make an awesome cheat sheet! There’s so much to learn for those new to this scholarship program and to android app development — so I hope this helps!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db2380f03a36" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>