Why Automation and CI/CD Matter for Developer Happiness

DevOps principles, especially CI/CD, are presented as ways to run software development organizations more efficiently, and the author believes that CI/CD makes developers happier.

While many resources highlight practical benefits such as fewer bugs and faster releases, the focus here shifts to how automation improves the developer experience, reducing the frustration of manually pulling code and restarting services.

Good engineers aim to automate boring tasks, because repetitive manual work leads to dissatisfaction and turnover; developers often quit bad experiences rather than bad jobs.

The author shares personal preferences: disliking manual deployment, enjoying merging pull requests, and preferring to see tests pass, illustrated with the command go test.

An equation often used to decide automation,

should_automate = time_to_automate < time_for_task * num_tasks

, is criticized as too practical, ignoring the emotional benefit of writing automation scripts, which many find more enjoyable than repetitive manual work.

Automation can turn a potentially tedious task into a more pleasant activity, saving time and making bug fixes almost as easy as code changes, whereas without automation, simple deployments can become painful and time‑consuming.

The author concludes that while not everything should be automated, a bias toward automation stems from human nature: it makes work more enjoyable, keeps motivation high, and ultimately improves effectiveness.