Loading…
5
Our demo white paper had 12 technical errors that a junior dev caught in 5 minutes
We sent out a threat detection case study to 200 prospects last week before someone noticed the network topology diagram had the firewall on the wrong side of the DMZ, so how do you guys actually verify technical accuracy before publishing?
2 comments
Log in to join the discussion
Log In2 Comments
parker1832mo ago
Used to think a fresh pair of eyes on the final draft was enough, but that firewall in the wrong DMZ would have made me look like an idiot to 200 people. Had a junior dev catch six errors in our specs last month, things like subnet masks being off by one digit and a log retention policy that didn't match our actual storage limits. Now I run everything past at least one person who wasn't involved in writing it, preferably someone lower on the totem pole who isn't afraid to call out dumb mistakes. Makes you humble real fast when a 22 year old shows you your fancy diagram is backwards.
5