3 ms·

> It's possibly something many of us should care more about, though. Definitely, but I'd argue that even with containers etc., we don't yet have the capabiliti

> It's possibly something many of us should care more about, though. Definitely, but I'd argue that even with containers etc., we don't yet have the capabilities to make what we know is right, as easy to operate as SaaS. > Suppose your company handles a fair bit of confidential information, and some of that information ends up in Notion as part of your general project management workflow. Many folks that post to HN seem to miss this even though they are probably very technically capable. Many IT people in small/medium organizations don't have the time to consider this. Sometimes relationships with big organizations force this reality and threats get addressed, but it's not the norm. Most IT managers are under pressure to cut costs, reduce staff, modify accounting (review vs capital budgets), coexist with shadow IT, etc. Cloud solutions seem fantastic to them, and they don't have the energy to fight with someone in marketing who introduces a rogue solution because they don't understand how the current Wiki works.

woolvalley 8y ago
> a rogue solution because they don't understand how the current Wiki works. That's usually a sign of an IT department not listening to the needs of their end users.
- zerkten 8y ago
  I think that's pretty common, so I don't disagree entirely. It can also be the case that you have increasing numbers of tech-savvy folks who feel that they can build their own tech solutions, but aren't actually equipped to build/select something that is equipped to serve the needs of their team or the organization. This can result in the team being left holding the baby when certain individuals leave, data loss, security issues etc. In 15+ years of enterprise probably two-thirds of the time I've seen this issues and it has been predictable that it would work out this way, but IT didn't help themselves by pretending their solution was better. When IT tries to learn and adopts the tool, or incorporates the needs then things work out better. But, that's only a third of the time.

woolvalley 8y ago

> a rogue solution because they don't understand how the current Wiki works. That's usually a sign of an IT department not listening to the needs of their end users.

zerkten 8y ago
I think that's pretty common, so I don't disagree entirely. It can also be the case that you have increasing numbers of tech-savvy folks who feel that they can build their own tech solutions, but aren't actually equipped to build/select something that is equipped to serve the needs of their team or the organization. This can result in the team being left holding the baby when certain individuals leave, data loss, security issues etc. In 15+ years of enterprise probably two-thirds of the time I've seen this issues and it has been predictable that it would work out this way, but IT didn't help themselves by pretending their solution was better. When IT tries to learn and adopts the tool, or incorporates the needs then things work out better. But, that's only a third of the time.