Quote:
Originally Posted by martin417
As an engineer, I work to engineering specs. If I meet those specs, I expect to be paid. You can imagine that I might be a wee bit upset if I were to design a product that meets the customer's specs, deliver that product, and be told "I'm not paying you because the product didn't do what I expected it to do". If your specs are not written clearly enough, that is your fault, not mine.
|
This is a good lesson for the students and for mentors that do not typically address similar challenges at work. Think more like an engineer that owns the company or an engineer helping to form a response to a proposal. Taking a risk (being able to satisfy) a vague requirement from a customer is NOT a good idea. You very well might not get paid and it does not matter if one is correct or not. In this case, the customer (FIRST) supplied a vague spec but did provide a compliance test.
If the specs are not written clearly, it is ALSO our responsibility to request clarification or we risk NOT getting paid (or tripping the sensor).