3 ms·
This is the exact problem. It ails many very senior engineers - the circumstances have changed, but they continue on insisting it is still 2010 (in this particu
by neonsunset 3y ago
This is the exact problem. It ails many very senior engineers - the circumstances have changed, but they continue on insisting it is still 2010 (in this particular case, closer to 2004). But hey, you were lucky enough for the problem to not cause significant issues, minor loss for the colleagues notwithstanding, good on you!
- pjmlp 3y agoAt least get .NET release date properly.