Your designers are going to be looking at the layout; they're not going to notice if it's slow, uses too much memory, is not maintainable, doesn't follow repo patterns, etc.

Do you think it is reasonable to expect a person with an arts degree to know this?

> Do you think it is reasonable to expect a person with an arts degree to know this?

There are plenty of people with arts degrees who know this, and PLENTY of dogshit engineers with CS degrees who don’t

"This works but the app is slow, can you optimize it." I'm not even kidding, most of the time this is all that's needed. Repo patterns don't really matter because humans barely end up looking at the code.

We've had a customer send us a prototype of what they wanted built with AI, and they don't have a college degree in anything. It followed our codebase patterns without any prompting, included tests, and all we had to do was wire up the backend.

> Do you think it is reasonable to expect a person with an arts degree

Of course it is.

The only people who think your fucking college degree determines your knowledge level and ability are teenagers and people who are so deeply untalented that it’s the only way they feel qualified.

This isn’t meant to be sarcastic: have you ever worked for a real company?

As we know from THERAC-25, etc., comprehensively verifying that code works the way it's expected to is not actually very easy - it's perhaps one of the hardest parts of building any system more complex than a toaster.

Thankfully the CRUD app that is being developed by some random startup is not likely to cause as much harm as the THERAC.

Depends on what it's doing.

Worth noting that you've slipped from "checking whether something works is easy" to "well, it's probably not as harmful as a very notable failure if it fucks up."

The bar lowers so quickly.