A reaction to https://x.com/shashpicious_/status/2038504244027007277:

The author says coding in an IDE is killing his design taste.

I don't dispute this. But it's not the IDE that's the root cause.

The author simply says that design details that he once obsessed at the start of the process are now ignored later in the process. And to him, the priority is now on designing something that "works" vs. "feels right".

The solution to this is something that I've previously written about: In the age of AI-assisted coding, move design to the tail of your process.

For a designer doing AI-assisted coding, will working in an IDE instead of a traditional design tool change your process? Of course it will. But it should only change the sequence of design, not its significance. If anything, you should spend more time as a designer in this process, not less.

If you're just settling for "what works" and using coding IDE as an excuse for compromised craftsmanship, that's a process problem, not a tool problem.