3 ms·
I remember thinking that the internal wiki at anzn was one of it's best workplace features. This was something used by just about every team and rarely needed i
by AndrewUnmuted 6y ago
I remember thinking that the internal wiki at anzn was one of it's best workplace features. This was something used by just about every team and rarely needed intervention from internal developers to operate smoothly.
This was prior to the migration though. I can't imagine how much upheaval there was resulting from the migration, language considerations aside. This is probably one moment where tech concerns should have taken a back seat to company stability.
- vsareto 6y agoMuch of that depends on their justification. It's entirely possible it was made only for broad risk-avoiding reasons due to PHP's reputation at the time (anyone could have "safely" made that decision, you don't need infosec skills to make that call). They could have done a detailed inventory of what they use and found a bad history of bugs like multiple auth bypasses, trivial RCE. Or they might have audited a few of the products themselves and saw the code quality was typically poor and prone to security issues.