I see it differently: if you’re not willing to consider how you could be better/faster/more productive with AI, you’re unwilling to adapt to the future, and not flexible enough. You’re going to slow down your employer. Most business text does not benefit from a user spending time on phrasing it, it’s not literature.
> if you’re not willing to consider how you could be better/faster/more productive with AI, you’re unwilling to adapt to the future, and not flexible enough. You’re going to slow down your employer
That's for their manager to judge. You can maybe share your opinion on the matter, and let them decide. Until then, collaboration is more important than your personal IC work, and usually more effective than 1 person working heads-down and another struggling.
Newer devs invariably discover that the "write the code" part of the job is just a small part of being an engineer, and less value-added than collaboration. Big successes are achieved when you make others successful, rather than isolating yourself and focusing only on your own work and your own success.
AI is not a suitable substitute for collaboration – we are discussing the case of sending AI summaries (1 human asking, 1 LLM answering through a meat proxy), instead of collaboration between 2 humans
