Week 7 draws to a close with my code being no further along, in terms of functionality, than it was when I started. In terms of how it’s structured and what it can support, however, it’s progressed in leaps and bounds. I’m now at a stage where I no longer feel like I’m faking it when it comes to the core of Rainbird. I know how it works, how it thinks and I know what we can make it do – both what it’s currently capable of, and what we could do with more people, money and time.
Now you may ask why a CTO has only just got to this point, but you’ve got to understand that we’re taking something that’s been over a decade in the making, written in a language I barely understand by someone who has a huge amount of knowledge in the problem domain. It’s not just a question of joining a startup, getting the code handed over to you and then getting up to speed with NodeJS. That was the easy bit. We completed that by about week 1. The rest was learning all the disparate fields and disciplines needed to understand how everything works. And even that I’ve only done to a basic level. I could spend years learning the idiosyncrasies.
If Rainbird were easy to create everyone would be doing it. Building this type of tech well is hard; it’s why, historically, it’s been so expensive to do. It’s why we fervently believe that Rainbird will succeed. Companies can use Rainbird to avoid precisely what I’ve been through in order to help write it, and what’s really cool is we’re now starting to see companies do exactly that.