I have an application built without any libraries using PHP, JavaScript, HTML5, CSS, and mySQL that will support major modern browsers - IE, Safari, FF, Opera, and Chrome.

One thing I've noticed is that most web jobs 90%+ ask for library experience of some sort.

About 10 % do not... they focus more on the language then language-libraries.

Why this lean toward libraries? I can understand that you don't want to have to re-write AES encryption algorithms and PHd level math things like that, but so much web development does not have any high level math at all.

What is the difference between jobs that focus on library use vs. jobs that focus on language?

closed as primarily opinion-based by durron597, GlenH7, gnat, user40980, user22815 Jul 6 '15 at 4:43

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    Uh because who the hell wants to pay our wages reinventing the wheel? – Rig Aug 8 '12 at 18:59
  • @Rig - Pretty much hit the nail on the head. That and 90%+ of experienced web devs will be at least somewhat familiar with a couple of frameworks in their given language. – Anonymous Aug 8 '12 at 19:03
  • 4
    The job listings that don't ask for library experience just assume that you'll be good enough to pick up the libraries. They don't actually mean they're not using libraries. – user16764 Aug 8 '12 at 19:25
  • You claim you wrote an application without using any "libraries" this makes me wonder how much work you had to do, to avoid using a library, to make your own job easier. – Ramhound Aug 9 '12 at 11:49
  • My app is for IE9+ and modern versions of FF, Safari, and Chrome....so it was not that difficult. Not supporting IE8 and below cuts out a lot of cross browser code. – user44388 Aug 14 '12 at 18:44

Ninety percent of all software applications that are being written by software developers earning a paycheck are line-of-business CRUD applications... unspectacular software that models business processes. These are domains where the process of developing software is already very well-understood, and libraries have emerged as a way to speed up the development of mundane, repetitive elements such as database access, data validation and the like.

Consequently, most employers expect developers with current knowledge of programming practices to know and understand these "tools of the trade," since it costs a lot of time, effort and money to reproduce that which has already been adequately created by someone else.

As to the other ten percent of software applications (those involving research or specialized domains such as aerospace), there is still a significant demand for custom code, as the problems posed by such environments do not always lend themselves well to the stitching together of generalized libraries.

  • I'm transitioning from what I would call personal project to professional. Most of my initiatives have been innovative - client side modeling of sessions, modification of the MVC ( things that might annoy, alarm dogma based companies ), etc., oddly I will probably re-write a standard based version of my app using Zend and jQuery, etc. so I can compare my work against "standards" – user44388 Aug 9 '12 at 18:58
  • People who write libraries and other work-saving tools are even more valuable than the people who use those tools to write apps. It requires significant expertise to write a tool that has a decent API, is useable in a wide variety of scenarios, and avoids breaking the bank from a memory/performance standpoint. – Robert Harvey Aug 9 '12 at 19:01