3 ms·

My experience seems to be a polar opposite of this.

• tabtab 8y ago
  A well-tuned web-stack can indeed lead to decent productivity. The problem is that the average shop either doesn't know how to tune the stack, or has no incentive to. A shop or domain settles on conventions, and one can potentially use these conventions to clean and tune a stack to fit an org like a glove. A handful of shops get it right. Web stacks have to be "managed", and if they have to managed, then the result depends on how well they are managed. The thing is, the tools I mentioned didn't need frameworks; they were frameworks. This reduced the urge and ability for "local creativity" to run amok with fads and experiments. Fear of keeping-up-with-the-IT-Jones often creates chaos in my observation. Devs have to stick the latest and greatest into the stack to placate the fear of being obsoleted.
  • sibeliuss 8y ago
    > Web stacks have to be "managed", and if they have to managed, then the result depends on how well they are managed Exactly! Without an engineer (or a team) to manage this then some serious problems can arise, including loss of productivity. If there _is_ someone managing this then productivity gains can be enormous.
    • tabtab 8y ago
      It's kind of like restaurants. The tools I mentioned are like franchises: you know what you are going to get ahead of time: a "B" to "B-" level of quality at "B" to "B-" prices. Individually-owned restaurants may be roach-motels, and/or have the Greatest Food You Ever Tasted. But it varies per owner and time.