Titel:Hvorfor FrontEnd developers, er et mere eftersøgt folkefærd !
Kategori:Udvikling: Web
Forfatter:Peter Rosenberg - Rosenberg-IT

 hej alle

Efter vores debatter dels på Årsmødet 2015 og vist et tilbagevendende mytisk emne, faldt jeg her på Quora over en efter min mening meget sigende forklaring, der måske også kan forklare hvorfor Notes/Domino ikke kunne følge med. 


Indlægget, besvaret 4 Apr. 2012, som bedste besvarelse af: Dawn Budge^(((user )?interface)|front end) developer$ 



If you are just starting out in front-end, I think you are on the verge of discovering what the phrase 'wicked hard' means.

Here's why 
1) what Nicholas Zakas calls 'the most hostile development environment in the world'. 
There are many browsers.  They have different bugs.  They implement the same features in different ways.  You do not control the upgrade cycle.  Take a look at PPK's compatibility tables and to get an idea of how big this is.   When I developed both server-side and front-end dev, I found the server-side much more liberating in terms of not having to test the same thing over and over.

There are many devices.  They have different input methods (mouse, keyboard, touch) and different outputs to consider (large screen, mobile, tablet, retina display, screenreader, assistive technology), and your end user can adapt the output (e.g. enlarging text, changing the colour settings, switching off CSS)

2) Then there's the less cut and dried stuff, and this is usually where techies less experienced in front end dev fail: SEO, accessibility, usability.  SEO because it is based on hints and whispers, and because you need to ensure that your content can still be accessed without JavaScript for the bot to be able to scrape it, accessibility and usability because the level of acceptable performance is subjective.  There is also a disconnect between the WCAG 2 guidelines and how you practically implement a site that will conform to the guidelines.  Let's just say, look at the length of the quickref on and you'll get an idea.

3) So much more work is being required of the client-side, so you can't get away with procedural javascript code anymore.  Architecting your solution is a necessity.  OO, modular JavaScript often using an MVC pattern is gaining increasing traction, as is testing with tools like QUnit and Jasmine.  If you are interested in learning more about this, I'd suggest looking up Addi Osmani, Stephan Stoyanov, Douglas Crockford, Christian Heilmann.  This is where more junior developers struggle, because JavaScript has a steep learning curve.

4) CSS is painful to work with once your site gets big.  It is very static.  You have to hold a lot in your head and develop strategies for regression testing effectively so you don't go round in circles to see if you've broken something. 

5) Between new devices emerging and new standards and features being developed along with a fast pace for implementation in some browsers (but not others), there's constantly new things to learn.

6) Sometimes you find yourself working with graphic designs that are hard to impossible to implement with the above constraints/challenges. 

Finally, time spent learning the above the hard way, because nobody teaching can cope with the pace of change. 

Diskussions forløb

11/16/2015Hvorfor FrontEnd developers, er et mere eftersøgt folkefærd ! (Peter Rosenberg) - Rustenborgvej 7a - 2800 Kgs. Lyngby - info at