NB, These are the mental rambling of an aged software engineer and AI-sceptic.
Writing computer code is a little like writing a well considered letter/document. In both cases we plan what we want to say, we have to consider that text in the micro (each statement/sentence) and the macro (the document/application as a whole.) But AI interference, I suspect in both cases, disrupts the thought process.
We used to say ‘software developers are not paid to write code, they are paid to think and solve problems’. This remains true even in these days of AI, perhaps even more so. But typing in code is itself part of the thought process and therefore the problem solving. Some might say the code is the ultimate expression of the software design process.
However, AI tools embedded in the Integrated Development Environments (IDEs), whilst some might find them useful, can be a serious distraction and disrupt the thought and coding process.
Before, or after disabling the AI tools, the process was easier. After studying the brief (task description) and considering candidate solutions, you start reading the code looking for the touch points. Identifying what code needs to be removed or changed and building a mental map of the code needed to effect an appropriate solution. You might not set out with a single solution in mind, expecting the existing code to inform your judgement.
