Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Ask HN: Writing embedded code without tests and without hardware?
2 points by dsab on June 19, 2023 | hide | past | favorite | 4 comments
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.



Do you have someone in factory who could run code for you?

Send them some stuff, put as much logging, sniff all network traffic... And make sure to cover your ass, your boss ordered this, he should have a full responsibility!


No, this is a prototype device.

My question is more oriented towards finding opinion-forming criticism of such a workflow, rather than protecting against the effects of a potential project failure. The code I was asked for is just a small fraction of our code base.

Yesterday I found this thread on HN [1] and I am impressed by the interesting topics that article raises. I wonder if similiar criticism exist somewhere over internet about mentioned workflow

[1] https://news.ycombinator.com/item?id=36380711


You are arguing from engineering point of view. Even if you come with very solid case, it may not work. Reasons for this decision may not be engineering related, and any reasoning you come up is simply irelevant!

Make sure there is paper trail. If it is medical device or something life critical, and testing is actually legally required, do what you have to do. Maybe start looking for a new job.

But it is your boss decision, not yours!


I forgot to mention: my boss argues this need by the fact that the management keeps asking him if we have already integrated it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: