4 ms·
And voila! Just like that, you now have 2 systems to maintain, support and debug. Do we redirect server side, use 302 or use JS to redirect ? docs and api don
by gofreddygo 2y ago
And voila! Just like that, you now have 2 systems to maintain, support and debug.
Do we redirect server side, use 302 or use JS to redirect ?
docs and api dont match, users don't RTFM, but lament that the engineering quality is low.
Support now needs to know which api endpoint the user with problems is hitting and why they cant repro when hitting the new endpoint.
Auth will be fun too, is it a domain redirect? subdomain? Cert rotations anyone ?
- chipdart 2y ago> And voila! Just like that, you now have 2 systems to maintain, support and debug. It's even worse, the "new" system is a layered mess where logic is spread across multiple systems and services, and is bound to accommodate all the original scenarios and ensure new changes remain compatible across multiple versions. It's a far worse situation than keeping the old APIs in. It's a proposed solution from someone who clearly did not even read the problem statement.