@inthehands the first thing I bring up in my ai coding workshops (I don’t give all that many, but they’ve been spanning from 2024 to now) is to focus on engineering quality and using a human centered “communication analysis”. If you can map who communicates with whom in order to build the final software (which includes everybody from user to customer to support to design to qa to management to developers), then it becomes much more easily apparent where to use ai tools. It can be the main code path but it’s usually much more effective to build better ticketing systems or design experimentation tools etc…
It also means that you can be an “ai assisted developer” without using any ai tools yourself, because you now get better tickets due to a vibecoded chrome extension that attaches the right internal docs, or something.
Of course not many large scale companies will change their approach, but I like to think that there’s a few teams out there who get to follow that framing and find renewed purpose (I know I do) by seeing how much quality can be improved by reshaping the narrative around the technology.