I’ve got a confession to make: I love standalone applications. Nothing buggers me more than getting a “DLL missing” error from an executable you’ve got from somewhere. Another problem is when an application requires some external data. Sometimes those files should be placed in relative directories alongside the executable, in the most disturbing case the paths are hardcoded.
Earlier this week we’ve had a nice chat with my colleague about an interesting task, which I’ve found quite entertaining and, most important, a nice interview topic.
The last article was more about general stuff and talks, now let’s get to some programming. To make it interesting for the wider audience, we shall try to make everything
constexpr. Also, I’ll give you some math and explanations.
One of the first tasks we give to all of our interns as a homework is to generate the additive white Gaussian noise (AWGN) and write it to the binary file. In this post, I’d like to discuss this problem a bit.
Disclaimer: this, by no means, is not a definitive description of the whole embedded-specific development. This is just a small good practice about interaction with hardware.