That use case is the "we should only have to pay one guy and he should know everything" use case. Or the "I have an idea for an app. I'm a company now." use case.
Know why so many bootstrap sites look pretty much exactly the same?
--- If someone wants to change the color of the header on a website, should it require a code change?
If there's a table that someone wants to change the border on, should that require a person who knows three languages? Or should that require a guy who read an html book last week?
Conversely, what if there's a bug report about an element that is not displaying on a Nook Color? Should that require a developer to look at? Or wouldn't his time be better used working on an actual programming problem?
--- I interviewed a developer recently and asked him about a particularly difficult challenge that he worked his way through. Usually people respond with a problem that manifested itself in multiple ways or tracking down an important bug in a widely used library. This particular answer was about an errant price change on a major retail web site that took 6 days to implement. A price change should be a zero down time absolutely no-brainer data change. But some idiot along the way decided that he should embed html AND javascript in his java class and it took a team of people several days to track down where exactly the error was that produced the errant price. There's stupid code like that all over the place.
With experience, you learn that you can avoid those kinds of problems completely with very little overhead early on.