31–40 of 83 posts
Some of these conflict: > Encourage a complex dev setup: running a service mesh with a dozen services at a minimum. ... > Build in-house versions of almost anything that's not a core competency. So if you need functionality A, B, C ... H, what do you do? Do you build them all in-house or do you have 9 different services each providing the functionality required?
> CIA produced a fantastic book during the peak of World War 2 called Simple Sabotage. Not quite right. The Office of Strategic Services did that. The CIA was created only in 1947 several years after the end of the second World War in 1945.
Excellent. Continue the good work.
The major thing that springs to mind here is I've never seen a compelling reason to believe that the original CIA suggestions actually worked. In my experience workers like that exist naturally and organisations are great at just sidelining them. I think in that section the CIA was just writing a listicle that sounded good [0]. The way to cripple a company is to get bad people promoted into management and have them o…
Oh yeah, this one really is fun. We used to joke that the CTO of one of the companies I worked for made a killing as his second job was for our competitors. Turns out the dude has been doing that for about 15 years between various places and now is about to retire, blameless in the eyes of everyone who doesn't understand what happened.
Duplicate (15d) https://news.ycombinator.com/item?id=40538920 and (5m) https://news.ycombinator.com/item?id=38707591
maybe merge the threads?
Clever framing of the authors own biases. I'd argue that for at least some of these, the opposite behaviour would be the true sabotage.
> CIA produced a fantastic book during the peak of World War 2 called Simple Sabotage. Not quite right. The Office of Strategic Services did that. The CIA was created only in 1947 several years after the end of the second World War in 1945.
> 4. Bring up irrelevant issues as frequently as possible. Excellent. Continue the good work.
Earlier quoted context omitted.
Oh yeah, this one really is fun. We used to joke that the CTO of one of the companies I worked for made a killing as his second job was for our competitors. Turns out the dude has been doing that for about 15 years between various places and now is about to retire, blameless in the eyes of everyone who doesn't understand what happened.
Doing what? Getting paid by a competitor to destroy his current company?