Is it important to be known as a full stack developer? The consultant's typical answer is that it always depends on the context. Some cynics might say that the term full stack is a loaded marketing term, but then these same people may also suggest that digital is likewise. Obviously, there is more meaning to the term than the thoughts that are recurring through some poor recruitment consultant's brain. There is a lot to be desired for large organizations that claim and advertise that they want to recruit only full stack developers. Are they cutting corners? Or are they genuinely interested in getting the best programming talent?

That said, from the discussion in this appendix, it is important to know the architecture of a project to a certain degree. For a couple of decades already, it has been impossible to be a jack of all trades in the software business and therefore, an engineer will specialize in a certain environment, field, role, or system. It is no longer possible to live completely closeted in an underground silo and resolutely say, all I want to know is Java on the server side because it is the only skill that I care about and it will always be that way. Decent professional engineers must be sympathetic to the other staff members including front-end developers, back-end developers, interface and UX designers, testers, stakeholders, and management. Everyone has an ultimate stakeholder and therefore they share the ultimate responsibility with accountability. Whether this means full stack or not depends largely on your attitude towards working life and knowing about and respecting the modern web architecture around you.