My Desk is an Optimal Container

When you do informatics codes, sooner or later you are concerned with data containers and their associated complexities for inserting, getting, sorting or whatsoever. Some of them are lists, vectors, map, set etc...

Sometimes you use a container for some stuff and you get unexpected low behavior. Then you go into your manager's office and ask for complexity of what you are doing. By the way, he convinces you that you are the last of the idiots of computer scientists (thing I take as an honor), and you just change your container.

But the people who are working on containers (have you ever looked to the STL (standard template library) to see how containers are implemented ? Not sure those people are human...) should try to investigate how my desk is working. It is very messy, there is a lot of stuff on it (even food sometimes) but I always find my items in a constant time.

Well, almost always. Notably when someone put it in order (presumably the housekeeper or some terribly insane industrial spy). Then we get the worst case complexity, and I seek over the same pile of thing all over again being sure that it has been here. But nope. My mess is an ordered one. Her (or his?) order is a chaos to me.

Note that (see the picture) some people who are apparently working on chaos theory (and practice ) apply the same methodology for their blackboard !!

Comments

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

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 the tissu

Robust Stable Objects Deformation

In this entry, I'll briefly speak about computing robustly the deformation on a given object represented by a Finite Element mesh. There are a handful of methods to do that more or less robustly, and I'll just discuss them, with a speaking a little bit about their distinctive aspects. Classic lagrangian formulation The most used one in industrial commercial packages (like abaqus, ansys, etc). This is simply a linearization of Green-Lagrange strain tensor and deriving it to get the proper residual and stiffness matrix from one single Newton step. This method is absolutely rigourous, meaning that as long your mechanical behavior is well captured by the strain model you'll get reliable results. However it has two main drawbacks: first you have to be careful when applying new forces or constraints and do it incrementally otherwise you may really blow up your model. For instance applying too much force will cause some elements to invert which won't be re-inverted thanks

New Horizons

Search This Blog