3 ms·
What? #2 and #5 exist only to support #7. #4 usefulness is completely dependent on the context. #9 is a joke, right? It's an anti-pattern for most of the web
by marcosdumay 4y ago
What?
#2 and #5 exist only to support #7.
#4 usefulness is completely dependent on the context.
#9 is a joke, right? It's an anti-pattern for most of the web based SaaS applications, and poisonous to anything that isn't SaaS.
And #12... Try that in a large regulated company and people may quite as well end up in jail.
- kqr 4y ago#2 is to improve quality, shorten feedback loops, and simplify merges. You get those benefits whether or not you're able to push things to your customer at will. Both #2 and #5 really just set a quality bar high enough to reduce long-term maintenance costs. I don't see why you wouldn't want that in a non-web scenario. #12 is not talking about deploying to production, and I don't see why you shouldn't be able to deploy to a dev environment from your machine. It's nice not to have to run everything locally. Even for non-EU companies. So aside from #9 which is of questionable utility for any type of development, no, I'm not convinced you've pointed valid examples.