I have a new junior getting some pointers from me. I feel like posting the Bernie meme.

If you are a CS professor, and reading this, read closely:

• Teach them where the source docs are.
• Teach them to find source docs on every topic you cover.
• Have them read the RFCs where appropriate.
• Have them implement what they read.
• The book you wrote is not a replacement for that (yes, there are exceptions, but you are probably not Knuth or Stevens, etc...).

I've been working as some kind of project lead, architect, manager, SME, etc for 25+ years in this field. The one thing that chaps my hide is the amount of graduates from every level through PhD who do not know basic concepts and have no idea where to find the source material.

I should not have to teach someone with a MS in Networking how to filter their own AS in BGP, or why it is important. Because they should have been exposed to the RFCs and implemented them enough to find that source AS poisoning is a basic problem. Showing them where this RFC is, and being able to track down mailing list or journal entries on this topic, should never be unvisited territory for an MS in Networking.

I should not have to teach someone with a BS how to subnet. It doesn't matter if their focus is languages, databases, or robotics. Everything touches a wire eventually. They should know the basics.

The guy with a HS diploma and some military experience should not ever have to teach your former students the basics. Especially if they have an "advanced" degree in that specialty.