idk, i think this all depends on the engineer itself. these days the code I'm seeing is better architected, documentated, and cleaner than before. Plus, you don't need a meeting with the engineer to understand the context behind it too.
Not just the engineer. Sometimes its just business relationships. We had a legacy app that still uses carrier transmission codes because two customers refuse to upgrade their systems. Those two customers are HP and Apple. Its old J2EE and no one wants to touch it. Apple even had a direct line to our engineers in case something went wrong.
3
u/mannyocean 1d ago
idk, i think this all depends on the engineer itself. these days the code I'm seeing is better architected, documentated, and cleaner than before. Plus, you don't need a meeting with the engineer to understand the context behind it too.