I‘m a Front-End Developer
But I am not a Javascript ninja, and I am proud of it
Sometimes the definition of Front-End Developer is a little ambiguous. Most of the time when people say “Front-End Developer” actually they mean “Javascript Developer”. But this definition is wrong. I think one of the most appropriate explanation of what we actually do is the following one, quoted from a recent blog post written by Jonathan Snook, longstanding web developer, author and :
Implementing a design means writing HTML and CSS (and some JavaScript) and ensuring that the design holds up under the various design constraints: different browsers, different dimensions, different resolutions, and different interaction methods (mouse, keyboard, gestures, screen readers). It also can mean building out prototypes for UX validation. These people are design-minded but not necessarily designers. These people are technically-minded but not necessarily developers.
People in this role provide a great bridge between design and engineering. I’ve often called these people the “arbiters of design”. They inform design of possibilities and constraints and help ensure that designers build a consistent and usable interface for as many users as possible. They help codify the design work. They have a developer mindset with concerns about render performance and load times and can work with engineering to build out a performant front-end.
This is the same description that Marco Cedaro gave of himself, when we met at the last Silicon Milkroundabout, and I remember thinking: “Wow, the same description fits me too!”. It seems we are not the only one thinking this way, then.
So yes, I am a Front-End Developer. And I am proud of it.