RFCs, also called Design Documents, let us describe software designs before implementation. But how do you make sure that RFCs get deep review and are seen by the right people? How do you help reviewers catch problems in a system’s design? We’ve been iterating on our RFC review process and here’s what we’ve come up with.
At Squarespace, the Edge team manages the TLS infrastructure, which handles the life cycle of millions of SSL certificates used by our customers. This makes us one of the largest users of Let’s Encrypt, a free, automated, and open certificate authority (CA).
This is part two of a two-part series. In part one we looked at organizational culture, and how code authors can make their code easier to review. In this final part, we’ll look at some strategies for performing more thorough and empathetic code reviews.
Code review is one of the most effective tools we have as engineers to safeguard the quality of our code. In this series of posts, we describe what a strong code review culture looks like and how to create it.
“The Nuts and Bolts” is a reoccurring Q&A with Squarespace engineers. Questions are compiled by their peers to guarantee we get right to the good stuff.
At the end of 2018, we made the decision to build our own Image Editor in order to give our customers essential tools and an intuitive experience. We just released a second version, which has several new powerful, high-quality adjustments including undo/redo and a suite of custom filters that are unmistakably Squarespace. This is how we built the filters.
What if tech debt wasn’t always an accident, caused by incorrect assumptions and unexpected circumstances? How would you spend a tech debt mortgage?
Here on Squarespace’s Strategy and Analytics team, we build models that predict customer lifetime value, forecast customer service demand, and even determine how much we should spend on those ubiquitous Squarespace ads you hear on your favorite podcast.
“The Nuts and Bolts” is a reoccurring Q&A with Squarespace engineers. Questions are compiled by their peers to guarantee we get right to the good stuff.
To streamline the template selection process, we released a search bar in the template store. After releasing the template search in English with support for over 100,000 unique search terms, we needed a quick way to provide the same experience in five additional languages. This post describes how we quickly internationalized the template search along with some challenges we faced along the way.
In this blog post I’ll describe the system we built for delivering front-end translations at Squarespace. I’ll describe how translation code is written, extracted, and translated, the rationale behind some of our architectural decisions, and some of the functional and internationalization-specific lessons we learned along the way.
What I’ve learned at Squarespace is that technical aesthetics can be described precisely and that developing that vocabulary to use in conversations with colleagues about the merits of designs can lead to more beautiful systems, which carry significant practical benefits.