News for hackers. Stuff that matters.

A comment on System design and the cost of architectural complexity. Parent comment

Re:System design and the cost of architectural complexity by babyshake on Thursday April 06, 2023 @02:21PM (#35472289)
> non-specific platitudes

Anything specific that tends to be used often?

[ Parent | on HN ]
Re:System design and the cost of architectural complexity by nerpderp82 on Thursday April 06, 2023 @02:24PM (#35472349)
It is org specific, I have already triggered myself and need to find a safe space.
[ Parent | on HN ]
Re:System design and the cost of architectural complexity by damiankennedy on Thursday April 06, 2023 @03:20PM (#35473104)
"Move fast and break things".

At 48 I've stopped fixing other people's things.

[ Parent | on HN ]
Re:System design and the cost of architectural complexity by runlaszlorun on Saturday April 08, 2023 @11:23AM (#35494134)
Prob OT but ‘break things’ old Zuck sure did. A bit sad given the billions folks made in the meantime.

I almost said that I’m surprised they weren’t held accountable… but we all know better.

[ Parent | on HN ]
Re:System design and the cost of architectural complexity by bradstewart on Thursday April 06, 2023 @03:44PM (#35473386)
Appealing to "best practice" without concrete, specific reasoning is a big one.
[ Parent | on HN ]
Re:System design and the cost of architectural complexity by whstl on Thursday April 06, 2023 @05:06PM (#35474450)
"We need to build something that scales" to justify virtually every single source of complexity.
[ Parent | on HN ]
Re:System design and the cost of architectural complexity by dahauns on Friday April 07, 2023 @09:21AM (#35481304)
Especially when then understanding of scaling only distinguishes between "unmaintainable monolith" and "full-blown web scale".
[ Parent | on HN ]