Discussion about this post

User's avatar
Mike Smith's avatar

It seems like as technology continues to improve, the number of cases where the system self constructs (grows) will increase. Eventually the boundaries we draw between life and machine will become blurred.

Although the distinction between evolved and engineered systems may be more durable. Living systems are survival machines with their own agendas. We build machines for particular purposes. They are extensions of our interests. I'm not sure how much market there will be for machines that self actualize.

Of course, looking much further down the road, the boundary between how we reproduce and what we design might itself become blurred.

Interesting topic Suzi!

Expand full comment
Wyrd Smythe's avatar

Wow, another great post, and so much meat on this bone I hardly know where to start.

For one the difference between building and growing. Perhaps one difference lies in who or what does the building. In contrast to things we build, things that grow do it themselves (sometimes with help from a gardener or parent). A tree builds itself; someone else builds a doghouse from the wood.

The thing about both blueprints and DNA (and rule 110) is that without the larger process for implementing the information, the information does nothing. FWIW, my computer science background calls blueprints, DNA, and the automata rules "data" rather than "code". The latter being the algorithms that operate on the data.

An important aspect of this being that data requires a process to implement it. A builder (and materials) to implement a blueprint, an algorithm to implement automata rules, the biologic engines that implement DNA (or RNA).

> "A blueprint tells you what the final structure will be before you begin. Rule 110 doesn’t."

I'm going to push back on that a little. As you say, rule 110 is deterministic and always has the same outcome. So, in a sense, rule 110 (plus the implementation process) does specify the final structure. DNA might be a more interesting case because, as you point out, environmental factors make its "blueprint" nondeterministic.

As an aside, there are blueprints and plans that are (at least somewhat) context dependent. For instance, Telco wiring diagrams with multiple options controlling how the switch behaves (which makes those diagrams hard to read sometimes).

> "Building is plan-driven. You know what you’re aiming for. Growing is process-driven. You have to let it unfold."

Oh, I like that. Good way to put it.

A couple of SF stories I've read feature "blank slate" Ai that starts off nearly useless and learns to function over time just as a human does. In one, the humanoid robots had to go through a "teenage" phase that was just as annoying and obnoxious as human teens can be. Nature evolved brains to navigate an ever-changing world, and it seems entirely reasonable that Ai would need to do the same.

As one more aside, I grinned about following an IKEA manual to "build" a bookcase. I'd call that "assembling" a bookcase. I've built bookcases and doghouses from my own designs. Which doesn't at all detract from your points but made me smile.

(And now I really want to code up a 1D automata to see how big the code is.)

Expand full comment
17 more comments...

No posts