<?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 Matt Schmaus on Medium]]></title>
        <description><![CDATA[Stories by Matt Schmaus on Medium]]></description>
        <link>https://medium.com/@mschmaus201?source=rss-d1193df5a6ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Jj43cJfS6yykuDL6ENl82g.png</url>
            <title>Stories by Matt Schmaus on Medium</title>
            <link>https://medium.com/@mschmaus201?source=rss-d1193df5a6ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:55:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mschmaus201/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[The Battle of Ephemeral Environments, March 2019]]></title>
            <link>https://medium.com/in-the-weeds/the-battle-of-ephemeral-environments-march-2019-e73968022105?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/e73968022105</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Fri, 29 Mar 2019 21:06:03 GMT</pubDate>
            <atom:updated>2019-04-01T22:49:04.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-PopVgIdIZUZvXwo1gLlQ.png" /></figure><p><a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/259373902/">Full Stack Engineering Meetup</a> was back with another event at <a href="https://grnh.se/mra7dx">Greenhouse</a>’s office. Both speakers gave talks on their teams’ approaches to solving a problem all growing engineering departments face — the sharing of a limited number of development environments. Below are each of the speakers’ intros and talk abstracts.</p><p><a href="https://www.linkedin.com/in/julesterrien/"><strong>Jules Terrien</strong></a><strong>, Software Engineer @ </strong><a href="https://askwonder.com/"><strong>Wonder</strong></a></p><p><em>Title: Make QA Easier with Wonqa, A New Tool to Create Branch-Specific QA Environments in AWS</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/213/0*SK74-9rv1qljqy4r" /></figure><p>Jules is a software engineer at Wonder where he’s worked on the full stack from React components to NodeJS applications and infrastructure projects. Before Wonder, Jules was at Nova Credit, a fintech startup based in San Francisco and prior to becoming a software engineer, Jules helped start a couple startups in and outside of tech.</p><p><em>Talk Abstract</em>: Wonqa is an open source library released by the Wonder team last year to help teams easily create QA environments. Prior to writing and using Wonqa, the Wonder team operated with a single QA environment which caused a number of problems as engineers had to synchronize deploys to avoid conflicts and allow product teams to QA accurately. With Wonqa, Wonder engineers can create QA environments per branch, hosted on custom domains, at the click of a button. Wonqa uses a number of awesome tools to make this possible including AWS, Docker and DNSimple/Certbot.</p><p>Check out Jules’ presentation <a href="https://drive.google.com/file/d/171MSMpbB0jqp22qWCgFYB1rS7mHcjnOe/view">here</a>!</p><p><a href="https://www.linkedin.com/in/pclalv/"><strong>Paul Alvarez</strong></a><strong>, Software Engineer @ </strong><a href="https://grnh.se/mra7dx"><strong>Greenhouse</strong></a></p><p><em>Title: Ephemeral Dev Environments at Greenhouse with Dajoku</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*gGENXpTKWXQSKjE0" /></figure><p>Paul Alvarez is a developer of internal tools and services at Greenhouse. He didn’t coin the name “Dajoku” but he likes it very much. He enjoys playing guitar and bass in progressive rock bands.</p><p><em>Talk Abstract</em>: This talk will cover Greenhouse’s solution to a problem all growing engineering teams face at some point. You’ve got an increasing number of developers simultaneously working on more and more branches of code, with a QA team to match. But what happens when the number of available environments stays constant? Enter Dajoku. With the ability to scale up and down pre-seeded environments within minutes, Slack messages like “@channel any of the dev1-dev9 envs free?” are no longer required to get code changes in front of others.</p><p>Check out Paul’s talk <a href="https://drive.google.com/file/d/1ZqVpytgaqOgr4YafW48TiSlcoxaKwrhD/view">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e73968022105" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/the-battle-of-ephemeral-environments-march-2019-e73968022105">The Battle of Ephemeral Environments, March 2019</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Magic with GraphQL — FSE Meetup, Nov ‘18]]></title>
            <link>https://medium.com/in-the-weeds/stack-magic-with-graphql-fse-meetup-nov-18-c7e03a1c459b?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7e03a1c459b</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 19:45:59 GMT</pubDate>
            <atom:updated>2018-11-30T19:45:59.983Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stack Magic with GraphQL — FSE Meetup, Nov ‘18</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WVgJq_tAmXOy33h6HLi20Q.jpeg" /></figure><p>This month the <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/">Full Stack Engineering Meetup</a> group hosted the inaugural event at <a href="https://grnh.se/mra7dx">Greenhouse</a>’s new offices — <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/255870238/">Stack Magic with GraphQL</a>! Both of our speakers presented their work with GraphQL. Here are speaker intros and quick abstracts they provided for their presentations…</p><p><a href="https://www.linkedin.com/in/drewbrien"><strong>Drew Brien</strong></a><strong>, Senior Software Engineer @ </strong><a href="https://grnh.se/mra7dx"><strong>Greenhouse</strong></a></p><p><em>Title: Resource Limitations in GraphQL: Trials and Tribulations</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/175/0*lVOpKt-j0gRkcpEO" /></figure><p>Drew is a Senior Software Engineer working on APIs at Greenhouse Software. A Boston native, Drew moved to NYC about 7 years back and has been working in software since. He enjoys snowboarding and watching Boston sports teams collect trophies.</p><p><em>Talk Abstract</em>: Drew will be discussing the concept of resource limitations in GraphQL APIs. While building the GraphQL API for Greenhouse’s Onboarding product, the Engineering team had to find a solution to the following problem: how do you prevent consumers from overwhelming the API infrastructure? While most REST APIs solve this issue by implementing a standard rate-limiting algorithm, this approach isn’t sufficient to protect GraphQL APIs. We will chat about how REST and GraphQL APIs differ in this regard, and we will compare a few solutions that we considered.</p><p><a href="https://www.linkedin.com/in/tanmaig/"><strong>Tanmai Gopal</strong></a><strong>, Co-Founder @ </strong><a href="https://hasura.io/"><strong>Hasura</strong></a></p><p><em>Title: Architecture of scalable and resilient NodeJS apps with GraphQL &amp; event-driven serverless</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*H0raHgPFzsxpN8Xy" /></figure><p>Tanmai is the co-founder of hasura.io. He is a polyglot developer whose areas of interest and work span React, GraphQL, NodeJS, Python, Haskell, Docker, Postgres, and Kubernetes. He is passionate about making it easy to build things and is the instructor of India’s largest MOOC, imad.tech, with over 250,000 students.</p><p><em>Talk Abstract</em>: The talk will cover how state of the application can be architected to be stored in the database itself and how updates to state can be used to build reactive user interfaces which update in real-time, with GraphQL Subscriptions and live-queries. We will then look at how serverless functions can be used to execute business logic and how these functions can be triggered on database events, which are updates to this state. In short it will cover the different architecture patterns, open-source tools used, code-samples, observed benefits, pros/cons, and how this pattern fits into the larger GraphQL and serverless revolution that we are undergoing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7e03a1c459b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/stack-magic-with-graphql-fse-meetup-nov-18-c7e03a1c459b">Stack Magic with GraphQL — FSE Meetup, Nov ‘18</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Redirects To Medium]]></title>
            <link>https://medium.com/in-the-weeds/aws-redirects-to-medium-74c844a89cd3?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/74c844a89cd3</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[greenhouse]]></category>
            <category><![CDATA[cloudfront]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 17:18:04 GMT</pubDate>
            <atom:updated>2018-08-06T17:18:57.134Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*zrOGSuRz43TpyeoWWvj49Q.png" /></figure><p>Ok, this blog post is a little meta. It’s a post about the history of Greenhouse’s blog — and some technical things too.</p><h4>Blogging: The Initiation</h4><p>In late 2015, a few engineers on the <a href="https://grnh.se/mra7dx">Greenhouse</a> engineering team pointed out that we’d been working on some interesting technical problems, but no one outside of our offices knew about them. Enter the Greenhouse engineering team’s first blog posts — a <a href="https://help.github.com/articles/using-jekyll-as-a-static-site-generator-with-github-pages/">Jekyll-powered</a>, static site. These posts were added to an AWS bucket and hosted at <a href="https://tech.greenhouse.io/">tech.greenhouse.io</a>. Each blog post was ultimately just an markdown file stored as an AWS object.</p><p>The writing of these blog posts continued for about a year. But after our team went through a substantial growth spurt, blogging fell by the wayside in favor of building more features, tackling technical-debt, and building out better processes for the growing team.</p><h4>Blogging: Redux</h4><p>Last summer, as I took over as organizer for the <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/">Full Stack Engineering Meetup</a> group and helped kick off our engineering team’s external branding initiative, I started to encourage more engineers to resume writing blog posts. This time though, I saw value in hosting them on our own Medium publication — <a href="https://medium.com/in-the-weeds">In The Weeds</a>. I saw both the Meetup group and a Medium publication as great mediums (no pun intended) to showcase the talent we have and technical problems we’re tackling here at Greenhouse.</p><p>A future post will cover the steps I took to reestablish a successful blogging culture. But for the context of this post, all you have to know is that a year later, we’re going strong and averaging a post every other week!</p><h3>Deploying the Blog</h3><p>For discoverability, design, and minimal maintenance purposes, we decided to start posting everything on <a href="https://medium.com/in-the-weeds">In The Weeds</a>. It made the process more straightforward and allowed our employees to begin building their own personal brands alongside Greenhouse’s. But we still had thirteen posts at the old <a href="https://tech.greenhouse.io/">tech.greenhouse.io</a> — hence my looking into redirecting requests from that AWS bucket to Medium.</p><h4>Old Blog Implementation</h4><p>Our old Jekyll-powered blog was set up to be hosted as an AWS bucket behind CloudFront. Authors would write their posts as markdown files and commit them to a GitHub repo. When someone would write a new post, they’d create a pull request against master and submit their new markdown file for “code” review. For each push up to GitHub, <a href="https://www.solanolabs.com/">Solano</a> (our CI service) would build the blog using Jekyll — and if successful would then run a deploy script. That script would check to see if the current branch was master , and if so, would write things to the AWS bucket. Once written to the bucket, all the markdown files in the _posts directory would be publicly visible on <a href="https://tech.greenhouse.io/">tech.greenhouse.io</a>. Here’s a portion of the script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PNa3BNKXSc8RZwwdnVssbQ.png" /></figure><h4>AWS Redirects</h4><p>With a number of our blog posts reaching reads in the tens of thousands, and significant SEO rankings we’d like to maintain, we couldn’t just copy/paste the blog post content and re-post to Medium. Well, we could — and we did, but there was more to it in order to maintain high ranking in search results.</p><p>We wanted all requests to the <a href="https://tech.greenhouse.io/">tech.greenhouse.io</a> posts to redirect to their corresponding copies on Medium. In order to do so, we had to call the put-object command on each post. Working off of Amazon’s <a href="https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html">PUT Object documentation</a>, I added the below code to the deploy script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nl9cdlKYJd2Y7p7NIvRkKg.png" /></figure><p><em>Of course, things never work the first time.</em> In order to test this, I curl&#39;d the above blog post, only to receive a 200 response. I was really hoping for a 301 redirect. Here’s the response…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzQkNeO-3XH4bcSF6dWQ4A.png" /></figure><h4>AWS Bucket Website Hosting</h4><p>Interestingly, you can see the redirect header Amazon documented I should see — x-amz-website-redirect-location is being set to the Medium URL I’d expect. But the request just wasn’t redirecting.</p><p>Rereading Amazon’s <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html">documentation</a> for configuring a webpage redirect, I notice a clue in, well, the first sentence. “<em>If your Amazon S3 bucket is configured for website hosting, you can redirect requests for an object to another object in the same bucket or to an external URL.</em>” I should have probably confirmed that the bucket was configured for website hosting, because it wasn’t! With a little help from the Infra team, we got this rectified.</p><p><em>Of course, things never work the second time.</em> When curl’ing, I was still seeing the same results. With a little more Googling, I came across another <a href="https://medium.com/cloud-io/put-redirect-301-in-s3-cloudfront-hosted-website-39bd9104ddbc">Medium post</a> and some <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-cloudfront-walkthrough.html">CloudFront documentation</a> which provided the final solution. We needed to update our CloudFront settings for this bucket to use the proper origin. Once properly set, a curl finally produced the 301 we wanted!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2WOLlBMa6oc34lqZbyHzg.png" /></figure><h3>Come Work with Us</h3><p>We’re hiring!</p><p>If you’re interested in learning more about <a href="https://grnh.se/mra7dx">Greenhouse</a> and some of the technical problems we’re currently working on, check out our Medium publication, <a href="https://medium.com/in-the-weeds">In The Weeds</a>. And if you’re interested in working with us, check out our <a href="https://grnh.se/mra7dx">open roles</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74c844a89cd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/aws-redirects-to-medium-74c844a89cd3">AWS Redirects To Medium</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Text Stack 2.0 — FSE Meetup, Jul ‘18]]></title>
            <link>https://medium.com/in-the-weeds/text-stack-2-0-fse-meetup-jul-18-c69b85a778cd?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/c69b85a778cd</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[meetup]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 22:16:37 GMT</pubDate>
            <atom:updated>2018-08-03T22:21:45.464Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aeKFf3gv_QVp_tnJC0BEXA.jpeg" /></figure><p>Last week the <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/">Full Stack Engineering Meetup</a> group hosted another event, <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/252518202/">Text Stack 2.0</a>, at <a href="https://grnh.se/mra7dx">Greenhouse’s NYC office</a>. Each of our presenters discussed their implementations of browser-based text editors. Below are the speaker intros and quick abstracts they provided for their talks…</p><p><a href="https://www.linkedin.com/in/sjbeatteay/"><strong>Sun-Li Beatteay</strong></a><strong>, Software Engineer @ </strong><a href="https://www.digitalocean.com/"><strong>DigitalOcean</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*u3G10HU8No5Ysp-2MNOiRQ.jpeg" /></figure><p>Sun-Li is a software engineer working at DigitalOcean on their Spaces product. He’s a recent transplant, having moved to NYC only a year ago from Seattle. He’s also an active writer on Medium where he <a href="https://medium.com/@SunnyB">posts tutorials and articles</a> about technology.</p><p><em>Talk Abstract</em>: Sun-Li will be talking about his experience building a decentralized collaborative text editor, Conclave, on a remote team. This talk will focus on the challenges that the Conclave team faced and their solutions. These topics include how to create a decentralized application using modern browser technology, maintain consistency in a distributed architecture, and cheaply scale a real-time application to handle many concurrent users. For anyone interested in dApps, distributed systems or fun open source projects, you won’t want to miss this presentation.</p><p>Check out Sun-Li’s talk <a href="https://drive.google.com/file/d/1xmP2dV0vVoUzozCGmEFqto0ELNM86dMj/view?usp=sharing">here</a>!</p><p><a href="https://www.linkedin.com/in/kareemamin/"><strong>Kareem Amin</strong></a><strong>, Co-Founder @ </strong><a href="https://base.run/"><strong>Clay</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/373/1*rA98vFUTXFE9xerUp4DIcg.jpeg" /></figure><p>Kareem is a co-founder of Clay, a rapid development platform that allows you to automatically pull data from the web and the SaaS services you use into a spreadsheet-like UI so you can quickly build flexible tools that automate your work. He’s previously led product and development teams at Microsoft, Sailthru, and News Corp/WSJ.</p><p><em>Talk Abstract</em>: We’ll walkthrough how to simulate AWS lambda using Docker containers to run user submitted code that is written in an IDE in the browser. We’ll motivate this discussion with the challenges of developing Lambda functions today and discuss what the future of software development looks like with serverless technology.</p><p>Check out Kareem’s presentation <a href="https://drive.google.com/file/d/1SZvSwQlWopAmS8i3qn2sdPQB5pLyfWvx/view">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c69b85a778cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/text-stack-2-0-fse-meetup-jul-18-c69b85a778cd">Text Stack 2.0 — FSE Meetup, Jul ‘18</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Wars: The Slack Awakens Recap — FSE Meetup, Apr ‘18]]></title>
            <link>https://medium.com/in-the-weeds/stack-wars-the-slack-awakens-recap-fse-meetup-apr-18-8d3db75e89bb?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d3db75e89bb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Fri, 20 Apr 2018 17:49:00 GMT</pubDate>
            <atom:updated>2018-04-25T02:11:53.981Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jI6Wc-erNIgFLRw-AUhBig.png" /></figure><p>We hosted <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/248099784/">Stack Wars: The Slack Awakens</a>, another <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup">Full Stack Engineering Meetup</a> at <a href="https://www.greenhouse.io/">Greenhouse’s</a> office, on Apr 12th. Our presenters each discussed projects they’ve built on top of the Slack platform. First up, Scott Underwood gave us a live demo of Troops’ CI solution which enables his team to deploy code from within Slack. Following him, Andrej also demoed his Slack chatbot which learns Slack channels’ discussion topics, notifies users when they post something off-topic, and recommends the relevant channel.</p><p>Below are the speaker intros and quick abstracts they provided for their talks…</p><p><a href="https://www.linkedin.com/in/scottlunderwood/"><strong>Scott Underwood</strong></a><strong>, Engineer @ </strong><a href="https://troops.ai/"><strong>Troops.ai</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*OxbIWoRICVBuyYxyTqhYiA.jpeg" /></figure><p>Scott Underwood is an engineering leader at Troops.ai, an NYC startup building artificial intelligence and workflow automation for Sales and Customer Success teams. Scott has over 8 years of experience in JVM based languages and has led engineering teams in ad-tech, modeling &amp; simulation, and computer vision.</p><p>Talk Abstract: Scott will walk through the challenges a growing engineering team faces to set up a scalable continuous integration solution, and how this so often leads to a Rube Goldberg CI pipeline. We will explore how Troops used chat ops to simplify its CI process, increase engineering transparency, and alleviate many headaches born out of managing and scaling multiple CI subsystems.</p><p>Check out Scott’s talk <a href="https://drive.google.com/file/d/1m4lHtaom0NsY1h3HL-nNpR1Sm7UQRo2S/view">here</a>!</p><p><a href="https://www.linkedin.com/in/aficnar/"><strong>Andrej Ficnar</strong></a><strong>, Data Scientist @ </strong><a href="https://www.schireson.com/"><strong>Schireson</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*0R1zQLjidZNNJnLTlfBKgg.jpeg" /></figure><p>Andrej is a data scientist at Schireson Associates, a strategic data science consulting firm focusing on media and advertising. There, he employs various modeling approaches to build custom data solutions for clients, and manages current data products. Previously, Andrej worked at Columbia and Oxford as a theoretical physicist with a focus on applied string theory.</p><p>Talk Abstract: Andrej will talk about building a <a href="https://aficnar.github.io/slackpolice/">smart bot for Slack</a> that learns each channel’s topic and warns users if they go off topic. The bot relies on an implementation of a new NLP method introduced at NIPS 2015, called Word Mover’s Distance. We’ll discuss the brains behind such a bot, some practical challenges in building it, and also see a live demo of the bot in action.</p><p>Check out Andrej’s presentation <a href="https://drive.google.com/file/d/1ybCcrLqQiT2Opgc8B5husPYXlkWAYrIr/view">here</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d3db75e89bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/stack-wars-the-slack-awakens-recap-fse-meetup-apr-18-8d3db75e89bb">Stack Wars: The Slack Awakens Recap — FSE Meetup, Apr ‘18</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stacky McStackface Recap — FSE Meetup, Feb ‘18]]></title>
            <link>https://medium.com/in-the-weeds/stacky-mcstackface-recap-fse-meetup-feb-18-e78c12a3f1ec?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/e78c12a3f1ec</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 16:22:55 GMT</pubDate>
            <atom:updated>2018-03-09T16:22:55.373Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kN8HeiTXnUvCy29mou7FMQ.png" /></figure><p>We’re back at it in 2018! We hosted <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/246645771/">Stacky McStackface</a>, another <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup">Full Stack Engineering Meetup</a> at <a href="https://www.greenhouse.io/">Greenhouse’s</a> office, on Feb 20th. Our presenters each discussed their work in the realm of data analytics. First, Greg Ratner guided the audience through building up a data analytics pipeline. Next, Thibault Sellam dove into his project which analyzes database query logs in order to automatically generate interactive data exploration interfaces.</p><p>Below are the speaker intros and quick abstracts they provided for their talks…</p><p><a href="https://www.linkedin.com/in/gratner/"><strong>Greg Ratner</strong></a><strong>, Co-Founder &amp; CTO @ </strong><a href="https://troops.ai/"><strong>Troops.ai</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*tOYYOF3PI9DfTgZzg2Wqjw.jpeg" /></figure><p>Greg Ratner is co-founder and CTO of Troops.ai, an NYC startup building artificial intelligence and workflow automation for Sales and Customer Success teams. Greg is a serial entrepreneur with passion for functional programming who has over 15 years of experience building and leading teams and scaling distributed software systems.</p><p>Talk Abstract: Greg will share a practical guide on how to build a full data engineering stack from the ground up for a growing startup. We will talk about the challenges of setting up business intelligence and data engineering solutions rapidly and discuss 3rd party tools available to simplify this process. At the end of this talk you will be armed with a blueprint to allow data-centric decision making in your organization and empower your business users with data.</p><p>Check out Greg’s presentation <a href="https://drive.google.com/open?id=1sZWGxOwaTPxxLNmPj15PjCEfEGGAXUSZ">here</a>!</p><p><a href="http://sellam.me/"><strong>Thibault Sellam</strong></a><strong>, Data Science Researcher @ </strong><a href="http://datascience.columbia.edu/"><strong>Columbia University</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CEi7qi3O80LOfaM0XNToGg.jpeg" /></figure><p>Thibault Sellam is a postdoctoral scientist at Columbia, working on data exploration, human-in-the-loop machine learning and more generally anything that involves data management, AI and people. Previously, Thibault was a PhD student at the University of Amsterdam (the Netherlands) where he studied data mining, and he took several breaks to work in the industry (Microsoft Research, JPMorgan) and tour with a French pop band.</p><p>Talk Abstract: Interactive tools make data analysis both more efficient and more accessible. Yet, designing interactive interfaces requires technical expertise and domain knowledge. Experts are scarce and expensive, and therefore it is currently infeasible to provide tailored (or precise) interfaces for every user and every task. In this talk, I will present a data-driven approach to generate tailored interactive interfaces. I will introduce Precision Interfaces, a system that examines an input query log, identifies how the queries change, and generates interactive web interfaces to express the changes.</p><p>Check out Thibault’s presentation <a href="https://drive.google.com/open?id=1_gcKJqbFHv4g4q-0VpcWgTDd5zJJgvh_">here</a>!</p><p>Thank you to everyone who joined us and participated in such engaging conversations! Look out for our next event in April covering Slack chatbot integrations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e78c12a3f1ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/stacky-mcstackface-recap-fse-meetup-feb-18-e78c12a3f1ec">Stacky McStackface Recap — FSE Meetup, Feb ‘18</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Handling URL-Encoded S3 File Names]]></title>
            <link>https://medium.com/in-the-weeds/handling-url-encoded-s3-file-names-6fa54ea35f55?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa54ea35f55</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[url-encoding]]></category>
            <category><![CDATA[sidekiq]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Wed, 20 Dec 2017 17:23:19 GMT</pubDate>
            <atom:updated>2017-12-20T17:23:19.992Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been working on Greenhouse’s Onboarding application for about a year and a half now. One of the more recent features I’ve developed was adding the ability to export tasks to a CSV. Given that this could reach tens of thousands of tasks for larger customers, my first approach didn’t work — I couldn’t fetch the data server-side, stream it to the client, and build the CSV file using JavaScript.</p><h3>The Feature Implementation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*AHbuNvI8V9OZlNY5CgVC4g.png" /></figure><p>Instead, I implemented the feature such that when a user clicks the “Export” button, the request kicks off a background job (using Sidekiq Batches) and returns the Batch ID to the client. The client then polls the server every second with this ID in order to get a status update — a boolean completion status and a list of any errors, if any.</p><p>Assuming there are no errors when the batch completes, the server uploads the file to S3 and then stores a temporary URL in Redis. Once the client learns that the file building and uploading is complete, it can use the Batch ID to retrieve the S3 URL from Redis. And with that URL, it’s just a matter of adding a download button to the DOM for the user to click. Easy.</p><p>Well…</p><h3>The Problem</h3><p>That’s where I ran into the problem. When generating this CSV, I’d set the file name to something like Tasks Export 2017-11-05 06_10 PM.csv. When clicking the download button though, I’d see a file named Tasks+Export+%282017–11–05+06%3A10+PM%29.csv. Not the most user-friendly experience…</p><p>I was naming the file properly, so why was this happening? Turns out that our wrapper around the AWS SDK automatically URL-encodes the key used for writing a file to S3. This is considered a best practice and is <a href="http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html">encouraged by AWS</a> (see the “<em>Characters That Might Require Special Handling</em>” section). There are certain characters that are valid and supported by most operating systems’ file services, but AWS requires them to be URL-encoded.</p><p>My first thought to deal with this hurdle was to use JavaScript to trigger the download and set the file name, but that just seemed like it would be too much work to support across all supported browsers. There had to be something more straightforward.</p><p>Then I decided to rely on the download attribute on anchor tags. Adding a value for that element attribute allows you to set the file name upon download — except when it doesn’t. There are a few exceptions to this rule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4ETebf8Oy7hkxcDnP8wmw.png" /><figcaption><a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a">Source</a></figcaption></figure><p>This attribute only works for same-origin URLs.</p><p>Given that the export files were stored in S3, regardless of what I put for the download value, it would be ignored. Internet safety for the win! One potential workaround I considered was to make a call to the server, allow the server to fetch the document from S3, and then respond to the client with it. But rather than adding even more server code, I found a one-line fix!</p><h3>The Solution</h3><pre>If the HTTP header Content-Disposition: gives a different filename than this attribute, the HTTP header takes priority over this attribute.</pre><p>With Onboarding’s use of the AWS SDK, writing a file to S3 uses the <a href="https://docs.aws.amazon.com/sdkforruby/api/Aws/S3/Client.html#put_object-instance_method">#put_object</a> method under the hood. Adding some more logging, here’s what I saw being passed in…</p><pre>put_object(<br>  :bucket_name=&gt;&quot;gho-dev-bucket&quot;,<br>  :content_length=&gt;243141,<br>  :data=&gt;TempfileObject,<br>  :key=&gt;&quot;stash/random/Tasks+Export+%282017–11–05+06%3A10+PM%29.csv&quot;,<br>)</pre><p>With no value for content-disposition in the header, the file’s name was being set by the argument key’s value. Luckily, #put_object accepts content_disposition as an argument! All I needed was to pass it the below line and, upon download, the file’s name would no longer being URL-encoded.</p><p>:content_disposition=&gt;“attachment; filename=\”#{filename}\””</p><h3>The Code</h3><p>Here’s what the relevant code looks like…</p><pre><strong>def </strong>stash_file(<em>file</em>, <em>filename</em>, <em>options</em>={})<br>  s3_options = <em>options.merge({<br>    key: &quot;stash/#{secure_random_key}/#{CGI.escape(filename)}&quot;,<br>    c</em>ontent_disposition: <strong>&quot;attachment; filename=</strong>\&quot;#{filename}\&quot;<strong>&quot;</strong>,<br>  <em>}</em>)</pre><pre>s3_object.write(file, s3_options)<br>  file_url = s3_object.url_for(:read, s3_options)</pre><pre>  $redis.<em>set</em>(redis_key, { url: file_url }.to_json)<br><strong>end</strong></pre><p>Accepting a Tempfile object, the file name, and options to be passed to #put_object, #stash_file will upload a file to S3 and store the S3 URL in Redis. S3Object#write calls #put_object under the hood.</p><p>Hope this has been helpful!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa54ea35f55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/handling-url-encoded-s3-file-names-6fa54ea35f55">Handling URL-Encoded S3 File Names</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stacksgiving Recap — FSE Meetup, Nov ‘17]]></title>
            <link>https://medium.com/in-the-weeds/stacksgiving-recap-fse-meetup-nov-17-eec57adde757?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/eec57adde757</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[timeseries]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[giphy]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Tue, 28 Nov 2017 23:32:55 GMT</pubDate>
            <atom:updated>2017-11-28T23:32:55.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlyXcKQ-TkBF0rE-9HSKSw.png" /></figure><p>Another month, another Full Stack Engineering Meetup! On Nov 15th we hosted an event back at <a href="https://www.greenhouse.io/">Greenhouse’s</a> offices. We had two themes to the night — time-series data and Thanksgiving food. Thanksgiving is my favorite holiday, so I use any excuse to get the cranberry sauce flowing, side dishes plenty, and of course the mac and cheese…stacked.</p><p>Both of our speakers spent the evening discussing their work in dealing with time-series data. Here’s a quick recap of <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/244719717/">Stacksgiving</a>…</p><p><a href="https://www.linkedin.com/in/fiona-condon-92327211/"><strong>Fiona Condon</strong></a><strong>, Search Engineer @ </strong><a href="https://giphy.com/"><strong>GIPHY</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*UGIwPPx9njL-5wN14P7LxA.png" /><figcaption>Fiona Condon</figcaption></figure><p>For those who haven’t used the internet in the past few years, GIPHY is one of the go-to sites for animated gifs. They serve 2.5 billion gifs every day to 300 million daily active users. They have a ton of time-series data and are able to support this traffic with an engineering team of only 25!</p><p>Fiona gave her talk “<a href="https://docs.google.com/presentation/d/1AjcT3IV6F90xvLkoPATqbWjpB2M1rpcxdvdQIE-xJUU">Unfussy User Analytics at GIPHY</a>”, covering her work in user and gif analytics, charting view counts over different intervals of time, and being able to display aggregate data. She gave a wonderful, holistic overview of the project’s technical and business requirements, dove into implementation details, covered collaboration techniques, and reviewed lessons learned from things that did and did not go well. Oh, and gif is pronounced with a hard “g” — we were told that GIPHY is pretty adamant about that. FYI.</p><p>Check out her slides <a href="https://docs.google.com/presentation/d/1AjcT3IV6F90xvLkoPATqbWjpB2M1rpcxdvdQIE-xJUU/">here</a> to learn more!</p><p><a href="https://www.linkedin.com/in/matvey-arye-70a270b5/"><strong>Mat Arye, PhD</strong></a><strong>, , Software Developer @ </strong><a href="https://www.timescale.com/"><strong>TimescaleDB</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*-hX3btZWZIpNaWEUgM6ldw.png" /><figcaption>Dr. Mat Arye</figcaption></figure><p>Mat delivered an incredibly comprehensive talk on his work with TimescaleDB — a extension to PostgreSQL. TimescaleDB is an open-source project and can be found <a href="https://github.com/timescale/timescaledb">here</a>.</p><p>Mat challenged the perception that there’s a tradeoff between query power and scale with relational databases. As he noted, most developers start with something like PostgreSQL and once their data hits a certain scale, transition to a NoSQL solution. TimescaleDB’s CTO, Mike Freedman, mentioned in his <a href="https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational-database-instead-of-nosql-d0cd6975e87c">blog post</a>, developers handling time-series data use NoSQL over a relational database at a rate of 2:1.</p><p>Mat explained that TimescaleDB fully supports SQL and is able to scale past 500 billion rows on a single node. I could dive more into his talk and overview of performance metrics, but would do it absolutely no justice. I definitely recommend checking out his slides <a href="https://drive.google.com/file/d/1Cpti3OqlN63rByjyNfCwy1cVucwA8x4L">here</a>!</p><p>Thanks to all those who came, and I hope this was helpful for those who weren’t able to make it! We’ll be taking December off and will pick things back up in 2018! Happy Thanksgiving and happy holidays!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eec57adde757" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/stacksgiving-recap-fse-meetup-nov-17-eec57adde757">Stacksgiving Recap — FSE Meetup, Nov ‘17</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FrankenStack Recap — FSE Meetup, Oct ‘17]]></title>
            <link>https://medium.com/in-the-weeds/frankenstack-recap-fse-meetup-oct-17-71c48a63e90?source=rss-d1193df5a6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/71c48a63e90</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Matt Schmaus]]></dc:creator>
            <pubDate>Wed, 01 Nov 2017 15:38:35 GMT</pubDate>
            <atom:updated>2017-11-01T15:38:35.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXGs8cujKyM9hV8HLyiKEg.jpeg" /></figure><p>A few months ago, I became a co-organizer of the <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/">Full Stack Engineering Meetup</a>, a growing community of 3200 engineers and technology enthusiasts. The group has always been run and sponsored by <a href="https://www.greenhouse.io/">Greenhouse</a>. It started back in November 2013 in the co-working space we used to occupy. Now we host many of the Meetups in our office near Union Square, and we also take the show on the road. This month’s event was hosted at <a href="https://www.usebutton.com/">Button</a>.</p><p>Here’s a quick recap of this month’s event — <a href="https://www.meetup.com/Full-Stack-Engineering-Meetup/events/243524826/">FrankenStack</a>…</p><p><strong>Antoine Leclercq on </strong><a href="https://workerholic.github.io/"><strong>Workerholic</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/1*iiPSHNy2psvO3AjcCGypkQ.jpeg" /></figure><p>Antoine Leclercq discussed his work on a background job processor he built in Ruby — Workerholic (I love the name). It’s open source, so go check it out and contribute! He took a deep dive into his approach, how it handles different types of jobs, and how it benchmarks against the industry standard Sidekiq. Hint: it’s faster! One of the more recent features I was working on for <a href="https://www.greenhouse.io/onboarding">Greenhouse Onboarding</a> involved introducing Sidekiq into our application, so it was pretty interesting to get a deep dive into the inner-workings of a background job processor. The biggest lesson I learned was the massive processing improvement by serializing data using JSON rather than YAML. Antoine noticed this in his benchmarking, made the switch from YAML, and saw a 55% improvement in processing time.</p><p><strong>Jimmy McGill on </strong><a href="https://www.terraform.io/"><strong>Terraform</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*Xq-fDNfFnzEMloMNmg2v7A.jpeg" /></figure><p>Jimmy McGill, Button’s VP of Engineering, gave a fascinating and entertaining talk on his team’s use of Terraform. Here’s a <a href="https://drive.google.com/file/d/0BxrAeBfc8LVNTTNhTElBRmFFWkU/view">link to his slides</a>. First thing I learned? Jimmy is hilarious (and I just want to listen to more of his talks). Beyond that — the high level differences between procedural versus declarative code to manage infrastructure. In short, procedural code is a bunch of shell scripts that are run on boxes that you SSH into. Declarative code on the other hand let’s you describe what you want your infrastructure to be at the end of the process.</p><p>One of the main issues with procedural code for building infrastructure is that it’s not much smarter than a shell script. If you forget an if statement somewhere, you can end up with duplicate infrastructure and begin monitoring the wrong system. Procedural code can be idempotent, but there’s no guarantee — it’s up to the developer to make sure of this. And, you know, developers maybe sometimes possibly make mistakes?</p><p>Terraform helps solve this problem. Because you’re describing what you want the end result to be, running create all the things a million times will only create that thing once. Another awesome feature is terraform plan. Let’s say you make changes to your Terraform code. Running terraform plan will show you the difference between what is currently in production, and what would be modified if you deployed your changes.</p><p>Hope this has been helpful for those that weren’t able to make it! Look out for next month’s event — Stacksgiving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71c48a63e90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/in-the-weeds/frankenstack-recap-fse-meetup-oct-17-71c48a63e90">FrankenStack Recap — FSE Meetup, Oct ‘17</a> was originally published in <a href="https://medium.com/in-the-weeds">In the weeds</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>