After many months of pondering, I’ve decided to join this space.
I’ve been following Jeff Hawkins’ work for about ten years now. It was pivotal for me in many ways, and I’m immensely grateful to him, the team at Numenta, and the late Matt Taylor, for bringing this research to us mere mortals, asking these questions out in the open - and even letting us join the discussion in some capacity.
A software engineer by trade, thirteen years in total, with the past eight years in infrastructure (bare metal, clouds, architecture, many many things). It’s easier to count languages and platforms I haven’t worked with, but Python has been my main personal tool for anything moderately complex and up.
Meanwhile, I’ve also been fiercely skeptical of the situation around “AI” and its trajectory, as well as much of the ongoing research conducted in the field and motivations behind it, for many years now. Acknowledging that, and therefore to avoid any unnecessary friction, I’m going to deliberately avoid most theoretical/philosophical discussions here, focusing on the software side of things instead. This is where I feel I could positively contribute to the project the most.
Currently I’m finishing up a major activity at my daily job. Once it’s done, I’ll be able to dedicate more of my time and brain power to Monty, which I’m quite looking forward to. While I categorically disagree with the project’s long term goals, I can definitely get behind the short term ones, where Monty becomes a packaged piece of software available to people to fiddle around with. This reminds me very much of Processing, which was huge back in the day - thanks to how accessible, yet powerful, it was. There was, and still is, a community, a library, etc. Shadertoy is another good example. This is close to how I see what Monty could become, at least in one of its first iterations.