Seems pretty similar to functional programming in that respect. When I write code in languages like Haskell, I tend to focus the most on two things:

1. The conceptual organization of the code (≈ layout) 2. The interfaces between components (≈ routing)

Static types and functional programming naturally lean into this: types provide a first-class way to sketch out layout and interfaces in code without needing to implement the code in full detail. I'm drawn to static types less because of correctness or preventing bugs—although I can't complain about that!—and more because they give me a quick, high-level sub-language to sketch out and iterate on the design of my code. Those same types then act as guideposts for how the codebase fits together, making it easier for me to understand projects written by others or revisit code I wrote but don't remember well myself.

It’s about supply chain management Routing and layout are tools you use in that management, but don’t mistake the tool for the problem it solves.

You always get functions handed to you in programming languages. CPU instructions are handed to you. Scheme, has a small core of special forms which are handed to you. You build up bigger specific things from small general things.

In factorio you create bigger functions from smaller ones as explained in the article in great detail. The routing and layout part is about organization, but the more abstract notions of combinations and ratios are "functional" in the sense of the article.

Isn't that the goal for the visual coding, or "programming without code" pipe dream? You get the premade logic, you just need to wire it up.

Factorio is the ultimate proof these tools are not any easier than just writing the code yourself.

Now I want to see the Verilogtorio post. Combined with a layout CAD too of course.