<?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 Luna on Medium]]></title>
        <description><![CDATA[Stories by Luna on Medium]]></description>
        <link>https://medium.com/@lunaceee?source=rss-76ccb607e2cc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*er7hupgjr2ZRqfrsFvcvkA.jpeg</url>
            <title>Stories by Luna on Medium</title>
            <link>https://medium.com/@lunaceee?source=rss-76ccb607e2cc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:09:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lunaceee/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[When do you graduate from a junior software engineer ?]]></title>
            <link>https://medium.com/@lunaceee/when-do-you-graduate-from-a-junior-software-engineer-b357ae8268fd?source=rss-76ccb607e2cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b357ae8268fd</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[work-culture]]></category>
            <dc:creator><![CDATA[Luna]]></dc:creator>
            <pubDate>Fri, 08 Feb 2019 21:44:43 GMT</pubDate>
            <atom:updated>2019-02-08T22:09:50.143Z</atom:updated>
            <content:encoded><![CDATA[<h3>When do you graduate from a junior software engineer?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*EsN5RDtOwge1oyv3.jpg" /></figure><blockquote><em>Everyone starts from some where, including being a junior software engineer.</em></blockquote><p>Like many of you, I got into software development from a non-traditional background. In this fast-paced environment, the time has flown like a bullet — it feels like yesterday when I wrote <a href="https://medium.com/netlify/how-i-joined-a-san-francisco-startup-as-a-software-engineer-adc70e54a2">this article</a>.</p><p>In a world with endless possibilities, it takes practice and patience not to feel overwhelmed and find out what’s most important to yourself — aka the North Star. It takes bravery and resilience to keep challenging your comfort zone. How do you measure success? What’s a fair evaluation of progression? If similar questions ever occur to you, read on.</p><h3>People first, technology secondary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/0*oYrqIdLMeBs5mrEQ.jpg" /></figure><p>In “theory”, coders don’t talk, they sit in front of a screen and fart out rainbow code that builds products magically, which might be the case in early-stage start-ups since it’s a one-man-band and the founder has to deal with all the things. However, as the company grows, things will have to change to ensure scalability and healthy growth. In “reality”, building a product usually requires efforts from a team of people, including but not limited to designers, product manager, front end and back end engineers. Communication is essential to guarantee success and productivity in an agile mindset. It’s important to be a team player, not a loner. Be upfront with your opinions while still paying respect to other people’s time and efforts.</p><h3>Keep calm and understand the problems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/0*Qkmah6UstXVRD3aM.png" /></figure><p>Easier said than done. When you’re in front of deadlines and unclear feature requests, it’s easy to feel rushed and wanting to keep your hands dirty. It’s even more critical that you understand the problem well enough to identify what’s needed and what not prior to implementation. I can’t remember how many times I jumped into code without over-sighting edge cases or over-engineering the problems. Of course, everything takes practice, even very experienced software engineers and designers misunderstand issues sometimes. Making mistakes and failing fast is part of the nature of software development. But understanding the problems, thinking in a large picture and being aware of the trade-offs is half of the success.</p><h3>Docs first, specs first, code last</h3><p>This is sort of related to the previous subject but more towards a team level. It is a relatively lofty concept but is also super beneficial. Sure, it’s not easy when it comes to execution in a fast-paced small company because it takes time and efforts from everyone in the team and “we need to ship things fast”. But in my opinion, it’s arguably a time concern because a poorly designed feature usually ends up costing more time bug fixing and issue tracking.</p><h3>Manage your agenda</h3><p>As a junior software engineer, there’re a lot of things to figure out to make the universe work for you. It’s like tooling in development, utilizing the tools correctly instead of fighting against them makes a massive difference to your daily life. Having your agenda under your control is one of the most important ones. As mentioned earlier, everything is teamwork. Sometimes, your work can be blocked by other people’s work. There can be various ways of solving the problem, which takes creativity and efforts. But the general rule of thumb is, try not to make things personal and feel discouraged, advocate yourself and reach out for help.</p><p>Sometimes, it’s also important to manage your manager to help you achieve your agenda. Your manager can be very busy and not always on top of your daily work. Make sure you proactively communicate your progress and concerns to help them do a better job.</p><p>Again, everyone is unique; my approach doesn’t have to fit into your shoes. But hopefully, you can get something out of it.</p><p>If you are curious about how to evaluate yourself as a software engineer according to the industry standard, I strongly recommend <a href="https://circleci.com/blog/why-we-re-designed-our-engineering-career-paths-at-circleci/">this article from CircleCI</a>.</p><p>It’s been an incredible journey working at an emerging startup in silicon valley. Seeing myself grow helps me feel confident and stay focused. Observing the company and team grow keeps me engaged and motivated. Witnessing the user growth reassures my faith in being in tech.</p><p>A year ago, I convinced myself to start from scratch and transition into software development. Today, I’m working with 40 plus incredible problem solvers to build a product <a href="https://twitter.com/NetlifyLove">that people love</a>, as a software engineer.</p><p>If you’re interested in helping us build a better product, feel free to drop us a line at <a href="/service/mailto:careers@netlify.com">careers@netlify.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b357ae8268fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adding Netlify CMS and redirects to Hexo site, the missing pieces]]></title>
            <link>https://medium.com/netlify/adding-netlify-cms-and-redirects-to-hexo-site-the-missing-pieces-c69a8ec053d1?source=rss-76ccb607e2cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c69a8ec053d1</guid>
            <category><![CDATA[redirect]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <category><![CDATA[internationalization]]></category>
            <category><![CDATA[hexo]]></category>
            <dc:creator><![CDATA[Luna]]></dc:creator>
            <pubDate>Thu, 26 Jul 2018 00:45:09 GMT</pubDate>
            <atom:updated>2018-08-09T00:42:14.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*LC1x7InkJ0izDq95fJEm-A.png" /></figure><p>Recently, I learned how to build and deploy my first Hexo site following <a href="https://www.netlify.com/blog/2015/10/26/a-step-by-step-guide-hexo-on-netlify/">A Step-by-Step Guide: Hexo on Netlify</a>.</p><p>In order to create a better editorial experience and support internationalization, I added Netlify’s CMS and redirect rules to my site. You can find <a href="https://templates.netlify.com/template/hexo-starter-theme-material/">my project on JAMstack templates</a> if you want to follow along. Now, sit back, grab a coffee and let me tell you what I discovered.</p><h3>Russian doll your repos — .gitsubmodule</h3><p>By default, Hexo generates boilerplate with a default theme called “Landscape”. It’s functional, it looks okay, but to be honest, it’s not what I want. It’s tempting to create a theme from scratch, but to quickly put together boilerplate with Netlify CMS and redirect rules, and to avoid maintenance worries, I decided to go with an existing one.</p><p>I found a popular theme called <a href="https://github.com/viosey/hexo-theme-material">Material</a>. I forked its Git repository and then added a <em>.gitsubmodules</em> file to the root folder of my site’s repo to include the theme as a sub-folder. If you’re not familiar with Git submodules, you can learn the basics by following along with this article: <a href="https://chrisjean.com/git-submodules-adding-using-removing-and-updating/">Git Submodules: Adding, Using, Removing, Updating</a>. There are lots of resources available to help you learn more advanced tricks about Git submodules. Google around if you want to dive deep.</p><h3>Add Netlify CMS to the site</h3><p>Following the tutorial “<a href="https://www.netlifycms.org/docs/add-to-your-site/">Add Netlify CMS to Your Site</a>”, I created an admin folder under my site’s source folder, which includes an <em>index.html</em> and a <em>config.yml</em> file.</p><p><strong>Add Netlify Identity Widget</strong></p><p>Netlify CMS works hand-in-hand with <a href="https://www.netlify.com/docs/identity/">Netlify’s Identity service</a>. To add it to my site, I needed to include the following script in the <em>&lt;head&gt;</em> of my CMS index page at<em> /admin/index.html</em>, as well as in the <em>&lt;head&gt;</em> of my site’s main index page.</p><pre>&lt;script src=&quot;https://identity.netlify.com/v1/netlify-identity-widget.js&quot;&gt;&lt;/script&gt;</pre><p>Normally, front matter is where we store and access data of a post. Hexo allows us to introduce external data and reuse it in different places by storing data files under <em>source/_data</em> folder. It’s like a “mini database” that we store modularized data. Both YAML and JSON format are supported.</p><p>My goal was to rewrite the <em>&lt;head&gt;</em> of my site’s main index page with the external script tag.</p><p>I noticed that in the <em>head.ejs</em> file under <em>themes/layout/partial</em> folder, the following condition is included to allow the use of a custom <em>&lt;head&gt;</em>.</p><pre><em>&lt;!-- Custom Head --&gt;</em></pre><pre>&lt;% if (site.data.head) { %&gt;</pre><pre>  &lt;% for (var i in site.data.head) { %&gt;</pre><pre>    &lt;%- site.data.head[i] %&gt;</pre><pre>  &lt;% } %&gt;</pre><pre>&lt;% } %&gt;</pre><p>All that’s needed to do now is to store the Netlify Identity widget script inside a <em>head.json/yml</em> file and put it under the <em>source/_data</em> folder.</p><p>Tada! A Netlify Identity widget has been successfully added to the site. Now I can manage CMS admin users for my site without requiring them to have an account with my Git host or commit access on my repo.</p><p><strong>Skip render folder and files</strong></p><p>It turned out, there were some conflicts between the CSS of the theme and the Netlify CMS admin interface. I noticed that Hexo allows us to specify folders and files that shouldn’t be rendered by the Hexo engine by adding the path to <em>skip_render</em> rule in the root <em>_config.yml</em> file.</p><p>Here’s what I did. I added the following rule to tell Hexo not to render anything under the admin folder.</p><pre>skip_render:</pre><pre>  - &quot;*admin/*&quot;</pre><p>It worked! Now the admin interface is no longer overlapping the site home page.</p><p><em>This might not be necessary, depending on what kind of theme you use. It’s just something to tuck under your belt in case you bump into the same issue.</em></p><h3>Internationalization and redirects</h3><p>Sometimes site content needs to be available in different languages for members of the audience who do not read in English. We can certainly make a site more personalized by using Hexo’s internationalization/localization and Netlify’s redirect rules.</p><p><strong>Multi-language support</strong></p><p>First, make sure you have all the language files added to the language folder under the theme folder. Our example theme has it set up for us.</p><p>Secondly, change the language setting in the <em>_config.yml</em> file to specify the languages you want to present your site.</p><pre>language:</pre><pre>  - [language_01]</pre><pre>  - [language_02]</pre><pre>  - [language_03]</pre><p>By default, the <em>i18n_dir</em> is set to be <em>:lang</em>, which means that Hexo will detect the language within the first segment of URL. This plays well with our redirect rules that’ll soon be added.</p><p><strong>Add redirect rules</strong></p><p>Netlify’s <a href="https://www.netlify.com/docs/redirects/#geoip-and-language-based-redirects">GeoIP and language based redirects</a> feature allows us to show targeted content according to geo location and browser preference. In our case, we’d like to show posts in our user’s preferred language.</p><p>You can add specific rules in a _redirects file under your root directory or <a href="https://www.netlify.com/docs/redirects/#structured-configuration">add more structured rules</a> in a <em>netlify.toml</em> file. The following examples are created in a <em>_redirects</em> file.</p><p>Example code of location based redirect rules:</p><pre>/ /china 302 Country=cn,hk,tw</pre><p>Example code of language based redirect rules:</p><pre>/ /zh-cn 302 Language=zh</pre><p>Now, if your users reside inside China, Hong Kong or Taiwan, they’ll be taken to <a href="https://yourwebsite.com/china">https://yourwebsite.com/china</a> when they type in the site URL. And if the language preference of their browser is set to be zh-cn, they’ll be taken to <a href="https://yourwebsite.com/zh-cn/">https://yourwebsite.com/zh-cn/</a>. You can apply this technique for any other languages.</p><p>Feel free to do whatever you want with your folder structure. But make sure that the file paths in the redirect rules match your folder structure. E.g., I created a zh-cn folder for all the pages in Chinese and added an about folder with an about page:</p><pre>source/</pre><pre>├── _data</pre><pre>│   └── head.json</pre><pre>├── _posts</pre><pre>│   ├── Platero</pre><pre>│   │   └── platero.jpg</pre><pre>│   ├── Platero.md</pre><pre>│   ├── hello-world.md</pre><pre>│   └── 你好.md</pre><pre>├── _redirects</pre><pre>├── admin</pre><pre>│   ├── config.yml</pre><pre>│   └── index.html</pre><pre>├── images</pre><pre>│   └── uploads</pre><pre>│       └── netlify-logo.png</pre><pre>└── zh-cn</pre><pre>├── about</pre><pre>│   └── index.md</pre><pre>└── index.md</pre><p>You might have noticed that in my <em>_redirects</em> file, I specified <em>/zh-cn/</em>about as a redirect rule for the about page in simplified Chinese. So when somebody visits <a href="https://yourwebsite.com/about">https://yourwebsite.com/about</a>, they’ll be redirected to <a href="https://yourwebsite.com/zh-cn/about">https://yourwebsite.com/zh-cn/about</a> if their language preference is <em>zh-cn</em>.</p><p><strong>Single language home page and archives page</strong></p><p>Time to get a bit fancier. By default, our theme shows all the posts in all languages on the home page. That doesn’t look great when we apply our redirect rules and target content based on language preference.</p><p>Luckily, I found a plug-in called <a href="https://github.com/xcatliu/hexo-generator-index-i18n">hexo-generator-index-i18n</a><strong> </strong>to solve the problem. It generates an index page for each language you have. And you can add configuration in your <em>_config.yml</em> file to show only one language on the index page.</p><p>Here’s how it works.</p><p>First you need to remove the existing plug-in in your <em>package.json</em> file:</p><pre>&quot;hexo-generator-index&quot;: &quot;^0.2.0&quot;</pre><p>Then, install the new plug-in. And then you’ll need to add <em>single_language_index</em> under <em>index_generator</em> in your <em>_config.yml</em> file, and set the value to be <em>true</em>.</p><pre>index_generator:</pre><pre>path: &#39;&#39;</pre><pre>per_page: 10</pre><pre>order_by: -date</pre><pre>single_language_index: true</pre><p>Also, add <em>:lang</em> in permalink so that the post links match the redirect rules.</p><pre>permalink: :lang/:year/:month/:day/:title/</pre><p>Now, if you go to the home page again, you should be only seeing posts in one language.</p><p>Same applies to the archives directory. You can use the <a href="https://www.npmjs.com/package/hexo-generator-multilingual-archive">hexo-generator-multilingual-archive</a> plug-in to localize archived posts, except that you don’t need to modify the <em>_config.yml</em> file.</p><p>That’s it. I hope this is helpful to you. Feel free to connect on <a href="https://twitter.com/lunaceee">twitter</a>. I’d love to hear from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c69a8ec053d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netlify/adding-netlify-cms-and-redirects-to-hexo-site-the-missing-pieces-c69a8ec053d1">Adding Netlify CMS and redirects to Hexo site, the missing pieces</a> was originally published in <a href="https://medium.com/netlify">Netlify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I joined a San Francisco startup as a software engineer]]></title>
            <link>https://medium.com/netlify/how-i-joined-a-san-francisco-startup-as-a-software-engineer-adc70e54a2?source=rss-76ccb607e2cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/adc70e54a2</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Luna]]></dc:creator>
            <pubDate>Sun, 07 Jan 2018 20:27:57 GMT</pubDate>
            <atom:updated>2018-01-07T21:19:04.369Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve gone through a few life-changing events in the past few years. I got a one-way ticket from Shanghai to San Francisco last year after deciding to call it home. I went through <a href="https://hackbrightacademy.com/">Hackbright Academy</a> after deciding to become a software engineer. And now, I’m one of the crew on a start-up ship, sailing towards the heart of the ocean with dreamers at <a href="https://www.netlify.com/">Netlify</a>.</p><p>There’s a lot to say about each of those life-changing experiences, and maybe one day I’ll write them down and share with you, but for now, I want to share what it was like to join Netlify.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vn9gmF6v5kBZ2IC-AOLLQ@2x.png" /></figure><h3>“We’re hiring. Let’s talk.”</h3><p>After I finished the software engineer fellowship program at <a href="https://hackbrightacademy.com/">Hackbright Academy</a>, I knew I wanted to pursue a career as a software engineer. I knew that given the chance to work in front end development, particularly to follow my enthusiasm for visual interactions and become a better communicator across design and development, I’d jump at it.</p><p>At the <a href="https://forwardjs.com/">ForwardJS</a> after-party, I bumped into <a href="http://mathias-biilmann.net/about">Mathias Biilmann</a><strong> </strong>who is the co-founder of Netlify. I was looking for alternative solutions to AWS for deploying my pet projects and hearing Matt describe Netlify’s platform had me immediately interested.</p><p>Towards the end of the conversation he said, “We’re hiring. Let’s talk.”</p><p>One of the first things I did after I went home was sign up for Netlify. With a few lines of code, I deployed my website successfully! It was way easier than I had even imagined.</p><p>Then I searched for Tweets from Netlify users. I saw a lot just like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*oN5J2IiKmC7j35KbyP6VVQ.png" /></figure><p>The combination of seeing the product in action and hearing from the community prompted me to reach out to Matt. He introduced me to David<a href="https://github.com/calavera"> </a>Calavera<a href="https://github.com/calavera">, CTO of Netlify</a>, and they gave me a short project as a technical assessment. The project was to create a single page application using React.js that consumes an API endpoint. The main goal was to evaluate my understanding of general front-end coding patterns, React.js, error handling, and asynchronous programming.</p><h3>“We’ll give you a laptop and you’ll figure things out. We’ll be here to help.”</h3><p>The technical assessment turned out to be one of the best experiences I’ve had interviewing!</p><p>I really appreciated the amount of empowerment and access the Netlify team provided throughout the interview process. I was given full autonomy to decide the scope of the project, interacted with the team over Slack to ask any questions that came up, and received constructive feedback after I submitted my work. I was able to get a sense of what it would really be like to work at the company.</p><p>During the final interview, Matt and his co-founder <a href="https://www.linkedin.com/in/christianbachdk/">Chris</a> indicated that, as an early stage start up, speed and shipping features are the top priority. While a candidate with experience is preferable, as the company grows, it’s hiring for drive, commitment to the space, and willingness to learn.</p><p>Soon after, I received the offer from Netlify. My first full-time job as a software engineer was at a San Francisco start-up!</p><p>“We’ll give you a laptop and you’ll figure things out. We’ll be here to help”. Matt said, half-joking.</p><h3>Shipping a feature on my second day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/353/1*gPgpsarYbCtjDRavuN0leg@2x.png" /></figure><p>While my friends were embracing Oktoberfest, I was celebrating my first day at Netlify.</p><p>Shortly after I greeted everyone in the office and found my desk, Matt offered me my first task to work on: updating Netlify’s <a href="https://www.netlify.com/docs/form-handling/">Form Handling</a> feature to add a hero card and CSV download button, enabling users to export all their form submissions.</p><p>Whoa… I couldn’t believe I was asked to implement a feature that directly interacts with users on day one!</p><p>But wait, where do I? How do I? What?!?</p><p>Luckily, my awesome teammate <a href="https://github.com/bcomnes">Bret</a> walked me through the codebase. Thanks to my supportive teammates, I was quickly able to start writing stories in <a href="http://storybook.js.org/">Storybook</a>. I deployed the form hero UI component the next day. From zero to “hero” in 24 hours!</p><h3>“There are no dumb questions!”</h3><p>In the first few days at my new job, good ol’ imposter syndrome found a burrow in my brain. Even though I’m no stranger to a professional working environment, it was still my first full-time job as a developer at a San Francisco start-up.</p><p>I was inundated with unfamiliar terms like <a href="https://jamstack.org/">JAMstack</a>, <a href="https://www.netlify.com/docs/continuous-deployment/">continuous deployment</a>, and <a href="https://www.netlify.com/docs/identity/">identity</a>.</p><p>My co-worker, Irene, sensed something and told me, “I know it’s really hard to believe that there are ‘no dumb questions’! I feel it all the time and worry that I’m going to sound dumb when I ask, but for every question you have, there is most likely at least one other person in the team with the same question who hasn’t dared to ask, and would really appreciate someone bringing it up.”</p><p>This is something I’ll remember for the rest of my life.</p><h3>Team Netlify</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*cf1GcKkWRLelgXHdt9zRKw@2x.png" /></figure><p>I was happily surprised by how many different viewpoints are represented at Netlify.</p><p>As a team of 20ish people, our footprints cover Spain, England, Portugal, Kenya, China and states across the U.S.. Nearly half of the team has international backgrounds.</p><p>Many of the team work remotely across several different time zones. Most of our communication happens over Slack or in GitHub issues. Most of the decisions and actions are made through GitHub.</p><p>I used to have doubts about working within a remote team structure — mostly because I’ve never experienced it before, and the effectiveness of communication remained a question mark for me.</p><p>Now, I’m convinced remote teams can really work. I’ve noticed that if there’s any problem with communication, it’s most likely not because of being in different locations and different time zones.</p><p>In fact, having a global team helps us best serve our clients from all over the world and allows potential candidates to have more flexibility in where they want to live.</p><h3>Three months in at Netlify</h3><p>Time flies, it’s been three months since I joined Netlify. In my first month I shipped two UI features, completed my first UX/UI research, wrote my first technical blog post and documentation, attended my first <a href="https://githubuniverse.com/">GitHub Universe</a> conference. The two months that followed brought more features and announcements, a week-long all-team gathering, and unexpected projects like implementing a UI for <a href="https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language">SAML</a> Support.</p><p>I can’t say enough about how much I appreciate the amount of support I’ve received from everyone on the team and the potential I see for my own growth alongside these amazing people.</p><p>From professional backgrounds to personal traits, every Netlifier strikes me as a superstar. Yet, everyone is humble enough to learn from each other and support each other and take care of each other when “shit happens”.</p><p>Along those lines, Netlify is still growing. If the above made you think that you might want to join us and help create an extraordinary platform for developers, check out our <a href="https://www.netlify.com/careers/">career page</a>.</p><p>As Matt says, “We’re hiring. Let’s talk.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adc70e54a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netlify/how-i-joined-a-san-francisco-startup-as-a-software-engineer-adc70e54a2">How I joined a San Francisco startup as a software engineer</a> was originally published in <a href="https://medium.com/netlify">Netlify</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>