Great post. But after reading this I am confused about the definition of 'scientific coder'. Are there truly developers that want to, and then are allowed to by their employer, to dive into the science behind what they are 'developing'? It seems like two completely different worlds to me. I do understand it the other way around though, it is really painful to read code written by some scientists even though it 'works'. I am in academia but I spend a lot of time trying to improve the quality of my code. Mostly out of the frustration I feel when I read somebody else's code and I don't understand it. Not because it's difficult but because it's poorly written. I don't wish that on anyone