Comment by atoav

As someone who programmed a campus identity managment service from scratch, both front-/backend without a trace of LLMs, as it was a while ago:

Yes there is such a thing as an inactive student and it is quite imortant for such a system to differenciate the two. However it is not really important to display it to the user, since that isn't really info someone inactive would see anyways.

And this is part of the problem: LLMs have this tendency to spill the beans (=implementation details) into frontend code. Aa someone who had both hats of the frontend and the backend guy, I still think LLMs aren't producing optimal results here.

Ideally you backend code is elegant, extensible and exactly what is needed to get the job done efficiently and reliably. The frontend however needs to be 100% thought from the perspective of the user (and sometimes from the perspective of a malicious attacker). LLMs still get mixed up with that split.