I agree. I picked up JavaScript recently (I&#x27;m an embedded systems and firmware guy, so gimme a break!), and decided to play around with designing a basic game. Using parts off of the shelf (bootstrap, parse, and google&#x27;s APIs) I could build a very pretty, responsive thing that worked well on a variety of devices.<p>While doing this, I was fumbling around from tutorial to tutorial, figuring out what&#x27;s what (I still mis-type &quot;backbone&quot; and &quot;bootstrap&quot;). Reading through the questions that others are asking on stackoverflow, I saw a recurrent pattern. Someone would ask &quot;How do I X?&quot; Someone would answer &quot;You do this, this, then that,&quot; explaining fairly-articulately the correct answer. A reply to that would be &quot;I don&#x27;t get it. Can you post a fiddle?&quot; Sometimes inside of those, you&#x27;d see (what I think) is a mis-use of a framework. It would work, but either dragged an entire framework into the picture, or caused a tremendous amount of work to happen, when there would usually be a much simpler solution (i.e. do I -always- have to use jQuery?).<p>I feel like the entry level of programmer might need to change into a different title. &quot;Software tradesman?&quot; I&#x27;d describe these as people that know how to assemble a list of components into a working whole. They can replicate a pattern, filling in blanks where appropriate, but can&#x27;t nip &#x2F; tuck to change it, and certainly can&#x27;t design and create a whole -new- component.