3 ms·
I think there is a happy medium. I think you can have a cutsey name that gently suggests what the service is responsible for. I don't fully know what task-serv
by ImPleadThe5th 4y ago
I think there is a happy medium. I think you can have a cutsey name that gently suggests what the service is responsible for.
I don't fully know what task-service does, I don't know how it differs from scheduled-task-service-v2. In the same way I don't know what starship does or how its different from rocketship.
But I can probably guess and easily remember what 'automated-task-scheduler' or 'The Taskinator' does.
I don't think it has to be an all-or-none thing. A well thought out cutsey name can be just as effective as a well thought out descriptive name. The issue is when the names are picked lazily or at random IMO.
- bmitc 4y agoI agree with there’s a middle ground, especially depending on what level you are in the stack. However, I would consider those examples you gave to be descriptive and certainly not overly cutesy or fun.