No time to name the layers
Welcome back; this article is part of the series called DaS™ — Naming convention.
The previous articles explored the impact of folder naming conventions. This article discusses the naming convention inside the CX and UI files before integrating them with our engineering colleagues.
Why does no one care?
If you talk to any outside of the design practitioner circles, no one would consider naming layers or how the work is done as far as it is shipped. Often though, it is the fundamental difference between the practical (speedy, dirty, copy and paste) and integrated (well organised, connected, regularly updated and automated) way that impacts the real world.
You wouldn’t care how your herniated appendix is removed so long as the stitches are minimal. So the cavity operation is done by the first-grade surgery student where the private well-known plastic surgeon will carry your stitches on your tummy and final speech that you should be all ok.
Fun aside, we often hear from our POs and PMs that no one cares. The agile manifesto says, “Working software over comprehensive documentation,” making everything else disposable. If no one cares, why should you?
