Articles tagged "Software & web development"

What rocket engineering can teach us about software engineering—and work in general

Our first Zapier company retreat of 2020 was in Orlando, which meant I got to spend my free day at the Kennedy Space Center.

How to set up an automated system to confirm form submissions

Not all form submissions end up in the inbox—some are sent to the spam folder. Create an easy, automated system to save time checking submissions.

Why you should hire early-career engineers

Early-career engineers, sometimes called "L1s," will have little to no experience, but they can be a more productive addition to your team than a seasoned engineer. Here's why.

4 ways to improve collaboration between programming and QA

Here are some tips I learned along the way to help with common issues that come up between developers and QA.

The 10 Best CMS Platforms

A content management system (CMS) is web-based software that allows you to build content-oriented websites, like blogs, eCommerce websites, or portfolios. A CMS is a must-have if you're regularly adding content to your website.

The journey of secrets in Kubernetes at Zapier

Secrets management is a very important part of continuous deployment and infrastructure as code.

How Zapier helped this founder keep engineers focused on product development

In the early years of my startup my co-founder and I faced a challenge familiar to many young tech companies: Our engineering resources were spread thin, with competing priorities and an ever-changing roadmap. Automation helped us

How Zapier uses KEDA

Zapier uses KEDA (Kubernetes-based event driven autoscaler) to keep up with our message backlog and help our backend workers scale.

The architecture behind Zapier's Zap History pages

Whenever a Zapier user wants to review what Zaps have run in their account, they visit their Zap History. Built on Next.js, the architecture that supports the Zap History pages, surfaces individual information about millions of Zap runs to our users.

The CAP theorem for engineering teams

The CAP theorem informs how we build distributed systems by describing the trade-offs we must make when splitting a system into multiple distributed parts. The same holds true when splitting an engineering organization into multiple teams.