And now we have all the silly arguments comparing web frameworks and CMS's. The CMS people will compare installing modules to writing code from scratch instead

And now we have all the silly arguments comparing web frameworks and CMS's. The CMS people will compare installing modules to writing code from scratch instead of installing a library and writing a bit of glue code. If they don't make that mistake they will probably underestimate how much more flexible, better written and better tested that library will be compared to the CMS module and overestimate how hard it is to glue in a general purpose library. The web framework people will underestimate just how fast it is to install a module into a completely integrated system and underestimate the time they would have spent integrating the library and writing the glue code. They'll also overestimate how often a client needs a piece of functionality that's in any way interesting instead of just a new skin on the same old thing. The answer is "The progression goes: CMS -> Web Framework -> Http related libraries" The question can be any of the following: "What web related stuff has the worst code quality? what has the best?" "How will the tools I use change as I get more experience in web development" "What tools will I use for the most boring web dev work? What about the most interesting?" "What tool skillsets in web development will earn me the most money" "What tool skillsets have the least amount of jobs? what about the most?" "What tools web dev tools will make me want to punch my monitor the most? and the least?" Feel free to come up with your own.