New Horizons

As engineers, we like to move things forward and, for those who have a little bit of experience (like me), having to work with legacy code can be a huge set back because we know it can be long, painful and slow-paced. But you don't have to make it harder that it needs to be for you and your team! Below are some common mistakes that occur when working with legacy code and possible ways to overcome them. 1. Should you really use it? That's probably the first and foremost question. Is it really necessary for your application to tap into this legacy code? Have you done extensive researches to see if there isn't a more modern library out there, with better licensing, design, architecture, library initialization, newest code features, documentation, unit tests, whatever than this old piece of code which is on your shelves? In case there is, ponder with caution the possible consequences of any choice, using as many criteria that you care for! Remember that this is an important cha

Observation I am terrible at keeping things going.  And this blog is no exception. I realized my latest entry was  8 years old. Shame!  Now, I am wondering why I even wanted to start this blog in the first place. But what's more important now for me is: why would I continue and commit entries in this blog right now? For what purpose ?  Why ? The answer came up straight for me.  I want to make this blog a way to  share  my own experience to a broader audience than my own little circle.  With the motivation that it might just help someone. For who? Someone who is like my younger self and who just might benefits from the knowledge of a more experienced one. But this may be misinterpreted as 'when you grow older you get wiser' which we all know is not exactly true [sarcastic laugh].  Sharing my own experiences, good or bad, my struggles or successes with technology, science, management, colleagues, creativity etc... might just help somebody! That's a powerful motivation