<?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 Philip I. Thomas on Medium]]></title>
        <description><![CDATA[Stories by Philip I. Thomas on Medium]]></description>
        <link>https://medium.com/@philipithomas?source=rss-760075200480------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*31h8knKLnLkFfn5cHk_yTg.jpeg</url>
            <title>Stories by Philip I. Thomas on Medium</title>
            <link>https://medium.com/@philipithomas?source=rss-760075200480------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:58:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@philipithomas/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[Denouement]]></title>
            <link>https://medium.com/staffjoy-blog/denouement-abe7d26f2de0?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/abe7d26f2de0</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Mon, 03 Apr 2017 20:27:31 GMT</pubDate>
            <atom:updated>2017-04-04T02:10:02.181Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we are filing the Certificate of Dissolution for<a href="https://www.staffjoy.com/"> Staffjoy</a>. Since <a href="https://blog.staffjoy.com/staffjoy-is-shutting-down-39f7b5d66ef6">announcing our shutdown</a>, I have been busy. I helped our former team transition, and they now all have accepted stable contract work or jobs. I open-sourced <a href="https://github.com/staffjoy">ten repos of our code on Github</a> (<em>see below</em>). I published the <a href="https://blog.staffjoy.com/staffjoys-pitch-decks-that-raised-1-7m-15812018968">pitch decks we used to raise $1.7M in funding</a> and our<a href="https://blog.staffjoy.com/staffjoys-yc-fellowship-application-5771c8a105cd"> Y Combinator Fellowship application.</a></p><p>Our small business customers transitioned to different scheduling tools, like <a href="https://joinhomebase.com/">Homebase</a>. Our large customers deployed Staffjoy on-premise using the open-source code. I returned 90% of our cash to investors last week. We will pay out remaining cash after completing final obligations (like taxes).</p><p>I learned a lot through starting Staffjoy. Even though it failed, I am glad that our team had the opportunity to go through this experience together. I’m optimistic about the future, and excited for next steps.</p><h3>Open-Source Overview</h3><p>We are leaving our <a href="https://www.staffjoy.com/">homepage</a> online to help provide teams with open scheduling options. The two Staffjoy apps are now free and open-sourced under MIT licenses.</p><h4>V1, AKA “Suite” — Auto-scheduling for hundreds of workers</h4><p>This app focused on automated scheduling, which reduced costs. Early customers emailed us spreadsheets, which we ran through calculations and returned. We went on to build a web app, mobile apps, and new algorithms . We kept each service in a different code repository, which is why there are so many links below. We stopped active development of this product in July 2016. An early architecture overview of the architecture is<a href="https://blog.staffjoy.com/our-stack-dcb03fc8b4d8"> available here</a>.</p><ul><li><a href="https://github.com/Staffjoy/autoscheduler">autoscheduler:</a> Original auto-scheduling algorithm and microservice. Deprecated in early 2016 in favor of Chomp and Mobius (below). Published for informational purposes — no longer compatible with the suite web app.</li><li><a href="https://github.cm/staffjoy/suite">suite:</a> Web app and API in Flask. The core repo of V1.</li><li><a href="https://github.com/Staffjoy/mobius-assignment">mobius-assignment:</a> Microservice that assigns workers to shifts, subject to compliance</li><li><a href="https://github.com/Staffjoy/chomp-decomposition">chomp-decomposition</a>: Microservice that converts forecasting data into shifts.</li><li><a href="https://github.com/Staffjoy/suite-cron">suite-cron:</a> Microservice that triggers the Suite cron jobs</li><li><a href="https://github.com/Staffjoy/mobile">mobile</a>: React Native mobile apps for Android and iOS. These are basic wrappers around the web app, not full implementations.</li><li><a href="https://github.com/Staffjoy/client_python">client_python</a>: Python API client for Suite, used for our smoke testing and microservices.</li></ul><h4>V2 — Schedule with text messages for small businesses</h4><p>This app solves a communication problem for small business scheduling. You can learn about our V1 to V2 journey in<a href="https://blog.staffjoy.com/staffjoy-v2-ca15ff1a1169"> Tommy’s blog post</a>. V2 provides a simple click-and-drag interface for managers. Workers receive shifts through text messages. We put all microservices in the same “monorepo” for simplicity. An overview of the V2 architecture is<a href="https://blog.staffjoy.com/staffjoys-v2-architecture-9d2fcb4015fd"> available here</a>.</p><ul><li><a href="https://github.com/staffjoy/v2">V2</a>: Complete code for V2 in a single repo</li></ul><h3>Key Learnings</h3><ul><li><strong>Don’t avoid hard decisions</strong>. Whether it’s hiring, firing, or shutting down, be decisive. If you put off decisions, you only frustrate those around you.</li><li><strong>Cofounders should have different skills</strong>. One of the issues we had was that our founding team had high overlap in our skills. This made it tough to divide ownership of areas of the business.</li><li><strong>We didn’t build a product for ourselves</strong>. This made it hard to tell whether we were making something people wanted. To compensate, we had to spend a lot of time doing research and prototyping.</li><li><strong>A founder should be the first salesperson</strong>. I realize now that we hired sales too early. We should have had a founder do sales. This is key for navigating product/market fit. In retrospect, I wish that I had done the first $30K+ in sales before hiring. With our V2 launch, I made myself the salesperson. Viewing leading data rather than lagging data contributed to a swift shutdown decision.</li><li><strong>Control money to make money</strong>. In workforce management, I now realize that controlling payroll data is key. It’s tough to quantify the creation of value otherwise.</li><li><strong>Have air cover</strong>. What’s the huge problem that you solve? When our first product pitched “reduce labor costs 10%”, prospects wanted to learn more. I realize that our V2 didn’t solve as urgent of a problem. “Share schedules in less time” fixed something that wasn’t broken.</li><li><strong>If it’s not working, shut it down</strong>. We had a firm acquisition offer on the table, and soft offers from others. I didn’t like the terms, and they would have required me to work as a product manager. Shrewd advisors and investors taught me that a soft landing was not necessary at such a young company, and that it was better to move on.</li><li><strong>Great investors provide support when there is bad news</strong>. It’s tough to share bad news. I learned that great investors empower leaders during pivotal events. Thanks to Ray Tonsing and Semil Shah for some great advice during difficult times.</li><li><strong>Good technical talent is hard to find</strong>. When in hiring mode, I spent about a third of my time trying to source and close candidates. Hiring a candidate through a recruiter can cost $20K or more.</li><li><strong>When sourced and managed well, contractors filled our development needs</strong>. I had many friends who wanted to support us, but were not candidates for full-time employment. Selective application of specialized contractors fulfilled most of our development needs.</li></ul><h3>Future</h3><p>Our biggest problem while building Staffjoy was getting good technical talent. We shut down with $1M in the bank, in part because we could not spend the money quickly enough.</p><p>We solved this problem in part by hiring part-time contractors. One contractor was bootstrapping a startup, and worked one day a week to cover living costs. Another was a public school teacher who wanted to keep coding on the side. Many had day jobs, but wanted to experiment with new technology in their free time.</p><p>Recently, I co-founded a new company called<a href="https://www.moonlightwork.com/"> Moonlight</a>. Moonlight is a marketplace for software engineers and designers to find part-time work. The company is in its early stages, and we are matching workers to projects by hand right now. (You can<a href="https://www.moonlightwork.com/apply/"> apply to work</a> or<a href="https://www.moonlightwork.com/work/"> start a project</a>). Our first projects have been providing<a href="https://www.moonlightwork.com/staffjoy"> support and modification of Staffjoy’s open-source code</a>. We plan to launch a full marketplace app by the end of the summer.</p><p>In the past few weeks, I started freelancing to better learn the industry and live the lifestyle. The future of labor is remote, so I am moving to Mexico City for the summer. I am using this time to research remote work and to find time for deep focus while building Moonlight.</p><p>I’m seeking connections while in Mexico City — <a href="/service/mailto:mail@philipithomas.com">please feel free to email me</a>. If you need help building software, or if you want a part-time software job, check out<a href="https://www.moonlightwork.com/"> Moonlight</a>.</p><p>This may be the final post on the <a href="https://blog.staffjoy.com/">Staffjoy blog</a>. But, we can still stay in contact through my <a href="http://newsletter.philipithomas.com/">personal newsletter</a> or <a href="https://twitter.com/philipithomas">Twitter</a>.</p><p>Thanks to everybody who worked so hard to build Staffjoy! I look forward to hearing about your future successes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abe7d26f2de0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/denouement-abe7d26f2de0">Denouement</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Migrate Databases Automatically]]></title>
            <link>https://medium.com/staffjoy-blog/dont-migrate-databases-automatically-5039ab061365?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/5039ab061365</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Thu, 16 Mar 2017 19:27:42 GMT</pubDate>
            <atom:updated>2017-03-16T19:27:42.239Z</atom:updated>
            <content:encoded><![CDATA[<p>When we started Staffjoy, the original <a href="https://gist.github.com/philipithomas/190de362654601da43a08f3dc63ce4eb">continuous deployment script</a> automatically <a href="https://en.wikipedia.org/wiki/Schema_migration">migrated schemas</a> in our MySQL database prior to deploying the application version. However, with <a href="https://github.com/staffjoy/v2">Staffjoy V2</a>, we stopped automated database migrations in favor of manual migrations.</p><p>Bryan on Twitter reviewed our <a href="https://github.com/staffjoy">open-source code</a> and asks why:</p><h3>Bryan Cinman on Twitter</h3><p>@philipithomas Here&#39;s one :). What was the reasoning behind running migrations manually in prod rather than as part of the deploy?</p><p>The short answer: <strong>Migrating databases and deploying an new version of application code at the same time creates a race condition that can take down an application.</strong></p><h4>Migrating Before Deploying? 🤔</h4><p>Most deployment systems migrate a database before deploying new application code. We <a href="https://gist.github.com/philipithomas/190de362654601da43a08f3dc63ce4eb#file-deploy-to-stage-sh-L39">did this for our V1 repos</a> — and it normally worked quite well. When adding a new feature, we would need to add new database columns. So, the deploy would migrate the schema to add those columns to the production databases, then afterward the code that used those columns would deploy. In most cases, this strategy works well.</p><h4>Dropping Columns 🚨</h4><p>Migrating before deploys causes problems when modifying or dropping a column. If you run a migration that removes a column in a table, the running application may still expect that column to exist. If the column is not there, it can take down the application until the code deploy finishes.</p><p>This may seem theoretical, but most <a href="https://en.wikipedia.org/wiki/Object-relational_mapping">ORMs</a>, such as <a href="http://docs.sqlalchemy.org/en/latest/orm/loading_objects.html">SQLAlchemy</a>, select every column individually in a row when loading a model. So, if you drop an unrelated column in the `<em>users`</em> table, trying to verify a user’s password can fail until the database includes the normalization that the model expects.</p><p>We encountered this issue in production first when dropping a column in our `<em>users</em>` table in Staffjoy V1. SQLAlchemy failed to load the user model, so all authentication failed. This created a <strong>100% error rate in our API</strong>, which prevented users from accessing the application, clocking in, or doing anything until the application deploy finished. Our <a href="https://aws.amazon.com/elasticbeanstalk/">AWS Elastic Beanstalk</a> deploys for Staffjoy V1 were quite slow, so the application was functionally unavailable for over 10 minutes as the error rate precipitously dropped each time a new application container replaced an old one.</p><h4>Recap — How to migrate a database while deploying an application 📖</h4><p>In most cases:</p><ul><li>Add a column or table <strong>before</strong> deploying application code</li><li>Remove a column or table <strong>after</strong> deploying application code</li><li>Renaming a column or table is a special case, and in most cases should be <strong>avoided</strong> in order to prevent downtime ⛔️</li></ul><h4>Migration-only deploys ❓</h4><p>Technically, a way to automatically migrate tables without race conditions is to only allow deploys to contain either database changes or application changes. So, if you are adding a new feature, deploy the database migration, then in a separate deploy change the application code. If you are removing a column, deploy the application code change, then afterward run a deploy that contains the database migration.</p><p>In practice, I find enforcing this pattern to be unrealistic. Making database changes in full before modifying application code takes significant planning and decisiveness. When working with ORMs that automatically generate migrations, application changes are functionally required to generate a migration. Testing these deploy race conditions is difficult, and when developers become complacent with combining deploying migrations and application changes together, catching issues that could create downtime due to race conditions can be hard.</p><h4>Compromise: Manual deploys 🙃</h4><p>Due to the above issues, all database changes in Staffjoy V2 were manually run. That way, we could decide how to migrate the database on a case-by-case basis. We would also be prepared to quickly rollback changes if error rates increased.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5039ab061365" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/dont-migrate-databases-automatically-5039ab061365">Don’t Migrate Databases Automatically</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staffjoy’s Pitch Decks That Raised $1.7M]]></title>
            <link>https://medium.com/staffjoy-blog/staffjoys-pitch-decks-that-raised-1-7m-15812018968?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/15812018968</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 22:11:27 GMT</pubDate>
            <atom:updated>2017-02-16T22:23:19.405Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.staffjoy.com/"><em>Staffjoy</em></a><em> is </em><a href="https://blog.staffjoy.com/staffjoy-is-shutting-down-39f7b5d66ef6"><em>shutting down</em></a><em>. This post is a part of our efforts to open source parts of our startup journey.</em></p><p>To raise money for a company, you pitch potential investors on your business. They evaluate it on a variety of metrics such as growth, the strength of the founding team, the size of the potential market, and the terms of the round in order to determine whether they will make money. It’s important to keep in mind that most startup investors are not looking for modest returns — they want your business to have a chance at being worth over $1 billion. Logistically, raising a round of funding in the Bay Area can take anywhere from few weeks to multiple months.</p><p>As a first-time entrepreneur, I found it intimidating to give so many presentations about a nascent company. However, seeing other companies’ pitch decks demystified the process for me. For the benefit of future entrepreneurs, we’re opening our pitch decks so that you can learn from them.</p><h4>Y Combinator Fellowship Demo Day</h4><p>November 2015. No money raised, but we received a $12K grant from Y Combinator at the beginning of the program. You can <a href="https://blog.staffjoy.com/staffjoys-yc-fellowship-application-5771c8a105cd">read our YCF application here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2F7a6e5556bd774b089b37998f1d4b4a36&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fphilipithomas%2Fstaffjoy-y-combinator-fellowship-demo-day-pitch-deck&amp;image=https%3A%2F%2Fspeakerd.s3.amazonaws.com%2Fpresentations%2F7a6e5556bd774b089b37998f1d4b4a36%2Fslide_0.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="463" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2c7f064e14c73dd2ebd149150c5adfd/href">https://medium.com/media/c2c7f064e14c73dd2ebd149150c5adfd/href</a></iframe><h4>Angel Round</h4><p>December 2015. $520K raised.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2Ff82a2b5d1aef442d811fa423dbdf2a5c&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fphilipithomas%2Fstaffjoy-dec-2015-angel-round-pitch-deck&amp;image=https%3A%2F%2Fspeakerd.s3.amazonaws.com%2Fpresentations%2Ff82a2b5d1aef442d811fa423dbdf2a5c%2Fslide_0.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="463" frameborder="0" scrolling="no"><a href="https://medium.com/media/26040a8bb1933edba910e1654c1eaa5c/href">https://medium.com/media/26040a8bb1933edba910e1654c1eaa5c/href</a></iframe><h4>Seed round</h4><p>July 2016. $1.2M raised.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2F9fd8713e34a04bd3b546d57ec1935d04&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fphilipithomas%2Fstaffjoy-seed-round-pitch-deck&amp;image=https%3A%2F%2Fspeakerd.s3.amazonaws.com%2Fpresentations%2F9fd8713e34a04bd3b546d57ec1935d04%2Fslide_0.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="463" frameborder="0" scrolling="no"><a href="https://medium.com/media/bcf8c68cf60769be212e533a2d965518/href">https://medium.com/media/bcf8c68cf60769be212e533a2d965518/href</a></iframe><h4>My learnings about pitch decks</h4><ul><li><a href="https://blog.ycombinator.com/how-to-design-a-better-pitch-deck/">Make it legible</a>.</li><li>Lead with traction — Right after the title slide, show impressive metrics about your business.</li><li>Don’t specifically put in the deck that you are raising, everybody already knows it. Verbally state the terms, if they have already been set.</li><li>Focus on the huge, unaddressed problem that you solve. The opportunity matters more than the product you made, at least in the early stages.</li><li>Marginal improvements over competitors are not enough.</li><li>Your competitors are not other startups.</li><li>The size of the market is important. I like using <a href="http://askwonder.com/">Wonder</a> to do market sizing research. Opt for a bottom-up approach, e.g. “There are 75 million hourly workers in the USA. With $5/worker/month, that gives a $4.5B total attainable market”. A market size of under $1B is probably too small to be a good venture capital investment and a market size over $50B probably is too broad to be credible.</li><li>Do a live demo of your product. It creates credibility. However, always have a backup of slides ready to walk through.</li><li>Pick a core metric that shows week-over-week growth, and feature it prominently. Revenue is always good, but it can be a lagging indicator (especially with large deal sizes). We use “people scheduled per week.”</li><li>Your “GTM” (go to market strategy) slide explains how to you plan to grow. Do research on sales strategy, and understand how the deal size correlates with different sales methodologies.</li><li>Some approximate rules of thumb for sane sales strategies based on annual contract value (ACV): &lt;$1K ACV = self-serve, $1K–30K ACV = inside sales, &gt;$30K ACV(but more likely &gt;$100K) = enterprise sales.</li></ul><h4>Operations Advice</h4><ul><li>Don’t send investors your full deck until after you have met with them. Have an abbreviated “overview” deck that gets distributed before meeting (with metrics, industry overview, and GTM slides).</li><li>After meeting a potential investor, send access to a “deal room” with the deck, term sheet, cap table, major contracts, and any other important documents.</li><li>Many later-stage investors will hear your pitch, even if they don’t intend to invest in such small rounds. It’s common to hear “Let’s talk later during your Series A” — this is called the “A Pass”. It’s not a waste of time though— some will invest personal money or make valuable introductions. However, you can always ask for introductions to their portfolio companies — so research the companies that they have invested in beforehand to see if any are sales prospects or potential integration partners.</li></ul><h4>Conclusion</h4><p>I hope that these decks help you to understand the information that an investor expects in order to determine whether a business is a good investment. However, don’t spend too much time on fundraising, particularly in the early stages — a great business matters far more than a polished presentation.</p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15812018968" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/staffjoys-pitch-decks-that-raised-1-7m-15812018968">Staffjoy’s Pitch Decks That Raised $1.7M</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staffjoy’s YC Fellowship Application]]></title>
            <link>https://medium.com/staffjoy-blog/staffjoys-yc-fellowship-application-5771c8a105cd?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/5771c8a105cd</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ycombinator]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Wed, 15 Feb 2017 20:56:53 GMT</pubDate>
            <atom:updated>2017-02-16T18:25:42.684Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Staffjoy is </em><a href="https://blog.staffjoy.com/staffjoy-is-shutting-down-39f7b5d66ef6"><em>shutting down</em></a><em>. This post is a part of our efforts to open source parts of our startup journey.</em></p><p>On July 20, 2015, Y Combinator announced a new program called the <a href="https://blog.ycombinator.com/yc-fellowship/">Fellowship</a>. It was a shorter accelerator program for earlier-stage companies. The application window was only one week.</p><p>We had been working part-time on our idea <a href="https://www.staffjoy.com/">Staffjoy</a>, and it was slowly growing. I would code before work every day at Philz Coffee, then head straight from work to customer meetings. It was becoming clear that we needed to go full-time on the business, and YC Fellowship seemed like a great impetus to kickstart our startup journey.</p><p>The application was an abbreviated version of the standard Y Combinator application. Because we spent so much time talking to customers about our business, completing the application only took about an hour.</p><p>To my surprise, we were offered an interview! I took a vacation day to Caltrain to Mountain View, where we spoke with YC partners Justin Kan and Jon Levy.</p><p>An update email arrived the next day. I originally thought that it was a rejection, because YC Core historically accepted applicants over phone. However, we were accepted! Staffjoy was one of <a href="https://blog.ycombinator.com/yc-stats/">33 companies</a> selected from over <a href="https://twitter.com/sama/status/626523690533027840?lang=en">6,500 applications</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1nmlB03Ym-sicfzMmQsrw.png" /></figure><p>The program started in September 2015, and lasted for eight weeks. Group and individual office hours were mainly in-person at the YC headquarters in Mountain View. During them, we would discuss challenges with our business, and receive feedback and analysis on how to grow. The program ended with a demo day, where we presented our growth and traction to YC alumni.</p><p>The YC Fellowship program continued on for two more classes as a <a href="https://blog.ycombinator.com/fellowship-v2/">completely remote program</a>. The program was <a href="https://techcrunch.com/2016/09/13/with-a-new-ceo-y-combinator-will-wind-down-fellowships-and-start-a-mooc/">ended last year in favor of a forthcoming open online course</a>.</p><p>Mentorship from YC was critical to growing Staffjoy, and access to its community has been a valuable resource. <a href="https://apply.ycombinator.com/">Applications to the Summer 2017 class of YC are now open</a>, so for the benefit of applicants — we are sharing the original YCF submission by Staffjoy.</p><h3>Staffjoy’s YC Fellowship Application</h3><p><em>Parts of the application had to be left out due to sensitive customer information, including the video.</em></p><p><strong>Which of the following best describes your progress?</strong></p><p>Closed beta</p><p><strong>What is your company going to make?</strong></p><p>We are building an application that makes teams more efficient by automating shift scheduling and management.</p><p><strong>In two sentences, say the most impressive thing about this team / startup.</strong></p><p>We’ve been able to decrease labor costs between 5% and 10% at alpha customers just by better matching workforce supply to labor demand. For context, for <em>[redacted — one pilot user’s workforce] </em>— this has resulted in a $30K/yr estimated cost savings.</p><p><strong>Please tell us in one or two sentences about the most impressive thing that each founder has built or achieved.:</strong></p><p>Together we built a meetup for OpenDNS called OpenLate that has grown to &gt;2400 members between the SF and YVR offices. It’s contributed to <em>[redacted]</em>% of 2015 engineering hires.</p><p><strong>Why did you pick this idea to work on? Do you have domain expertise in this area? How do you know people need what you’re making?</strong></p><p>We both did academic research on scheduling in college, where Philip stumbled across the workforce scheduling problem. We want to bring applied mathematics to workforces. We’ve worked closely with key customers such as <em>[redacted]</em> to improve the algorithms, and now are amid deployments to their workforces.</p><p><strong>What’s new about what you’re making? What substitutes do people resort to because it doesn’t exist yet (or they don’t know about it)?</strong></p><p>1) It’s fast — the algorithms outpace human schedulers and academic papers on the “Nurse Rostering Problem”. <br>2) It’s efficient — our algorithm schedules 5%-10% better than a human. <br>3) It provides compliance — e.g. <em>[redacted]</em> considers it core to switching their workforce from 1099 to W-2 because it lets them cap couriers at 29 hours/week for compliance purposes.</p><p><strong>Who are your competitors, and what do you understand about your business that other companies in it just don’t get?:</strong></p><p>Our main competitor is Kronos, a hardware-based business that does $1B/yr in revenue. Key Kronos customers, e.g. Starbucks, are dissatisfied due to antiquated user experiences and bad workforce treatment. We are differentiating by building tools that workers love.</p><p><strong>How will you get users? How do or will you make money? How does this become a giant company?:</strong></p><p>We plan on targeting the retail, hospitality, and manufacturing industries for sustainable growth, which will require attending trade shows and building an inside sales team. We will charge an annual fee per scheduled user. The company becomes giant due to the product’s stickiness and projected low churn.</p><p><strong>How long have the founders known one another and how did you meet?</strong></p><p>We have known each other for 5 years, and we met through a tech student group while in college.</p><p><strong>How many users do you have?</strong></p><p>2 companies</p><p><strong>How much revenue? (one sentence max, if zero just say ‘none’):</strong></p><p>$5K ACV; hoping to close $15K this month.</p><p><strong>What is your monthly growth rate? (in users or revenue or both):</strong></p><p>Growing # of schedules generated by ~7% week over week.</p><p><em>Tomorrow we are opening the pitch decks from our seed rounds on </em><a href="https://blog.staffjoy.com/"><em>blog.staffjoy.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5771c8a105cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/staffjoys-yc-fellowship-application-5771c8a105cd">Staffjoy’s YC Fellowship Application</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staffjoy is shutting down]]></title>
            <link>https://medium.com/staffjoy-blog/staffjoy-is-shutting-down-39f7b5d66ef6?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f7b5d66ef6</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[scheduling]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Tue, 14 Feb 2017 21:20:08 GMT</pubDate>
            <atom:updated>2017-02-14T21:20:08.959Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2015 we started <a href="https://www.staffjoy.com/">Staffjoy</a> with the goal of creating flexibility for workers and businesses. The project began as an automated scheduling algorithm that I started as a college senior project. We found first customers in on-demand startups, which needed help managing growing workforces.</p><p>In September 2015, Staffjoy joined Y Combinator’s inaugural <a href="https://blog.ycombinator.com/yc-fellowship/">Fellowship program</a> and became our full-time job. During the program, we <a href="https://techcrunch.com/2015/10/22/staffjoy-launches-from-yc-fellowship-helping-businesses-automate-their-workforce-scheduling/">launched a scheduling application</a> based on our algorithms. The company tried expanding to non-startup customers as we grew, but we learned that our software was not a good fit for their needs. Some business managers did not think of scheduling in such a mathematical way. Others already had sophisticated workforce management systems. In the end, we lacked the resources to compete for enterprise contracts.</p><p>Last summer, we set out to build a V2 of Staffjoy focused on small business and simple communication. We found that many small businesses still use paper or spreadsheets. Their biggest scheduling problem was communication, because many workers relied on prepaid phones. V2 addressed this issue by using text messages to share schedules with hourly workers. After a <a href="http://venturebeat.com/2017/01/10/staffjoy-raises-1-2-million-to-help-small-businesses-manage-workflow-scheduling/">public launch in January</a>, we found that people were willing to try the product, but the conversion rate to paying customers was not high enough to sustain the business.</p><p>Our early adopters supported the vision and were happy users of the product. However, after 18 months of effort, the product has strayed away from our original vision, and we have failed to achieve product/market fit. I considered pivoting the business into a new concept in a different space with new co-founders, but that didn’t seem fair to investors or future employees. So, we have decided to return over $1M in cash to our investors and shutdown Staffjoy.</p><p>We will be shutting down Staffjoy service on March 15, 2017. We are immediately turning off new account signups and any pending subscription renewals. We plan to open-source the code for Staffjoy on <a href="https://github.com/staffjoy">our Github page</a>. Customers will have until the shutdown to retrieve existing data from Staffjoy. At that time, we will delete all user data.</p><p>Thank you to everybody that supported and built Staffjoy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f7b5d66ef6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/staffjoy-is-shutting-down-39f7b5d66ef6">Staffjoy is shutting down</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Philip’s Newsletter — Issue #10]]></title>
            <link>https://medium.com/@philipithomas/philips-newsletter-issue-10-942e2d42405d?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/942e2d42405d</guid>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Thu, 29 Dec 2016 21:12:00 GMT</pubDate>
            <atom:updated>2016-12-29T21:12:00.697Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello from Arizona. I’ve been enjoying recharging and reading this holiday break ahead of the public launch of Staffjoy V2.</p><h3>Writing</h3><figure><img alt="1*xsu3jhmpwbhsmcoiv1ynkq" src="https://cdn-images-1.medium.com/max/740/0*1RSI5N0FY806mrpk." /></figure><p><a href="https://blog.staffjoy.com/staffjoys-v2-architecture-9d2fcb4015fd?gi=5d3a639c6b12&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Staffjoy’s V2 Architecture — Staffjoy Blog</strong></a><strong> — </strong><a href="https://blog.staffjoy.com/staffjoys-v2-architecture-9d2fcb4015fd?gi=5d3a639c6b12"><strong>blog.staffjoy.com</strong></a></p><p>A look at how we built Staffjoy V2</p><figure><img alt="1*blgowtgcrj0q9hobwxsqjg" src="https://cdn-images-1.medium.com/max/740/0*_ZiJklLpLqsSGQ7J." /></figure><p><a href="https://42hire.com/3-questions-with-staffjoy-ceo-philip-i-thomas-2bc4369ba024?gi=2444f006c375&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>3 Questions With Staffjoy CEO Philip I. Thomas — Don’t Panic, Just Hire</strong></a><strong> — </strong><a href="https://42hire.com/3-questions-with-staffjoy-ceo-philip-i-thomas-2bc4369ba024?gi=2444f006c375"><strong>42hire.com</strong></a></p><p>I was interviewed for the blog “Don’t Panic, Just Hire”, and I discussed our pivot for Staffjoy.</p><h3>Articles</h3><figure><img alt="7fccb75f25d36501f1efe466719c9f35?1482175707" src="https://cdn-images-1.medium.com/max/740/0*96gndg_XFn0IDL66." /></figure><p><a href="http://cdixon.org/2011/02/05/selling-pickaxes-during-a-gold-rush/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Selling pickaxes during a gold rush</strong></a><strong> — </strong><a href="http://cdixon.org/2011/02/05/selling-pickaxes-during-a-gold-rush/"><strong>cdixon.org</strong></a></p><p>After building software for awhile, I’ve been thinking a lot about the tools that our business needs. Chris Dixon describes this as “selling pickaxes during a gold rush”.</p><h3>Books</h3><figure><img alt="Social" src="https://cdn-images-1.medium.com/max/740/0*Ez9f30l4zKM4m0yd." /></figure><p><a href="https://stripe.com/atlas/guide?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Stripe: Atlas Guide</strong></a><strong> — </strong><a href="https://stripe.com/atlas/guide"><strong>stripe.com</strong></a></p><p>A book that outlines the basics of running a company, from incorporation to bookkeeping.</p><figure><img alt="Nav sprite global bluebeacon 1x optimized. cb281044790 " src="https://cdn-images-1.medium.com/max/740/0*SEqZffNhK3QQlS_b." /></figure><p><a href="https://www.amazon.com/gp/product/1491933178/ref=as_li_qf_sp_asin_il_tl?camp=1789&amp;creative=9325&amp;creativeASIN=1491933178&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=11683080aa329f63e47d90be75d394d6&amp;tag=sagacionlook-20&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>The Hitchhiker’s Guide to Python: Best Practices for Development</strong></a><strong> — </strong><a href="https://www.amazon.com/gp/product/1491933178/ref=as_li_qf_sp_asin_il_tl?camp=1789&amp;creative=9325&amp;creativeASIN=1491933178&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=11683080aa329f63e47d90be75d394d6&amp;tag=sagacionlook-20"><strong>www.amazon.com</strong></a></p><p>A book about Python software development — but does not specifically talk about the programming language. I found it helpful to learn about best practices, “gotchas”, and popular tools. I wish that it existed for more programming languages.</p><figure><img alt="Nav sprite global bluebeacon 1x optimized. cb281044790 " src="https://cdn-images-1.medium.com/max/740/0*kXGjCGmHBcRzH_lC." /></figure><p><a href="https://www.amazon.com/gp/product/0345453743/ref=as_li_qf_sp_asin_il_tl?camp=1789&amp;creative=9325&amp;creativeASIN=0345453743&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=976248d2261d0ca4ed24594657b256c5&amp;tag=sagacionlook-20&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>The Hitchhiker’s Guide to the Galaxy</strong></a><strong> — </strong><a href="https://www.amazon.com/gp/product/0345453743/ref=as_li_qf_sp_asin_il_tl?camp=1789&amp;creative=9325&amp;creativeASIN=0345453743&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=976248d2261d0ca4ed24594657b256c5&amp;tag=sagacionlook-20"><strong>www.amazon.com</strong></a></p><p>The original Hitchhiker’s Guide made a great vacation read. 42!</p><h3>Gadgets</h3><figure><img alt="14693911 1808859189370350 2562268727336763392 n" src="https://cdn-images-1.medium.com/max/740/0*Oau4BuzR3Hn3aigT." /></figure><p><a href="https://www.instagram.com/p/BMdgVUxjRq2/?hl=en&amp;taken-by=unimaticwatches&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Unimatic Watches</strong></a><strong> — </strong><a href="https://www.instagram.com/p/BMdgVUxjRq2/?hl=en&amp;taken-by=unimaticwatches"><strong>www.instagram.com</strong></a></p><p>I saw this on Instagram on my birthday, and really liked their designs. I read the <a href="https://www.hodinkee.com/articles/unimatic-modello-uno-u1-b-dive-watch-hands-on">story of the company and its founders on Hodinkee</a>, and ended up buying the U1-C as an everyday watch.</p><h3>Apps</h3><h4><a href="https://slackhq.com/slack-calls-now-with-100-more-video-50bf365a0d98?gi=6e57383606fa&amp;ref=producthunt&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue">Slack Video Calls</a></h4><p><a href="https://slackhq.com/slack-calls-now-with-100-more-video-50bf365a0d98?ref=producthunt&amp;gi=6e57383606fa">slackhq.com</a></p><p>This is a game-changer for users of Slack.</p><h4><a href="https://www.spacious.com/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue">Spacious</a></h4><p><a href="https://www.spacious.com/">www.spacious.com</a></p><p>Spacious turns restaurants into co-working spaces during the day. I love this idea.</p><figure><img alt="Social logo" src="https://cdn-images-1.medium.com/max/740/0*HU22l_1o7ynaJSph." /></figure><p><a href="https://bold.co/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Bold</strong></a><strong> — </strong><a href="https://bold.co/"><strong>bold.co</strong></a></p><p>We have an internal blog at Staffjoy for user interviews and other notes. Our system is hacked together — Bold seems to be a better way.</p><figure><img alt="Educate f4fd9a62c091d639ca3f33834e6164fd9e4d8e9aa79fe8d8f912a1d9c4b20262" src="https://cdn-images-1.medium.com/max/740/0*d8OPUIuCTqf24UwS." /></figure><p><a href="https://www.intercom.com/customer-support-software/knowledge-base?r&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Knowledge Base Software | Intercom</strong></a><strong> — </strong><a href="https://www.intercom.com/customer-support-software/knowledge-base?r"><strong>www.intercom.com</strong></a></p><p>Intercom rocks. This new product in their suite seems like a worthy addition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=942e2d42405d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staffjoy’s V2 Architecture]]></title>
            <link>https://medium.com/staffjoy-blog/staffjoys-v2-architecture-9d2fcb4015fd?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d2fcb4015fd</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Wed, 21 Dec 2016 17:53:25 GMT</pubDate>
            <atom:updated>2021-12-21T16:02:39.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*xsu3JHMpWbhsmCOIv1yNKQ.jpeg" /></figure><h3>Summary</h3><ul><li>Docker on Kubernetes using Google Container Engine</li><li>Bazel build system</li><li>Go microservice backend</li><li>Redux front-end applications</li><li>gRPC for internal communication</li><li>Structured logging</li></ul><h3>Background</h3><p>We built Staffjoy V1 using <a href="http://flask.pocoo.org/">Flask</a> (covered more <a href="https://blog.staffjoy.com/our-stack-dcb03fc8b4d8">here</a>). Things worked well — until we started to build more services and integrations. Each service required its own new repo, new CI jobs, and new servers. There had to be a better way!</p><p>Around July of this year, we decided to completely redo our product. We had to make some major changes to data normalization and deployments. We decided that starting fresh would be the best way.</p><p>With V2, we wanted to focus on messaging and integrations. We decided to use a microservice approach. One way we maintain simplicity is by using different databases for different services. That way, changes are less scary, and new services can use the best datastore for their needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pS-k8X90ze9qlbB62uj4fQ.png" /><figcaption>Staffjoy’s backend services are all written in Go. (The Go gopher was designed by <a href="http://reneefrench.blogspot.com/">Renee French</a>.)</figcaption></figure><p><a href="https://en.wikipedia.org/wiki/Strong_and_weak_typing">Weak typing</a> caused most of our runtime errors in V1. To address this, we decided to use strong typing everywhere possible. So, V2 uses <a href="https://developers.google.com/protocol-buffers/">protocol buffers</a>, <a href="http://golang.org/">Go,</a> and <a href="http://mysql.com/">MySQL</a>. (Our frontend uses Javascript, but I aspire to change it to <a href="https://www.typescriptlang.org/">Typescript</a>!) Based on my Go experience at <a href="https://opendns.com/">OpenDNS</a>, I thought that it would address our issues with Python. In particular, I like being able to execute asynchronous tasks without queues. This simplifies tasks such as sending email or executing callbacks.</p><p>To force ourselves to immediately think in microservices, we made a radical decision. We separated account logic and company logic into separate services. The services have separate MySQL databases, separated by a firewall. This forces us to rely on gRPC instead of SQL JOIN statements to get a worker’s name.</p><h3>Development and Build System</h3><p>To start, we chose to use a monorepo. We store all code for V2 in a single <a href="https://github.com/">Github</a> repo. Logic becomes centralized, which allows for easier refactoring across the code base. It also allows us to provision new services using committed configuration files.</p><p>Google recently open-sourced <a href="https://bazel.build/">Bazel</a>, a build system inspired by their internal Blaze system. It makes monorepos fast by caching builds. Bazel also understand how code changes invalidate its caches. This means that building our 14 Docker images normally takes less than a minute. Bazel works smoothly with Go and its dependencies. But, we still have not figured out how to best handle JavaScript dependencies.</p><p>When you publish a shift on Staffjoy, we send a text message to each worker alerting them of their schedule. The process of changing a shift can involve as many as six different microservices. To aid development, we want our developers to be able to run the complete environment on their laptop. We chose to run run Kubernetes inside of <a href="https://www.vagrantup.com/">Vagrant</a> for development purposes. One reason we did this is that we rely on Kubernetes’ DNS for service discovery. To save RAM, we sometimes JavaScript code against our staging environment.</p><h3>Faraday — Authentication and Proxy</h3><p>When a user logs in, we set a JSON web token. We built a proxy layer called Faraday to manage user authentication. Faraday reads HTTP request, then sets internal metadata about the authentication and authorization. This allows internal services to identify users with minimal code. Faraday also routes requests to the correct service inside Kubernetes.</p><p>Faraday is the only Staffjoy service that faces the Internet. Because all web traffic goes through it, we added in some convenience features. For instance, Faraday improves security in a variety of ways. It redirects HTTP traffic to HTTPS, and it sets HSTS headers. Every request has its latency measured by Faraday and reported to <a href="https://cloud.google.com/trace/">Google Cloud Trace</a>. In the future, we plan to continue improving Faraday. For example, we plan to standardize favicons through it.</p><h3>Web Apps in Redux</h3><p>Our front-end applications use <a href="https://webpack.github.io/">Webpack</a>, <a href="https://facebook.github.io/react/">React</a>, and <a href="https://github.com/reactjs/react-redux">Redux</a>. These libraries have made it straightforward to build complex interfaces, such as draggable cards. In development, we use <a href="https://github.com/storybooks/react-storybook">react-storybook</a> to build components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rLb3n1Q2r3uFSmy2wyzXUg.png" /><figcaption>Staffjoy Scheduling UI</figcaption></figure><h3>Protocol Buffers and gRPC</h3><p>If you’re used to a JSON over HTTP REST API, then Protocol Buffers with gRPC serve a similar purpose. Protocol Buffers are a strong-typed serialization tool from Google. The library generates clients in a variety of programming languages. gRPC is a messaging protocol over HTTP2. Instead of REST endpoints, gRPC defines functions on Protocol Buffer message types.</p><p>To build a REST API for use by our front-end applications, we use <a href="https://github.com/grpc-ecosystem/grpc-gateway">grpc-gateway</a>. It lets us annotate gRPC functions to map them to HTTP routes. It even auto-documents every endpoint using <a href="http://swagger.io/">Swagger</a>- check out our <a href="http://company.staffjoy.com/ui/">company docs</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bANxwAh3D-52JLV_wdTxgw.png" /><figcaption>grpc-gateway automatically generates a Swagger specification for the API</figcaption></figure><p>We use the <a href="https://github.com/go-gorp/gorp">Gorp</a> library where possible to map Go structs to database columns for simple CRUD. To use Protocol Buffers with Gorp, we need to add tags to the generated protocol buffer structs. We do this using <a href="https://github.com/gogo/protobuf">GoGoProto</a>, a library that extends Protocol Buffers.</p><p>Finally, we use <a href="https://github.com/sirupsen/logrus">Logrus</a> for structured logging. Stackdrivers’ logging interface makes it easy to query structured logs. We have already implemented a full audit log for keeping track of all changes to the database.</p><h3>Building a Bot</h3><p>To tell workers when they have shifts, Staffjoy communicates through text messages. In our user studies, we found that many restaurant managers share schedules over SMS. We aim to replace this manual workflow with an notification bot.</p><p>We started with a simple bot, and we improve it almost every day. We chose to make the messaging logic agnostic of the communication layer. This means that we can add new messaging systems in the future.</p><p>Using Go, we send asynchronous messages about shift changes to the bot service. The bot service then decides how to notify workers. In the future, we plan to build in better state management. We also want workers to be able to query the bot.</p><h3>Continuous Integration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OekV89u3Q15LScNrvO10pw.png" /><figcaption>Clean Jenkins with only three jobs</figcaption></figure><p>We use Jenkins to test, build, and deploy Staffjoy’s Git repo. We only have three jobs:</p><ul><li>Pull request tester</li><li>Build, test, and deploy changes from the “master” branch to our staging environment</li><li>Promote builds from staging to production</li></ul><h3>Conclusion</h3><p>Microservices took time to configure, but have already been helpful. Most backend services now have three or fewer Go files. This simplicity reduces the overhead of making changes or adding new services.</p><p>If you’re interested in hacking on microservices, messaging, and scheduling — <a href="http://staffjoy.com/careers/">we’re hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d2fcb4015fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/staffjoys-v2-architecture-9d2fcb4015fd">Staffjoy’s V2 Architecture</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Philip’s Newsletter — Issue #9]]></title>
            <link>https://medium.com/@philipithomas/philips-newsletter-issue-9-f24527e111d7?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/f24527e111d7</guid>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Mon, 05 Dec 2016 17:43:13 GMT</pubDate>
            <atom:updated>2016-12-05T17:43:13.167Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been a crazy few weeks. I went to St. Louis to judge a hackathon. The Staffjoy V2 entered limited availability. We launched a new series called <a href="https://www.amazon.com/gp/product/0307463745/ref=as_li_tl?ie=UTF8&amp;tag=philipithomas-newsletter-20&amp;camp=1789&amp;creative=9325&amp;linkCode=as2&amp;creativeASIN=0307463745&amp;linkId=fd5b40e25eba5482809b601c0789b5a5">Breaktime</a>. I had a great Thanksgiving in Denver. And, we’re continuing to <a href="https://www.staffjoy.com/careers/">grow our team</a>.</p><h3>Personal</h3><p><strong>Launching Breaktime — </strong>At Staffjoy, we launched a new series called Breaktime, where I interview small business to learn the stories of their success. For the first episode, I interviewed Tyler Zimmer, the owner of Kaldi’s Coffee, to learn about how he scaled his business from one store to fifteen while developing a strong wholesale business.</p><figure><img alt="Kaldis coffee" src="https://cdn-images-1.medium.com/max/740/0*5C9jyyq_2q2ZBU4y." /></figure><p><a href="https://www.staffjoy.com/breaktime/kaldis-coffee?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Breaktime by Staffjoy Episode 1 — Kaldi’s Coffee</strong></a><strong> — </strong><a href="https://www.staffjoy.com/breaktime/kaldis-coffee"><strong>www.staffjoy.com</strong></a> <br> In the first episode of Breaktime by Staffjoy we interview Tyler Zimmer, owner of Kaldi’s Coffee, to learn the business strategies that helped them grow.</p><p><strong>Healthcare + Technology — </strong>I went to my alma mater to judge a healthcare-focused hackathon. It was inspiring to see project focus on improving human health- the resulting projects seemed so much more impactful than other hackathons I had been to.</p><figure><img alt="1*4pnre0ovyj vlmxw mjnxa" src="https://cdn-images-1.medium.com/max/740/0*piq_fic9RXFROnhD." /></figure><p><a href="https://blog.staffjoy.com/staffjoy-founders-name-the-future-of-health-tech-at-archhacks-2016-2fbaa9e843dd?gi=58b4be384664&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Staffjoy Founders Name the Future of Health Tech at ArchHacks 2016</strong></a><strong> — </strong><a href="https://blog.staffjoy.com/staffjoy-founders-name-the-future-of-health-tech-at-archhacks-2016-2fbaa9e843dd?gi=58b4be384664"><strong>blog.staffjoy.com</strong></a> <br> Our Co-Founders, Andrew and Philip, just got back from judging the ArchHacks hackathon at their alma mater, Washington University in St. Louis (WashU). There was plenty of nostalgia as they…</p><p><strong>Books for Engineers — </strong>While judging the same hackathon last year, I started a tradition of giving away books as our company prize. This year, we gave away six books that have impacted the trajectory of Staffjoy.</p><figure><img alt="1*d5vjr g8k6hsxwa4n0czxq" src="https://cdn-images-1.medium.com/max/740/0*Yk32-HCWkzuZN0c4." /></figure><p><a href="https://blog.staffjoy.com/6-book-recommendations-for-new-software-engineers-e7c095bef205?gi=c37f298789ad&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>6 Book Recommendations for New Software Engineers — Staffjoy Blog</strong></a><strong> — </strong><a href="https://blog.staffjoy.com/6-book-recommendations-for-new-software-engineers-e7c095bef205?gi=c37f298789ad"><strong>blog.staffjoy.com</strong></a> <br> School will never teach you everything you need to know, that’s just not how it works. Learning on the side, however, will get you to where you need to be if you have dreams of starting your own…</p><h3>Articles</h3><p><strong>Before Growth — </strong>As we launch the V2 of Staffjoy, this article reflects our experience that effort put into a great product pays off.</p><figure><img alt="Sam hedcut 1200" src="https://cdn-images-1.medium.com/max/740/0*oTKdmq4K6RjaZI6B." /></figure><p><a href="https://blog.ycombinator.com/before-you-grow/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Before You Grow — Y Combinator</strong></a><strong> — </strong><a href="https://blog.ycombinator.com/before-you-grow/"><strong>blog.ycombinator.com</strong></a> <br> Startups are defined by growth, but growth isn’t step one in building a great company. If you focus on trying to grow before you make a product people love, you are unlikely to succeed.</p><p><strong>Stop JSON over HTTP — </strong>Staffjoy V2 has about 15 microservices. We chose Google’s open source gRPC and Protocol Buffers as the internal communication protocol instead of something like JSON over HTTP. This article explains the technology and why it’s so performant.</p><figure><img alt="1*x7i iyhpdnncsyjlm1u0hw" src="https://cdn-images-1.medium.com/max/740/0*OGcrBnTfCC3aa6Wy." /></figure><p><a href="https://medium.com/@shijuvar/building-high-performance-apis-in-go-using-grpc-and-protocol-buffers-2eda5b80771b?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue#.jfpv1eogd"><strong>Building High Performance APIs In Go Using gRPC And Protocol Buffers — Medium</strong></a><strong> — </strong><a href="https://medium.com/@shijuvar/building-high-performance-apis-in-go-using-grpc-and-protocol-buffers-2eda5b80771b#.jfpv1eogd"><strong>medium.com</strong></a> <br> APIs are backbone of modern applications. APIs are powering the backend for web client and mobile client applications, and also used for…</p><p><strong>Fat is good — </strong>I’ve been in a near-constant state of <a href="http://eatingacademy.com/nutrition/ketosis-advantaged-or-misunderstood-state-part-i">ketosis</a> for about eight months. My brain has been fueled almost exclusively by fat, not sugar. I think that the lack of blood sugar fluctuations during the day has improved my cognitive performance. This article discusses the changing attitude toward fat in the scientific community after decades of preaching “high carb / low fat” diets.</p><figure><img alt="Ed3d3905 521f 4f0d a9f82d2ca349e157 agenda" src="https://cdn-images-1.medium.com/max/740/0*hDM-D7mjKELbIKQb." /></figure><p><a href="http://blogs.scientificamerican.com/mind-guest-blog/the-fat-fueled-brain-unnatural-or-advantageous/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>The fat-fueled brain: unnatural or advantageous? — Scientific American Blog Network</strong></a><strong> — </strong><a href="http://blogs.scientificamerican.com/mind-guest-blog/the-fat-fueled-brain-unnatural-or-advantageous/"><strong>blogs.scientificamerican.com</strong></a> <br> Disclaimer: First things first. Please note that I am in no way endorsing nutritional ketosis as a supplement to, or a replacement for medication.</p><h3>Books</h3><p><strong>A second-person novel — </strong>I thoroughly enjoyed this story about family, business, and love. The writing style is unique — it is written in the style of a self-help book, which you as the main character as you go from slums to riches. No character has a name — they’re always referred to by their relation to you. Highly recommended.</p><h4><a href="https://www.amazon.com/gp/product/1594632332/ref=as_li_tl?camp=1789&amp;creative=9325&amp;creativeASIN=1594632332&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=7677ce87b575c7c07a91ed79b2f822c7&amp;tag=philipithomas-newsletter-20&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue">How to Get Filthy Rich in Rising Asia: A Novel</a></h4><p><a href="https://www.amazon.com/gp/product/1594632332/ref=as_li_tl?camp=1789&amp;creative=9325&amp;creativeASIN=1594632332&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=7677ce87b575c7c07a91ed79b2f822c7&amp;tag=philipithomas-newsletter-20">www.amazon.com</a></p><p><strong>Revisiting a business classic — </strong>Rework, by the team at <a href="http://basecamp.com/">Basecamp</a>, just passed its ten-year anniversary. The book focuses on building sustainable internet businesses. I found myself highlighting passages, and even sharing parts at our company all-hands.</p><h4><a href="https://www.amazon.com/gp/product/0307463745/ref=as_li_tl?camp=1789&amp;creative=9325&amp;creativeASIN=0307463745&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=fd5b40e25eba5482809b601c0789b5a5&amp;tag=philipithomas-newsletter-20&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue">Rework by Jason Fried and David Heinemeier Hansson</a></h4><p><a href="https://www.amazon.com/gp/product/0307463745/ref=as_li_tl?camp=1789&amp;creative=9325&amp;creativeASIN=0307463745&amp;ie=UTF8&amp;linkCode=as2&amp;linkId=fd5b40e25eba5482809b601c0789b5a5&amp;tag=philipithomas-newsletter-20">www.amazon.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f24527e111d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Philip’s Newsletter — Issue #8]]></title>
            <link>https://medium.com/@philipithomas/philips-newsletter-issue-8-c37ba6f83763?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/c37ba6f83763</guid>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Thu, 20 Oct 2016 23:47:47 GMT</pubDate>
            <atom:updated>2016-10-20T23:47:47.045Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello from Portland — we’ve been on a Staffjoy offsite here, and we’re beginning transition Staffjoy V2 into Limited Availability. Learn more at <a href="https://www.staffjoy.com/">Staffjoy.com</a>.</p><h3>Articles</h3><p><strong>Nobel Peace Prize — </strong>I wrote in my <a href="https://www.getrevue.co/profile/philipithomas/issues/philip-s-newsletter-issue-4-28834">Newsletter #4</a> that I thought that Juan Manuel Santos, President of Colombia, could win a Nobel Peace Prize for his work. It happened sooner than I expected (considering that the peace process has yet to reach a denouement), but alas he will be awarded the 2016 Nobel Peace Prize.</p><h4><a href="http://www.nobelprize.org/nobel_prizes/peace/laureates/2016/press.html?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue">The Nobel Peace Prize 2016 — Press Release</a></h4><p><a href="http://www.nobelprize.org/nobel_prizes/peace/laureates/2016/press.html">www.nobelprize.org</a> <br> Nobelprize.org, The Official Web Site of the Nobel Prize</p><p><strong>Mental Health — </strong>San Francisco has such a rampant homelessness, drug, and mental health crisis that the police deparment has launched a mental health SWAT team.</p><figure><img alt="10californiatoday facebookjumbo" src="https://cdn-images-1.medium.com/max/740/0*qDwA-kIKWui6Wdl9." /></figure><p><a href="http://www.nytimes.com/2016/10/10/us/california-today-san-francisco-police-mental-health.html?_r=2&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>California Today: San Francisco Fields a Mental-Health SWAT Team</strong></a><strong> — </strong><a href="http://www.nytimes.com/2016/10/10/us/california-today-san-francisco-police-mental-health.html?_r=2"><strong>www.nytimes.com</strong></a></p><p><strong>Fancy Credit Cards </strong>— The Chase Sapphire Reserve card is new, but already half of my friends seem to have one. I find its quick success among millennials to be insightful. With other credit card companies like <a href="https://getfinal.com/">Final</a> coming online, it becomes clear that status and perks outweigh features and security.</p><figure><img alt=" 1x 1" src="https://cdn-images-1.medium.com/max/740/0*1vvW6HSKOW-gprrI." /></figure><p><a href="http://www.bloomberg.com/news/features/2016-09-22/how-chase-made-the-perfect-high-for-credit-card-junkies?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>How Chase Made the Perfect High for Credit Card Junkies</strong></a><strong> — </strong><a href="http://www.bloomberg.com/news/features/2016-09-22/how-chase-made-the-perfect-high-for-credit-card-junkies"><strong>www.bloomberg.com</strong></a> <br> The $450-a-year Sapphire Reserve card has points-and-miles-obsessed millennials fired up.</p><p><strong>Startup Origin Stories — </strong>I’ve been on a podcast kick this week, and NPR’s new show <em>How I Build This</em> has become a quick favorite of mine. I liked hearing the founders talk about the origins of their businesses — ranging from tech companies like Instagram to more analog businesses like Spanx.</p><figure><img alt="Hibt podcast tile sq 8d9498b292dc7a759bf4b7fc776dfe0e4c09da68" src="https://cdn-images-1.medium.com/max/740/0*x6hmjTowk84_Ktfw." /></figure><p><a href="http://www.npr.org/podcasts/510313/how-i-built-this?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>How I Built This</strong></a><strong> — </strong><a href="http://www.npr.org/podcasts/510313/how-i-built-this"><strong>www.npr.org</strong></a></p><p><strong>Growth at Uber — </strong>I was unfamiliar with Ed Baker, but his work at Uber seems fascinating. He reminds me of Alex Schultz (who gave a <a href="http://startupclass.samaltman.com/courses/lec06/">great lecture about Facebook’s growth team at YC’s startup class</a>).</p><figure><img alt="2b302a76 b63f 4d42 b743 c976655dc498" src="https://cdn-images-1.medium.com/max/740/0*rj0QjY_0FAJdpVB-." /></figure><p><a href="https://www.theinformation.com/the-man-driving-growth-at-uber?token=6KQ5PoqctK6wCh9JxCpXmg&amp;utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>The Man Driving Growth at Uber</strong></a><strong> — </strong><a href="https://www.theinformation.com/the-man-driving-growth-at-uber?token=6KQ5PoqctK6wCh9JxCpXmg"><strong>www.theinformation.com</strong></a></p><p><strong>Amazon keeps growing — </strong>This powerhouse of a company is starting to dominate in yet another market — video content. I had no idea that they sell so many premium TV subscriptions.</p><figure><img alt="B7bd9530 ee48 4f1f bade 68192d90892f" src="https://cdn-images-1.medium.com/max/740/0*f9beMct-Nj4HiSQ7." /></figure><p><a href="https://www.theinformation.com/amazon-lures-hollywood-with-channels?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Amazon Lures Hollywood with Channels — The Information</strong></a><strong> — </strong><a href="https://www.theinformation.com/amazon-lures-hollywood-with-channels"><strong>www.theinformation.com</strong></a></p><h3>Apps</h3><p><strong>Learn a Language — </strong>I’ve continued using Duolingo to improve my Spanish — I’m currently on a 100-day streak. They recently released a fun “bot” tool that mimics text message conversations. I also recently learned that more advanced language learning tools are only available on their website.</p><figure><img alt="Duo200" src="https://cdn-images-1.medium.com/max/740/0*vSXoaLkcN967rhDK." /></figure><p><a href="https://www.duolingo.com/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Duolingo</strong></a><strong> — </strong><a href="https://www.duolingo.com/"><strong>www.duolingo.com</strong></a></p><p><strong>Facebook at Work — </strong>With the success of companies like Slack, Facebook has entered the enterprise communication game with its own software offering. Workplace by Facebook is completely separate from standard Facebook, with completely separate accounts and apps. I think it will be valuable for driving culture at large (&gt;1000) person companies, particularly those with distributed teams or more blue-collar workforces. However, I think that it focuses more on discourse than collaboration, making it serve a different use case from Slack.</p><figure><img alt="Workplace share" src="https://cdn-images-1.medium.com/max/740/0*06CXSgQ8nu4liaR_." /></figure><p><a href="https://workplace.fb.com/?utm_campaign=Revue%20newsletter&amp;utm_medium=Newsletter&amp;utm_source=revue"><strong>Workplace by Facebook</strong></a><strong> — </strong><a href="https://workplace.fb.com/"><strong>workplace.fb.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c37ba6f83763" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Update from Staffjoy’s Founders]]></title>
            <link>https://medium.com/staffjoy-blog/an-update-from-staffjoys-founders-830e6d496b23?source=rss-760075200480------2</link>
            <guid isPermaLink="false">https://medium.com/p/830e6d496b23</guid>
            <category><![CDATA[scheduling-software]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Philip I. Thomas]]></dc:creator>
            <pubDate>Sat, 24 Sep 2016 00:45:00 GMT</pubDate>
            <atom:updated>2016-09-24T00:45:00.876Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0StrS0e5GZALskBMQ1hHtw.jpeg" /></figure><p>We are working on a big update to <a href="https://www.staffjoy.com/">Staffjoy</a>. Below is the letter that we sent to our customers last week:</p><p>Dear Staffjoy users,</p><p>We have some exciting news to share — our team has been working hard on a new, better version of Staffjoy based on your feedback. We’re calling it <strong>Staffjoy V2</strong>, and it involves a completely redesigned scheduling experience.</p><p>Over the coming weeks, you will begin to see changes across our website and apps. However, finishing V2 will be an ongoing process that lasts for a few months.</p><p><strong>What does this mean for you?</strong> As an enterprise client, you use features that we have not yet built back into V2 (like claiming shifts or timeclock). So, for now your company will continue using the current product.</p><p>We are working hard to finish building the features you need, and we invite you to tour V2 when it launches. When it’s ready for your company, we will work with your team for a seamless transition.</p><p>Thanks,</p><p>Philip and Andrew</p><p>Founders</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=830e6d496b23" width="1" height="1" alt=""><hr><p><a href="https://medium.com/staffjoy-blog/an-update-from-staffjoys-founders-830e6d496b23">An Update from Staffjoy’s Founders</a> was originally published in <a href="https://medium.com/staffjoy-blog">Staffjoy Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>