3 ms·
> Very technologically cool, but I'd much rather inject the new functionality into the source code. From there it can it make its way through the unit tests, in
by toast0 4y ago
> Very technologically cool, but I'd much rather inject the new functionality into the source code. From there it can it make its way through the unit tests, integration tests, deployment, health/readiness checks, and if all that passes then I'll allow it to be called.
Generally, you do make the changes in source code, compile it, do all your pre-flight checks, and then hotload it. Honestly, sometimes the pre-flight check is just 'does it compile', but that's philisophical; you can put whatever process in place you want. But from my experience, it's much nicer to upgrade in place than start new, move traffic, drain old (not always in exactly that order). Sometimes, it's not realistic to avoid starting new and moving traffic, but it's nice when you can.
Most people aren't patching the VM bytecode by hand (to my knowledge).
- worthless-trash 4y agoThere was that.. interview with a witch. I was a little enamoured by her. https://aphyr.com/posts/341-hexing-the-technical-interview https://aphyr.com/posts/341-hexing-the-technical-interview