To make any system work that relies on collaboration we first have to admit that what we are asking for is charity. Yes, there are great benefits when working closer together, many of which are long term gains and big picture wins. In this article however I’d like to focus on the thought process we must go through in order to create a healthy and productive collaborative environment.
Working with npm on the front end comes with many issues. A summary of this can be found in this npm blog post. In the following article, I explore the way we use and reuse front end components (such as Sass partials) seamlessly through the npm registry.
For the purpose of this article let’s look at the most fundamental issue for the front end: dependency hell.
Npm embraces modular architecture of software development. Do one thing only and do it well. This works well in theory and means you can pick from a gazillion great modules to build your thing.
The example above shows how this would work in a perfect world. Each module can reuse all of it’s dependencies. …
As a front-end developer one of our main responsibilities is accessibility. I am sure there are some that would disagree with me, but for me it comes down to this: Accessibility means the front-end I write is accessible to more people and to me that’s what a front-end is all about. I promise I won’t say things like “social responsibility” and “the right thing to do” in this article. Those are just nice-to-haves, so let’s put the Karma aside for now and have a look at one aspect that’s cause of many disputes between designers and front-end developers.
“Gentlemen, you can’t fight in here! This is the War Room.” …