I guess it depends on my audience. When building some sort of library, I'll generally stick to something properly descriptive.
For an app, it depends if it's public or not. I get much more creative if no one else has to care.
At my work there's been a history of some very obtuse backend service names, so the pendulum has swung hard in the other direction for many teams. I prefer a little bit of fun, but still making it fairly easy to associate service with function. For example the mileage tracking service we named "trippy", and the marketplace backend "bazaar".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I guess it depends on my audience. When building some sort of library, I'll generally stick to something properly descriptive.
For an app, it depends if it's public or not. I get much more creative if no one else has to care.
At my work there's been a history of some very obtuse backend service names, so the pendulum has swung hard in the other direction for many teams. I prefer a little bit of fun, but still making it fairly easy to associate service with function. For example the mileage tracking service we named "trippy", and the marketplace backend "bazaar".