It might mean you can update copy on static portions of a website, and know how the CSS is holding some of it together without being able to alter it. It might equip you to better participate (as a stakeholder) in a redesign of an internal site, or a client site because you are better able to understand an explanation of how the code works with in modules (why or why not something can happen as part of a build) that have been designated for the build or what it might take to alter those modules (too costly, would erode consistency of the UX). It may enable you to better work with the UX team and in turn, cleaner hands offs to the dev team. Or if you present yourself as someone who likes to code, understands the syntax but isn't planning on coding a site, it may make it easier for you to work across teams.
Share your insight
Join an authentic community that helps women support each other at work. Share your professional experience or ask for advice — you can even post anonymously.
3 Comments
Join the conversation