<?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 The Meteor Chef on Medium]]></title>
        <description><![CDATA[Stories by The Meteor Chef on Medium]]></description>
        <link>https://medium.com/@themeteorchef?source=rss-42aaa036cf74------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rR0SMTd5VWVAUrtM.png</url>
            <title>Stories by The Meteor Chef on Medium</title>
            <link>https://medium.com/@themeteorchef?source=rss-42aaa036cf74------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:28:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@themeteorchef/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[Improving App Performance with Meteor APM and Galaxy Pro]]></title>
            <link>https://blog.meteor.com/improving-app-performance-with-meteor-apm-and-galaxy-pro-24787d7ff05b?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/24787d7ff05b</guid>
            <category><![CDATA[web-hosting]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 18 Jul 2017 19:04:58 GMT</pubDate>
            <atom:updated>2017-07-18T19:04:58.392Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our experience setting up Galaxy Pro for <a href="https://www.ilovemeteor.com/">I ❤ Meteor</a></h4><p><em>This is a guest post that originally appeared </em><a href="https://themeteorchef.com/tutorials/meteor-apm-galaxy-pro"><em>on The Meteor Chef</em></a><em>, a community-maintained resource for Meteor documentation and education.</em></p><p>When we at The Meteor Chef last checked in our site <a href="https://www.ilovemeteor.com/">I ❤ Meteor</a>, we’d <a href="https://themeteorchef.com/tutorials/deploying-with-meteor-galaxy">successfully deployed the application to Meteor’s Galaxy Hosting Service</a> and rigged up DNS so users could access the app. Since then, the folks behind Galaxy at Meteor Development Group released an upgraded version of Galaxy —<a href="https://blog.meteor.com/introducing-galaxy-professional-built-in-apm-5e063839a4aa"> Galaxy Pro</a> — that introduces some interesting features to further simplify the devops process.</p><p>Since we deployed, the performance of I ❤ Meteor has been a bit of a mystery. Save for general performance metrics in the Galaxy Dashboard (Active connections, CPU usage, and Memory usage) it’s been difficult to identify bottlenecks in the application and work toward improving performance. To help with this, Galaxy Pro has introduced a new feature — Meteor APM (application performance monitoring) — that gives insight into potential problem areas like:</p><ul><li>Publication and Subscription performance</li><li>Meteor Method performance</li><li>Live Query performance</li><li>Client and Server error tracking</li></ul><p>In this tutorial, we’ll take a look at how to configure and make use of Meteor APM, learning how to improve the overall performance of our application. We’ll learn how to enable performance monitoring as well as client-side error tracking to keep our eye on as much as possible.</p><p>In addition to improved performance tracking, Galaxy Pro also gives us access to IP Whitelisting: a means for getting the IP addresses that Galaxy makes requests from. We’ll see how to make use of this by setting up a staging database for I ❤ Meteor on the <a href="https://www.mongodb.com/cloud/atlas">MongoDB Atlas</a> service — a hosted MongoDB solution — which requires the IP addresses of the servers connecting to the its databases.</p><p>To get started, we’ll need to do some housekeeping to make sure our app plays nice with Galaxy Pro, and more specifically, Meteor APM. Let’s do it!</p><h3><strong>Prerequisites</strong></h3><p>Before we get started, make sure to complete the following steps. <strong>This will ensure that you have all of the code and dependencies you need</strong> to complete the tutorial. Because we already built I ❤ Meteor <a href="https://themeteorchef.com/tutorials/deploying-with-meteor-galaxy">in another tutorial on deploying with Galaxy</a>, we’ll use the code from there to save us some headaches. After you’ve cloned a copy of the app, make sure to install all of the dependencies in the next section.</p><pre>git clone <a href="https://github.com/themeteorchef/deploying-with-meteor-galaxy.git">https://github.com/themeteorchef/deploying-with-meteor-galaxy.git</a> <strong>&amp;&amp;</strong> cd deploying-with-meteor-galaxy <strong>&amp;&amp;</strong> npm install</pre><p>If you’d rather just see the changes made for this tutorial, you can download the repo for this tutorial separately:</p><pre>git clone <a href="https://github.com/themeteorchef/enhanced-deployments-with-galaxy-pro.git">https://github.com/themeteorchef/enhanced-deployments-with-galaxy-pro.git</a> <strong>&amp;&amp;</strong> cd enhanced-deployments-with-galaxy-pro <strong>&amp;&amp;</strong> npm install</pre><p><strong>Keep in mind</strong>: if you download this second repo, you will already have the necessary packages and code installed and can skip to the “Upgrading to Galaxy Pro” section below.</p><h3><strong>Preparing for Galaxy Pro</strong></h3><p>Before we dig into upgrading I ❤ Meteor’s deployment to Galaxy Pro, we need to make a few minor tweaks to our application locally. First, it’s important to note that Galaxy’s Meteor APM offering is a rebranded version of another service, Kadira, which was <a href="https://blog.meteor.com/mdg-acquires-kadira-apm-96dfb3167fe5">purchased by the Meteor Development Group in March, 2017</a>.</p><h4>First: remove any Kadira packages</h4><p>Kadira was fairly popular in the Meteor community and had its own set of packages for enabling application performance monitoring. If you were a Kadira customer in the past, before you add the packages below you’ll want to remove any Kadira-related packages. Specifically, you’ll want to remove the meteorhacks:kadira with meteor remove meteorhacks:kadira.</p><h4>Requirements for Meteor APM</h4><p>With any Kadira-related packages uninstalled, next, we need to add support for two packages that will enable support for Meteor APM:</p><pre>meteor add mdg:meteor-apm-agent</pre><p>This package will enable support for Publication and Subscription monitoring, Meteor Method monitoring, and Live Query monitoring.</p><pre>meteor add meteorhacks:zones</pre><p>This package will give Meteor APM better access to client-side errors. This is important because we want to be able to see when something goes wrong in one of our user’s browsers (the client).</p><p>With these installed, we’re all set to start monitoring the performance of our application and find any performance holes we need to plug. Before we do, though, we need to upgrade our application to Galaxy Pro.</p><h3><strong>Upgrading to Galaxy Pro</strong></h3><p>Coming up, we’re going to make a few changes to our application in order to test out some of Galaxy Pro’s features. Before we do, though, we need to make sure that we’ve upgraded our containers on Galaxy to Galaxy Pro. Good news: it’s super easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8zB0p_snjo1RVvEeJqpQMw.gif" /><figcaption>One click to upgrade? Not bad at all.</figcaption></figure><p>Assuming you’ve already deployed your app to Galaxy (if you haven’t <a href="https://themeteorchef.com/tutorials/deploying-with-meteor-galaxy">make sure to give our deployment tutorial a read</a>), click on the domain for the application you’d like to upgrade and head to the “Settings” tab. From there, at the top of the page you’ll see a button “Upgrade to Professional” that will delete your application and send you a bill for $1,000,000 USD, via fax.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OU40e3SLI7i21XiNcnF3-A.png" /><figcaption>Price changes when you enable Galaxy Professional on your containers, as of July 2017.</figcaption></figure><p>Poor jokes aside, no, this will prompt you with a confirmation to upgrade your existing containers to Galaxy Professional (<strong>fair warning</strong>: this will increase the price per hour on your containers slightly — with charges increased from your container tier’s base price). Once complete, you’ll see some new options and information appear in the same space.</p><h4>Make sure to deploy after installing packages and upgrading</h4><p>In order to get access to the features we’ll demonstrate below, it’s important to deploy your application after adding the packages we’ve outlined above. Without them, Meteor APM will not be able to read any data from your application.</p><p>To demystify the service a bit, we’ll spend the rest of the tutorial walking you through how Galaxy Professional can help to improve the performance and extensibility of your Meteor application.</p><h3><strong>Adding images and monitoring performance with APM</strong></h3><p>While version 1 of I ❤ Meteor was neat, something we’ve been missing is images to help projects stand out. Now, we’re going to add support for attaching an image when submitting a project which, conveniently, will require a remote API call to Amazon S3 to store the image. This is great because it will help us to understand how to use Galaxy’s new APM feature and figure out how to speed things up for users.</p><p>While we’re not going to a deep dive on how to implement image uploading (<a href="https://themeteorchef.com/tutorials/uploading-files-to-amazon-s3-with-react">give our uploading files with Amazon S3 tutorial a read if you’re curious</a>), we <em>do</em> want to call attention to how we’re ultimately passing images to Amazon S3 on the server. After the file is read on the client, we pass the details of the file (including its raw data) up to a method which then passes the file along to Amazon S3 for storage. While we expect our writes to be fairly speedy, there’s no guarantee.</p><p>Our call to S3 (in our /imports/api/projects/server/methods.js) looks like this:</p><pre>export <strong>const</strong> submitProject = <strong>new</strong> ValidatedMethod({<br>  name: ‘projects.submit’,<br>  validate: <strong>new</strong> SimpleSchema({<br>  title: { type: String },<br>  url: { type: String },<br>  createdBy: { type: String },<br>  image: { type: Object, blackbox: <strong>true</strong> }, <br>  }).validator(),<br>  run(project) {<br>   <strong>const</strong> projectToInsert = project;<br>   projectToInsert.owner = <strong>this</strong>.userId;<br>   <strong>return</strong> s3.putObject(project.image)<br>   .then((image) =&gt; {<br>     <strong>if</strong> (image) projectToInsert.image = image;<br>     <strong>return</strong> Projects.insert(projectToInsert);<br>   })<br>   .catch((error) =&gt; {<br>     <strong>throw</strong> <strong>new</strong> Meteor.Error(‘500’, `${error}`);<br>   });<br>  },<br>});</pre><p>Inside of our projects.submit method, we make a call to a module method s3.putObject to actually fire the upload. Notice that we do this <em>before</em> we insert a project into the database, meaning, we need to wait for a URL back from S3 before the project is created in our database.</p><h3><strong>Measuring performance</strong></h3><p>To get a feel for how our method performs, if we hop over to Meteor APM, we can see the general response time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oyEu-mwIlajfBe5BZsspuA.png" /><figcaption>Monitoring Method performance in Meteor APM.</figcaption></figure><p>In the <a href="https://apm.meteor.com/">Meteor APM dashboard</a>, if we flip over to the “Methods” tab and click on the projects.submit method, we can see that the response time was 276ms (milliseconds). This means that from the time we clicked the submit button, it took 276ms for our method to send back a response. Generally speaking, that’s not bad for a remote call, but we can do better.</p><p>We want to pay attention to is how Meteor APM is helping us. Without this information, we’d be more-or-less guessing on the performance of our method call. With APM, we’re getting <em>real</em> and <em>live</em> data about the performance of our application, allowing us to make quick fixes and deliver a better experience to customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eYSQVIe4Vb5bL1TRAz9WWQ.png" /><figcaption>Monitoring Pub/Sub performance in Meteor APM.</figcaption></figure><p>Switching over to the “Pub/Sub” tab and clicking on our projects publication, we can see that its performance is pretty terrible. The 1688ms “Response Time” listed here means that from the time the client connected to the app, it took nearly two seconds to receive a response from the server for just this one subscription.</p><p>In our /imports/api/projects/server/publications.js:</p><pre>Meteor.publish(‘projects’, <strong>function</strong> projectsPublication(query, projection, paginationLimit) {<br>  check(query, Object);<br>  check(projection, Object);<br>  check(paginationLimit, Number);<br> <br>  <strong>const</strong> queryToAssign = query;<br>  <strong>const</strong> projectionToAssign = projection;<br> <br>  <strong>const</strong> isFavorites = queryToAssign[‘favoritedBy.userId’];<br>  <strong>const</strong> isSubmissions = queryToAssign.owner;<br> <br>  <strong>if</strong> (isFavorites) queryToAssign[‘favoritedBy.userId’] = <strong>this</strong>.userId;<br>  <strong>if</strong> (isSubmissions) queryToAssign.owner = <strong>this</strong>.userId;<br> <br>  <em>// projectionToAssign.limit = paginationLimit;</em><br>  <strong>return</strong> Projects.find(queryToAssign, projectionToAssign);<br>});</pre><h4><strong>Why is that number so high?</strong></h4><p>Well, technically, on the client I ❤ Meteor is set up with infinite scrolling pagination, meaning, we limit the number of posts on screen to 24 projects on first load. In the code above, we’ve commented out this limit, meaning <em>all</em> projects are published to the client at once. For our example “Response Time,” we loaded up our database with 1000+ documents. Translation? Without a limit our publication is sending 1000+ documents to <em>each</em> client as soon as they connect.</p><p>You may be thinking “Jeeze, two seconds is pretty good…isn’t it?” If we only had one user? Sure, not terrible. However, this is the response time for a single connected client, meaning, for each user that connects, they’re all receiving this response time. The punchline is that the response time is high because we’re sending too much data on load (the user obviously cannot see all 1000 projects at once) and our server is having to process each of those requests, leading to an unnecessary waste of server resources.</p><p>Again, good-guy APM is letting you know who’s got their hand in the cookie jar so we can correct it. In case the correction isn’t clear, we just need to uncomment our limit in our publication on the server so that it properly kinks the hose, only letting out a few projects at a time. That sounds suggestive. It isn’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1URcu76kd3_PI61CBNGstg.gif" /><figcaption>Reviewing the stack trace for our pub/sub response time.</figcaption></figure><h3><strong>Improving performance</strong></h3><p>Updating our publication code to include our limit again, if we redeploy, we can see a significant improvement in response time, down to 404ms. This is much better, however, we can improve it further. While the “Response Time” here is helpful, Meteor APM can help us dig in even further and see more information about the stack trace of our request (literally, the timeline of operations between opening the connecting and getting a response).</p><p>In the GIF above, if we look at the stack trace for our projects publication — accessible by clicking on a point in the “Response Time (ms)” chart and scrolling down to click on the blue button under “Traces at” — we can see a blip in our stack trace. Here, our response time seems to be slowing down because we haven’t <a href="https://themeteorchef.com/tutorials/deploying-with-meteor-galaxy%23tmc-setting-up-a-database">enabled MongoDB oplog support</a>.</p><p>If we follow the breadcrumb trail laid by Meteor APM and add support for MongoDB oplog tailing to our application, we can see our application’s performance improve on our next deployment:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7HDMzosEJbAMJRL0JuvHQ.png" /><figcaption>You can almost smell the money this is saving.</figcaption></figure><p>Well dang, Meteor APM, you just earned your keep <em>fast</em>. With just two changes that would have otherwise been next-to-invisible, we dropped our pub/sub response time down from 1688ms to 141ms, gaining our users back 1.5 seconds of their lives. Impressive, right? What if we apply this same process to our methods? Making a quick modification to our method code in /imports/api/projects/server/methods.js:</p><pre>export <strong>const</strong> submitProject = <strong>new</strong> ValidatedMethod({<br>  name: ‘projects.submit’,<br>  validate: <strong>new</strong> SimpleSchema({<br>    title: { type: String },<br>    url: { type: String },<br>    createdBy: { type: String },<br>    image: { type: Object, blackbox: <strong>true</strong>, optional: <strong>true</strong> },<br>  }).validator(),<br>  run(project) {<br>    <strong>const</strong> projectToInsert = project;<br>    projectToInsert.owner = <strong>this</strong>.userId;<br>    <strong>const</strong> imageToInsert = projectToInsert.image;<br>    <strong>delete</strong> projectToInsert.image;<br> <br>    <strong>const</strong> projectId = Projects.insert(projectToInsert);<br> <br>    s3.putObject(imageToInsert)<br>    .then((image) =&gt; {<br>      <strong>if</strong> (image) Projects.update(projectId, { $set: { image } });<br>    })<br>    .catch((error) =&gt; {<br>      <strong>throw</strong> <strong>new</strong> Meteor.Error(‘500’, `${error}`);<br>    });<br> <br>    <strong>return</strong> projectId;<br>  },<br>});</pre><p>Where above our new project creation was dependent on receiving a URL back from Amazon S3 <em>first</em>, here, we’ve refactored our code to <em>not</em> do this. Instead, we create our project first and <em>then</em> attempt to store our image on Amazon S3. On the client, we have a placeholder image loaded until we get a response back from S3. Once we do, we go ahead and update the project we just inserted into the Projects collection. With this, we skip an unnecessary wait on Amazon S3 and can respond to the user much quicker.</p><p>If we deploy this change to Galaxy and look at our Method response time…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IotAQ9FSITbV8f8wmxhZuA.png" /><figcaption>Our newer, better response time.</figcaption></figure><p>Put some relish on that hot dog: it’s eatin’ time! Wait…what? Ignoring that, though not as dramatic, we’ve managed to decrease our projects.submit method’s response time by 80ms. While this may seem trivial, when it comes to application performance an “every penny counts” attitude is key. Any time we can save our users means happier customers and a lighter load on our servers. Win!</p><h3><strong>Watching for and correcting client-side errors</strong></h3><p>Galaxy APM makes this almost a little…<em>too</em> easy. Regardless, we should take a look as there are a few discrete steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cb3iWahMebJwU9iFBFknxA.png" /><figcaption>In case our instructions don’t make any sense, Meteor APM offers their own, too.</figcaption></figure><p>First and foremost, we need to make sure that we’ve enabled support for client-side error tracking by installing the meteorhacks:zones package. In case you’re wondering, yes, this package <em>was</em> originally offered by the folks at Kadira but is now maintained by the Meteor Development Group (translation: safe as spaghetti sauce). From your project, in the terminal:</p><pre>meteor add meteorhacks:zones</pre><p>Once this is installed, make sure to deploy your application to Galaxy as any client-side errors in your development environment will <strong>not</strong> be tracked. Once your application is deployed, head over to the “Errors” tab in Meteor APM (visible in the top-left of the dashboard beneath the “Meteor APM” logo). If any client errors occur on <em>any</em> connected client, they will now appear here.</p><p>As an example, if we connect to our deployed application (e.g., https://www.ilovemeteor.com) in the browser console we can run:</p><pre>setTimeout(() =&gt; { <strong>throw</strong> <strong>new</strong> Error(‘These pretzels are making me thirsty!’); }, 100);</pre><p>After a few seconds — potentially a bit longer if there are clouds over San Francisco — we should see our error pop up in Meteor APM:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gjl0y4KUPYU2RryJqJJzw.png" /><figcaption>Client-side errors appearing in Meteor APM.</figcaption></figure><p>Pretty neat, right? Not only do we see the errors that were thrown, but we get access to the user’s browser information, the exact date and time the error occurred, the URL they were on when the error occurred, and a full stack trace. Having this information means solving client-side errors much faster, avoiding the whack-a-mole “works on my machine” strategy for bug fixes.</p><blockquote>Looking for more?</blockquote><blockquote>While we’ve covered the basics of working with Meteor APM, we highly recommend reading <a href="http://galaxy-guide.meteor.com/apm-getting-started.html">the Getting Started with APM guide</a> to get a detailed look at the APM dashboard and all of the features it includes.</blockquote><p>With this in place, next, let’s take a look at Galaxy Pro’s IP whitelisting feature to see how we can connect our app to third-party services securely.</p><h3><strong>Enabling and using IP whitelisting</strong></h3><p>As part of our upgrade, one thing I ❤ Meteor has been missing is a staging server. While the app’s production database is hosted on mLab, for staging, we want to test out hosting our database on the MongoDB Atlas service. In order to connect to any databases we create on Atlas, we’re required to list the IP addresses of any servers connecting to the database. Fortunately, with Galaxy Pro we can get access to this information and set up our connection without a lot of fuss.</p><h4><strong>Getting access to Galaxy’s IP addresses</strong></h4><p>You <em>may</em> be thinking “I already know how to do this” if you were paying attention earlier when we upgraded I ❤ Meteor’s containers to the “Professional” level on Galaxy. If not, what we need to do is head back to Galaxy dashboard and access the “Settings” tab for our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2GDKtN7EMNPsTL0PApFcPQ.gif" /><figcaption>A really, super difficult button click to enable IP Whitelisting. /s</figcaption></figure><p>Up toward the top under the now-visible “Galaxy Professional” block, we want to click the “Enable IP Whitelisting” button. When we do, we’ll automatically see a list of IP addresses mapping to our containers appear over on the left in green (and see the “IP Whitelisting” header show “Enabled” instead of “Disabled”). That’s it! Now we have access to the IP addresses for our container.</p><p>To make sure usage is clear, let’s jump over to the MongoDB Atlas service where our database will be hosted and see how to put these addresses to use.</p><h4><strong>Making use of our Galaxy IP addresses</strong></h4><p>We’re going to skip ahead a bit in the process now and assume you’ve already signed up for a MongoDB Atlas account here. Once you’ve signed up and created your first cluster, you should be logged in and see a message about your cluster being deployed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oMcekaO_FzuR3eu7ayJAqg.png" /><figcaption>A suggestion to set up IP Whitelisting while our cluster is deployed.</figcaption></figure><p>Inside of that message, we can see a suggestion to set up IP Whitelisting for our app under the “Security” tab in our dashboard. If we jump over there, we can click on the green “Add IP Address” button to reveal a modal to enter our IP addresses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WjjhqHSHtCp2tUqUp3k9w.png" /><figcaption>Adding IP addresses for Galaxy to our cluster.</figcaption></figure><p>As the helper text suggests, this will allow us to securely connect to our database on MongoDB Atlas without any issues. Optionally, we can set a comment (a wise choice) to let us know who issues this IP address. For convention sake, something like Meteor Galaxy #1 (up through #4 for each IP address) should do the trick.</p><p>Once we’ve added each of these, we’re all set! If we boot up our production app, we should have access to our database on MongoDB Atlas without any issues. If you’re feeling curious, try removing these IPs to see how the connection fails. <a href="https://www.youtube.com/watch?v=TWHOQC88Qxc">Destruction</a>!</p><h3><strong>Wrapping up</strong></h3><p>Well, that about does it for now! I ❤ Meteor is up and running on Galaxy Pro, we’ve configured our app for performance monitoring and error tracking, and we even connected our staging server to a database using IP whitelisting. From here, it’s up to us to keep a watchful eye on performance and errors.</p><p>If we run into any snags, though, Galaxy Pro offers prioritized support, meaning any support requests are bumped up in Galaxy’s support queue for faster service! Nice.</p><p>Pretty good. <a href="https://youtu.be/O_05qJTeNNI?t=7s">Pretty, pretty, pretty, pretty good</a>.</p><h3><strong>Takeaways</strong></h3><ul><li>Galaxy Pro gives us access to a great set of tools for monitoring application performance and behavior with Meteor APM.</li><li>If our application uses third-party services that require access to our server’s IP addresses, Galaxy Pro’s IP whitelisting is a must-have.</li><li>Overall, Galaxy Pro is pretty dang easy to set up. Just a few packages and a few clicks to improve our devops setup.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24787d7ff05b" width="1" height="1" alt=""><hr><p><a href="https://blog.meteor.com/improving-app-performance-with-meteor-apm-and-galaxy-pro-24787d7ff05b">Improving App Performance with Meteor APM and Galaxy Pro</a> was originally published in <a href="https://blog.meteor.com/">Meteor Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thinking Like an Artist]]></title>
            <link>https://medium.com/@themeteorchef/thinking-like-an-artist-cd77f233224f?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd77f233224f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[thinking]]></category>
            <category><![CDATA[artist]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 16 May 2017 14:54:28 GMT</pubDate>
            <atom:updated>2017-05-16T15:00:17.679Z</atom:updated>
            <content:encoded><![CDATA[<p>I had an interesting childhood growing up.</p><p>My mother, a commercial artist, worked alongside her father running his architectural rendering business that focused on hand-painting photorealistic images of proposed developments. Clients would hire my grandfather and his team to conceptualize what a piece of architecture would look like after it was built. The end goal being to either present a possible future (to secure funding or other resources — like a prototype in software development) or, to build momentum around the eventual unveiling of a property.</p><p>It was a truly unique business because the work the company produced was world-renowned, yet, was operated from a tiny suburb in Northwest Ohio — a mostly rural state — here in the United States. As a child, I — along with my brother and cousins — often found ourselves running around the office building my grandfather had designed and built for the business, oblivious to the work taking place or the caliber of clients traversing the halls.</p><p>Inside of just a few square miles, my grandfather had built a small empire, encompassing the studio, his own custom-designed home, and a string of high-end neighborhood developments. As if this weren’t enough, he had an impeccable eye for detail; laughingly unmatched — he’s well aware of his talents — by his contemporaries. It was — and is, still in his seventies — a family joke that the man is notoriously fussy. Mistakes were seldom tolerated, with the bulk of his discontent being shouldered on the argument “well why wouldn’t you do it this way?”</p><p>Albeit delivered in a more gentle package, this same attitude trickled down to my mother who espoused the same values in her own work. Though she passed away in 2009, some of her early illustration work still hangs on my living room wall, constantly reminding me of the (self-imposed) legacy I need to live up to. A legacy that speaks to an unshakeable commitment to detail, quality, and having the patience and persistence to produce things that others can — and often will — not.</p><p>This past weekend, I had the chance to visit my grandfather at his home where, still to this day, he works with a small number of clients, mostly overseeing the work of digital artists (he’s since downsized his operation). Following a lengthy conversation on his porch, he excitedly took me inside to show me some of the work one of those artists produced recently. Pulling up a set of chairs to his computer, he scanned through his email to open an attachment containing a low-res rendering, a work in progress for a current client.</p><p>While the work was certainly impressive, what struck me most was his enthusiasm for the details. He zoomed into the proof, pointing out things that most others would ignore: the intricacy of the stone work on the building’s facade, the texture of the clothing on the people placed in the scene, and — my favorite — a nitpick about how the work in question was noticeably missing shadows beneath the plants draped in the planter positioned in front of the building’s entrance (something he let the artist know to fix). It was in this moment, watching the smile on his face, that it was affirmed that the man was a true artist.</p><p>While I’ve yet to live up to the work that he, my mother, and their team produced, I’ve found a similar obsession with detail in my own work (much to the frustration of those that I work with). When it comes to software, though many would consider the visual design to be where the details stop, they seldom are. The interface is just one piece of the puzzle, with arguably bigger details like interactions, copywriting, and overall composition of a product remaining as cornerstones.</p><p>Driving back home on Saturday, I had a long think about what it means to be an artist. While it’s easy to package certain affectations into a figurine that <em>looks</em> like an artist — an unfortunate reality to contend with these days — living a life that embodies the values of an artist is impossible to facsimile. Quite literally, you have to live it. Whatever work you find yourself producing at the moment — irrespective of scope or prestige — is the most important thing you can be doing. You must commit yourself fully, being careful to consider how your approach will dictate the outcome.</p><p>A comical anecdote my grandfather shared during our conversation was his desire and subsequent method for learning to play piano recently. Sitting and staring at the keys to learn notes wasn’t enough. In-between complaints about films that show someone playing the piano on the lower-octave keys of the instrument while the matching audio is in a higher-octave, he explained that his own practice is performed entirely in the dark. His focus being on memorizing the position of the keys and the notes they produce physically, first, allowing for — in his opinion — a more organic, less-predictable music to be produced each time he plays.</p><p>While it’s a bit trite to condense into one thing, what artistry boils down to is caring about the details. Not just feigning care, but really <em>giving a damn</em>. Not succumbing to the pressure of others and worrying about what they may think. Honing your process and understanding that how you get there is just as — if not more — important as getting there. Your focus is always one hundred percent on producing the best possible work, no matter the cost (both time and monetary). This is an incredibly difficult attitude to embody, one that necessitates a high level of confidence in your work; past, present, and future.</p><p>In respect to software development, this may seem difficult, if not impossible. The truth is that at any given point in time, there are maximums. You will only be so good — and able to do so much — at different points in your career. Work must ship eventually and bills have to be paid. The point isn’t to be a stubborn jerk, but to recognize that what you’re producing today is far from your best and that you can get better. That, in forcing yourself to produce your best possible work <em>today</em>, you inch closer to perfection in the future. All the while recognizing that while you’ll never achieve perfection, each effort you make toward achieving it means that what you <em>do</em> produce is always at its acme.</p><p>This is why I’m picky about who I work with. If I catch even a whiff of opportunism in someone’s actions, I immediately — perhaps to my detriment — dismiss their work. A great example of this is the reason that I work with Benjamin, the editor here at TMC. Working together elsewhere before we teamed up on TMC, it was abundantly clear that he has an ongoing love affair with detail.</p><p>Submitting my writing to him for approval, it’s not uncommon to get an email containing quibbles like “you should use an en dash here instead of an em dash.” While his personality dictates his comments always being delivered with a patient, honest apology, I love receiving his feedback because I’ll know that he looked at my — and others — work with the eye of an artist; not just someone going through the motions to get paid.</p><p>When I look at how my grandfather behaves, it’s clear that while he understands the importance of running a business to make money, his actions and the life they’ve produced suggest that his true motive is doing interesting, exceptional work. Making a point to invite only those who care as much as he does about the craft of what he’s producing, never concerning himself with external opinions. It’s taken him a lifetime to afford the ability to do this, but in that lifetime, he never wavered from his vision of what was correct.</p><p>This is, in my eyes, what thinking like an artist is all about.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd77f233224f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Tools Are Not Your Product]]></title>
            <link>https://medium.com/@themeteorchef/your-tools-are-not-your-product-dad63f19d892?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad63f19d892</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 28 Mar 2017 14:06:36 GMT</pubDate>
            <atom:updated>2017-03-28T14:06:36.450Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the inevitabilities of building a piece of software will always be deciding what to build it <em>with</em>. Try as we might, defining and implementing the “perfect” stack will always be elusive. It’s difficult to admit, but in reality, from the second we start writing code, we’re maintaining a legacy project.</p><p>“But wait! I’m using the latest version of Blerga, Flerga, and Derga! And the developer who wrote the boilerplate I’m using said it was future proof! <em>You’re crazy</em>.” Perhaps all of that is true right now. How about in six months? A year? Two years? It doesn’t matter how we frame it: dealing with change is part of the job. The latest and greatest tech will always become the done and over with eventually.</p><p>As a mentor, “what should I build this with?” is easily the most common question I get. My answers vary depending on the person I’m working with, but generally the answer is “use what you know.” A truth that took me a long time to accept is that for the majority of the software we build, especially for the first few versions, the stack we use matters very little. Sure, there are some idiosyncrasies that will dictate the need for certain tools to be used, but by and large, the tools we use have very little impact on the product we’re trying to build.</p><p>Thinking like this is tricky. It requires you to take off your engineering hat and put on your customer hat. One way to do that is to consider your experience with other products throughout your day. How often, unless you’re just being a geek (guilty), do you think about or concern yourself with what those products are built with? Think about it. Is your measuring stick for how useful a product is what code it was written with? If you know that your favorite app is written in Python (Instagram) or PHP (Facebook), are you just going to stop using it?</p><p>Unless you’re bananas, of course not. Guess what? The same applies to your own customers. Just like <em>you don’t</em> with other products, your own customers don’t care what you build your software with. They just want to know that it solves their problem and does so consistently without any hiccups. Funny enough, producing such a result is usually quite tricky with bleeding-edge tools. It’s usually the old and boring stuff that works best.</p><p>So, wait…should I not use Meteor, or React, or the other stuff you write about? That depends! How well do you understand those tools? Do they give you some sort of advantage in respect to time-to-market? Do they solve a unique problem in your own product? Or, as is usually the case, are they just the “cool new thing” that everyone’s talking about? Knowing the difference is key.</p><p>If you’re going to build a successful product, you have to know when you’re just being a geek playing with new toys and when you’re making a well-informed business decision. This isn’t to say that there’s anything wrong with playing, but if you’re ever going to ship anything, you have to learn how to turn off your nerd ego and say “this will do for now.” The truth is that there will <em>always</em> be some part of your software that’s out of date. Some part that’s not the hottest new thing but works pretty damn well. Something that your code buddies may snark at but your customers won’t even know exists.</p><p>As long as your tools enable you to deliver a functional solution, what you use matters very little. Forget about the hype and focus on the problem you’re trying to solve. Your fellow nerds aren’t the one’s paying your bills, your customers are.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad63f19d892" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[It’s Not Easy]]></title>
            <link>https://medium.com/@themeteorchef/its-not-easy-5d5e2967916?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d5e2967916</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[perseverance]]></category>
            <category><![CDATA[meteor]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 13:43:26 GMT</pubDate>
            <atom:updated>2017-03-20T13:43:26.597Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past few weeks, I’ve been spending a lot of time learning. Initially, my focus was on trying to wrap my head around GraphQL and Apollo, and this past weekend, I wanted to take a swing at building a non-Meteor Node.js application. While learning both, it really sunk in: this stuff is hard. <em>Really hard</em>.</p><p>GraphQL is a total paradigm shift in respect to handling data, while getting a Node.js app up and running requires a lot of fiddling with complex tools like Webpack. Neither are a walk in the park to wrap your head around, especially on first pass. Even worse, while the internet <em>is</em> littered with examples, most are mystical. Sure, repos exist with examples, but <em>seeing</em> the code is not the same as <em>understanding</em> what the code is doing. Most of my time was spent connecting the dots between various repos and doing a lot of trial-and-error.</p><p>Now, if I were to mutter this in a group of even moderately-experienced developers, they’d scoff; at least internally. “Pssh, this is easy! I figured it out in ten minutes.” Without a doubt, whenever I’ve even hinted at struggling with something, there’s always been another developer waiting with baited breath to tell me in so many words that I’m an idiot, they’re smarter than me, and so on.</p><p>Web development is not easy. It’s certainly become <em>easier</em> than in the past, but it’s far from easy. When we codify things as “easy,” it inevitably leads to discouragement. If Übernerd A says it’s easy, then I must be an idiot for not getting it…right? Of course not. But this is the sort of culture we’ve begun to engender. When someone doesn’t know, we offer up helpless quips like “read the docs” when we know damn well good documentation is rare.</p><p>Instead of peacocking, we should strive to develop a culture where we take the time to properly explain things to other developers. Even if there’s no immediate return, on an altruistic level, we know we’re putting another well-informed developer into the ranks. No, that’s not easy. Yes, that requires selflessness. But even within the confines of your own team, it can mean the difference between someone leveling up quickly–effectively, making your life easier–or cowering away with a brilliant idea because they shudder at what the other developers will say.</p><p>What I feel is most important is understanding that the people who are less-experienced are the people who will need to know in the future. It seems a bit counterproductive to create a spirit of isolation around knowledge. If software development was war, wouldn’t it be worth your time to teach the person next to you in the trenches how to load their rifle properly?</p><p>Yes, your knowledge was hard-won. That’s a great thing. But what’s also great is being able to help others to understand what your process looked like to get to that point. Did <em>you</em> read the docs, or did you spend six hours one Saturday playing whack-a-mole with some new tech’s API? It’s funny, when you help others out, they tend to help you out in return, without you even asking. Taking the time to counsel others can pay serious dividends later.</p><blockquote><em>“You can get everything in life you want if you will just help enough other people get what they want.”</em></blockquote><blockquote><em>— Zig Ziglar</em></blockquote><p>Even with something like Meteor, building software is still a challenge. Most of our examples are trivial, so of course, we trick ourselves into thinking “with this new tool, I can build anything in minutes!” Of course, once you try to test the flexibility of <em>any</em> framework or tool, reality sets in. Everything has caveats. Everything has shortcomings. There is no perfect tool. No perfect solution. In order to create anything, you really have to know your stuff. That’s not easy.</p><p>If you’re in a position of power or looked up to by other developers in any way, be careful how you speak. Even if factually speaking your brain could “totes crush their brain, dude,” there’s no need to assert that. Whenever you do, you look like an asshole and you discourage the other person from putting in the necessary effort to get to your level. People don’t forget when you’re a jerk, but they also don’t forget when you were really helpful. Guess which side you want to be on.</p><p>As for the developers who have been caught in the Vortex of Insecurity™ that is many-a-developer’s ego, understand this: move at your own pace. There’s nothing wrong with <em>not</em> getting things quickly. It takes time. It takes patience. The majority of my own knowledge came from a ton of time spent just hacking at stuff. Putting pieces together, making mistakes, and really grinding it out…<em>over ten years</em>.</p><blockquote><em>“You always want to consider your inner scorecard–how you feel about your own performance and success. You should worry more about how well you perform rather than how well the rest of the world perceives your performance.”</em></blockquote><blockquote><em>— Warren Buffett</em></blockquote><p>Forge your own path. If it takes you six months to learn some new thing, so be it. Don’t psyche yourself out because the person sitting next to you figured it out quicker or made a little quip about getting there first. Better, learn the thing and then take the time to help another developer who is struggling with it later on.</p><p>Oh, and don’t forget to remind them: “just keep at it. It’s not easy.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d5e2967916" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pace Yourself]]></title>
            <link>https://medium.com/@themeteorchef/pace-yourself-9490aa906684?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/9490aa906684</guid>
            <category><![CDATA[coders]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Wed, 01 Feb 2017 19:22:22 GMT</pubDate>
            <atom:updated>2017-02-01T19:25:21.292Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/pace-yourself"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>Don’t beat yourself up if you can’t ship your Meteor app’s minimum viable product in three days from now. And if you’re planning on staying up all night to meet a deadline, consider making a better plan.</p><p>As a web developer, your mind is one of your most valuable assets. Giving it proper rest and relaxation can go a long way to making your career as a web developer enjoyable, sustainable, and free of burnout.</p><p>Just a note: this post contains lightweight spoilers for the 1999 film <em>The Matrix</em>. I guarantee that I’m not ruining the movie for you, but if you’re totally spoiler averse — stop reading now. Also, feel free to disagree with this post. If, <a href="http://paulgraham.com/head.html">like Paul Graham</a>, you work better in 12–18 hour “stretches,” don’t let me stop you. I’m just here to question whether that way of working is sustainable.</p><h3>Computer people aren’t actually machines</h3><p>You’ve seen movies about computer people. Many computer people are colored as reclusive, sleep deprived, mentally unstable, and drugged-out geniuses. Sometimes they are people with intentional haircuts and leather coats, and other times they are skinny, greasy children with sleep in their eyes. Most notably, computer people are categorized as machines who get stuff done <em>well</em> and <em>quickly</em>.</p><p>This is definitely just a stereotype: many responsible programmers are mothers and fathers who sleep through the night and drink a serving of coffee in the morning. They’re not geniuses, either. Just regular people. You may even know some developers who <em>aren’t</em> moms and dads and still don’t align with the computer nerd character from your favourite films. So, where does this stereotype come from?</p><p>I think part of it comes from real-life computer people. It’s us computer people who have 48 hour-long hackathons, who quit their jobs to work at startups where every employee does the work of two or three nonexistent employees. It’s computer people who start multi-million dollar businesses out of their garages.</p><p>There is all kind of lore about developers who work like this:</p><ul><li><a href="https://en.wikipedia.org/wiki/Lisbeth_Salander">Lisbeth Salander</a> from <em>The Girl with the Dragon Tattoo</em> series is pale, eats a lot of delivery pizza, is a genius, and works very quickly.</li><li>Cameron Howe from <a href="https://en.wikipedia.org/wiki/Halt_and_Catch_Fire_(TV_series)"><em>Halt and Catch Fire</em></a> (played by Mackenzie Davis) can do anything if she’s left alone in a room with a computer for a few days.</li><li>Kevin Flynn, creator of <em>TRON</em> in the film <a href="https://en.wikipedia.org/wiki/Tron"><em>Tron</em></a> can literally manipulate the game’s environment just by thinking about it because of his insane sudo powers.</li></ul><p>There is a lot less lore about people having real lives and <a href="https://www.kennethreitz.org/essays/the-reality-of-developer-burnout">burnout being real</a>.</p><h3>We’re not heroes, let alone superheroes</h3><p>Don’t panic. You don’t have have to be a notorious, drugged-out hacker in order to be a good developer. You don’t have to look like Neo before he found out what The Matrix was.</p><p>If you’ve forgotten, he looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/0*PPh468zRl30A2Epx.png" /></figure><p>And his living quarters looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*VZktw3OBZZ8nNMvP.png" /></figure><p>In <em>The Matrix</em>, Neo is accepted by Morpheous’s team in part because he’s a talented hacker. The movie shows that Neo is a talented hacker by making sure he looks like he barely sleeps and like he hasn’t changed his lightbulbs in twenty years.</p><p>I realize that Neo is an exaggerated version of how our western culture views computer people. But if you ask me, our cultural model of what a tech industry success story looks like is just as unsustainable. There’s nothing wrong with working from 9:00am-ish to 5:00pm-ish, taking weekends off, and taking an extra day or two to complete a task. If you have bags under your eyes, something’s wrong.</p><p>Programmer superheroes aside, what can we learn from real-life software engineers? Are we setting an unhealthy precedent for how we are supposed to work?</p><h3>Setting a new precedent</h3><p>Let’s say that you don’t take our culture’s view of computer people too seriously.</p><p>There isn’t a good enough reason to try to emulate the rapid-fire, overnight success and growth of Facebook, or how quickly the<em>Halt and Catch Fire</em> cast can ship their computer, the Cardiff Giant.</p><p>Still, do you find yourself getting excited about what you’re working on and staying up all night with it? Or even just missing dinner with your family a few nights every month? It’s great to be excited about your work, but there’s no harm in closing your code editor and waiting until the next day to finish some code. It’s possible to be “on a roll,” or “in the zone,” and doing a lot of good work all at once. But it’s magical thinking to think that a hyperproductive zone state is not reproducible.</p><p>Every time that you give up time with your loved ones, to sleep, or to learn something new in order to pump out some code and get paid, <em>you’re proving the stereotype right a little bit</em>.</p><p>Plan your day ahead of time. If you can’t get it all done, make a note and try to estimate more accurately next time. Most importantly: put in your time, and clock out when it’s over. Just try to pace yourself!</p><p>Especially if you’re a business owner, it can be easy to get to work early and leave work late — and work too often. Our culture doesn’t frame overworking as <em>a risk</em>. When you don’t sleep or never stop thinking about work, you can let other things (and people!) in your life slip away.</p><p>In extreme cases, you might be doing permanent damage to your body if you’re constantly giving up sleep to get stuff done, and keeping yourself up with coffee, sugar, and other less-common supplements.</p><h3>Resources</h3><p>If you’re feeling burned out, overworked, or anxious about your next deadline, take a break and give yourself a pat on the back. Here are some resources if you need some help getting control of your head space back:</p><ul><li><a href="http://www.sleepwithmepodcast.com/">Sleep With Me Podcast</a> is a podcast that attempts to bore you to sleep. If you have issues getting to sleep because your mind is still in problem solving mode, focus on this truly boring podcast.</li><li>Read Charlie Hoehn’s essay <a href="http://thoughtcatalog.com/charlie-hoehn/2013/05/i-dont-think-about-work-all-the-time-anymore-and-im-seriously-way-happier/">I Don’t Think About Work All The Time Anymore And I’m Seriously Way Happier</a> and get another perspective on the detriments of workoholicism.</li><li>The best article I could find with legitimately practical tips on forcing yourself to leave work was <a href="http://lifehacker.com/5832503/how-to-stop-working-and-go-home-at-night">How to Stop Working and Go Home At Night</a> on Lifehacker.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9490aa906684" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Audit Your Processes]]></title>
            <link>https://medium.com/@themeteorchef/audit-your-processes-12e0101f09a0?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/12e0101f09a0</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[getting-things-done]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Fri, 27 Jan 2017 22:45:58 GMT</pubDate>
            <atom:updated>2017-02-01T19:26:36.809Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/audit-your-processes"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>At The Meteor Chef, we’re fans of <a href="https://en.wikipedia.org/wiki/Mise_en_place">mise en place</a>. Before we start to work, everything should be in its place. This isn’t just because we want things to look nice. It’s because we don’t want to have to think about the same menial tasks that we hate doing every day. We want to cut these out of our workday as much as possible.</p><p>If you’re taking it seriously, mise en place makes things more efficient, more organized, and helps the focus remain on the <em>important</em> things rather than <em>every</em> thing. You could apply mise en place to your coding process. Even just using something like <a href="https://textexpander.com/">TextExpander</a> can mise-en-place-ize your code habits by helping you power through the CSS vendor prefixes you always forget, your app’s @import statements or other one-liners that crop up too often in your JavaScript files.</p><h3>Mise en place</h3><p>Mise en place is not a specific set of rules that shape your work and your work process. This is the greatest thing about mise en place. For me, a big part of putting everything in its place means clearing my work desk of distracting materials, closing all of my open browser tabs, and making sure I’ve looked over any emails in my inbox. If that sounds underwhelming, it’s because it is.</p><p>The bigger, longer-term part of mise en place for me is making sure that I am making the most of my time. That means spending less time creating invoices for clients, writing the same shit over and over, and revisiting my to-do lists and calendars to jog my memory about the tasks I have to complete today.</p><p>The goal is this: to reduce my repeated work. To turn myself into a human with dignity and an efficient machine at the same time. I want to be flexible and productive and creative, without the weekly burden of hours of tasks <em>that I have no interest in doing</em>.</p><p>Let’s use email as an example, since email really stresses me out. My end goal is to get in and out of my inbox as quickly as possible.</p><h3>Audit your processes</h3><p>Because I have a goal to reduce the amount of time I spend in email, I have to consciously audit how and why I use email.</p><p>To achieve email mise en place, then, I need to not only think about how I use email <em>while</em> I’m dealing with it, but I also need to set aside time to <em>prepare</em> a better process. Once I’ve prepared a better process, I can test it out to see if it improves the email experience for me. If not, I set aside time to tweak the process and try again.</p><p>At first, this can seem like a long, unpaved road. If I’m not careful, I’ll get carried away auditing a bunch of email clients, or specific features of email clients. Or I’ll get carried away auditing a new way to organize canned responses to specific types of emails. Or setting up email filters. Or worse. You get the picture.</p><p>The best trick is to not get carried away. If you find yourself getting carried away, schedule a rigid ten minutes once a day (or once a week) to experiment. Let your experiments last for weeks at a time. Make small, iterative changes to your process and let things either stick or fall away.</p><p>Over the last year and a half, my email process has felt increasingly less stressful. I spend less time dealing with emails than I used to. And, after spending a year and a half seriously test-driving four different mail clients, learning some keyboard shortcuts, and improving my labelling system, I’m in and out of my email in around fifteen minutes every day. Not bad.</p><h3>Audit for quality</h3><p>Steve Jobs was interviewed for a documentary called <em>An Immigrant’s Gift: The Life of Quality Pioneer Joseph M. Juran</em>. Jobs speaks of Dr. Juran’s scientific approach to quality. Every aspect of a process should be examined and deconstructed. Nothing should be mysterious. Here’s a quote:</p><blockquote><em>I think the things that we’ve learned most from Dr. Juran are to look at everything as a repetitive process, and to instrument that process and find out how it’s running. And then start to take it apart and put it back together in ways that dramatically improve its effectiveness in a very straightforward way. No magic. No pep rallies. Just, looking things directly in the eye, seeing them as repetitive processes, and re-engineering them.</em></blockquote><p>If you’re interested, <a href="https://www.youtube.com/watch?v=XbkMcvnNq3g">here’s a link to the full interview</a>.</p><p>Repetition is useful. If a task is repeated, it helps to measure the importance of task. If you look at how something is repeated, and when it is repeated, and how often, you can start to determine if the task (or some part of the task) can be automated. In some cases, maybe the repetitive task can be thrown out all together, or replaced by something else.</p><p>Going back to the example of email, I realized that I was hurting myself by using my inbox as a half-assed to-do list. (<a href="http://www.43folders.com/2006/03/20/action">Merlin Mann would be so angry</a>.) This made the quality of my to-do list half-assed, and the quality of my email inbox half-assed. It was all half-assed, and the system wasn’t evolving in any way. If I needed to perform a task before I could rightfully archive a message, that message would stay there, haunting me, in my inbox until the task was complete.</p><h3>Acknowledge the brokenness of your system</h3><p>Because I used my inbox as a to-do list, there were messages that would stay there for months. In some scenarios, the task I needed to perform before I could archive the message would be a “someday” task. In other cases, it was an entire entirely optional task, which I’d never (in my right mind) have time to do. The consequence felt worse than just another message lying around. These messages were taking up space in my short-term memory that they didn’t need to occupy.</p><p>Now, when I <em>really</em> can’t justify archiving an email, I can use <a href="http://sparkmailapp.com/">Spark</a>’s snooze function to defer the email until it’s actually time to deal with it. Yeah, it only took me a year and a half to figure that out.</p><p>But on that year-and-a-half path, I also figured out exactly how I should and should not use my email-snoozing powers. My system, from start to finish, makes more sense to me now, and it makes me more productive. Now, maybe someday I’ll actually be happy.</p><p>Trust me, mise en place is real. It can help you remove barriers to your productivity. Audit how you work, and find your secret weaknesses. It is totally worth it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12e0101f09a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Falling Behind]]></title>
            <link>https://medium.com/@themeteorchef/falling-behind-b2bf31bc4ac4?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2bf31bc4ac4</guid>
            <category><![CDATA[long-term-thinking]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 13:49:59 GMT</pubDate>
            <atom:updated>2017-02-01T19:26:09.250Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/falling-behind/"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>Well.</p><p>It’s Thanksgiving here in the U.S. tomorrow and v3.0 of the site still isn’t out. My original target for launch was mid-September which has come and gone. Before you ask “he’s not quitting Meteor, <a href="https://voice.kadira.io/its-time-thank-you-bye-meteor-115dd649a8#.5gxv72hyn">too</a>, is he?!,” no, not quite. Instead, I wanted to use this (frustrating) opportunity to teach my fellow developers what I’ve learned about falling behind on a project. It’s an uncomfortable reality, certainly, but it does happen. As opposed to roasting myself on a spit in my head, it seems wise to share some lessons I’ve learned during the development of v3 of this site and — hopefully — guide others down a less arduous path than my own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*La6FqB_FIkAt8UHb63qEPA.png" /><figcaption>I love Homer.</figcaption></figure><p>Something, something, turn lemons into lemonade…</p><h4>How v3 became an idea</h4><p>Version three of this site has been an idea — in some capacity — since version two launched in July of 2015. When that version was released, I decided to move forward with our existing stack: <a href="https://www.siteleaf.com/">Siteleaf</a> (a static-site service) and Amazon S3. Not only was it inexpensive, it was quick, too. In respect to development, though, it wasn’t terribly efficient. To try and take advantage of what I was learning with Meteor, I built a separate app, <a href="https://themeteorchef.com/blog/behind-the-scenes-kitchen/">Kitchen</a>, which served as a pseudo-CMS for the site. This worked, but it was the equivalent of a rope bridge: Kitchen and the site itself communicated solely over API requests. It worked, but it wasn’t getting to the top of the hill.</p><p>In November of last year, Benjamin joined me to help out with editorial duties. Fairly quickly, the system that I was used to wrangling myself started to show its lack of flexibility. I spent a few weeks doing upgrades which _did_ help, but still, the twine-between-two-tin-cans set up was not ideal. Speaking with Benjamin about this, we decided that a rebuild of the site would be necessary. When, though, was unclear.</p><p>After much debating, I decided back around April of this year that a rebuild was a priority (both for business and sanity sake). We discussed a few big areas that we wanted the rebuild to cover:</p><p>- Meteor and React-based!<br>- A proprietary comments system that made it easier for us to respond to readers.<br>- A more articulated version of our coaching service (<a href="https://themeteorchef.com/chefs-table">Chef’s Table</a>), tailored around lessons and customer behavior since its launch in November 2015.<br>- An improved membership experience, complete with members-only content.</p><p>Just as our ideas were taking shape, Meteor’s future was a bit uncertain due to the front-end fiasco of Blaze vs. React. Having spent the past six months tinkering with React (and watching its adoption grow in the JavaScript community), though, I decided it was the right choice and committed to getting started with the build. My original goal for completion was mid-September.</p><p>That was all well and good until…</p><h4>That damn messy life stuff</h4><p>Around the beginning of May, I saw a long-term relationship come to an end which left my head decidedly a mess for the better part of the summer. Coupled with a mounting pile of unexpected expenses and work (writing, contract work, and v3 itself), progress was at a crawl. I knew getting it done was important — if not essential — but the human factor was unavoidable. The lesson I knew but needed to be reminded of then: working incessantly, if not well-paced, can hurt you. I forged ahead, albeit slowly, with the occasional multi-day gap in between work sessions.</p><p>By about July, I was toast. Following a conversation two months prior about meditation with a friend, I made a snap decision to apply to attend a <a href="http://www.ryanglover.net/articles/vipassana/">silent retreat</a> at the end of August. Uncertain if I’d actually attend, I was accepted around June and decided that a break (and what would serve as my first vacation in years) was imperative. Affirming that with Benjamin, we set up a plan to make sure things on the site would keep running while I was gone.</p><p>The realigned goal around v3 was to make a push to finish the bulk of the site before I left and launch it after I returned. Leading up to my departure, I grinded on the site as much as possible (many weekends I was a ghost), but the chosen complexity was simply more than I estimated for a single developer to finish in the time I’d allotted alongside my other work. Safe to say, September came and went with my head still down at the keys.</p><h4>Navigating the uncertainty of Meteor</h4><p>I’d be remiss if I didn’t point out that Meteor — as a project — is changing. Over the summer, I went to visit a friend in Oakland and work outside of my usual space for a few days. As part of that trip, I booked a visit to (finally) meet the folks at MDG (Meteor Development Group). It was a quick visit — just lunch at their HQ and a walk and talk to get coffee — but it was enough to see where things were at overall and more importantly, where the team’s focus was at. What I saw was what I expected: a mixture of <a href="https://www.meteor.com/hosting">Galaxy</a> and <a href="http://www.apollodata.com/">Apollo</a> work. The team there was noticeably abuzz about GraphQL and its potential. Talk of Meteor itself was limited (though, I spent most of my time talking to <a href="https://twitter.com/stubailo?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Sashko S.</a>—Apollo&#39;s lead — so take that with a grain of salt).</p><blockquote>As we’ve communicated over the past 6+ months, we’re investing heavily in Apollo to make Meteor better so it attracts a much larger community of professional developers to ensure it’s longevity. At the same time, we’re aligning Meteor (and Apollo) to the modern professional developer ecosystem vs. continuing to make it a closed, esoteric stack that may be easier-to-use for some but only for small slice of the app dev world.</blockquote><blockquote>The world of developer tools and platforms has evolved since the early days of Meteor and MDG’s decisions in R&amp;D and commercial efforts reflect where we think the future is heading. A cornerstone of the strategy of expanding to a larger market of professional developers also includes new commercial products and paid services which we’ve already begun delivering for GraphQL via Apollo while continuing work on Meteor &amp; Galaxy too.<br> <br>— <a href="https://forums.meteor.com/t/is-it-time-to-leave-meteor-mdg/27346/9?u=themeteorchef">Mark Trang, MDG</a></blockquote><p>Something that’s been on my mind for a long time (at least a year) is taking TMC’s style of teaching to other technologies. As a business owner who’s focus is on teaching technology (Meteor being an initial focus), I have to remain aware of the waning interest in Meteor within the development community. That doesn’t mean Meteor is going away, or dying, or tailing some other <a href="https://www.youtube.com/watch?v=ggJboWWo7lM">apocalyptic scenario</a>. It just means that, if <em>this</em> business (TMC and its successors) is to exist in the long-term, it has to adapt and expand beyond Meteor.</p><p>That said, <strong>v3 is being built with Meteor for a reason</strong> and I continue to recommend and teach it to others for the same one: Meteor is, without a doubt, the most well-considered, easy to use web development platform out there. It’s a serious boon for solo developers and small teams in respect to what you can accomplish. It’s certainly evolved in complexity over the last twelve months, but regardless, it still remains a dream to work with.</p><p>The reason I bring all of this up is that work on v3 slowed quite a bit as I considered how best to architect the new site so that it could support content beyond Meteor. From experience, I knew that it was far easier to slow down and make those decisions now than to scramble about later. Being both the captain of this ship, its primary author, and lead developer means a constant orchestration of effort which from time-to-time leaves certain pieces of the puzzle without attention. C’est des affaires.</p><h4>You can do anything, just don’t give up</h4><p>v3 is close (broken record, I know). Here’s what’s on my list as of writing:</p><p>- Proofing the existing work. I’m confident that everything is sound, but it’s been built over a six month term so I’d like to give it a once-over to be certain.<br>- Marketing pages need to be designed and implemented for the new Memberships offering and Chef’s Table.<br>- Updating content/comment imports. The importers are done but we’ve been writing (and you’ve been commenting!) since they were initially completed.<br>- Route authentication. I purposefully left this out so that I could easily move around the site while developing. The pattern is in mind, it just needs some code-fu.</p><p>This is the reality of building big stuff as a solo developer. It isn’t easy. I mention this not to peacock but as a reminder to those on the road. You can literally do anything, of any size, but you have to remain aware of the long-term, consistent effort required. Don’t be like me and naively convince yourself that “it’s easy!” When you recognize a problem as difficult, it helps to adjust your personal expectations and makes longer timelines less anxiety-inducing.</p><p>In addition to realistic scoping, if I have any other advice, it’s to complete your ideas. <a href="https://themeteorchef.com/blog/dont-quit/">See them through</a>. But, more importantly, take some time to think both up front and as you go about what the future of your idea looks like (read: <a href="http://seanwes.com/behindthebrand/024-your-next-ten-years/">long-term thinking</a> over short-term thinking). One of the reasons I’m optimistic about what we’re doing here is that I started thinking about this site in a post-Meteor context over a year ago. That, coupled with your incredibly positive feedback on our work (thank you!) helps me to realize our success comes down to sheer effort and patience, as well as remembering to keep an ever-watchful eye on the future of web development (and what that means for building a software business).</p><p>v3 will be launched, come hell or high water. Back to work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2bf31bc4ac4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overcoming Overwhelm]]></title>
            <link>https://medium.com/@themeteorchef/overcoming-overwhelm-5790128e697d?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/5790128e697d</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[stress]]></category>
            <category><![CDATA[overwhelm]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[fear]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 12:13:02 GMT</pubDate>
            <atom:updated>2017-02-01T19:27:48.644Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/overcoming-overwhelm/"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>Building software is bananas. Especially when you do it alone.</p><p>For the past five months, I’ve been focused on rebuilding this site from scratch using Meteor. Originally, it was — and as you’re reading it when this is being published, is — a static site, built with <a href="https://www.siteleaf.com/">this service</a>. It’s worked in a simplistic sense, but has lacked a lot of what we needed to take the site from a hobby to a business. For the better part of a year, I debated back and forth whether or not we should make the jump to Meteor. Was it time? Was it ready? Did I know enough about it to swerve around the inherent potholes that would arise? Earlier this year in June, I decided out of frustration that yes, it was time.</p><p>The work that needed to be done was incredibly overwhelming. I’d need to rearchitect nearly everything: the publishing system — which existed as its own Meteor app, poorly connected to the static site by the HTTP equivalent of twine — the membership system, the coaching system, and even the comments (up until v3 we’ve relied on Disqus). In short: I didn’t think I could do it. Fast forward several months, though, and we’re in the (ever-infinite) home stretch. During this time, I’ve realized a few things that have helped me to resolve some of the anxiety around Building Big Things™.</p><h4>Let it have sharp edges</h4><p>I’m decidedly in the perfectionist camp. If I see a billboard with poorly spaced typography in public, I start to twitch. Map that misbehavior to my own work and you can imagine that it’s sometimes difficult to get things out the door. I’m not alone. A lot of the folks I coach through <a href="https://themeteorchef.com/chefs-table">Chef’s Table</a> exhibit the same behavior: “but it doesn’t look right!” In a perfect world, perfection would be king. Unfortunately, the world we live in is messy and <em>imperfect</em>. Accepting this as you comb your way through a mound of work is an incredible salve.</p><p>Sharp edges needn’t mean that something looks bad or doesn’t work, just that it isn’t, in your opinion, perfect. It means looking at a problem and asking “is the core idea being expressed? Is this usable? Does it <em>solve the problem I’m trying to solve</em>?” If your answer is “yes” or leaning toward it, consider moving to another problem. Only when something is dysfunctional or flat out broken (technically or aesthetically) should you — in the early days — over-invest in its production. If you’re the sole developer on a project like I am, you only have two choices: lose your marbles trying to get everything just right or make it look <em>really good</em> and live with a few pointy corners.</p><p>The secret: nobody notices the tiny stuff that you miss. Yes, that’s frustrating. Yes, they should learn to notice, but there’s nothing we can do about it. Instead of letting it infuriate you, use it as fuel. Don’t cut corners on purpose, but when you’ve put a good amount of time into something and it works, move on. <a href="http://sethgodin.typepad.com/seths_blog/2016/10/beating-yourself-up.html">Don’t beat yourself up</a>.</p><h4>Parts not wholes</h4><p>Another overwhelming thought is the sheer amount of work that needs to be done on a big software project. We’ve all sat in a room, scanning a spec sheet remarking “this will be easy!” only to find ourselves hunched over a chunk of code, biting our nails as we kill hour six on what we described as taking “just an hour!” My personal take? <strong>Smash your idea into pieces</strong>. Tiny, easy little pieces. Don’t think about the entire feature, just think about one line of code, one function. Conquer <em>that</em> first and then move to the next step. Whenever you catch yourself worrying about the whole thing, stop.</p><p>Let’s look at a practical example of this. Last night, I was working on moving the comments for the site from Disqus to our new custom system. The problem is chewy and involves a ton of steps. I was most definitely overwhelmed. There’s the initial problem of getting the XML-based export from Disqus (<a href="https://www.youtube.com/watch?v=Y6Rms5J7nGI">hold up, it is!</a>) to JSON, then figuring out how to pair a comment to a post, then mapping that comment over to the new system, <em>and then </em>worrying about child comments. STOP. The problem is irrelevant, but I can guarantee that you’ve hit this same point before. Instead of worrying about everything at once, I looked at each chunk as its own victory.</p><p>As soon as I got the XML into a more-modern JSON, I paused for a bit. Then I sat back down and figured out how to associate a comment with a post in the DB. Then I paused for a bit. Next, I wrote a little script to handle the mapping of the Disqus-specific fields to the new system. Guess what I did next? WENT TO BED. The problem isn’t finished, but I’m paying that no mind. I could have sat up last night and tried to finish, but instead, I went to sleep knowing that <em>progress</em> had been made and <em>parts</em> have been solved.</p><h4>Embrace systems and patterns</h4><p>There’s a lot of code that gets repeated on the new site and not by accident. One of the biggest culprits is email. In the past, I used to just drop in a call to <a href="https://themeteorchef.com/snippets/using-the-email-package/">`Email.send()`</a> wherever I needed it. On this project, though, looking at the parts, I realized that it would simply be too much to manage to entrust all of the email going out of the app to one-off sends. Instead, I realized that building a single, modular system to handle sending was best. What this meant was a single API for sending emails (specifically, HTML) in the application.</p><pre>sendEmailNotification(‘startMembership’, {<br> email: user.emails[0].address,<br> firstName: user.profile.name.first,<br>});</pre><p>With a simple API like this, it meant that a major task could be handle easily <em>and</em> consistently. Instead of introducing worry around whether or not everything looked the same, I know that it does because it’s all being routed through the same system. Yes, it took some time up front to design that system, but compared to the time I would have spent writing each send by hand — and panicking about consistency — it’s a serious boon on progress. Whenever I send, now, I just pass the name of the email I want to send and the payload of data to use with it. In my module, I just add a new method to handle that type of email:</p><pre>startMembership({ email, firstName }) {<br> sendEmail(‘standard’, {<br> to: email,<br> replyTo: ‘<a href="/service/mailto:customers@themeteorchef.com">customers@themeteorchef.com</a>’,<br> subject: ‘Thank you for subscribing!’,<br> }, {<br> title: `Howdy${firstName ? `, ${firstName}` : ‘’}!`,<br> subtitle: ‘You\’re a member now.’,<br> body: Assets.getText(‘email-templates/start-membership.html’),<br> });<br>},</pre><p>It’s a bit hard to tell here, but the `standard` being passed as the first argument tells the module that I just want to use the standard HTML email template for this. To handle the dynamic parts, I either pass a variable, or in the case of the `body`, a compiled version of a sub-template specific to that email. That’s it. The point here isn’t so much the code as it is <strong>learning to invest time into things that will save you time later</strong>. When you do, you reduce overwhelm significantly because you know that you won’t have to think through a problem over and over. You’ve already solved it, now you just need to apply the solution.</p><h4>Breathe, it’s just code</h4><p>When all is said and done, it’s important to remember that this isn’t life or death: it’s just code. As I shared recently, it’s <a href="https://themeteorchef.com/blog/dont-quit/">easy to get overwhelmed and want to quit</a> when the finish line isn’t in sight. That’s okay. When you <em>do</em> get overwhelmed, push your chair back from the desk and walk away for however long it takes to find your center. Don’t let anyone ever tell you this stuff is easy, it isn’t. It takes an immense amount of skill, talent, and determination to build a meaningful software product. Realize that you’re not alone. There are <em>tons</em> of developers sweating it out with you.</p><p>P.S. If you ever find yourself in a situation where you’re not calling the shots and have a manager or other form of stakeholder who’s pushing you beyond your limits, <a href="/service/mailto:ryan.glover@themeteorchef.com">give them my email</a> and I’ll happily let them know just how hard it is to do what you do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5790128e697d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[More Than One Way]]></title>
            <link>https://medium.com/@themeteorchef/more-than-one-way-1e3bf1c3ed0d?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e3bf1c3ed0d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 18 Oct 2016 11:56:10 GMT</pubDate>
            <atom:updated>2017-02-01T19:28:15.254Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/more-than-one-way"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>A common question I get asked is “what is the best practice for this?” Most of the time, I hesitate to bubble up an answer because a reality I’ve accepted over the years is that <em>best practices don’t exist</em>. Said a bit more eloquently, best practices are just an idea. There isn’t an official book called Here’s How To Do It™. We certainly have plenty of <em>suggestions</em> on what is best, but to point to one thing and say “this is it!” is only ever correct (at best) in the short-term.</p><blockquote>“Everything we hear is an opinion, not a fact. Everything we see is a perspective, not the truth.”</blockquote><blockquote>— Marcus Aurelius</blockquote><p>The best solution is the one that works for you and your understanding in that moment. Yes, there’s always going to be a better way to do something but it’s important to constantly ask how much that matters in the pursuit of your goal. From time to time, I like to go back and look at project’s that I’ve worked on. Applications, websites, and everything in between are still up and running on code that, today, I would turn my nose up at.</p><p>Read that again: they’re still running. That doesn’t mean they’re perfect, and that doesn’t mean they’re entirely up to date, but they <em>work</em>. They work because instead of debating over the infinite number of ways that I could have built them, I just chose one and built it. I didn’t worry about scaling them prematurely, and I wasn’t terribly concerned with structure. In retrospect, had I <em>not</em> built those things using the knowledge and patterns I had at that point, I wouldn’t know why they’re not the best today. The only way to truly <em>know</em> is to <em>do</em> and learn from your mistakes.</p><blockquote>“Enjoy the resistance. Let it fuel your idea and if your idea is bad, simply iterate over it. Figure out, maybe, ‘oh, this was the wrong idea, I’m glad I explored it.’ But if you don’t explore it, you can’t actually see the difference […]”</blockquote><blockquote>— Leon Gersing, <a href="https://vimeo.com/54042336">Keep Software Weird</a></blockquote><p>So is that it? Just write code willy nilly and hope that it works out okay? Not entirely. While it’s more difficult to do when you’re early on in your career (roughly, your first 1–5 years), if you’re a real nerd like me something you’ll start to do is study patterns. Eventually, you’ll get frustrated by writing code that seems more squirrelly than it should be and ask “what’s a better way to do this?” Note: that’s not “what’s the <em>best</em> way…”, but “what’s the <em>better</em> way?”</p><p>This, in my opinion, <em>is</em> what is best: seeking out better forms of what you’re already doing, not a singular “best.” What’s neat about this approach is that your work is always evolving along a consistent path that you (or even your team) understand. Your work gets better and you understand it because it’s simply an improved version of what you’ve already been doing. Jumping from practice to practice and tool to tool in search of the holy grail makes this next to impossible. It’s been said before but I’ll drill it home: <em>the holy grail does not exist</em>.</p><p>Well, perhaps that’s not entirely true. The holy grail might exist for <em>you</em>, but not for everyone else. Speaking personally, at the moment, Meteor is my holy grail. It does nearly everything that I want and need it to do. It’s not perfect and it doesn’t fit every single use case, but it works and I understand it. Without a doubt, that will eventually change. One day, I’ll look back and scoff “Meteor! Why did I ever use that?!” Meanwhile, I’ll be staring at some new-fangled best practice, convinced that this is the last thing I’ll ever need to learn…until next Tuesday.</p><p>Be weary of bests. What’s best is only ever best in someone’s opinion, not a pre-ordained truth. Best is — and will only ever be — relative to the individual (or a small group), not the crowd. Don’t believe me? I’ve never been to <a href="https://www.yelp.com/biz/the-spice-house-chicago">this store</a> here in Chicago, but Yelp tells me it’s top rated. If I <a href="https://www.yelp.com/biz/the-spice-house-chicago?sort_by=rating_asc">switch the sorting mechanism</a> on the review list to be “Sort by Lowest Rated,” there are plenty of people who think they can do better. Case in point: whether it be code or spices, someone will always think a thing is “the best” while plenty of others will disagree. Be your own arbiter of quality and utility. Take in other opinions, certainly, but realize that no matter what you pick it will be in the form of The Gospel According <em>to</em>, not The Gospel.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e3bf1c3ed0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Quit]]></title>
            <link>https://medium.com/@themeteorchef/dont-quit-ce60d1ec1784?source=rss-42aaa036cf74------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce60d1ec1784</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[self-doubt]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[perseverance]]></category>
            <category><![CDATA[quitting]]></category>
            <dc:creator><![CDATA[The Meteor Chef]]></dc:creator>
            <pubDate>Tue, 11 Oct 2016 12:50:59 GMT</pubDate>
            <atom:updated>2017-02-01T19:26:57.594Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This essay was </em><a href="https://themeteorchef.com/blog/dont-quit/"><em>originally published on The Meteor Chef</em></a><em>.</em></p><p>It’s strange to admit, but over the last few months, I’ve thought about quitting my work on TMC. A roadblock would appear, either technical or personal, and I’d wonder “is there a point to all of this?” It’s funny, when you’re in the thick of a project, nothing sounds more satisfying than hanging up the towel and stealing away to a dark, musty cave. Alas, knowing full well the results of quitting in the past — and despite the pangs of self-doubt — I’ve forged ahead. Now, with my work on version three of the site nearing a close, I can say wholeheartedly that I’m glad I haven’t quit.</p><p>Quitting is easy. As soon as you decide to quit, you forfeit all responsibility. A weight is lifted from your shoulders. In some cases, quitting is perfectly acceptable, if not preferable. Speaking from experience, it may be wise to <a href="http://www.ryanglover.net/articles/proper-is-shutting-down-october-29th-2014/">quit when you’re putting time into work that you don’t care about</a> or chasing a dragon that doesn’t exist (an unprofitable idea). Unfortunately, most quitting isn’t supported by sound logic. It’s born out of fear, laziness, and contentment with the status quo. An unwillingness to put in the hard work necessary to get to the next plateau.</p><p>Not quitting is a skill. It takes practice. For each leap that you take — scale relative only to yourself — pay close attention to the _good_ that came from it. What did you learn? What didn’t you know before? As you progressively spend more time not quitting, you can see the things that help you and the things that hurt you. For me, one of the biggest aids has been to keep a private notebook. In it, I jot down what I’m learning at a high level. Ideas, quotes by people I look up to, and little reminders of what I was doing at that point in time. By being able to see where I came from, it’s far easier to understand how that led me to where I am and — hopefully — where I’m headed. Reflecting on this sort of stuff can really help to squash the desire to quit.</p><p>Something I like to ask myself when teetering on the ledge: “so what happens now?” It’s a simple question, but incredibly thought provoking. Whenever I ask it, my answer is pretty consistent. I know that I’ll go back to being frustrated, creatively unfulfilled, and longing to be like all of those people I look up to. Just reading that now scares me a bit. I really don’t want to go back to that. How can I avoid it? Don’t quit.</p><p>While I can sit here and wax poetic about not quitting, what I can’t do is speak to your circumstances. Everyone is different. Parents get sick, kids puke into your dresser, and that jerk next door can’t help but let his tacky Halloween decorations glow directly into your living room. C’est la vie. I’ve unfortunately had to deal with a lot of setbacks over the last decade. While they were far from fun — watching a grown man cry is about as fun as getting caught naked in a brush fire — what I promised myself is that I wouldn’t let these things stop me. No matter what, no matter who, I wouldn’t quit.</p><p>If you’re working on something, please take heed and stay the course. There’s no guarantee that what you’re after is on the other side of all your hard work, but that doesn’t mean the journey isn’t worth your efforts. We live in a world where it’s far easier to announce than it is to persevere. Saying “hey look at my new thing!” is fun, but eventually, you’ll look back and see nothing but a trail of false starts. The only way to avoid that is to not quit. To keep going. To push yourself beyond all reason.</p><p>Never quit. Always pursue what’s in your mind and your heart to the best of your abilities and resources. Life is far too short to not try. If you ever get scared or shit feels too heavy, <a href="/service/mailto:me@ryanglover.net">I’m always just an email away</a>. I’ve been in the trenches long enough to know that quitting sounds sublime when the world is weighing down on you. But, and I say this from a place deep in my heart: when you quit, you kill a part of that voice that brought you to where you are. That good one that made you rush home from work to put time into your project. The one that had you scribbling down ideas in a notebook in traffic. The one that will get you to all of the places you want to go if you just let it speak.</p><p>Listen close, it says “don’t quit, don’t quit.”</p><p>Enjoy this? We’d love it if you <a href="https://twitter.com/themeteorchef">followed @themeteorchef on Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce60d1ec1784" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>