I agree and this is why I don't think all of the things listed in the last section should be included in the term fullstack. To me I think of the term as defining the application code itself, not the meta code around it which includes things like deployment and CI/CD.
Being fullstack doesn't mean you know everything, it means you have an end to end understanding of all parts of your application independent of the different aspects of your application that change across different deployment providers.
I think we’re mostly on the same page, but I just don’t think it is a relevant or healthy concept. The moment you codify the idea of “end to end understanding” people will take that as a new minimum and I’d bet you anything we’d start seeing “Fullstack Plus” as the new buzzword as people start inflating resumes and job postings and egos.
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 agree and this is why I don't think all of the things listed in the last section should be included in the term fullstack. To me I think of the term as defining the application code itself, not the meta code around it which includes things like deployment and CI/CD.
Being fullstack doesn't mean you know everything, it means you have an end to end understanding of all parts of your application independent of the different aspects of your application that change across different deployment providers.
I think we’re mostly on the same page, but I just don’t think it is a relevant or healthy concept. The moment you codify the idea of “end to end understanding” people will take that as a new minimum and I’d bet you anything we’d start seeing “Fullstack Plus” as the new buzzword as people start inflating resumes and job postings and egos.