Career wise it's better to be a "Software Engineer" and be flexible about what tech you're working on.
There are studies done based purely around job titles and the term "Software Engineer" usually makes more than similar titles such as "developer" or "software developer".
Being a "web developer" is vastly more specific and can actually pigeon hole you into a specific domain of work. Sure it might actually pay more than a generic term of "Software Engineer", but unless you are against anything but web development having a more generic title might help in terms of career flexibility.
Finally, focusing on the technical aspects of your job is fine as well, but most developers/coders are some form of software engineer, which engineers solutions to problems using software. It's that distinction that usually takes you from "doing cool stuff" to "doing cool stuff that solves some problem", along with everything that comes with solving problems.
I personally go by the title of Software Engineer, and usually denote what I'm focusing on at the time. Even though I'm mostly doing front-end engineer work, I like to be part of the overall process of the software as a whole, as the front-end is just where the code goes, but the problem and overall solution is what ultimately matters.
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.
Career wise it's better to be a "Software Engineer" and be flexible about what tech you're working on.
There are studies done based purely around job titles and the term "Software Engineer" usually makes more than similar titles such as "developer" or "software developer".
Being a "web developer" is vastly more specific and can actually pigeon hole you into a specific domain of work. Sure it might actually pay more than a generic term of "Software Engineer", but unless you are against anything but web development having a more generic title might help in terms of career flexibility.
Finally, focusing on the technical aspects of your job is fine as well, but most developers/coders are some form of software engineer, which engineers solutions to problems using software. It's that distinction that usually takes you from "doing cool stuff" to "doing cool stuff that solves some problem", along with everything that comes with solving problems.
I personally go by the title of Software Engineer, and usually denote what I'm focusing on at the time. Even though I'm mostly doing front-end engineer work, I like to be part of the overall process of the software as a whole, as the front-end is just where the code goes, but the problem and overall solution is what ultimately matters.