Among the year-in-review pieces published by tech figures, Guillermo Rauch's 2019 in Review ranges widely — modern architectures, individual apps, philosophical movements. For engineering teams, the most operationally relevant thread is his argument about "deploy previews":

A salient feature is the transition we are seeing away from code review into deployment preview.

Code review is undeniably important (specially speedy code review), but nothing beats teams collaborating by sharing URLs to the actual sites that are being worked on and experiencing them directly.

What a preview URL changes

The idea is that every push to every branch — or, at minimum, every pull request — gets its own URL. That is a step beyond conventional staging environments; call it "Super Staging." Jamstack is what makes it practical, and both Netlify and ZEIT perform it automatically.

The benefit runs in two directions. The author and her co-workers can inspect changes against a production replica. In addition, a set of automation tools can run against those same URLs, which yields more stable development workflows.

One terminology note from the post: the author prefers the generic name "Pull Merge Requests", but ends up expressing that name as either just "Pull Request" or "Merge Request" based on the platform (Git via [email protected] defaults to "Pull Request" whereas GitLab uses "Merge Request"). Bitbucket also uses "Pull Requests".