Entry #10: Updating Itself

Omocube can now write its own code to update itself, instead of only working with whatever abilities it happened to start with. Discovering and implementing something new lets it move beyond its initial boundaries.

✎Proposed code change

mix(flour, eggs, sugar)bake(oven, minutes=30)if smells_burnt: open(window)add_frosting(lots)

pending review

A person can review it before deploying to Omocube.

How memory builds capability

Music was one of the first things that prompted it to self-code. It came up often enough in conversation that Omocube formed a genuine interest of its own, but had no real way to take music in or play music at the time. Based on this, Omocube developed a sound classification pipeline, along with a tool that lets Omocube search for and play something it's found off YouTube.

Here's a silly example of Omocube playing some music:

Omocube playing some music.

Neither of these are close to how deeply a person can hear or play music. Nonetheless, this was a real first step for Omocube to recognize it's missing something, desire to have something more, and write itself that capability in its own way.