hn.today

Do Repeat Yourself

arcentry.com149 points51 comments
Screenshot of Do Repeat Yourself

A fictional bank illustrates the costs of treating duplicated software and varied technology stacks as problems to eliminate. Three teams build similar customer features - filtered lists, charts, and CSV/PDF exports - but choose tools suited to their needs and deliver their products on time. A new platform leader responds by mandating Go, React, and Kubernetes, then building shared components to avoid repeated work. The uniform stack proves a poor fit: investment banking depends on Erlang for specialized, fast-moving workloads, while the credit-card team’s simpler PHP application does not benefit from a Go migration. Shared components also fail to accommodate particular needs, and requests for changes and documentation queue behind platform priorities. Teams spend the year adapting rather than shipping.

The central argument is that eliminating duplication is not the same as improving efficiency. Different requirements, expertise, and working styles can justify separate implementations; abstractions built to cover every variation tend to become cumbersome and slow teams down. Service-oriented architecture offers a different balance: teams retain autonomy inside their services while relying on shared interfaces and protocols to work together. The platform team should standardize delivery formats and REST API conventions, provide common visual styling and portal infrastructure, and maintain shared documentation - not dictate each team’s internal stack or force universal components. Some duplicated code and repeated solutions are acceptable trade-offs. The measure of efficiency is whether teams build good products, deliver on time, and collaborate without obstructing one another, not whether they minimize code or technology choices.

Read on arcentry.com51 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

Solid 2.0

Solid 2.0

Solid 2.0 is now stable, five years after version 1.0, with a smaller API and diagnostics designed for AI agents. Its reactive graph now handles asynchronous computations, while built-in server functions support RPC calls and persistent Server-Sent Events connections. (solidjs.com)

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.