from Hacker News

Hi, I am working as embedded software engineer. We write very large amounts of unit and functional tests and it suits me and I understand where the need comes from.

Unfortunately, from time to time I'm told by my boss to write glue code for devices that we haven't received yet and that are poorly documented. I wouldn't mind writing code like this if I was writing some kind of integration test at the same time, but I don't write such a test. Therefore, the only feedback I get that my code works is the compilation status - and that's the problem, it's very hard for me to motivate myself to write such code.

Do you know any interesting articles on this subject, so that I can use them to persuade my boss of this type of work? Or maybe you have a different opinion and you don't mind writing code this way? The last question is: what English idiom to use to describe this type of work? I'm not a native English speaker and I don't know how to look for inspirational articles on this topic.