> But the author gave a project idea where most of the project was figuring out UX concerns of non existing users. > If you do UX then you need users to actual

> But the author gave a project idea where most of the project was figuring out UX concerns of non existing users. > If you do UX then you need users to actually test what you write on. No offense to azhenley but why do you expect any different? They asked a CS professor for a project idea. How many CS professors have project ideas that come with UX case-studies? How many CS professors have the resources to guide students to coordinate actual UX tests outside of a research grant? It's an outside-of-class project. It doesn't need a compelling use-case. > It is a horrible project no matter how you view it. Too harsh, this has yet pedagogical value. Because, you know, they are students. Bulk (if not all) of the work you typically do at school teaches you things even if they are not portfolio-worthy. > Building out a lot of UX features without users is an anti pattern, better write a bare bones implementation first and then work from there. I agree with the thought but, again, this isn't real-world software engineering. I feel I can't emphasize this enough. Maybe these students have been writing from-stdlib-up CLI tools ever since and their teacher thought it's time to expose them to APIs other than stdlib. Who knows. Might as well raise pitchforks that finding the most valuable customer for Northwind Traders (LLC) is counter-productive because the database is outdated. Better gather data first, why not normalize the schema while you are at it, so you can stream it to the cloud and get a better analysis than plain SQL. (Calm down, Northwind is a sample database for education purposes.)