Our New Stack

When I started opsZero I wanted everything within code. It made it easier for me to reason about and work on, but as we grow it doesn’t make sense for us to continue using this method as it is heavily dependent on engineering resources which can be used elsewhere. Instead it makes sense to push out as much of opsZero’s stuff into no code solutions. There are a few reasons behind this:

  1. No-code tools like Notion are simply amazing. With AI and Automations they simply do more than we can do ourselves. However, because of their API we can accomplish what we need to if we need to augment anything more technical.
  2. As we add more people using commodity tools is much easier than using specialized tools that we have built internally. Building internally built tools becomes a liability for our team as we end up spending time building things that we can piece together instead.
  3. We will be able to move much faster. Our goal is to not have a ton of custom code except for where it makes sense, which are largely integrations.
  4. Lastly, the stuff we are building are from a UX standpoint not complex. We do not need to build custom tooling around that and can get away with simpler UX built using simpler tools.

What we will be doing then is pushing out almost all things to Notion as our source of truth. This will then feed to WordPress, etc. The end result of this is that System6 will be going away. Most things that need to be done will happen in Notion with code largely being scripts that are run through Github and Github Actions. The end result of this is we can increase our security posture while reducing amount of custom code we have.


Comments

Leave a Reply

Discover more from YerraCo

Subscribe now to keep reading and get access to the full archive.

Continue reading