2 ms·
I wonder if you actually read the story. The author displays incompetence in technology administration at multiple steps. From committing the basic design erro
by inopinatus 11y ago
I wonder if you actually read the story. The author displays incompetence in technology administration at multiple steps.
From committing the basic design error of using hard-coded credentials at all; to committing them to any kind of repository; to failing to check on the visibility of that repository; to giving those credentials privileges they did not need; to failing to act effectively on warning messages.
And all this, apparently, is laid at the feet of Visual Studio.
I have no love of the Microsoft ecosystem, but the author does not acquit themselves well in this incident. The arrogant claims of seniority in the opening paragraph seem ironic in this light.
- LeonB 11y ago> all this, apparently, is laid at the feet of Visual Studio I wonder if you actually read the story. He admits several faults including most if not all of those you mention.
- inopinatus 11y agoSo what? Admitting fault isn't absolution. He really does go out of his way to blame the tools.
- schrodinger 11y agoThe tool has a huge bug! Even if he wasn't putting credentials in there, it could still have led to sensitive source code getting out or something!
- x0n 11y agoArticle updated - VS wasn't the issue. He had installed a 3rd party github extension (from github themselves) that overrides the built-in Git support in visual studio... bug was found, confirmed and fixed yesterday though, so a quick turnaround.