As front-end developers and designers, we’re constantly refining two interfaces simultaneously: one for visitors who load the website, the other for developers who have to tackle the code in the future, when adjustments or full-scale redesigns must be made. Yet we tend to assign the role of “user” to the first group, often forgetting that the code we write must work for developers in a similar way. We shouldn’t forget that developers are users, too.
If this is the case, then our convention for naming and organizing files
is critical if we are to ensure active (and efficient) development in
the future. But do we really design the partials, files and directories
that make up this interface with a particular set of users in mind, with
a set of clear goals, combined with precise, well-defined
documentation? I don’t think we do.
Recently, Robin Rendle has been working
on many different projects, each wildly different from each other. And
the various problems he has faced while switching between the projects has
made him wonder how we can drastically improve front-end accessibility.
Comments
Be the first to write a comment
You must me logged in to write a comment.