News for hackers. Stuff that matters.

A comment on Ask HN: How to avoid over-engineering software design for future use cases?.

Re:Ask HN: How to avoid over-engineering software design for... by ChicagoDave on Tuesday June 23, 2020 @09:29AM (#23613634)
It’s hard to flip your brain, but abstractions are bad. Copying code for different business purposes is good. Simple patterns are vastly better than complex frameworks, even if you think it improves unit or integration testing.
[ Parent | on HN ]
Re:Ask HN: How to avoid over-engineering software design for... by Wilem82 on Wednesday June 24, 2020 @08:14AM (#23626973)
> abstractions are bad

They're as good as you make them. Abstractions aren't bad by themselves.

> Copying code for different business purposes is good.

Only when it makes sense, ie when you can't make a good abstraction.

[ Parent | on HN ]
Re:Ask HN: How to avoid over-engineering software design for... by ChicagoDave on Friday June 26, 2020 @11:02PM (#23659178)
Nope. Different domains shouldn’t share code or data. One domain may have a customer record with address info and another domain may have a customer record with past purchases.

Abstractions end up wiring things together that blur business rules.

[ Parent | on HN ]