> if it’s your job to know things[,] GPT is coming for your paycheck > if it’s your job to discover truly novel information, GPT can’t compete with you It's n

> if it’s your job to know things[,] GPT is coming for your paycheck > if it’s your job to discover truly novel information, GPT can’t compete with you It's not only the price of the part; it's also knowing where to put it. Labor is the bulk of the cost. GPT as an instant aggregator of tribal knowledge would be grand: hook it up to Slack, git, Jira, and corp wiki. Set up a /gpt chatbot and ask all kinds of stuff: * /gpt what did we do yesterday, what are we doing today * /gpt what do they mean when they talk about event sourcing; why would that cost more story points * /gpt which schemas have a column that contains PII * /gpt which builds are failing consistently Another idea is, for siloed teams, each person interacts with GPT if that's more comfortable. Then any person's query is answered by the AI. Regardless of LLM capabilities, there may always need to be a human to (blamelessly review post-mortem with) or page. As much as ChatGPT--or future tools--help automate typing language, hierarchy almost totally ensures a "person of appropriate role and responsibility" is there.