Rails Scales!

Setting Up Ownership for Your Application

It may be hard to imagine for people working in a startup with ten engineers, but major companies that use monolithic architectures (or monolith-ish, as in big applications that are accompanied by a few services) can have hundreds of engineers merging commits into the same Rails app.

The basic concept is brutally simple: each and every file in your codebase should have an owner. This does not mean that only the owner of that file can modify it. It just means that any change needs to be approved by the owner.

How do we enforce ownership? There are multiple ways, but maintaining the rules of the system can be difficult if you have to build something by yourself, with its only purpose being to enforce ...