If the software should let me do X, I can click around and confirm that I can do X. I think most people would consider that the definition of “works,” rather th

If the software should let me do X, I can click around and confirm that I can do X. I think most people would consider that the definition of “works,” rather than the quality of the code, the validation that the proper thing was built, etc. Looking at the code can tell you whether it was “implemented properly” - or at least, if it was done reasonably competently. Relationships, though, can help you know if that properly implemented code was likely a fluke or not. Does the person ask questions? How do they ask questions? How do they communicate? How do they capture requirements? How do they push back when something seems unclear or unwise? etc.