[nec4b]

The frontend feedback is much harder for AI. AI needs to be able to see the page with all the moving parts and sounds and have a bit of sense for the layout and taste in colors etc. I think it much harder for AI to recognize what feels good for the human user. Backend is devoid of that personal touch. By definition you are building for the machine. You have APIs, databases and infrastructure which is logical and easy for LLM to interact with. "All it needs" is curl and it can run in a loop the whole day improving backend software.

[JimDabell]

I think you’re conflating development and design there. I’m saying that development is at risk, I’m not commenting on design. Taste in colours and things like that are design.

[nec4b]

I'm not. I really fail to see where do you see frontend development to be easier for AI to pick up compared to backend. As I said frontend is writing code for an user interface and backend for a machine interface.

[JimDabell]

You think “taste in colours” is a development task not a design task‽

[nec4b]

Knowing that a white font is not visible on white background is not really a design job is it? Calling an API on the other hand requires mostly logic and documentation or do you disagree?

[JimDabell]

Forget AI exists for a moment. You’ve got a team of humans working on a project. You’ve got a backend developer, a frontend developer, a DBA, a platform engineer, a graphic designer, a UX person, a product manager, and a QA person.

Whose responsibility is it to select the colours? You think this is the responsibility of one of the developers‽ You don’t think “having taste in colours” is solidly owned by the designer‽ You think this is a developer task not a design task‽

Aside from that, the specific example you chose is an area where we have deterministic algorithms for judging contrast – we don’t even need AI for that, regular old procedural code can do it.