5 ms·
> I started with B2B credits in FC and told him "Fibre Channel uses exactly the same approach as hop-by-hop windows we had in X.25, with the same results…" resu
by Terr_ 11y ago
> I started with B2B credits in FC and told him "Fibre Channel uses exactly the same approach as hop-by-hop windows we had in X.25, with the same results…" resulting in confused blank stare. Further down the conversation I said "FCoE uses lossless Ethernet, which uses PAUSE frames, which are exactly the same thing as Ctrl-S and Ctrl-Q on an async link." Same result.
Or -- to play contrarian/devil's-advocate -- perhaps you should find more ways to convey these timeless logical concepts that don't depend on ancient war-stories or shared-suffering involving "dead" technologies? I'm not saying you have to turn your baseball cap sideways and start saying "dawg", but effective communication means you need to update your metaphors and analogies at least once in a decade as your audience changes.
If the past contains useful lessons, sometimes the best thing you (i.e. direct contemporaries who were there) can do is to isolate the most important, broadly-useful parts, and cut them loose from the gnarly matrix of specifics. Then you can teach the lesson over and over in a way that doesn't depend on audiences who worked with Tech X from years Y to Z.
- vezzy-fnord 11y agoTo be fair, you have a point. Most of this knowledge is buried in poorly indexed or in some ways restricted vaults of papers in the ACM or various foundations, institutes and research universities. Some form of search engine for digging up prior art in CS and systems research is in order. A one canonical and easy to use resource for programmers and architects to look up before they go off reinventing flat tires.
- hueving 11y agoThis can't be overstated. If you dump a pile of acronym diarrhea on someone from a bunch of dead technologies and get upset when you get a blank stare, it is 100% your own fault for lacking the communication skills or abstraction skills to separate useless jargon from important concepts.
- deleted 11y ago[deleted]
- brianmwaters_hn 11y agoThis is an attitude I see more and more of today, and I think it's unfortunate. The slides in question aren't "a pile of acronym data;" they're made of lingo that would be recognizable to anyone who works in the field of networking - even if they don't understand the specifics of the protocols in question. At any rate, the author's complaint isn't that "kids these days" haven't heard of all these acronyms, it's that they haven't learned any of the technical details behind those acronyms, and that those details are still relevant. Finally, I have a bone to pick with the "it's the older generations' responsibility to educate the younger generation" idea that I hear so often. At the end of the day, it's everyone's own responsibility to educate themselves, and we all know there's plenty of materials available for that.
- nickpsecurity 11y ago"Finally, I have a bone to pick with the "it's the older generations' responsibility to educate the younger generation" idea that I hear so often. At the end of the day, it's everyone's own responsibility to educate themselves, and we all know there's plenty of materials available for that." I'm on your side of the discussion overall but that's unrealistic. It took me a decade to get so much of this knowledge and wisdom out of papers on programming, OS design, networking, security, etc. I just found some more foundational work in past months that should've been in every classroom for its relevance but nobody's heard of it. The problem is that the stuff is scattered all over the place and not in pure form at all. There's books, papers, brochures, lectures, etc. These might have good details, fluff, or a varying mixture of each. Many great works can only be found behind paywalls (IEEE, ACM). Others are on academic sites, specific blogs, or places like CiteseerX where you have to know what you're looking for ahead of time. Our field is anything but a clean, integrated presentation of what really mattered, matters, and might matter. It's a huge, scattered mess that we expect new crowd to just automagically sort through and discover necessary stuff. Prior generations certainly have some responsibility to make that easier rather than harder. I do my part with posts here and elsewhere directing people to specific techs that solved (or nearly so) the problems they are talking about. Need a more thorough solution, though, for the various sub-fields of I.T. before I'll blame the newcomers for prior generation's mess.
- nickpsecurity 11y agoI'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 ago