|
|
|
|
|
by _the_inflator
1066 days ago
|
|
This as a dynamic mapper in a backend layer can be huge. For example, try to keep up with (frequent) API payload changes around a consumer in Java. We implemented a NodeJS layer just to stay sane. (Banking, huge JSON payloads, backends in Java) Mapping is really something LLMs could shine. |
|
Code/functionality archeology is already insanely hard in orgs with old codebases. Imagine the facepalming that Future You will have when you see that the way the system works is some sort of nondeterministic translation layer that magically connects two APIs where versions are allowed to fluctuate.