<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/do-repeat-yourself-3plfy1hg5" -->

---
title: Do Repeat Yourself | daily.dev
description: A fictional story about Megabank illustrates why forcing all teams onto one tech stack backfires. A new platform VP, Mike, tries to standardize every team on...
canonical: https://daily.dev/posts/do-repeat-yourself-3plfy1hg5
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Do Repeat Yourself | daily.dev
og:description: A fictional story about Megabank illustrates why forcing all teams onto one tech stack backfires. A new platform VP, Mike, tries to standardize every team on...
og:url: https://daily.dev/posts/do-repeat-yourself-3plfy1hg5
og:image: https://api.daily.dev/og/posts/3plFy1hG5.png
og:image:alt: Do Repeat Yourself
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Do Repeat Yourself

**[Hacker News](https://daily.dev/sources/hn)** · 7 min read · 10 upvotes · 0 comments

## Summary

A fictional story about Megabank illustrates why forcing all teams onto one tech stack backfires. A new platform VP, Mike, tries to standardize every team on Go, React and Kubernetes plus shared components, which stalls the investment banking and credit card teams who need Erlang and PHP respectively. The fix is service-oriented architecture: let teams keep their own stacks but standardize on Docker containers, static CDN-loaded frontends, a RESTful API with Swagger docs, a shared CSS framework, and a common documentation base. Efficiency returns not by eliminating duplication but by removing cross-team friction.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://arcentry.com/blog/do-repeat-yourself>

## Questions this post answers

### What should a platform team standardize on instead of forcing every team to use the same tech stack?

Standardize on interfaces and boundaries, not implementation. A platform team can require backend services ship as Docker containers, frontends compile to static CDN-loaded files, APIs follow RESTful HTTP conventions documented with Swagger, and a shared CSS framework for consistent look and feel, while letting each team pick its own language and framework internally.

_Weighing how much to standardize across teams? daily.dev surfaces architecture debates like this one._

### Why did forcing every team at a company to adopt Go and React cause problems in this example?

The investment banking team needed Erlang for decentralized networking to handle fast-moving market data and order execution, while the credit card team found Go's goroutines and pointer-based concurrency overkill compared to the simple MVC model PHP already gave them. Forcing a single stack created teething pains and delayed shipping for both teams.

_Debating a company-wide stack mandate? daily.dev keeps real-world architecture tradeoffs like this one close at hand._

## Community take

How the wider developer community reacted, aggregated from 1 discussion and 46 comments across hackernews (as of 2026-11-17).

**TL;DR:** Discussion largely agrees that blanket DRY-ing or forced standardization is naive, with many offering their own rules of thumb (rule of three, WET, etc.) for when duplication is acceptable, though some push back that shared UI/design systems still have real value.

**Sentiment:** 30% positive · 55% mixed · 15% skeptical

**The case for**

- Writing things twice (or thrice) before abstracting helps find the right abstraction level and avoids premature, unnecessary generalization.
- Duplicated code is easier to reason about and fix in isolation, especially under time pressure like production incidents.
- Letting teams keep their own stacks avoids a bottleneck platform team and preserves years of team-specific expertise.

**The pushback**

- Bad abstractions can introduce much harder-to-diagnose bugs than simple duplicated code ever would.
- Without any coordination, duplicated implementations can drift apart and cause inconsistent behavior.
- Rejecting any UI/component standardization can lead to a visibly inconsistent, mish-mashed product experience for users.
- Forced top-down unification efforts are often driven by fads (e.g., 'better for AI') rather than genuine technical need.

**By community**

- hackernews (mixed): Commenters mostly riff on when duplication vs abstraction is appropriate, trading mnemonics and rules of thumb, while a vocal minority argues standardized UI/design systems are still worth pursuing incrementally.

**Hottest debate:** Whether cross-team UI/design consistency is a legitimate exception worth standardizing, or just another case where forced unification backfires.

**Open questions**

- Where exactly should the line be drawn between 'acceptable repetition' and 'needs abstraction' in large organizations rather than small codebases?
- Can shared component libraries be rolled out incrementally without recreating the same cross-team friction the post warns against?

**Highlights**

> Absolutely. The rule of thumb is that two things should be abstracted together iff they should change together. The down-sampling constant matching the upweighting factor? Don't repeat yourself. Needing a half-dozen subtly different circular buffer definitions? Circumstances vary, but repetition is probably fine. Two pieces of code which are literally identical? As you said, the syntactic duplication suggests there's an underlying semantic duplication you might want to iron out, but if the two callsites really want the potential for independent behavior then byte-for-byte code duplication can make more sense. But, like the rest of software, even that's just a guideline. Suppose you've been painted into a corner where code needs to be synced between languages. There are solutions, but especially if it happens rarely then those solutions might be a lot more expensive than just a comment at both locations.
> — [hansvm on hackernews](https://news.ycombinator.com/item?id=50531810)

> "Duplication is far cheaper than the wrong abstraction" - Sandi Metz[0] [0] https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
> — [eiriklv on hackernews · 2 comments](https://news.ycombinator.com/item?id=50530838)

> 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.
> — [kstenerud on hackernews · 1 comments](https://news.ycombinator.com/item?id=50529294)

> > 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.
> — [gavmor on hackernews](https://news.ycombinator.com/item?id=50526630)

> 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.
> — [donatj on hackernews](https://news.ycombinator.com/item?id=50529828)

**Source threads**

- [hackernews](https://news.ycombinator.com/item?id=50516689) · 122 points · 46 comments

## Similar posts on daily.dev

- [My 2026 Tech Stack is Boring as Hell \(And That is the Point\)](https://daily.dev/posts/my-2026-tech-stack-is-boring-as-hell-and-that-is-the-point--zw58f0sjv) · DEV · 176 upvotes · 10 comments
- [How to Avoid Rebuilding Infrastructure for Every New Project](https://daily.dev/posts/how-to-avoid-rebuilding-infrastructure-for-every-new-project-7ef5jmirl) · freeCodeCamp · 33 upvotes · 1 comments
- [Microservice dogma nearly tanked our seed round](https://daily.dev/posts/microservice-dogma-nearly-tanked-our-seed-round-zevryg2em) · LeadDev · 13 upvotes · 3 comments
- [Building Reusable Component Libraries That Actually Survive Enterprise Scale](https://daily.dev/posts/building-reusable-component-libraries-that-actually-survive-enterprise-scale-6ceykjdhq) · SitePoint · 4 upvotes · 0 comments
- [Have less stuff](https://daily.dev/posts/have-less-stuff-llfkpnl7e) · RUBYLAND · 1 upvotes · 0 comments

---

Tags: [#architecture](https://daily.dev/tags/architecture), [#microservices](https://daily.dev/tags/microservices), [#company-culture](https://daily.dev/tags/company-culture), [#platform-engineering](https://daily.dev/tags/platform-engineering)

[View this post on daily.dev](https://daily.dev/posts/do-repeat-yourself-3plfy1hg5)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Do Repeat Yourself","url":"https://daily.dev/posts/do-repeat-yourself-3plfy1hg5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/do-repeat-yourself-3plfy1hg5"},"datePublished":"2026-11-17T10:14:55.173Z","dateModified":"2026-11-17T14:31:01.376Z","description":"A fictional story about Megabank illustrates why forcing all teams onto one tech stack backfires. A new platform VP, Mike, tries to standardize every team on...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/aeba37da40024d2607f3e8aa1b44d32a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/aeba37da40024d2607f3e8aa1b44d32a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/do-repeat-yourself-3plfy1hg5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":9},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"architecture,microservices,company-culture,platform-engineering","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Do Repeat Yourself"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/do-repeat-yourself-3plfy1hg5#faq","mainEntity":[{"@type":"Question","name":"What should a platform team standardize on instead of forcing every team to use the same tech stack?","acceptedAnswer":{"@type":"Answer","text":"Standardize on interfaces and boundaries, not implementation. A platform team can require backend services ship as Docker containers, frontends compile to static CDN-loaded files, APIs follow RESTful HTTP conventions documented with Swagger, and a shared CSS framework for consistent look and feel, while letting each team pick its own language and framework internally. Weighing how much to standardize across teams? daily.dev surfaces architecture debates like this one."}},{"@type":"Question","name":"Why did forcing every team at a company to adopt Go and React cause problems in this example?","acceptedAnswer":{"@type":"Answer","text":"The investment banking team needed Erlang for decentralized networking to handle fast-moving market data and order execution, while the credit card team found Go's goroutines and pointer-based concurrency overkill compared to the simple MVC model PHP already gave them. Forcing a single stack created teething pains and delayed shipping for both teams. Debating a company-wide stack mandate? daily.dev keeps real-world architecture tradeoffs like this one close at hand."}}]}
```

