Those of you who work in an organisation that makes heavy use of GenAI coding assistants: how did you educate your developers that if they automate sweeping changes to user-facing code, they MUST also automate the corresponding sweeping changes to user-facing documentation?
Or have you identified a strong correlation between embracing GenAI coding assistants and not giving a flying fuck about user-facing docs?
@xahteiwi It works better for markdown, but from what I see, the agent I'm working mostly with (claude) is also capable of editing other docs format that are not Office formats like DocX. If your docs live in a wiki like e.g. Confluence or MediaWiki the agent could do it if there is a sufficient capable MCP. Also at least claude is able to work with multiple git repositories.
The funny thing is, the better documented and accessible the processes are the better the agents are.
@hikhvar Consider that screenshots are typically cropped, or include highlights, or blur parts to hide information that is private or uninteresting, etc. So, automating such screenshot updates is an "interesting" task.
Consider further that you may have hundreds of screenshots that are all affected by a change of one line of CSS, rendering your "let's ask a human" approach impractical.
And sadly, not thinking about this sort of thing is exactly what I mean by not giving a fuck about docs.
Florian Haas
Christoph Petrausch
Lars Marowsky-Brée 😷