| ▲ | nslsm 5 hours ago | |||||||
It's very easy to know when code is wrong: it doesn't work the way it's expected to. So you explain to the AI what's wrong and the AI fixes it. | ||||||||
| ▲ | only-one1701 5 hours ago | parent | next [-] | |||||||
This isn’t meant to be sarcastic: have you ever worked for a real company? | ||||||||
| ▲ | esafak 5 hours ago | parent | prev | next [-] | |||||||
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? | ||||||||
| ||||||||
| ▲ | thunderfork 3 hours ago | parent | prev [-] | |||||||
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. | ||||||||
| ||||||||