Why Developers Should Learn to Love Regulation

In recent years, there has been a growing perception that developers harbor a disdain for regulation. The assumption is that it slows down the process of shipping code and is perceived as a financial burden. However, upon closer examination, it becomes clear that regulation serves as a crucial safeguard against the encroachment of automation.

To gain insight into the future of work, a comprehensive analysis was conducted of 46 computing careers using widely available data sources such as regulators, central banks, and payroll verification systems. This research sought to identify which jobs were at risk of being automated and which jobs exhibited a higher degree of resilience.

The findings revealed that the primary factor determining a job's fate was not the developer's skill level or coding prowess, but rather the number of regulatory barriers they encountered in their role.

Four key barriers to automation were identified: liability, regulation, restricted data, and the human as a liability absorber. Developers who lack at least two of these mechanisms in their workflow are more susceptible to automation, as the absence of these safeguards renders them vulnerable to replacement by AI systems.

Liability refers to the need for a named individual to assume responsibility for errors and accept the associated consequences. In situations where a mistake could result in significant fines or legal action, a designated human must be present to bear that burden. Regulation mandates that changes undergo approval before implementation, adding an extra layer of protection against rapid adoption of AI-driven solutions.

Restricted data ensures that sensitive information remains inaccessible to third-party models, preventing potential misuse or exploitation. Lastly, the human as a liability absorber underscores the importance of retaining human oversight to prevent catastrophic consequences, as algorithms can be held accountable for their actions in the eyes of the law.

Rather than focusing on the competitiveness of coding skills, developers should instead seek employment in industries that have robust compliance mechanisms. By familiarizing themselves with these regulatory frameworks, professionals can position themselves as valuable assets within organizations that prioritize safety and accountability. The regulatory moats that were once seen as hindrances are now recognized as the very factors that will safeguard jobs in an increasingly automated world.