212. Modelling Developer Infrastructure Teams (shopify.engineering)
213. Bridging the Gap Between Developers and End Users (shopify.engineering)
214. Understanding GraphQL for Beginners–Part Three (shopify.engineering)
215. Connecting with Mob Programming (shopify.engineering)
216. A Guide to Running an Engineering Program (shopify.engineering)
217. Perspectives on React Native from Three Shopify Developers (shopify.engineering)
218. Shopify-Made Patterns in Our Rails Apps (shopify.engineering)
219. Shopify's Path to a Faster Trino Query Execution: Infrastructure (shopify.engineering)
220. High Availability by Offloading Work Into the Background (shopify.engineering)
221. Understanding GraphQL for Beginners–Part Two (shopify.engineering)
222. Understanding GraphQL for Beginners–Part One (shopify.engineering)
223. Let’s Encrypt x Shopify: Securing the Web 4.5 Million Domains at a Time (shopify.engineering)
224. Rate Limiting GraphQL APIs by Calculating Query Complexity (shopify.engineering)
225. 10 Lessons Learned From Online Experiments (shopify.engineering)
226. Querying Strategies for GraphQL Clients (shopify.engineering)
227. Schematizing Deletion at Scale (shopify.engineering)
228. Updating Illustrations at Scale (shopify.engineering)
The Polaris team creates tools, education and documentation that helps unite teams across Shopify to build better experiences. We created Polaris, our design system, and continue to maintain it. We are a multidisciplinary team with a range of experience. Some people have been at Shopify for over 6 y...
229. Shipit! Presents: How We Write React Native Apps (shopify.engineering)
230. How Shopify Built An In-Context Analytics Experience (shopify.engineering)
231. Other Driven Developments (shopify.engineering)
Mental models within an industry, company, or even a person, change constantly. As methodologies mature, we see the long term effects our choices have wrought and can adjust accordingly. As a team or company grows, methodologies that worked well for five people may not work as well for 40 people. If...
232. Three Ways We Share Context at Shopify Engineering (shopify.engineering)
233. How I Define My Boundaries to Prevent Burnout (shopify.engineering)
There’s a way to build a model for your life and the other demands on you. It doesn’t have to be 100 hours a week. It might not even be 40 hours a week. Whatever sustainable model you come up with, prioritize fiercely and communicate expectations accordingly. I’ve worked this way for three decades t...
234. A Five-Step Guide for Conducting Exploratory Data Analysis (shopify.engineering)
235. Dynamic ProxySQL Query Rules (shopify.engineering)
ProxySQL comes with a powerful feature called query rules. The main use of these rules at Shopify is to reroute, rewrite, or reject queries matching a specified regex. However, with great power comes great responsibility. These rules are powerful and can have unexpected consequences if used incorrec...
236. Management of Native Code and React Native at Shopify (shopify.engineering)
A year ago, we announced our decision to place our bets, and our developer resources, on React Native. As you could expect, the move was met internally with a mix of excitement and apprehension, but a year later, we are still convinced that we made the right decision.
237. How Shopify Dynamically Routes Storefront Traffic (shopify.engineering)
238. Building Smarter Search Products: 3 Steps for Evaluating Search Algorithms (shopify.engineering)
239. How to Build a Web App with and without Rails Libraries (shopify.engineering)
How would we build a web application only using the standard Ruby libraries? In this article, I’ll break down the key foundational concepts of how a web application works while building one from the ground up. If we can build a web application only using Ruby libraries, why would we need web server ...
240. Remove Circular Dependencies by Using Dependency Injection and the Repository Pattern in Ruby (shopify.engineering)
There are dependencies between gems and the platforms that use them. In scenarios where the platforms have the data and the gem has the knowledge, there is a direct circular dependency between the two and both need to talk to each other. I’ll show you how we used the Repository pattern in Ruby to re...