Great read! I think you should checkout the Research Software Engineering communities, for example US-RSE (I can't post a link unfortunately). It feels like target audience you are writing about.
great post. I feel like the set of people is larger in pure research environments. like you have "only" scientists who previously have stayed away from difficult languages like C and Fortran, leaving those use cases to a small group of people. the arrival of julia and the prospect of writing performant code in a more user friendly way has opened many doors.
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
Feel free to leave a comment! I learning how this blogging platform works together with you :)
Joshua Ballanco
Just a guy with some ideas...
Hey Matthijs Cox! Just came across this post linked from the most recent JuliaHub blog post. Not sure if you were aware when writing this, but I actually gave a talk at the third JuliaCon on this very subject! (The comment engine won't let me link directly, but if you search YouTube for "JuliaCon 2016 The Two Cultures of Programming" it should pop right up.)
Really neat to see I'm not alone in this view :-)