4 ms·

I think that may be true if you focus on breadth rather than depth. I work mostly on Windows, so maybe my case is special, but I'm still using knowledge about

I think that may be true if you focus on breadth rather than depth. I work mostly on Windows, so maybe my case is special, but I'm still using knowledge about 8086 machine language I learned 40 years ago when I'm looking at a memory dump from a crash report today. I occasionally dip into web-based stuff and although the top layers are different, underneath is usually HTTP / TCP / UDP / IP. What I learned with Ethereal in 1998 is still pretty useful today. Truly new stuff doesn't come around that often. Maybe it's the difference between thinking about fashion and clothing.

wink 4y ago
I think the timeless skills you mentioned are much more useful for debugging, troubleshooting, and maybe overall architecture though. I couldn't for the live of me create a React app (because I stopped doing frontend long ago) but I can absolutely help with any of the networking, HTTP, or lower level stuff even if I'm just involved with the backend.
- amelius 4y ago
  Yes, and if only 5% of work is architecture and advanced troubleshooting, while 95% of the work is plumbing in the language-du-jour then you see where the problem is.