While true, there's little guarantee that the functionality will be exposed in a manner that's useful for anything except the specific use case the person was writing for. If you're cutting corners on architecture, aren't you likely to cut corners when designing an API too?
User talk:Daniel Kinzler (WMDE)/FauxRequest
Using FauxRequest in Production code may be acceptable as a short term solution, but should be considered tech debt that needs to be addressed in a timely manner.
IMO change "Production" to "prototype". I know we already have a long history of prototypes becoming deployed as production solutions, but we shouldn't encourage that.
The idea is not to encourage that. But people argue that there are advantages to using this in production, so I thought it fair to record them - and rebut them in the discussion section. We'll need to find someone else to argue in their favor, and rebut the con arguments ;)
But this is in the "conclusion" section.
There are no older topics