3 ms·

>> ...don't mix your business & professional lives... Hard advice for the co-founder of the company to follow, I'd expect.

zeveb 9y ago
> Hard advice for the co-founder of the company to follow, I'd expect. If my co-founder used his personal machine for work, or his work machine for personal use, we'd have words. I honestly can't believe this got downvoted to -4. Is it really so insane to say, 'don't mix your personal and business computing'? Is it really so crazy to impose a small amount of discipline which prevents a personal breech from endangering your entire business and all your customers? edit: seriously, will one of the 8 people who've downvoted these comments post a substantive comment? I honestly don't understand the anger.
- wila 9y ago
  Not voted you down, but you are victim blaming. What if it was another piece software? Who says he used it only for private use? and please don't ask about why you get voted down, it derails the discussion (and pretty much always is yet another down vote magnet)
  - ryandrake 9y ago
    "Victim blaming" is a phrase designed to shut down discussion. Why are victim's actions always beyond criticism? In this case, the victim fully documented his opsec mistakes, which is often very difficult to admit to, and likely learned from them. And I think we're all better off having read his account of what he did right and what went wrong!
- watwut 9y ago
  Probably because there are practical reasons for many people to prefer carrying around one laptop instead of two.
  - zeveb 9y ago
    Yes, it is a chore to carry around two laptops — I'm really not a fan. But then, I don't carry around my personal laptop much: I do most of my personal computing on my desktop, and my work computing on my work laptop. When I travel, I'll chuck my work laptop in my checked baggage (carrying the battery with me, of course) and carry my personal laptop on with me. It's a chore, but it prevents the sort of cross-domain spillage we see in this article. I think it's worth some minor inconvenience to me in order to prevent major damage to my company and my customers.

zeveb 9y ago

> Hard advice for the co-founder of the company to follow, I'd expect. If my co-founder used his personal machine for work, or his work machine for personal use, we'd have words. I honestly can't believe this got downvoted to -4. Is it really so insane to say, 'don't mix your personal and business computing'? Is it really so crazy to impose a small amount of discipline which prevents a personal breech from endangering your entire business and all your customers? edit: seriously, will one of the 8 people who've downvoted these comments post a substantive comment? I honestly don't understand the anger.

wila 9y ago
Not voted you down, but you are victim blaming. What if it was another piece software? Who says he used it only for private use? and please don't ask about why you get voted down, it derails the discussion (and pretty much always is yet another down vote magnet)
- ryandrake 9y ago
  "Victim blaming" is a phrase designed to shut down discussion. Why are victim's actions always beyond criticism? In this case, the victim fully documented his opsec mistakes, which is often very difficult to admit to, and likely learned from them. And I think we're all better off having read his account of what he did right and what went wrong!
watwut 9y ago
Probably because there are practical reasons for many people to prefer carrying around one laptop instead of two.
- zeveb 9y ago
  Yes, it is a chore to carry around two laptops — I'm really not a fan. But then, I don't carry around my personal laptop much: I do most of my personal computing on my desktop, and my work computing on my work laptop. When I travel, I'll chuck my work laptop in my checked baggage (carrying the battery with me, of course) and carry my personal laptop on with me. It's a chore, but it prevents the sort of cross-domain spillage we see in this article. I think it's worth some minor inconvenience to me in order to prevent major damage to my company and my customers.