My problem is my coworkers always misinterpret my reasons for writing tests. they think i must want to make an artisimal work of art, or they think I’m challenging them in some way. in the PR they don’t take the scope of the project into account and start pitching to my boss edge cases i didn’t test for. is it an organizational problem, sure. but tests are not written into a proposal and are billed as engineering hours. get it working and ship it it’s our business model, making tests a niceity.
My problem is my coworkers always misinterpret my reasons for writing tests. they think i must want to make an artisimal work of art, or they think I’m challenging them in some way. in the PR they don’t take the scope of the project into account and start pitching to my boss edge cases i didn’t test for. is it an organizational problem, sure. but tests are not written into a proposal and are billed as engineering hours. get it working and ship it it’s our business model, making tests a niceity.
/rant
Admittedly, there is a bit of
Them: “It works”
Me: “I don’t believe you. Prove it”
that people might not like. But usually the people who take the most offense are the worst coders.