<?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 Cecilia Chang on Medium]]></title>
        <description><![CDATA[Stories by Cecilia Chang on Medium]]></description>
        <link>https://medium.com/@ceciliafchang?source=rss-3a965622bb1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eKETSAjlQ6Hdfr-46D2UXQ.jpeg</url>
            <title>Stories by Cecilia Chang on Medium</title>
            <link>https://medium.com/@ceciliafchang?source=rss-3a965622bb1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:41:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ceciliafchang/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[From Hospitality to Tech]]></title>
            <link>https://medium.com/@ceciliafchang/from-hospitality-to-tech-b857237396c2?source=rss-3a965622bb1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b857237396c2</guid>
            <category><![CDATA[hospitality]]></category>
            <category><![CDATA[hospitality-management]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Cecilia Chang]]></dc:creator>
            <pubDate>Sun, 03 Dec 2017 06:55:35 GMT</pubDate>
            <atom:updated>2017-12-03T07:15:36.581Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*cbkdTWlZx6VFW-z425zDPg.jpeg" /><figcaption>Behind the front desk at NYNY Hotel and Casino</figcaption></figure><p>Let me start off by telling you why I got into the hospitality field. I have always loved interacting with people and being able to help them in some way. When I was younger, I participated in countless community service events, from feeding the hungry and mentoring children at the YMCA to helping raise awareness at events like Susan G. Komen’s Race for the Cure. It just feels great to help other people and make an impact on their lives. It is the reason why I joined a community service fraternity in college and why I joined Food Bank For New York City (<a href="https://www.foodbanknyc.org/">https://www.foodbanknyc.org/</a>)when I moved here last year. Therefore, I’m not surprised I fell into the hospitality field. That and the fact that I love hotels. Also, my friends would always tell me that I am a people-person and that this field would be perfect for me.</p><p>After college, I started my career as a Management Associate at MGM Resorts. It was an amazing opportunity working at some of the largest hotels in the world. I was able to train in every single department (~30) and learn how to manage a casino hotel (here’s a short video of my experience <a href="https://youtu.be/P47BpqskJ1A">https://youtu.be/P47BpqskJ1A</a>). Afterwards, I became an Assistant Front Desk Manager at NYNY, working on the overnight shift for 3 months before luckily getting the day shift. Everyone would say, after working in Vegas, you can work anywhere, and they are right. The experiences you gain there are beyond any that you will experience at a regular hotel. The volume of people you deal with on a daily basis can’t compare to those elsewhere, as you get casino guests, food and beverage guests, and pretty much all guests coming to the front desk to complain. I commend all the hard working front desk agents and managers in Vegas as it is not an easy job to keep your composure with the demanding clientele in Vegas. I have to say that this experience made me question whether hospitality was right for me.</p><p>So two and a half years after moving to Vegas, I embarked on a new journey to teach English in Prague, which I did for about half a year (that is a whole other challenge I will write about later, as well as moving to England, Hong Kong, and New Zealand). I knew teaching English wasn’t right for me, and I didn’t completely write off hospitality, so I almost got a job as a Front Desk Supervisor in Macau. Although it would have been a great opportunity for me to work on my Mandarin, I quickly realized that I did not want to work at another casino hotel. I moved to New Zealand instead on a working holiday visa. While I was there, I did take on other jobs that were hospitality related, such as working for accommodation at hostels and B&amp;Bs. I also met people along my travels that were software engineers. It sparked my interest that they were working from their laptops and traveling around the world. Then, when I took on a temp job as a branch coordinator at Crown Relocations in Dunedin, NZ for a couple months, I came to realize that I am capable of being a software engineer. Crown uses multiple systems to manage their daily workflow and I was able to pick those up quickly (of course, this is not the same as building your own systems, but I know that when I set my mind on something, I will make it happen). I started wondering how these systems worked on the back end, and whenever the system was glitchy, how it would be like to fix those issues and not have to get someone’s help to do so. When my year in New Zealand was up and I decided to move back to the states, I started looking into how I can start a career in tech. I talked to one of my software engineer friends and he told me about bootcamps. After reaching out to other friends and doing research, I came across Grace Hopper Academy, a bootcamp for women with deferred tuition. I knew it was perfect for me. There was just one little problem. I needed money as I had carefully depleted my savings due to my years of traveling. Since I still had a passion for helping others, I decided to get a job in hospitality until I saved up enough to support myself through the bootcamp. In the meantime, I started teaching myself how to code on codecademy. It was silly how amused I was when I learned how to display an alert box in the browser. Once I saved up enough, I applied to the program…and here I am….ready to graduate! I have learned so much and am ready to find a job that will continue to challenge me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b857237396c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey at Grace Hopper Academy]]></title>
            <link>https://medium.com/@ceciliafchang/senior-phase-at-grace-hopper-academy-15aef9c2d307?source=rss-3a965622bb1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/15aef9c2d307</guid>
            <category><![CDATA[grace-hopper]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Cecilia Chang]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 05:12:59 GMT</pubDate>
            <atom:updated>2017-12-03T21:39:22.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*rr5_XzY2vKD-BH5TuAdkfg.png" /></figure><p>I can’t believe I only have one more week at Grace Hopper. Senior Phase, the latter 6 weeks of our program, just flew by. This is because we were so focused on the 3 projects we had that time just got away from us. This is completely opposite of Junior Phase, the first half of our program, where we learned the stack and how to pair program. A typical day consisted of a lecture (where we learned about a technology), a workshop (which you do in pairs), and the review (where our instructors went over the workshop and answered any questions). However, it is a bootcamp, so technically, we are learning everything at rapid speed and it is no wonder our journey is almost over.</p><p>We are currently putting the finishing touches on our Capstone projects, which is the biggest project we have and the one we will demo next week. My group decided to create a game called Global Kitchen. It is a restaurant simulator game that introduces players to international recipes they may not have otherwise heard of. We were inspired by the creators of Cooking Dash, but we wanted to make something that was also educational. As a global traveler and food lover, I was very enthusiastic about this aspect. I was, however, a little skeptical about creating a game. I was never a gamer, but was intrigued by what we came up with and loved the challenge of tackling something completely new. It has been a real adventure and I am proud of what we have accomplished thus far. We decided to use PixiJS, which is a Javascript-based framework for rendering graphics using WebGL, in combination with Redux, which we used to manage our game state and dispatch actions. Pixi was the real challenge for us as it is a framework, not a game engine, and there was not enough detailed documentation online. We basically had to build everything from scratch, which took a lot of time and effort. We also lost two days of group work due to Thanksgiving which I think really impacted us. In retrospect, we should’ve used a game engine, but I have to say that Pixi did teach us a lot.</p><p>The second project we had was our Stackathon project, which was a solo project that consisted of 2 days of in-class work and the optional weekend work. There was no criteria so everyone got the chance to create something they’re interested in. I decided to create an app called HungerMatch. Since I am an indecisive eater when I’m hangry (and not a cook), I wanted to create an app that would limit my restaurant choices. Usually I would spend too much time looking through Yelp because there’s a never-ending array of choices. To use HungerMatch, you would sign in and choose a flavor (spicy, sweet, salty, sour, umami) and it would access your location and use Yelp’s API to match you with 1–3 restaurants near you. I started off making a mobile version of the app using React Native. I always wanted to make a mobile app so I thought this would be a cool way to start. I chose to learn React Native since we didn’t have much time and it was the closest to our stack. If you want a brief introduction to React Native, feel free to check out my other post <a href="https://medium.com/@ceciliafchang/react-native-vs-plain-old-react-bb0f27677cfd">https://medium.com/@ceciliafchang/react-native-vs-plain-old-react-bb0f27677cfd</a>. I did run into some issues while debugging and somehow broke my ios simulator Saturday night. As a result of this, I panicked and made a web version of the app using React-Redux and Express to ensure I had something to demo on Monday. I ended up fixing my simulator problem and therefore had two things to demo. However, I didn’t want to risk a live demo via ios simulator so I recorded a screencast instead, which I highly recommend in case your live demo doesn’t go according to plan.</p><p>The first of our projects was Grace Shopper, where we built an e-commerce site selling past Nic Cage roles as if they were to reoccur in the future. Originally that was not the plan, but of course, our direction shifted as the days progressed. We had a little over a week to complete this project and it was definitely a challenge as it was the first time we worked in a group and learned about Agile workflow. Merge conflicts were also terrifying at first as most of us only knew the basics of git, but we soon realized that there was nothing to be afraid of. Instead, we should embrace merge conflicts. The main goal of this project was to teach us how to work together as a team via Git and Agile and get us to commit early and often. I felt like it taught us a good lesson and prepared us for Capstone. It also prepared us for Stackathon because when I first finished Junior Phase, I honestly had no clue how much I retained. The experience of making something ourselves showed us that we indeed learned a lot.</p><p>Although Senior Phase has been more stressful, I definitely enjoyed it more. It’s great to see what we’re all capable of, which is a drastic change from day one where we went into class wide-eyed. If you’re a prospective student, just be prepared. There’s a lot to do and not much time. That’s the whole idea of a bootcamp. It’s going to be weird not seeing my cohort everyday, but we all have very exciting journeys ahead of us and I can’t wait to see where everyone ends up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15aef9c2d307" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native vs. Plain Old React]]></title>
            <link>https://medium.com/@ceciliafchang/react-native-vs-plain-old-react-bb0f27677cfd?source=rss-3a965622bb1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb0f27677cfd</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-navigation]]></category>
            <dc:creator><![CDATA[Cecilia Chang]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 03:13:17 GMT</pubDate>
            <atom:updated>2017-11-16T15:37:40.429Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8Zxbnn7E4LLe1OEFh_hvQ.png" /></figure><p>Before you start, please be aware….React Native is CONSTANTLY changing.</p><p>However, if you want to create a mobile app and you know React, the easiest option is to use React Native. If you are like me, your initial thought is that this will be quite easy…a smooth transition maybe? In many ways, they are similar. Both use JSX and both allow you to incorporate Redux and React-Redux. However, there are also quite a few differences. This is a quick comparison of the two and is based on my experience with Create React Native App.</p><p>**Note** The code below is taken from my Stackathon project for Grace Hopper Academy, HungerMatch, where I created a mobile app (using React Native and React-Redux) and a web app (using React-Redux) for indecisive eaters who need to narrow down their nearby restaurant choices.</p><pre>import React, { Component } from ‘react’;</pre><pre>import { AppRegistry } from ‘react-native’;</pre><pre>import { Provider } from ‘react-redux’;</pre><pre>import Navigator from ‘./client/components/Navigator’;</pre><pre>import store from ‘./client/store’;</pre><pre><br>export default class HungerMatch extends Component {</pre><pre>  render() {</pre><pre>    return (</pre><pre>      &lt;Provider store={store}&gt;</pre><pre>        &lt;Navigator /&gt;</pre><pre>      &lt;/Provider&gt;</pre><pre>    );</pre><pre>  }</pre><pre>}<br></pre><pre>AppRegistry.registerComponent(‘HungerMatch’, () =&gt; HungerMatch);</pre><p>1) You start off by registering your app root Component with AppRegistry like in the above example.</p><p>2) The JSX tags are different. You do not use divs, h1s, etc.</p><p>a. &lt;Text&gt; = h1, h2, h3, h4, h5, h6, p (essentially all your texts)</p><p>b. &lt;Image source={{uri: ‘http://www.example.com/logo.png’}} /&gt; = &lt;img src=’http://www.example.com/logo.png’ /&gt;</p><p>c. &lt;Button onPress={} title=”spicy” /&gt; = &lt;button onClick={}&gt;spicy&lt;/button&gt;</p><p>d. &lt;View&gt; = &lt;div&gt;</p><p>There are also different types of Views: &lt;ScrollView&gt; and Lists (&lt;ListView&gt;, &lt;FlatList&gt;, &lt;SectionList&gt;). I’m not going to get into the details here, but you can find some quick comparisons on <a href="http://www.reactnativeexpress.com/">http://www.reactnativeexpress.com/</a>.</p><p>3) You style on your component. There are two ways to do so:</p><p>a. Inline-styling:</p><pre>&lt;Text style={{ fontSize: 27 }}&gt;&lt;/Text&gt;</pre><pre>&lt;View style={{ marginTop: 15 }}&gt;&lt;/View&gt;</pre><p>b. Using StyleSheet from react-native:</p><pre>Import {StyleSheet} from ‘react-native’;<br></pre><pre>const styles = StyleSheet.create({</pre><pre>  container: {</pre><pre>    flex: 1,</pre><pre>    flexDirection: ‘column’,</pre><pre>    justifyContent: ‘center’,</pre><pre>    alignItems: ‘center’,</pre><pre>    margin: 35</pre><pre>  },</pre><pre>  logout: {</pre><pre>    marginTop: 35,</pre><pre>    backgroundColor: ‘skyblue’,</pre><pre>    borderWidth: 2,</pre><pre>    borderColor: ‘steelblue’</pre><pre>  }</pre><pre>});</pre><pre>return (</pre><pre>  &lt;ScrollView style={{ padding: 20 }}&gt;</pre><pre>    &lt;View style={styles.container}&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Spicy’)} title=”spicy” /&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Sweet’)} title=”sweet” /&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Salty’)} title=”salty” /&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Sour’)} title=”sour” /&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Umami’)} title=”umami” /&gt;</pre><pre>    &lt;/View&gt;</pre><pre>    &lt;View style={styles.logout}&gt;</pre><pre>      &lt;Button onPress={() =&gt; navigate(‘Login’)} title=”Logout” /&gt;</pre><pre>    &lt;/View&gt;</pre><pre>  &lt;/ScrollView&gt;</pre><p>The most common styles are listed here <a href="http://www.reactnativeexpress.com/view">http://www.reactnativeexpress.com/view</a>. Notice that all the properties are written in camelCase (i.e. backgroundColor instead of background-color).</p><p>4) Instead of React Router, there is React Navigation, which has StackNavigator, TabNavigator, and DrawerNavigator. You can take a look at this quick start guide <a href="https://reactnavigation.org/docs/intro/quick-start">https://reactnavigation.org/docs/intro/quick-start</a>. I’ll go into a little more detail about StackNavigator since it is the one I used for my project. It is also the one that is the most common.</p><pre>import { StackNavigator } from ‘react-navigation’;</pre><pre>import Login from ‘./Login’;</pre><pre>import Home from ‘./Home’;</pre><pre>const RootNavigator = StackNavigator({</pre><pre>  Login: {</pre><pre>    screen: Login,</pre><pre>    navigationOptions: {</pre><pre>      headerTitle: ‘HungerMatch’</pre><pre>    }</pre><pre>  },</pre><pre>  Home: {</pre><pre>    screen: Home,</pre><pre>    navigationOptions: {</pre><pre>      headerTitle: ‘Home’</pre><pre>    }</pre><pre>  }</pre><pre>});</pre><pre>export default RootNavigator;</pre><p>Each object key in StackNavigator (Login, Home, etc.) represents a screen. I have Login and Home as separate components that I’m importing into Navigator. You can also add a headerTitle…as you guessed it, the title of that screen.</p><pre>const { navigate } = this.props.navigation;</pre><pre>&lt;Button onPress={() =&gt; navigate(‘Spicy’)} title=”spicy” /&gt;</pre><pre>&lt;Button onPress={() =&gt; navigate(‘Sweet’)} title=”sweet” /&gt;</pre><p>In my Home component, I have buttons that link to the next screens, such as Spicy and Sweet. You can do this by using this.props.navigation.navigate. This is because each component you’ve registered to StackNavigator has access to navigation as a prop.</p><p>If you also need to pass a prop down to your next screen/component, you can do so like this:</p><pre>.then(results =&gt; {</pre><pre>this.props.navigation.navigate(‘Matches’, { data: results });</pre><pre>})</pre><p>After I passed my query results to my Matches component, it is able to access those results using this.props.navigation.state.params.data.</p><p>There you have it! These are the basic differences of React Native compared to regular React as of this moment.</p><p><em>P.S. It was really awesome being able to build a mobile app from scratch, well mostly scratch. There are still a lot of things I want to add to my app, but I’m glad React Native has made things so much easier for me.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb0f27677cfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>