On my quest for a good Flask book, I saw this book from Tarek Ziade. We are more or less of the same generation, both from France and he wrote a far better introductory book to Python in French than mine. He also founded the French Python community (AFPY), so I always had a huge respect for the guy. And the book was appetizing.
Sometimes Visual Studio and Xcode projects just get out of hand. The private project I’m working on has 130 subprojects, all in a single solution, that’s just too much to display in one window. And then I learnt that projects can actually be moved to folders, just like what is possible for files in a project (so you don’t have Source Files and Header Files, but something custom, for instance following the file hierarchy).
They are activated differently, and it’s sometimes not as straightforward, but it works great once it is set up. And as this works for Xcode projects and Visual Studio projects, I was really eager to sort out my Audio Toolkit main project, so it will be the basis of the tests here.
There are a lot of books on software project management best practices. But usually, they are not guides to work with people. And it is people who make projects, not money or computers.
A few years ago, I mentioned that the registry pattern was my favorite pattern in Python. Well, it may also be my favorite C++ pattern.
TortoiseSVN is one of the best and well-known GUI for SVN. It has also given birth to parallel projects for all the other VCS (TortoiseHG, TortoiseGit…). It’s only fair a book is dedicated to it.
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.
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.
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.
Debugging software is one of the complex actions in software development. It’s not just about using a debugger, it’s about how do you manage bugs. This book has a pragmatic (amazing, don’t you think?) approach on this matter.