3 ms·
Why should it matter to HQ? The result of the work probably matters (i.e. a document), but the software used to create it? Doesn't really matter so long as it c
by indymike 6y ago
Why should it matter to HQ? The result of the work probably matters (i.e. a document), but the software used to create it? Doesn't really matter so long as it can be read. There are so many ways to do IT than the old central control of all the things model from the 90s.
- chiefalchemist 6y agoBecause...Security? That's not an issue? Imagine one unintend breach and poof! customer data splattered across the (dark) web. I can't imagine how security and privacy are of no concern. Has that been cleared by legal? Or is it laziness and/or negligence?
- renewiltord 6y agoBecause they trust you to do it right. At a certain stage of organization, if you put a lot of barriers in people's way your company will fail.
- stu2b50 6y agoAt the same time, IT is not everyone's forte. If you're a office worker that types documents and looks at spreadsheets, should you be expected to know if the document suite you're using has a zero day that was just released? I trust you're not being malicious, and I trust that you're not trying to be insecure, but software is a complex world now.
- renewiltord 6y agoNo you're right which is why usually you have some very sane default like Google Sheets and then let people escape hatch when they need to. Then you hire the people who won't use the escape hatch to bring Bonzibuddy PolitburoSuite to do their spreadsheets.
- chiefalchemist 6y agoSo you're a WFH developer AND a sec expert? If you had those skills you wouldn't be writing code. For example, would you use SMS for 2FA? (Hint: Many trust it, but shouldn't, right?) This isn't about trust or not. It's about liability. It's about accountability. It's about reasonable expectations. It's about making sure you're not putting your team in a compromising position. It's about not assuming.
- deleted 6y ago[deleted]