Does your code need a performance boost? Ask us!
Photo by Alenka Skvarc on Unsplash
We hope you are relaxed and enjoying your holiday period. We really do. So it may seem ironic that this blog post is about being in a hurry. Kind of. Let me explain myself:
Apart from the kind of hurry you may experience when you are afraid of missing a train, or the oppressive feeling of fearing not meeting a deadline, we are very familiar with another type of hurry: the one caused by slow code.
Did you experience this? We certainly do. And our engineers proposed some solutions too. Using more efficient programming languages, or letting your graphical processing unit (GPU) do the hard work, are classical solutions for these problems.
Writing testable GPU code, by Ben van Werkhoven, reminds us that using GPU programming is no excuse for abandoning best practices. In particular, it is very advisable to use unit tests. Here he teaches us how.
C++ Compile-Time exceptions, by Patrick Bos, sheds some light on the notoriously obscure topic of templates in C++ and their cryptic error messages. Couldn’t these messages be more readable? Patrick says yes, and shows us how.
Why use an FPGA instead of a CPU or GPU?, by our former colleague Atze van der Ploeg, delves into something some of us software engineers tend to forget: the hardware side of things.
What about you? Do you have something to share? If that’s the case, feel free to use the comments section below. But, if you want to enjoy a hurry-less summer, feel more than free to wait until September.
