Being remote means you not always have a face to face contact with your customers, with the domain experts or with the right people who know you the business you try to model works. This must not be an excuse to skip the modeling part. It is even more important to have a good shared understanding of the domain and the problem you try to solve, to build & use the ubiquitous language.
If you ever wondered how to make 3rd party API call from Aggregate and not clutter it with dependencies, you may find this post interesting.
How to migrate legacy Rails apps into DDD/CQRS in a relatively safe way?
This is the story how we once migrated an in-house event store, that reached its limits, to Rails Event Store.
TLDR: You can use raise Exception and raise Exception.new - they’re identical as a result and it’s 4 characters less.