Developing your own DSP framework
Would You, Could You, Should You?
For any company creating digital audio devices, there is always a time when a fatal decision must be made: shall you create your own audio framework, use something pre-existing, or maybe outsource it to a cheaper team in a different time zone?
In this talk, I will give an insight of the considerations that led my current employer to develop its own framework, starting with general design aims and possibilities.
After dealing with the general aspects, I will focus on the technical side and provide concrete examples that illustrate the possibilities of following C++ and good software practices to make your code safer, speeding up your development and accelerating your time to market by re-using code between projects and allowing different teams to work in parallel.
Finally, I will summarize some common problems that can be faced when developing your own source. And more importantly, how to be clever enough to survive the fall thanks to a bit of that over-engineering that you frowned upon initially.
Miguel Jimenez-Carvajal
Software Mad Hatter with almost 20 years of experience in R&D, working across different industries (transport, telecoms, air traffic control, medical) and stack levels, from desktop to embedded c, and anything in between. This has given me regular exposure to different languages, mainly C, C++, Java, Matlab, python.
For the last 7 years I have been working for Kef Audio, developing internal desktop tools, embedded systems, and doing a bit of devops. I am currently juggling management and technical work depending on the hour as Head of the software department in R&D.
https://www.linkedin.com/in/mjimenezc/