Do Repeat Yourself

max_sendfeld 65 points 19 comments November 16, 2026
arcentry.com · View on Hacker News

Discussion Highlights (7 comments)

parpfish

So, instead of DRY code we should have DRY code?

jedbrooke

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.

umvi

Or as the go proverb goes "a little copying is better than a little dependency" ( https://go-proverbs.github.io/ )

phptogowasfinet

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.

gavmor

> 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.

hankbond

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.

Jackobrien

Would have sworn it said ancestry.com

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed