News for hackers. Stuff that matters.

A comment on An overengineered solution to `sort | uniq -c` with 25x throughput (hist). Parent comment

Re:An overengineered solution to `sort | uniq -c` with 25x t... by theemptiness on Monday October 27, 2025 @02:55AM (#45718093)
Small semantics nit: it is not overengineered, it is engineered. You wanted more throughput, the collection of coreutils tools was not designed for throughput but flexibility.

It is not difficult to construct scenarios where throughput matters but that IMHO that does not determine engineering vs overengineering. What matters is whether there are requirements that need to be met. Debating the requirements is possible but doesn't take away from whether a solution obtained with reasonable effort meets the spec. Overengineering is about unreasonable effort, which could lead to overshoot the requirements, not about unreasonable requirements.

[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by mabster on Monday October 27, 2025 @03:01AM (#45718125)
We had similar thoughts about "premature optimisation" in the games industry. That is it's better to have prematurely optimised things than finding "everything is slow". But I guess in that context there are many many "inner-most loops" to optimise.
[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by chii on Monday October 27, 2025 @03:07AM (#45718160)
> That is it's better to have prematurely optimised things than finding "everything is slow".

or you found that you've optimized a game that is unfun to play and thus doesn't sell, even tho it runs fast...

[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by wongarsu on Monday October 27, 2025 @06:42AM (#45719435)
The best-practice solution would be to write a barely optimized ugly prototype to make sure the core idea is fun, then throw away the prototype and write the "real" game. But of course that's not always how reality works
[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by chii on Monday October 27, 2025 @08:14AM (#45720090)
> not always how reality works

yep. The stakeholder (who is paying the money) asks why the prototype can't just be "fixed up" and be sold for money, instead of paying for more dev time to rewrite. There's no answer that they can be satisfied with.

[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by mabster on Tuesday October 28, 2025 @05:38PM (#45739578)
Or the timeline just doesn't have capacity for experimentation so the expectations are clear right from the start!
[ Parent | on HN ]
Re:An overengineered solution to `sort | uniq -c` with 25x t... by mabster on Tuesday October 28, 2025 @05:37PM (#45739563)
In context most of the major optimisation work was on the engine. The game code can be and usually is slow but we do try to tame things in an O() sense.

I worked licensed titles for a while and that area the quality of a title and whether it sells were largely uncorrelated haha!

[ Parent | on HN ]