Most definitely. There's a lack of understanding around this stuff--the difference between ciphers (stream translation) and codes (semantic replacement). I've made a lot of hacks like this in my 20+ year SWE career and been met with misguided interpretations--which is why documenting excessively to explain the WHY as much as the WHAT is critical. Additionally, this is a great example of why I replaced Java with Node.js and SQL with JSON files in S3. Speaking JSON all the way down the stack prevents odd data type conversion and library assumptions. The old way was like speaking in English (JSON), formulating sentences in French (Java), and remembering everything in German (SQL). Now it's English all the way down.
Most definitely. There's a lack of understanding around this stuff--the difference between ciphers (stream translation) and codes (semantic replacement). I've made a lot of hacks like this in my 20+ year SWE career and been met with misguided interpretations--which is why documenting excessively to explain the WHY as much as the WHAT is critical. Additionally, this is a great example of why I replaced Java with Node.js and SQL with JSON files in S3. Speaking JSON all the way down the stack prevents odd data type conversion and library assumptions. The old way was like speaking in English (JSON), formulating sentences in French (Java), and remembering everything in German (SQL). Now it's English all the way down.