If a full stack developer can out do a specialized developer in their are of expertise, what does that mean?
I don't trade skill in one area for general knowledge. Even if I did, most things that are overly specific to a certain domain are searchable in documentation.
So which is it? Do we need to be "problem solvers" or encyclopedias? The same types of articles claiming we can't be goo full stack developers are the ones telling me that "it's not about memorizing a bunch of languages, it's about problem solving"
Well, memorizing every little bit about one thing is the near opposite of the general mentality of problem solving.
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.
If a full stack developer can out do a specialized developer in their are of expertise, what does that mean?
I don't trade skill in one area for general knowledge. Even if I did, most things that are overly specific to a certain domain are searchable in documentation.
So which is it? Do we need to be "problem solvers" or encyclopedias? The same types of articles claiming we can't be goo full stack developers are the ones telling me that "it's not about memorizing a bunch of languages, it's about problem solving"
Well, memorizing every little bit about one thing is the near opposite of the general mentality of problem solving.