"Duplication is far cheaper than the wrong abstraction" - Sandi Metz[0]
[0] https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
Or as the go proverb goes "a little copying is better than a little dependency" (https://go-proverbs.github.io/)
We are exactly where the hypothetical bank is. Our large outer company gobbled up nine or ten smaller companies with disparate stacks (PHP, Haskell, C#, a few others). After a couple years of integrating through shared APIs, new management is trying to force us all into a single platform - Go and Node+React.
We have thousands of years of combined experience in our various technologies and we are to throw that away in the name of "unity" for a stack literally no one in the company was using but "it should be good for AI"
A bigger part of the positives of repeating yourself is that yourself is plural in this case and other people kind of suck and solving your own problems should be easy.
As an example, I put in a request with the platform team to set the UI toolkit to internal instead of private so it can be more easily accessed cross organization. I have been waiting like six months. No one knew who was in charge of it. ALL our repos have been mandated internal for years so our disparate orgs can read each others code. AFAIK we're the only team that actually lives up to it.
I am annoyed by the lot of it.
I was with them right up until the admonition against standardizing the UI components. This is not an all-or-nothing proposition. You build a standardized library incrementally, and you slowly migrate codebases over to use them. I've seen some pretty horrendous UI mish-mash in what should appear to be a single application, because each piece was done independently and then stitched together.
You end up with drifting implementations that may or may not come from the same root at different points, where the same fix has to be applied multiple times as each team learns the lessons for what not to do, etc. Effectively what DRY is about.
reminds me of WET: Write Everything Twice. Instead of immediately jumping to DRY, actually write out the two similar tools, then see what actually makes sense to combine into a shared dependency.
I've always found DRY to be more useful when applied to data rather than code. Eg don't have two versions of an enum, or a mapping, or the information in some database.
What I'm missing here, is the security aspect. The author does mention that "there are capabilities, such as DevOps, that are best handled centrally", but I'd expect Mike the VP to put security in the platform team's responsibility, as well as in each team.
The sentiment is somewhat understandable, especially in the world of fast-moving AI-enabled companies all around us. The example doesn't really sound motivating out of the gate.
> All three teams adhered to the corporate branding guidelines, so their products look and feel reasonably similar. They also work fairly well and were shipped on time. This is the opposite of how things play out in most of the world's large companies, from any major bank to supposedly tech-savvy giants like Google. Every time you cross an app boundary or even a team boundary within a single product, all bets are off. At best, the UI differs in small, annoying ways (button styling, UI element rounding radii), or at worst, you need to go through separate login and payment flows.
> whenever the user switches from the account view to the investing tab, a whole new JS framework is loaded. But, given all other factors, this is an acceptable trade-off. I guess it's acceptable if you are going from one major product to another, but accepting this when switching between parts of an application that are supposed to be coherent (same banking app, same money involved) tells the customer that you don't care about their experience that much. Accepting this also massively increases the chances that the UX will be different, since frameworks tend to come with their own patterns that shape developer thinking.
Of course, it's OK to repeat yourself as many times as needed to keep shipping products that affect the bottom line of the business and help customers achieve more. At the same time, as a company transitions to multiple products or breaks up the monolith of its main product, it should also start building the DNA for maintaining a coherent UX. This is less about using the same technologies under the hood and more about crystallizing the foundational API shapes and packaging them in a way that allows teams to offer customers a consistent set of UX expectations across internal company boundaries.
In practice, this means that some choices have to be made in a BDFL-style fashion: one general-purpose OLTP database with a preferred way of interacting with it (ORM or not), one JS framework with components supporting shared data structures (with escape hatches for specialized use cases), and one opinionated design system covering the vast majority of use cases across the company's major products.
> there are capabilities, such as DevOps, that are best handled centrally
It's okay to say that you have an Ops team in 2026. If it's not DevOps then let's not call it that.
I thought this was ancestry.com and I was like "yeah repeat yourself by having kids i guess, thats kinda how ancestry works", why is this on hackernews?
Then I clicked and read and nodded a bunch.
Would have sworn it said ancestry.com
I've seen this story many times, and most of them, these inefficiencies are kind of made up by the team not wanting to move. Generally, the UI team has good excuses related to Not-Built-Here, and the article provides precisely one such. Not saying Backend does not also have good excuses but
> They just need a simple model-view-controller architecture like PHP provides. Having pointers to memory addresses and managing concurrency via goroutines rather than just writing linear PHP that Apache runs in parallel is really much more than they bargained for
Is the kind that I've seen be the team's fault, with at least two instances of a guy going in and fixing the problem according to the new spec within three work days.
> Except maybe for the investment banking team. They really need their Erlang architecture for decentralized networking - after all, they process fast-moving market data, order execution, and the like.
I don't know... it seems to me that Go might actually be perfectly adequate for these workloads. The goroutine scheduler is a reliable way to handle concurrent market feeds AFAIK.
Go can also do MVC just as well as PHP. Hell, the standard library has net/http and html/template, or you can reach for Using gsx (or templ) and your UI components are just compiled Go functions.
I think the real problem in this scenario is that there's a bottleneck "platform" team. This takes the "dev" right out of devops.
I'm just not sure that "you can't do everything in golang and react" holds water. You can do pretty much anything in anything, these days.
DRY is supposed to be about reducing connascence, IMHO. You don't need a "platform" team to do that. You need transparency between teams so there's no duplicate effort. Something like a shared backlog.
repetition is work, just because we can automate doesn’t mean we should avoid tedious work in favour of more fun but more inefficient work.
not many other disciplines have this issue, all trades workers like carpenters or welders just repeat and repeat
[flagged]
[flagged]
Sometimes syntactic duplication can give you a hint to underlying semantic duplication. But it's no more than a hint.
DRY doesn't mean don't repeat a similar looking block of code, it means try to structure your code so that each element of the design has a single representation.
There's no shortcut to good design where no thinking is required, much as a lot of people seem to wish there were.