Hello. I noticed Steve is writing a book about his time at Google: I have a lot of good stories saved up that I’d love to share. Google corporate didn’t much c

Hello. I noticed Steve is writing a book about his time at Google: I have a lot of good stories saved up that I’d love to share. Google corporate didn’t much care for my blogging, and even though they never outright forbade it, I received a lot of indirect pressure from various VPs. So eventually I stopped. Sad. But that’s not where my mind’s at today. Those stories will have to wait for my book. I can completely relate with this. I used to work at S2 games on Dota 2, and at Matasano as a pentester. Both cases led to a lot of interesting stories, and I have often thought of writing a book collecting these into a single work from the perspective of a programmer, simply putting thoughts to paper. There is a book, With the Old Breed https://www.amazon.com/Old-Breed-At-Peleliu-Okinawa/dp/0891419195 https://www.amazon.com/Old-Breed-At-Peleliu-Okinawa/dp/08914... It's the perspective of a WW2 solider, and simply chronicles events one after another with very little personal flair. Simply a linear sequence of events. The end result is fascinating, and works like this seem rarely published. My question is, how can I do this without ruining my career prospects? Is that a valid concern? All of my stories are generally positive, and I don't think any of them would cause drama. I just want to reminisce about the good times, and collate the perspective of fellow devs and pentesters. Obviously, sharing specific details that were covered under NDA is out. That's not what this is about. But I do want to be careful not to gain a reputation as someone who will reveal company secrets if you hire me. Any tips? It's a scary prospect, but it seems worth doing.