This week was mostly focused on building our open-source projects. I’m really happy with my team, and I feel like we’re all relatively aligned on what we want to do and what we want to get out of this. It’s been really satisfying to pick a project and identify what our skill sets are and how they might have potential synergy. I’m especially really excited to see that all of us know how to use Python and to pick a project that I think will be useful going forward, not just for us but for actual users. Nanobot seems really interesting. I really like the fact that it seems to be a much more trimmed-down version of OpenClaw, which I think is one of the most interesting technologies to come out recently.

However, I do think it’s going to be a bit difficult identifying exactly what we want to build because Nanobot gets a lot of concurrent contributions because this is a really fast-moving space. I’m a bit worried that by the time we pick something, someone else will start working on that. However, I feel like there’s a lot of work that can be done, so I’m really not too worried that we’ll be stuck. I think there’s a lot of great stuff we can do here, especially in terms of adding new functionality, and minor bug fixes are always, of course, rampant for us to clean up.

Another minor thing I’m aware of, however, is the fact that even though this is a fast-moving project, they care a lot about code quality. We want all of our code to be as high-quality and as compact as possible, because they seem to really care about having readable, concise, and maintainable code. That’s something that I think is especially applicable for this project versus other projects.

So far, we haven’t really built any actual code. We’ve done a lot of setup for our environments. All of us have set up our OpenClaw tokens, and we’ve all set up local Docker deployments, so it seems like we’re making pretty good progress on getting to work on our development pipelines. However, actually making contributions is going to take a couple of days, probably, because we need to identify exactly what our targets are.

We haven’t had any conflict yet either. It seems that everyone’s pretty aligned in what we’re trying to do. The one thing I’m worried about is that, in the longer term, there might be a bit of competition over who gets to do what. I think that can happen when the project is so new and so interesting. However, as long as all of us remain humble, I think that shouldn’t really be a problem. I know that I personally would be fine with doing something less glamorous as long as it means that I get to contribute to something so important here. Also, typically higher impact projects require more difficult code, so it really comes down to who is willing to sacrifice more time for that.

This project choice overall aligns quite well with my taking stock exercise because I really did express a lot of interest in deep tech and AI, and I think this is a pretty good synthesis of that.