News for hackers. Stuff that matters.
Re:Architecting LARGE software projects [video] by ribelo on Thursday August 14, 2025 @04:20PM (#44905200)
He basically just described the FCIS[0] architecture—the same one Gary Bernhart laid out thirteen years ago. We love reinventing the wheel. Chaplicki did it with ELM, Abramov with Redux, day8 did it with re-frame, and the beat goes on.

I’m still amazed it isn’t obvious: every piece of software should be a black box with a pin-hole for input and an even tinier pin-hole for output. The best code I’ve ever touched worked exactly like that and maintaining it was a pleasure, everything else was garbage. I push this rule in every project I touch.

[0] https://www.destroyallsoftware.com/screencasts/catalog/funct...

Re:Architecting LARGE software projects [video] by leecommamichael on Thursday August 14, 2025 @04:30PM (#44905331)
Could you point to the place in the video that you felt resembled this principle most? I don’t really see the connection, but am open to it.
Re:Architecting LARGE software projects [video] by thisoneisreal on Thursday August 14, 2025 @09:55PM (#44907797)
"The Unaccountability Machine" does a great job summarizing the thought of Stafford Beer, who explained basically exactly what you said as the only viable strategy for designing and managing complex systems.
Re:Architecting LARGE software projects [video] by preommr on Thursday August 14, 2025 @10:14PM (#44907899)
> Chaplicki did it with ELM, Abramov with Redux, day8 did it with re-frame, and the beat goes on.

None of these projects reinvented the concept of FCIS.

These are just projects that had functional elements, or were outright functional languages. This is like saying jsx reinvented markup languages.

Re:Architecting LARGE software projects [video] by pjmlp on Friday August 15, 2025 @05:31AM (#44910276)
I think the actual point was,

> We love reinventing the wheel.