I have pretty good knowledge of back-end development and somewhat lower knowledge of front-end development and I do both on my job because front-end dev colleague doesn't have experience with React. But as soon as there is design work, I pull back and let him to do the job because I suck at CSS (I only know some basics) and I have no idea about UI / UX. I called myself full-stack developer before, but seeing how far front-end development progressed I don't dare to do it anymore. Back-end development is what I'm most comfortable with and that's what I put primarily in my resume.
Designer & recovering multi-tasker. Work in UX & UI design & like to understand enough about coding to be able to talk to and collaborate better with developers. (Hope you do the same for us designers
Imagine you needed your home's electrical system rewired. Do you want to hire a handyman aka "full-stack tool user" or an electrician? The handyman can replace a light socket. The electrician can make sure your house doesn't set on fire because of bad wiring.
Similarly, look at what sports teams are: a collection of people who have complementary skills and specialties. Point guards and power forwards wouldn't swap positions. Catchers and pitchers wouldn't swap positions. Teams succeed when they are composed of people with complementary specialities. Sure, a pitcher can catch a throw to home. A point guard can rebound. Designers can understand code. Developers can (and should!) understand design principles.
I've been on interviews where the company uses Agile. When I've asked how the person you're hiring for would complement the skills of the current staff, and I'm met with blank stares, it tells me it's a company that hires using a laundry list of "skills" for every job, not one that thinks of building an effective team.
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 have pretty good knowledge of back-end development and somewhat lower knowledge of front-end development and I do both on my job because front-end dev colleague doesn't have experience with React. But as soon as there is design work, I pull back and let him to do the job because I suck at CSS (I only know some basics) and I have no idea about UI / UX. I called myself full-stack developer before, but seeing how far front-end development progressed I don't dare to do it anymore. Back-end development is what I'm most comfortable with and that's what I put primarily in my resume.
Imagine you needed your home's electrical system rewired. Do you want to hire a handyman aka "full-stack tool user" or an electrician? The handyman can replace a light socket. The electrician can make sure your house doesn't set on fire because of bad wiring.
Similarly, look at what sports teams are: a collection of people who have complementary skills and specialties. Point guards and power forwards wouldn't swap positions. Catchers and pitchers wouldn't swap positions. Teams succeed when they are composed of people with complementary specialities. Sure, a pitcher can catch a throw to home. A point guard can rebound. Designers can understand code. Developers can (and should!) understand design principles.
I've been on interviews where the company uses Agile. When I've asked how the person you're hiring for would complement the skills of the current staff, and I'm met with blank stares, it tells me it's a company that hires using a laundry list of "skills" for every job, not one that thinks of building an effective team.