Michael MacTaggert is a software developer looking for work, host of a law review podcast called Amicus Lectio, and a moderator of Programming Discussions (invite.progdisc.club). Follow me on Twitter!
KT is best when the host is also explaining things about the project, and not essentially speaking documentation. The person receiving it should learn the context of why things are the way they are and the team's stance on the project's components. Could this be conveyed in documentation? Sure, but it's easier to convey the emotional side of things in person than it is in text.
If you think about it as an opportunity to interact with the presenter and get their gloss on why, it can be a bit more interesting and valuable.
For my part, "KT" usually meant waking up early and listening to someone drone on about something I knew I would never ever interact with and them resisting attempts at being personable. As much as it is theoretically valuable, I would prefer never to hear the phrase again.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
KT is best when the host is also explaining things about the project, and not essentially speaking documentation. The person receiving it should learn the context of why things are the way they are and the team's stance on the project's components. Could this be conveyed in documentation? Sure, but it's easier to convey the emotional side of things in person than it is in text.
If you think about it as an opportunity to interact with the presenter and get their gloss on why, it can be a bit more interesting and valuable.
For my part, "KT" usually meant waking up early and listening to someone drone on about something I knew I would never ever interact with and them resisting attempts at being personable. As much as it is theoretically valuable, I would prefer never to hear the phrase again.