Neither are those points a definition of a backend developer. The point I was trying to make is that the rationale behind creating a development team should involve more than simply separating people by their preferences. To me, this is like trying to compose a Dairy Queen blizzard by separating out the like parts. All you end up with is a cup on candy pieces and some vanilla ice cream when what I really wanted (as the end user) was a tasty combination.
To put this another way: When devs are separated into two teams (UI and backend), how have you seen it work out? Where do most of the bugs occur? Where do you see most of the work occur? Do you feel that it was an efficient use of everyone’s time?
The company where I work has been working like that for the last 15 years. Well, almost. There are teams having both backend and fe devs separately, but it's still one team. We have around 500 developers in multiple countries. We even have separate teams only dedicated for DB operations. BE devs usually not writing any SQL queries for example, they are using stored procedures.
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.
These are all great points to identify a great developer/person. None of them describes "Full Stack" developer.
Neither are those points a definition of a backend developer. The point I was trying to make is that the rationale behind creating a development team should involve more than simply separating people by their preferences. To me, this is like trying to compose a Dairy Queen blizzard by separating out the like parts. All you end up with is a cup on candy pieces and some vanilla ice cream when what I really wanted (as the end user) was a tasty combination.
To put this another way: When devs are separated into two teams (UI and backend), how have you seen it work out? Where do most of the bugs occur? Where do you see most of the work occur? Do you feel that it was an efficient use of everyone’s time?
The company where I work has been working like that for the last 15 years. Well, almost. There are teams having both backend and fe devs separately, but it's still one team. We have around 500 developers in multiple countries. We even have separate teams only dedicated for DB operations. BE devs usually not writing any SQL queries for example, they are using stored procedures.