The most important purpose of a title is to communicate your role. It isn’t to stroke your ego, or to tell people what you aspire to be, or how you personally view yourself outside of your job.
Since communication is context sensitive, not everyone’s definition will apply to you. However, in my corner of the united states, I and my peers generally perceive coder or programmer as a relatively straightforward general software writer, without worrying about much else. On the other hand, a full stack software developer implies they contribute to every aspect of getting the problem solved from a technical front. A computer scientist is mostly dealing with research, and generally isn’t production using anything. A frontend engineer is supposed to be very efficient at getting the data into a great UI quick, but isn’t expected to be as good at backend performance or networking. Engineer in general has a very different meaning outside the US, but again in my corner it’s more an emphasis on technical mastery than developer (who might have more meetings and glue work to do with the business and stakeholders).
People can be good or bad at a number of things, so just like music genres, a good title tells you what they’re probably not doing, and what they’re probably doing.