Why not blogging?

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 for me to share and continue making those blog posts but with a different intent.

In a nutshell I would like to:

Share experience on stuffs that worked for me or didn't, trying to analyze why
Summary of stuffs that helped me (books, talks, videos) and why
Discussing with others about their positive or negative experiences and retrospect
Figuring out the best ways to share what I believe to be the most insightful

Building a Better World

I truly think we should all try to make things better than they are. That's a beautiful statement but how to make it happen for real is often more difficult! I just want to make baby steps in that direction and start by trying to build on top of what I learned to be useful. It's only the first step that count.

I clearly hope that this will bring a lot of positive change!

Comments

Shear waves, medecine and brain

Yesterday evening, too bored by what TV was proposing to me, I decided to watch a conference of Mathias Fink , a french researcher working on multidisciplinary application of waves. Specially shear waves. Here is a brief summary of his talk. In solids, waves have two principal components: compression waves (P-waves for primary) moving in the direction of propagation, and shear waves (S-waves, for secondary) that make ripples in the plane orthogonal to that direction. Since compression waves propagate in the direction of propagation, they move faster than shear waves. Usually ultrasound equipment in medicine only use compressional waves. But since human tissues have a high bulk modulus, the P-wave speed is relatively constant (around 1580 m/s). Human tissues are very stiff if you apply isotropic constraints on them (like pressure of water). However M. Fink and his colleagues proposed a new way to investigate human tissues by first sending a strong compressional wave in ...

We're not playing dices !

Software programming and design is an amazingly complex task. Specially when it concerns numerical applications, that generally require optimization to get results in a reasonable time. For that purpose the basic pattern is usually to write the code as simple as possible, debug it and when it works to begin the optimization process. This asks for some nerves, and patience, two things I usually don't have in real life , but for programming yes. This design pattern makes sense because we are doing things really sequentially. You first wrote some c++ class and then add some feature progressively, and when you come up with essentially different concept (I mean a concept that should be well separated from the first one), you write an other class and so on... Usually the class-writing process follows the solving process you have in mind. For instance you have to make some initialization on your model first, then you declare some variables for the computation, the computation then f...

5 Tips to work with legacy code

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...

New Horizons

Search This Blog