Articles tagged "Software & web development"

Shopify vs. Square: Which merchant solution is best for your business? [2023]

Shopify's expansive eCommerce features make it best for companies that operate online, while Square's POS features stand out for brick-and-mortar businesses.

What is information systems? Definition, uses, and examples

Information systems refers to the tools and strategies that organizations use to collect and manage data in order to improve their operations.

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.

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

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.

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.