3 ms·
How about: Every app that I need a user to access requires three requests to IT. Each application must go through a pre-approval process and a separate set of
by ebiester 14y ago
How about:
Every app that I need a user to access requires three requests to IT. Each application must go through a pre-approval process and a separate set of meetings to determine requirements.
That's not to mention that many applications have a view/edit distinction, requiring nearly the same page based on permissions. If you make the choice to split this page into two applications, your UI will have to be written twice rather than an if statement in the view logic. (Oh, and wait until the change request comes in..)
Maybe your system will work in small businesses and direct to customer apps. It's a non-starter in many other places.
- lobster_johnson 14y ago> Every app that I need a user to access requires three requests to IT. Then you have (voluntarily or as a result of placing yourself in such an organization) hobbled yourself and your ability to be an efficient developer. If your escape route through a beaurocracy — in order to accomplishing your goals — is to compromise in your technical design, then you have my sympathy. That is a situation I could never tolerate personally. (Do you really use Ruby? Sounds like Java would be something an organization of this type would use.) > That's not to mention that many applications have a view/edit distinction That requirement is certainly not incompatible with the model.