Anyway it's more complicated than what you make it sound. For instance, if you don't like the culture at Google, you have a choice to not work for Google. And if you don't like the culture in some field of research you also have the option to not join that field of research. For sure, you don't know _exactly_ what you're getting into before you get into academia, but students who are interested in doing a PhD already have some experience -often, substantial experience- of how things go and even of the behaviour of the professors they choose as their advisers, with whom they may have done a Master's project etc. Some have publishe papers, presented posters and joined conferences already from their Master's or degree. And so on. Very few people just stumble into a PhD by mistake.
Wiser now, I know I was wrong about the classes. As this article shows academic code experience does not necessarily mean anything in terms of code smells. That author sounds like how I used to code. I guess some never realized there are better ways, that their code doesn’t have to be so Byzantine and hacky.
But I guess part of the problems with "publish or perish" is that there is very little incentive to keep working on code after a paper is submitted.
Edit: So, I spent a few years in the industry before starting my PhD so code quality was important to me especially because my first proper job was in a shop that did code reviews and all. How did you get to appreciate the need for good coding standards? And how did you learn how to do it right? If you don't mind me prying! :)
Whether it's true or not, I don't know, but it wouldn't surprise me.
Preparing for the next paper?
Switching to Python and seeing enough python code helped too, but I think other widely used languages would have been about the same like JavaScript. Seeing a lot more code than just googled matlab snippets was a big part of it.
Anyway essentially it had become increasingly apparent that “there’s got to be a better way!”
It's not just a computer science problem btw -- it encompasses physics too.
Most people in my field use either IDL or Python (if they're doing data analysis) or C/Fortran (for heavy-duty simulations). Some also know Matlab or Mathematica. I've been trying to convert people to Julia -- it's gonna supplant Python for data analysis and maybe even C/Fortran for simulations.
But that said, am I totally in the wrong on that?