derekstavis

We thought a lot about this, and decided to not wait since we are a pretty small team and having more hands helping us to catch any problems early on would help us to make better technical decisions as we continue evolving the core platform. In addition to that, we gained a pretty robust CI step to keep us accountable around the guarantees that we want to provide. Reliably and consistently storing data is of utmost importance for us.

The plan is to engage with Jepsen again once we have a system that passes the current suite, expand the test surface even further, and continue iterating until we are satisfied with the results. There won't be a public release before that is true.

Working with Jepsen also sparked a couple other interesting ideas, like building a Python language fuzzer to ensure that many shapes of Python programs work as intended in Capela. That's something we would love to do in the future.

Re: Antithesis - absolutely. Kyle mentioned them to us and we think it will be a very interesting product for us to adopt to further ensure we're delivering a reliable product.

Kyle connected us already - we definitely plan to leverage their product for extra layers of verification!

Darklang is pretty fascinating, and was brought to our attention when we started demo-ing Capela to some folks in the industry. I think where Darklang (and others like Skip [1]) falls short is that it is a new language. Capela instead leverages typed Python, an existing and pretty familiar language to most programmers (and LLMs).

[1]: https://skiplabs.io

Derek from Capela here. Marketing was not our primary purpose, but I guess it worked out as such ;)

The primary reason for us engaging early on with Jepsen is that we care a lot about correctness, consistency and reliability, and we wanted the best in this field to establish a baseline of tests that we must make sure our platform passes before we even put it the hands of anybody.

There's Oh My Fish too (https://github.com/oh-my-fish/oh-my-fish), the very first and original fish package manager (or shell framework, as we like to call it). I use it because of the nice default theme and the node version manager (nvm) compatibility plugin.