Sometimes, we need a fun book to free the stress from long months of work. I was (and still am) in this position with a complex work and different side-projects (like scikits.learn), and I appreciate a book that can bring a smile and some humor.
Did you ever attend an unfruitful meeting? I have. I also prepared such meetings, to my shame. The issue is getting people to communicate and to create during these meetings, and getting the mood to this point is not an easy task.
I didn’t think this could deserve a post, but a friend of mine asked me about how to wrap a C++ class in Fortran, which means wrapping it in C.
I thought of one obvious way, but there is also a typesafe version that should be used.
After my review of Intel Parallel Studio and then my post of Advisor Lite, I had the opportunity of doing the beta of Intel Advisor and then the final version of Parallel Studio.
The review will not be as thorough as the one on Advisor Lite, because Advisor is an update of Advisor Lite. It has some additional features, and that’s what I’d like to focus on.
I won’t dwell into the details of Intel’s new offer, suffice to say that Intel took the opportunity of changing some offers name and of incorporating some parts of Parallel Studio in its other products, and of course on Linux (which was left alone until then).
If there is something we all should do in our jobs, it would be innovate. But sometimes, although we (try to) innovate, we don’t see the fruit of this hard work. Why? Is there something not right with the way we innovate?
Scott Berkun has released his second edition of the Myths of Innovation, and it tries to answer to these questions and more.
There are some effects that are simpler than other. Digital ones are generally easier than analog ones, and purely digital filter are also easier than digitally-transformed analog ones. Linear filters such as passband, cutband, … are easy to digitally design, chorus can be achieved through some spectral computations, delay and reverbation are computationnally expensive but easy to code.
It said that analog devices have a unique sound that digital devices cannot achieve. In fact, much is due to the simplications that occur when digitizing an analog device. One of the most blatant examples is the overdrive, which I took from Simulanalog.
It has been a few years since I’ve learned about DVCS (Distributed Version Control Software), and there are always some battles between the three main containders. The Centralized VCS war was won by Subversion, but the DVCS is far from over. I had the chance to use those three tools for work, free-time and open source projects. I do not claim that my time using them is enough to have a solid conclusion, but for me, there is a clear winner.
Once more, a Pragmatic Bookshelf book, this time on release management. In this book, I expect a wide intersection with other books on agile processes, but perhaps with less depth than other books.
Today, I encountered an issue with subprocess calls. I was faced with the need of redirecting output streams from a subprocess call to the standard outputs and simultaneously to log files.
Testing is one of the basis to create robust and correct code. O’Reilly has published in its “Beautiful” series a lot of books on different parts of the development process. This is the testing part.