[ok_dad]

At my current job, we have services like "watcher" which watches some data and alerts someone about issues. Should we have called it "alerter"? Who knows, but if I worked at a bird related startup it might have been called Canary, which also makes sense to me. Who cares what we name things, just have good documentation so it's readily discoverable.

I still don't understand what some of our stuff does and it has common names that are descriptive, because documentation sucks. They could be called Widget and Whoozit for all I care, as long as there is documentation!