How 'DevOps' Is Killing the Developer (2014)
To be fair, it&#x27;s the combination of DevOps done wrong and Full Stack done wrong that will cause interminable chaos.  Like &quot;Agile,&quot; it&#x27;s the given manager and team&#x27;s understanding and method of implementing DevOps and Full Stack that are the issue.<p>The term &quot;Full Stack Developer&quot; is especially problematic because taken at it&#x27;s literal meaning it suggests that a developer should be fully competent at ALL aspects of developing an application, which necessarily include deep understanding of system administration, database administration, tertiary dependency (caching apps like Redis, for example) administration, network infrastructure configuration and maintenance -- all of which are impossible for one person and we haven&#x27;t even gotten to code yet!  I think a different term needs to be coined which implies variability until defined at a given shop.  I propose &quot;Wide Area of Responsibility (AOR) Developer&quot; which, for Acme Corp, might mean &quot;Is competent in writing server-side REST endpoints AND managing development&#x2F;production database schemas AND load balancing traffic to production web servers&quot; whereas at XYZ LLC it might mean &quot;Can develop UX designs in Sketch to customer specs and then code them with HTML, CSS, and a JavaScript framework along with writing the REST endpoints into which back-end developers will connect business logic from myriad systems based on the contract the &#x27;Full Stack Devs&#x27; specified for the needs of the UI.&quot;<p>Just a thought.