3 ms·
I'll give you that. Someone called me on this in a security discussion by recommending people get a glossary. The terms were all recent and modern in this case
by nickpsecurity 11y ago
I'll give you that. Someone called me on this in a security discussion by recommending people get a glossary. The terms were all recent and modern in this case but mainstream crowd apparently wasn't aware of any of them. So, I went back and explained each one so the reader would have context in the previous post. The vote count indicated that worked better.
That's happened enough that I sent out a recommendation to a bunch of people in high security industry to straight up drop our terminology when addressing a wide audience, look up what they call everything we talk about, and go through a major revision process on each post to translate it to their language. Might be able to get adoption of some of the techniques that already solved so many problems but just have no awareness or willingness to understand how they're normally presented. Not sure how many are going to do that rather than say "it's not our fault they didn't Google (topic) 101 to get the basic terminology and foundations."
I feel revision and avoiding acronyms particularly will help us but transferring the wisdom will still be an uphill battle. Especially with the Silicon Valley startups...
- brianmwaters_hn 11y agoTotally agree with everything you're saying, but I would point out the the article is not about addressing a lay audience, it's about addressing network engineers who are supposedly lacking some historical/technical knowledge of their own field of work.
- nickpsecurity 11y agoI expect network engineers to understand what they do day to day. Do they really need to understand the whole history of the field to do that? Mostly not: just specific things necessary for their jobs. Our economy and resources are sort of rigged in that direction. So, we might need to use a preemptive solution where we present various principles, tactics, pro's, and con's to them rather than a full history lesson they'll think is useless. Ideally, they'll learn it all. I've learned the world is rarely ideal. Need a practical alternative to ideal...
- mentat 11y agoThat's just it, those who do not understand history are doomed to repeat it. By not learning about it they will make poor day to day decisions which lead to the exact same mistakes decades later.
- nickpsecurity 11y agoIt's true. Most of history is probably useless, though. So, you need to know which parts to learn. Most people getting into network engineering don't have 5-10+ years to figure that out on top of work, family, fun, etc. So, the most relevant parts of history of a subfield should be accessible in a way that doesn't require that level of effort. That's like making people studying mathematics, mechanical engineering, etc look through every ancient manuscript and writing to unearth the best principles and techniques for their field day-to-day and project-to-project. Makes no sense. And this is coming from a guy whose gone to the extreme of studying everything in several sub-fields of IT: over 12,000 academic or professional papers in my archive on top of the books, etc. Skimmed most, fully read some, and re-read a tiny few (gold mine). Took a long time to get to that tiny few. No justification for that except that generation made little to no attempt to get that stuff to me in an accessible way. And now my generation is repeating the mistake for the next. Or do you really think it's optimal that every learner have to spend 3-5 years per sub-topic digging through the whole of knowledge on it just to find the few things that might pay off?
- ak217 11y agoDo you keep track of your gold mine in a list somewhere? Would be interested in looking at it. :)
- nickpsecurity 11y agoBefore I can wholesale share it, I have to go through to figure out which ones are locked in to ACM/IEEE to exclude them from the list. The rest are [mostly] disorganized because I started pulling them in batches of 20-100 a day. So, there's a little work to be done there before I can publish them. I've saved your username and email somewhere so I can notify you when I get around to doing that. What topics are your core interests? My main focus is high security IT and software/system verification with a number on programming, hardware design/synthesis, software engineering, networking, databases, filesystems, OS's, and high-performance computing. Might send you a few samples of each in your interest to let you see the kinds of things people overlook. I should have time this week.