[Brozilean]

I basically realized this when I was at an internship talking to a buddy about a compilers course I could be taking and his language he was making for fun. He was talking about a couple topics I'd probably go over in the course.

Then a more senior coworker came over to join the convo and mentioned a few similar words that were clearly jargon related to compilers etc. He spoke with such confidence that I didn't want to admit I didn't know about them, but figured I shouldn't be ashamed at not knowing stuff. I asked him what it meant and he said he didn't really know and wasn't entirely sure. ¯\_(ツ)_/¯

[hinkley]

I once mentioned off-hand that I was a SIGPLAN member so that I could get the proceedings and learn about future tech in compilers and JITs and GC.

One person did a double-take, looked at me, and said, "You can understand those?" I knew exactly what he meant, and consoled him by saying "only about 2/3rds," at which point all of the tension drained out of his shoulders. I had communicated that yes, some of it is just bullshit not fit for consumption, and that he was not an idiot.

As a Feynman dilettante, if you can't have a human conversation about a subject (note: conversation, not 'curing cancer'/winning the Nobel) then you don't really know the subject. Or perhaps more generously: It doesn't matter if you know it because you can't pass that knowledge on. You are dead end as far as human progress is concerned.

I suspect Tech people feel this more than pure researchers, because we know that in a couple years we will be focusing on something else, and 5 years at most we will be gone. If we haven't passed on our knowledge, then there will be consequences that are readily apparent. In academia you get so many opportunities to connect and if you connect with 5 people, you probably feel like your work is done, and you forget about people like me who regret ever encountering certain teachers because they set me back or in one case, put me off a course I believed I would stay to the end.

Me, I have 10-15 people not of my choosing and I have to connect with 2 and 1/2 of them. It's a tempest in a teapot.

[laurentdc]

I've noticed that "I have no idea" as an answer is one of the boldest statements you can make in the workplace.

Most people are playing fake it till you make it most of the time (until shit hits the fan, then incompetence becomes dangerous and you get to see who's been swimming naked)

[thevirtuoso1973]

You and your senior coworker are allowed to not know things, and furthermore, allowed to talk about things that you don't know much about.

Was your role or the senior person's role related to compilers? You don't have to authoritatively know something to talk about it, and I never assume anyone knows anything authoritatively if they talk about it nonchalantly.