<?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 Allie Schwartz on Medium]]></title>
        <description><![CDATA[Stories by Allie Schwartz on Medium]]></description>
        <link>https://medium.com/@Allieschwa?source=rss-cd464e1f6769------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_RWTnXwuqyDtHljNDZqqbg.jpeg</url>
            <title>Stories by Allie Schwartz on Medium</title>
            <link>https://medium.com/@Allieschwa?source=rss-cd464e1f6769------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:42:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Allieschwa/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[How to Prevent Ugly Pricing Surprises]]></title>
            <link>https://medium.com/gomix/our-users-help-us-determine-price-31dba0e22744?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/31dba0e22744</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[pricing-strategy]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Mon, 19 Dec 2016 16:35:47 GMT</pubDate>
            <atom:updated>2016-12-19T18:45:20.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*RtWPOVTL_r1m2mbTpo4Yzg.png" /><figcaption>Don’t Break the Piggy Bank</figcaption></figure><p>At Fog Creek, we build products to last. <a href="http://www.fogbugz.com/">Fogbugz</a>, our task management tool, for example, has been our flagship product for over 16 years. Our newest creation, <a href="https://gomix.com/">Gomix</a>, is built to last the same way.</p><p>Over the years we’ve found that a key to building a sustainable business is supporting our users, both with functionality and simply by listening to their needs. Our customers are often pleasantly surprised by our commitment to them, and by how much we care about their success.</p><p>One area where we don’t want our users to feel surprised is pricing. We never want to make the typical mistakes that companies often do, like suddenly charging for features that used to be free or putting constraints on the ways people can use our platforms. Making money on a new product is tricky and the road to success is littered with failed attempts. Lucky for us, we’ve been around a long time, and we’re confident that we know a couple of principles about what not to do.</p><p>One pattern we’ve seen arise in with other platforms and software is introducing a product with great features, then putting those features behind a paywall once they’ve come to be relied upon by their users. That kind of interruption can be detrimental to getting work done, and can cause real, tangible pain to users.</p><p>We’ve also learned not to complicate the process of buying things by adding too many a la carte purchasing options that overwhelm. To be totally honest, that’s a mistake we’ve made in the past. We learned from our users that part of making people’s’ lives easier is creating a painless buying experience that’s easy to immediately understand.</p><p>That brings us to our next step: collaborating with our community to figure out the best, most sustainable business model for Gomix.</p><p>We plan to consult with our users well before we’ve introduced payment options for Gomix. We’ll be working to see which features have the most value, and what’s worth paying for. That information will help decide how we ultimately let people pay for Gomix. We’ll start by proposing some models that make sense, but we want to hear your feedback at this early stage, too — even before we begin building our full payment infrastructure.</p><p>You can help start our conversation by joining our support forum: support.gomix.com and starting a thread, or talking to us on <a href="http://www.twitter.com/gomixme">Twitter</a>, showing us what you’re making, and letting us know which features are adding value to your experience. Just as importantly, we’d love to hear about new capabilities or platform features that you’d be willing to pay for. Together, we’re gonna make great stuff. We can’t wait!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31dba0e22744" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gomix/our-users-help-us-determine-price-31dba0e22744">How to Prevent Ugly Pricing Surprises</a> was originally published in <a href="https://medium.com/gomix">Gomix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Gomix calls it “remixing”]]></title>
            <link>https://medium.com/gomix/why-gomix-calls-it-remixing-8e1d6482828?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e1d6482828</guid>
            <category><![CDATA[gomix]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Mon, 12 Dec 2016 16:39:08 GMT</pubDate>
            <atom:updated>2016-12-12T16:39:08.581Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*mGBVJUFzLArfkP-6." /></figure><p>Many people are familiar with the idea of building off of someone else’s work to make your own creation. For developers, the idea is often called “forking” (like “a fork in the road”, not “what you use to eat a salad”). Forking is a familiar term for people who know version control and other heavy-duty systems for keeping track of code.</p><p>Outside of the tech space, regular people who use business software often refer to these kinds of features as “Track Changes” or viewing revisions.</p><p>Neither of these terms worked for explaining the process of building upon other people’s work in Gomix. We needed a word that clearly communicated a few key principles:</p><ul><li>You start with something that <em>works</em>, not a pile of parts that you have to assemble yourself.</li><li>You build on the creative work of others, in collaboration with others, because nobody can do it all alone.</li><li>The process of building on other people’s work should be clearly understandable and based on simple concepts that can be visually represented.</li></ul><p>Gomix provides sparks — seeds or notions or starting points you can copy, manipulate and transform into the apps of your dreams. Any time spent worry about overhead or complicated concepts can distract from that vision in your mind.</p><p>That’s why the word “remix” is so important.</p><p>Pirijan, one of the Gomix team members who leads our design efforts, talks about why “forking” was never the right name for an act of creation:</p><p><em>“With forking, the assumption is you’ll take a project, make improvements to it, and submit those improvements back to the author to make the original better. That approach is great for building libraries, but not for self expression and making personal tools, which is much more of what we wanted.”</em></p><p>The inspiration for using “remix” to refer to the process of taking an app and personalizing it came from the world of music. Pirijan explains,</p><p><em>“When you remix a song, you’re taking a version of that track, adding your own stuff onto it, and now it’s a fully original song. That was much closer to what we wanted to inspire people to do”</em></p><p>Ultimately, that’s exactly the realm we wanted to ground Gomix in — the world of creativity and inspiration, where the ideas we’re expressing take precedence over the tools used to build them.</p><p>If you’re looking for inspiration, check out our <a href="https://community.gomix.me/">community</a>, where the sparks of your future ideas might be living this very moment! You can also follow Gomix on <a href="http://www.twitter.com/gomixme">Twitter</a>, where we highlight some of our favorite projects that’ve come from remixing the work of others. And when you’re ready, dive into the Gomix community and start remixing your way to something great.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e1d6482828" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gomix/why-gomix-calls-it-remixing-8e1d6482828">Why Gomix calls it “remixing”</a> was originally published in <a href="https://medium.com/gomix">Gomix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Move Your Career Forward, Come Work at Fog Creek!]]></title>
            <link>https://medium.com/make-better-software/move-your-career-forward-come-work-at-fog-creek-ab5e66fd0dfd?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab5e66fd0dfd</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Mon, 05 Dec 2016 19:24:02 GMT</pubDate>
            <atom:updated>2016-12-05T19:24:22.384Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jpIbn5qSfC32QeWGe8XZpQ.jpeg" /><figcaption>Fog Creek takes Texas, Dec 2015</figcaption></figure><p>Fog Creek is unique in about a million ways. We’re a small tech company, but the products we’ve created touch millions of people, on the scale of Google or Facebook. We’re different — we believe if we hire the smartest, most capable people who can get things done, that’ll they’ll create amazing products we’ll be happy to sell. And for 16 years, it’s worked.</p><p>Want to know a bit more about how we set ourselves apart from the crowd? Check out this handy info graph:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgKX-0lPdVUKu7IDxXXhgg.png" /><figcaption>Pretty great, huh?</figcaption></figure><p>Now here’s the best news — we’re hiring! If you’re ready to join a company that invests in it’s employees just as much as it’s products, then check out our <a href="http://www.fogcreek.com/careers/">careers page</a>. Who knows, we may be looking for exactly you!</p><p>If there’s not a position available that currently matches your skill set, don’t fret. We open up new spots across teams all the team. You can find our most recent listings on our careers page, or on <a href="http://www.twitter.com/fogcreek">Twitter.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab5e66fd0dfd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/move-your-career-forward-come-work-at-fog-creek-ab5e66fd0dfd">Move Your Career Forward, Come Work at Fog Creek!</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Use FogBugz for Recruiting]]></title>
            <link>https://medium.com/make-better-software/how-we-use-fogbugz-for-recruiting-482a63dc0be1?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/482a63dc0be1</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Tue, 22 Nov 2016 17:48:09 GMT</pubDate>
            <atom:updated>2016-12-05T19:08:56.515Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/410/0*W_Ku6o2-uxgYyKSR.jpg" /></figure><p>If I told you I ate my own dog food, would you think I was gross? Or would you know what I meant? That at Fog Creek we use our products internally as a kind of quality control and real-world test case.</p><p>Well, it’s the latter. I swear! One way we eat our own dog food at Fog Creek is by using FogBugz as an Application Tracking System (ATS) for all our recruiting. We’ve used FogBugz in this fashion for as long as our company’s been in business (some 16 years and counting!), and it works really well. I’ve outlined the process below so you can replicate it within your own company too.</p><h4>Handling Job Applications</h4><p>The first step is to have an Admin create a Project that will act as your Inbox. At the Creek, all applications from candidates sent to jobs@fogcreek.com arrive in our Inbox. Every case is initially assigned to “Recruiting” which is a catch-all account we created so as to not overwhelm. I sort the inbox reverse chronologically by Area, so the most recent, “Not Spam” cases are the ones I see first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*zlPx7XxlUeIayQNj.png" /></figure><p><em>Note: these are screenshots from our *actual* recruiting inbox — the names and cases are blocked out to protect our applicants!</em></p><p>We’ve set it up so every candidate who applies to a position at Fog Creek receives an auto-response from our Recruiting Robot with information about how recruitment works at Fog Creek.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*hhF7PIgJKKwAuITF.png" /></figure><p>With this response, candidates don’t have to worry if you’ve received their resume or not, and the fact that it’s canned, but still has personality sets it far apart from the generic forms most ATSs send out. We get loads of love for our robot — it sets the tone that this recruitment process actually won’t suck.</p><h4>Reviewing Cover Letters</h4><p>Moving on: We’ll use the story of a fictitious candidate who applied for a QA position at Fog Creek to walk you through our application process.</p><p>As the de-facto Head of Recruiting, I’m the first to take a look at each resume and cover letter. If you have a larger team, you can assign any member you like to this task. When I click into my applicant’s case, I see that Martha loves Fog Creek and that she wants to join our QA team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*KGup-E8dLSaorCOM.png" /></figure><p>Using the “Correspondent” column on the left, I can also see that Martha’s applied to Fog Creek before.</p><p>As the robot promised, we get back to every applicant, moving forward or not. If Martha were lacking, I’d reply to her email with a polite rejection using a snippet. Luckily for her, Martha has passed my initial screen. For my next step, I’ll move her from the Inbox to our Recruiting Queue, another Project in our FogBugz instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ipAKKGLrAmJv85yb.png" /></figure><p>At this point, I also update the case’s Area — which corresponds to the position to which the candidate is applying — and the Milestone, which correlates to the whichever stage of the interview process the candidate is in. At Fog Creek we have 10 potential milestones, which include things like ‘Sales Pitch’, ‘SysAdmin Take Home Problem’ and ‘In-person with CEO’ — you can set your milestones to match whatever recruitment processes you have in place.</p><p>Lastly, I assign Martha’s case to Jude and request a resume screen. I’ve updated the “Due” date on the left side of the case and given Jude 1 full day to complete his screen. This is a great way to get rid of one of tech recruiting’s worst bottlenecks — waiting on developers to screen resumes! Lastly, I’ve subscribed to the case to make sure I see all updates. For example — if the candidate writes back in, I’ll get an email alerting me to the correspondence.</p><h4>The Recruiting Queue</h4><p>While Jude is reviewing Martha’s resume, let’s pause, and I’ll tell you a bit more about the Recruiting Queue. And just so you know — you’re about to get a super exclusive look into our *actual* queue — you are so lucky!</p><p>I organize my queue as follows: All active cases, sorted by Area (Position), then Milestone (Stage in the Process). Currently, I’m hiring on my SysAdmin &amp; Support teams; you’ll see candidates for those 2 positions, plus Martha’s QA resume, below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*e-wf7T5GWBAD-PqI.png" /></figure><p>I sort this way so I can see how many candidates I have in the queue for each position, and so I can tell, of those candidates, how many are in each stage of the process. I star the cases that require my attention but I haven’t had time to respond to yet.</p><p>Sometimes I want to take stock of how many candidates I have in each stage of the process, so I’ll re-sort by Milestone to see how many “code screens” or “in-person interviews” are taking place this week and next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*zggLDnDUUh9x59oc.png" /></figure><p>I try to evenly distribute the load of recruiting and not put too much work on any one person. When I want to double check to make sure I’m meeting my goal, I’ll switch it up and resort by “Assigned To”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*NOBWc37xXMB_PfqG.png" /></figure><p>Yikes! I’ve got a lot of work to do. So let’s move on quickly!</p><h4>From Resume Screening to Interview</h4><p>Back to Martha: Jude has now completed his screen and (hurray!) Martha is moving on to the next round, which is a code screen. He’s assigned his case back to me, the Recruiter, to move her forward.</p><p>Because I subscribed to the case, I got an email with Jude’s assessment. I click into the case, change Milestone to “code screen”. Then use my snippets again to reach out to Martha and schedule an interview. I can email her right from FogBugz, which is handy for keeping all correspondence in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*KKS1O2sWxmok-kY8.png" /></figure><p>Before I send, I’ll also update the “Due” date. I usually give candidates a day or two to respond.</p><p>Once we’ve gotten to the in-person stage, I notify each person interviewing Martha so they can add their interview times to their calendars. I keep the case assigned to myself as I’ll be facilitating the interview while Martha’s in the building.</p><p>After each interview, the interviewer edits the case with his/her feedback on the candidate’s performance. In Martha’s case — all hires! (we only hire those we all agree on, <a href="https://blog.fogcreek.com/video-guide-how-to-hire-developers/6-hire-or-no-hire/">here’s why</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*eyasEwfbFb2x0jUE.png" /></figure><h4>Sending out Offers</h4><p>The next stage is the fun part of recruiting — the offer stage! Hiring people is the best; it’s also full of conversations that include personal and private information that a potential new employee doesn’t necessarily want to share with their potential new co-workers. To preserve Martha’s privacy, I move Martha’s case from the “Recruiting Queue” project to “Hiring” which has limited access. We have 2 Milestones in Hiring — Offer &amp; Onboarding. Right now, Martha is in the Offer Stage, because we made her an offer. If Martha accepts the offer, she’ll move to “onboarding”. After her first month at the company, she’ll move from “Hiring” to our “Archive,” another secure project with access limited to admins, so that no employees can see what their coworkers said when hiring them.</p><p>And that’s it! We’ve gone from application to hire entirely within FogBugz. So, if you’re frustrated with the ATS your recruiting team is using, or if you’re a recruiter looking for a new system, I’d definitely recommend FogBugz. It’s simple, clean, easy to use, easy to teach(!) and reliable. If you have questions or want more information on how this works, find me on <a href="http://www.twitter.com/allieschwa">Twitter</a> or email me — allie@fogcreek.com.</p><p><em>Want to hire the best developers? </em><a href="https://blog.fogcreek.com/video-guide-how-to-hire-developers/"><em>Watch our video guide</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=482a63dc0be1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/how-we-use-fogbugz-for-recruiting-482a63dc0be1">How We Use FogBugz for Recruiting</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it means to not worry about healthcare.]]></title>
            <link>https://medium.com/make-better-software/health-care-parental-leave-75c5d91e30f0?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/75c5d91e30f0</guid>
            <category><![CDATA[parental-leave]]></category>
            <category><![CDATA[parenting]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Tue, 15 Nov 2016 15:40:17 GMT</pubDate>
            <atom:updated>2016-12-22T14:49:07.758Z</atom:updated>
            <content:encoded><![CDATA[<p>At Fog Creek, we often discuss our values and policies because we’re really proud of them. Today we want to describe a real-world example of how our health and parental leave policies serve our employees to demonstrate what we mean.</p><p>Fog Creek’s parental leave is designed to implement one of our founding principles: we hire the most skilled, capable people and treat them like humans, with the utmost respect. One of our employees, Jacob, generously agreed to share his family’s story to illustrate the difference this makes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*0OH00a4KlOfWsvgV." /><figcaption>Jacob, the guy in the hat</figcaption></figure><p>Jacob is a senior member of our technical staff. He was a summer intern at Fog Creek in 2006, joined full time in 2007, left at the end of 2009 to work for another company, and then rejoined us remotely in the Spring of 2013. At the end of that year, Jacob and his wife were facing challenges having a baby. It would not be possible without medical intervention. Luckily, they had access to specialists who could help them.</p><p>During that unsure time, Fog Creek’s policy of providing truly comprehensive health care gave Jacob peace of mind. Our plan covers all our US based employees. The basic concept is: <strong>Your insurance is free. You pay nothing. You have no copayments, no deductible, you don’t pay for any doctor visits or prescriptions.</strong> It is by far the best health coverage deal you will find at any employer in America.</p><p>We’ve had this policy at Fog Creek for over 10 years. What we’ve learned is with that kind of coverage, employees like Jacob have an easier time navigating even the most fraught and challenging life experiences. Jacob put his faith in Fog Creek to make good on our promise of all inclusive health care, and we worked to show that faith was justified. A year later, Jacob and his wife Jennifer found out they were pregnant.</p><p>The next 9 months were full of check ups, genetic screenings, ultrasounds, and prenatal visits, all of which Fog Creek covered. When Jacob’s wife went into labor in January of this year, our health care let them focus on recovery without worrying about the cost of hospitalization. Jacob did not pay a single bill out of pocket and, in January, their beautiful son, Jackson, was born.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VGwz7zbOoHsKUB59FMxmgQ.jpeg" /></figure><p>As a resident physician caring for sick patients in the hospital, Jacob’s wife does not have the time flexibility of an employee at Fog Creek. She and Jacob decided that he would be the primary caregiver of their newborn. At Fog Creek we give <strong>all new primary caregivers, including adoptive and foster parents, 12 weeks off at 100% pay</strong> (employees who are in their first year scale up from 3 weeks of leave at hire to the full 12 weeks). Combined with vacation and flex time, Jacob was able to spend the better part of 7 months taking care of his new baby.</p><p>Our policy had its intended effect of making a major life transition as easy as possible for our employees and their families. For Jennifer, going back to work was easier knowing Jacob would be with her son all day. For Jackson, Jacob thinks their time together made a huge difference on his early personality.</p><p><em>“If he’d only had 6 weeks or something it would have been different for sure.”</em></p><p>Many companies use well-intentioned but vague language to describe the benefits they offer, and the goals behind those benefits. We’re very grateful to Jacob for being brave enough to share his family’s story, with the hope of outlining not just how we want to treat our employees at Fog Creek, but how every company can invest in supporting their employees and their families.</p><p>If those values make sense to you, and would help you do your best work, we hope you’ll <a href="http://www.fogcreek.com/careers">come join our team.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75c5d91e30f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/health-care-parental-leave-75c5d91e30f0">What it means to not worry about healthcare.</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Companies We Love]]></title>
            <link>https://medium.com/make-better-software/companies-we-love-347fe628b71f?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/347fe628b71f</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[khanacademy]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Fri, 11 Nov 2016 21:31:16 GMT</pubDate>
            <atom:updated>2016-12-05T19:09:28.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*fbOrwDnsxBx8v50m." /></figure><p>Obviously, if you want a great career in tech, our first choice is that you <a href="http://www.fogcreek.com/careers/">come work at Fog Creek.</a> But we wanted to take a moment to do something unusual, and highlight a job listing from <em>another</em> organization:<a href="https://boards.greenhouse.io/khanacademy/jobs/15823#.WCYgSOErJSN"> Khan Academy</a></p><p>Khan Academy is a really amazing non-profit with an inspiring mission to, “to provide a free world-class education for anyone, anywhere.” They started as a team of 1, and have grown to over 80 people, including one of our former colleagues who was among the first to join founder Salman Khan in his quest. Or, as they stated in their job listing:</p><p><strong><em>“Our team includes people from Google, Apple, Facebook, Mozilla, Microsoft, Pixar, Fog Creek, and tiny startups”</em></strong></p><p>We’re proud that working at Fog Creek is a credential that permanently upgrades the careers of everyone who comes through our doors. And that’s what we see when other organizations are proud to have our alumni on their teams.</p><p>We’re always inspired by companies like Khan that are actively engaged in the fight to make education and tech more inclusive and available to everyone, and see that work as directly connected to the values that our team members try to support every day. Khan Academy is worth a look from anybody who wants to learn, and if you’re looking to build your skills to succeed at Fog Creek or beyond, come give us a look.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=347fe628b71f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/companies-we-love-347fe628b71f">Companies We Love</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Support & Continuous Learning]]></title>
            <link>https://medium.com/make-better-software/support-continuous-learning-7775eb9a8fcd?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/7775eb9a8fcd</guid>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Thu, 10 Nov 2016 17:57:02 GMT</pubDate>
            <atom:updated>2016-12-05T19:09:51.397Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*g4WxYeYSzqrF3hbGkGUDXg.gif" /></figure><p>Support is a big word at Fog Creek. We support our products, we support our customers, and most importantly we support our employees.</p><p>One of the ways we support our staff is through our investment in continuous learning.</p><p><em>“I have the opportunity to learn something new every time I come to work. If there’s something I want to become an expert on, I will be given the room and the time” — Rachel Sharp, Fog Creek SysAdmin</em></p><p>We give each of our employees $3,500 a year and 3 paid vacation days to use to cover the cost of attending a conference — and that’s not just for coders or technical employees, that’s for everyone on our staff. When they return to the office (or to their remote office if that’s the case) we encourage our employees to share what they’ve learned with a write up or a tech talk. Our team members can even use their dev dollars to bring speakers to the office for workshops, and when they do, we triple the budget, since it’s benefitting so many people on the team.</p><p>Why do we go to these lengths to support our employees? For one it means we’re often able to promote from within. For example, members of our support team have gone on to become SysAdmins, Project Managers and Developers, and two of current Sr. Engineers started their careers at Fog Creek as interns in 2007 and 2008. And while we want everyone to stay at Fog Creek and do the best work of their careers, we also know that enhancing and improving our team’s skills has helped them go on to succeed later in other organizations as well.</p><p>On a philosophical level, we do it because we believe the employee/employer relationship should be reciprocal. Our job is not just to pay our employees with hopes that they, in return, will do what we say and make us look good. Rather we give our employees the tools they need to succeed at work and in their careers and in return they feel trusted and supported enough to come up with big ideas that we can then…you guess it…support!</p><p>It goes back to our core belief: We hire the most skilled, capable people, treat them with genuine respect, and give them the means to succeed. If that sounds like something you might be into, <a href="https://www.fogcreek.com/careers/">check our our open jobs!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7775eb9a8fcd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/support-continuous-learning-7775eb9a8fcd">Support &amp; Continuous Learning</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Don’t Offer Unlimited Vacation]]></title>
            <link>https://medium.com/make-better-software/why-we-dont-offer-unlimited-vacation-c15a0c9ce271?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/c15a0c9ce271</guid>
            <category><![CDATA[vacation]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Mon, 07 Nov 2016 19:53:37 GMT</pubDate>
            <atom:updated>2016-12-05T19:04:52.536Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PDpWnLArLSABFT535LSoxQ.jpeg" /></figure><p>At Fog Creek we’ve always tried to be generous with our time off policies. From parental leave to sick days to vacation, we believe in work life balance and we encourage our employees to take time off when they need it. But we <em>don’t</em> have unlimited vacation days.</p><p><strong>Here’s why: </strong>the unlimited vacation day policy feels like a scam…and that’s because it is. Studies show it <a href="http://money.usnews.com/money/blogs/outside-voices-careers/articles/2016-06-06/unlimited-vacation-sounds-great-heres-the-problem-with-it">can lead</a> to employees taking <em>less</em> time off because of the social pressure to work and the uncertainty about what’s appropriate.</p><p>The main issue with the unlimited vacation day policy is it puts the onus on the employees to decide how much time is appropriate to take off. It’s a loaded decision, one that comes with unspoken bias and judgements, especially if expectations aren’t clearly communicated. When people don’t know an exact policy, they’ll err on the side of trying not to get in trouble. For employees it can make taking vacation feel like a trap, rather than the stress relieving experience it should be. No good.</p><p>Instead, at Fog Creek, our vacation days accrue. All of our full time employees with anywhere up to 3 years of tenure get 20 vacation days, which is well above the <a href="http://www.bls.gov/news.release/ebs.t05.htm">national average</a>. After the 3 year mark, we bump our employees up to 25 days.</p><p>Giving our employees a concrete and generous number of vacation days sends a clear message — we know you need time off! Your work life balance and mental health is as important to us as it is to you.</p><p>Not only do our vacation days roll over, we’re lenient about an employee going over by an extra day or two. Another important point: We don’t count our sick days towards vacation — if you’re sick, you’re sick, and you should stay home because <em>you’re sick</em>! Nobody should have to take a vacation day because a toddler in your kid’s preschool decided to share Hand, Foot and Mouth Disease with the class.</p><p>The goal of our vacation policy is straightforward, and it’s the same as ever benefit we offer our employees: we want to make sure unnecessary stressors don’t keep our team from living well. If that sounds like something you want to get from your employer, maybe you should come<a href="http://www.fogcreek.com/careers/"> join us at Fog Creek</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c15a0c9ce271" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/why-we-dont-offer-unlimited-vacation-c15a0c9ce271">Why We Don’t Offer Unlimited Vacation</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We noticed an interesting article yesterday:]]></title>
            <link>https://medium.com/make-better-software/we-noticed-an-interesting-article-yesterday-f6af5b8c2033?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6af5b8c2033</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 19:04:44 GMT</pubDate>
            <atom:updated>2016-12-05T19:11:44.514Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*6-6mmTjjX5yqn0LHcC_WYg.jpeg" /></figure><p>We noticed an interesting article yesterday:</p><p><a href="https://www.l2inc.com/everyone-wants-to-work-at-a-tech-company/2016/blog">Everyone Wants to Work at a Tech Company</a></p><blockquote>“Fewer Americans search for jobs at Nike — regularly named one of the best companies to work for — than at the tech giants”</blockquote><p>At Fog Creek we definitely see people interested in working in tech — but at a different kind of environment. Tech doesn’t just mean “giant billion-dollar company”. Over the years we’ve had supremely talented team members join our scrappy shop after considering offers from Google, Microsoft, Amazon, and other tech giants. Some even worked at those companies first, and then chose to join us, growing to become senior members of our team.</p><p>So why would a developer get an offer from the biggest tech company in the world and still decide they’d rather work at Fog Creek? What we’ve found is that they love the fact that by working at Fog Creek, they can make an impact on the tech industry that is on par with our much larger compatriots, while working at a much more human, and humane, company. We make tools that nearly every coder uses daily, like<a href="https://www.crunchbase.com/organization/stack-overflow"> Stack Overflow</a>. We built<a href="http://fortune.com/2016/10/31/trello-project-management/"> Trello</a>, and we created<a href="http://www.fogcreek.com/fogbugz/"> FogBugz</a>,<a href="http://www.fogcreek.com/fogbugz/"> </a>our stalwart suite of tools for making better software, which is running better than ever. We’ve got even more fun and innovative stuff coming, despite having a team small enough that we know the names of each other’s’ pets.</p><p>How do we do it? It’s pretty simple. We hire the most skilled, capable people, treat them with genuine respect, give them the means to succeed, and they create valuable products we’re proud to sell. That’s it. That’s the secret sauce. Well, it’s not really a secret. Maybe it’s just sauce.</p><p>We truly believe work should be rewarding and enjoyable — that’s why we all joined Fog Creek in the first place! If that sounds good to you, we’d love you to<a href="http://www.fogcreek.com/careers"> join us</a>. Help us build the tools that will build the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6af5b8c2033" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/we-noticed-an-interesting-article-yesterday-f6af5b8c2033">We noticed an interesting article yesterday:</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Combat Imposter Syndrome]]></title>
            <link>https://medium.com/make-better-software/how-we-combat-imposter-syndrome-c72b2ad69a1f?source=rss-cd464e1f6769------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72b2ad69a1f</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[remote]]></category>
            <dc:creator><![CDATA[Allie Schwartz]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 19:28:47 GMT</pubDate>
            <atom:updated>2016-12-05T19:07:46.602Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-7z8dgAllQwECDOvklCO3w.jpeg" /></figure><p>At Fog Creek we’ve always put a top priority on hiring people who get things done, which means we’re a company that welcomes a lot of generalists. We hire capable people, but we don’t expect our new employees will come in knowing how to do everything their jobs will require right off the bat. Our goal is to give our new employees a full 3 months of room to spend on just learning.</p><p>But giving new employees this flexibility can also increase one unintended consequence: imposter syndrome.</p><p>It makes sense, right? You get this amazing job at this really forward thinking company, even though you might not be an expert at every detail of every subject mentioned in the job listing. It’s stressful!</p><p>Because we believe strongly that a good quality of life and an environment that builds happiness and productivity are integral to our success, we have to combat this imposter syndrome. We like to do it early and often during an employee’s first 90 days at Fog Creek. We’ve got a few methods.</p><p>During a new employee’s first week we lay it out flat: <strong>don’t panic!</strong> It’s written as part of our social rules (which are heavily influenced by our friends at <a href="https://www.recurse.com/manual#sec-environment">The Recurse Center</a>, formerly Hacker School) and it’s required reading for everyone’s first day at Fog Creek. Here’s the key piece:</p><blockquote>“We hired you because we believe you will be a positive influence at Fog Creek, and we think investing in you and your continuous growth in your career is worthwhile. This bears repeating so we’ll say it again: we hired here because we want you here. Don’t worry about how how well you know SQL or about that family vacation you planned before you started working here. You are here because we believe in you — the rest is a journey we take together.”</blockquote><p>Telling someone not to worry doesn’t do the trick alone. At Fog Creek we give all of our new employees continuous feedback during their first 3 months to make sure their goals and the goals of their team are aligned. At 30, 60 and 90 days we do a check in with all of our new employees. A few days before we ask them to prepare answers to the following:</p><ol><li>What are you doing well?</li><li>Where can you improve?</li><li>What do you want to learn in the next 30 (90) days?</li></ol><p>We ask each new employee’s team lead to answer the same questions, then we go over the answers to make sure they’re in alignment. And we fix any bugs that we identify.</p><p>How does this help combat imposter syndrome? It gives our new employees a concrete answer to that most nagging of questions — am I doing OK? Am I meeting the company’s needs and expectations?</p><p>The goal is simple: make sure everyone on our team feels confident and comfortable in their place at our company. If that sounds like something you want to get from your employer, maybe you should come <a href="https://www.fogcreek.com/careers/">join us at Fog Creek.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72b2ad69a1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/make-better-software/how-we-combat-imposter-syndrome-c72b2ad69a1f">How We Combat Imposter Syndrome</a> was originally published in <a href="https://medium.com/make-better-software">Glitch: Make Better Software</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>