5 ms·
Large parts of this post are naked apologism for grave aberrations in computer science research, the equivalent to code smells that have calcified and are now "
by YeGoblynQueenne 6y ago
Large parts of this post are naked apologism for grave aberrations in computer
science research, the equivalent to code smells that have calcified and are
now "how we've always done things" because nobody has the courage to do
anything to fix them, or even knows how. That these are addressed to new PhDs
as "this is the real world and you must get used to it" is just tragic. The
surest way for all this garbage to remain the way it is, is for new PhDs to
accept it as it is and not try to do anything to change it.
- voxl 6y agoAsking new PhD students to change culture is like asking Entry-Level Developers to change the management culture of Google.
- asdff 6y agoThe difference is all professors were once lowly PhD students.
- Xelbair 6y agowhich makes it even worse, as they want to propagate it further.
- throwaway2245 6y agobut not all PhD students become professors - only those who successfully (choose to) navigate the status quo.
- YeGoblynQueenne 6y agoMy comment is not asking anything of anyone. It's pointing out that trying to convince new PhDs, who might see the distortions in their field for what they are, that it's all in their mind and everything is OK, is only perpetuating the awful situation. 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.
- StandardFuture 6y agoI imagine this is all due to the more-than-obvious pyramid-esque scheme of academia: offer 12 professorship positions to 200 PhD students. I mean, the "smartest people in the world" are apparently the ones falling for this scam. It is just a breeding ground for brown-nosing, politics, and even straight corruption. It is laughable but it is also doing a massive disservice to the potential of human civilization.
- Legogris 6y agoWhat makes you think that more than 10% of PhD students even desire professor positions?
- ketzo 6y agoNot GP, but everything I've heard of PhD programs is that you're basically destined for academia. From my (admittedly ignorant!) perspective, it seems like only 10% of PhD students don't desire professorships. But that said, am I totally in the wrong on that?
- asdff 6y agoIn the life sciences from the people I know in the field, probably 20% of PhDs are considering academic positions. You can do a lot in the private sector with a PhD even well outside of your field, especially if you manage to pick up some data science skills along the way.
- mint2 6y agoI did a chemE grad program and my matlab coding was horrendous, my versioning and organization were also bad. I’d had one intro matlab class and an intro Mathematica class and then zero coding classes. For the longest time I thought if only I’d taken more programming classes I would be able to do better. 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.
- YeGoblynQueenne 6y agoYes, that bit about horrible code that caused such distress to an MSc student was particularly bad. Personally, I wouldn't be caught dead releasing that kind of code. It's not like there's a deadline for releasing code, most venues don't require it and it usually takes months for the review process to complete at conferences (years even in journals). There's nothing stopping one from working on the code at a leisurely pace once a paper is submitted, then releasing the code whenever it's fit for public presentation. There is no social contract that says you have to publish exactly the code that was used to produce certain results, just show that there is some code that does what your paper says it should. And if a precise record of what was done when is needed- well, that's called "git". 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! :)
- lambdatronics 6y agoIt's a form of technical debt for the research culture. It's also a prisoner's dilemma: putting in the extra effort to be different just puts you at a competitive disadvantage b/c the system doesn't offer any rewards for going beyond the bare minimum. (Heck, you open yourself up to liability by publishing your code -- people misuse/misunderstand it and blame the poor results on you, people expect you to support it, people find bugs and it reflects poorly on you...) The system selects for people who either don't see the issue or are not bothered enough by it to insist on behaving differently. It's not just a computer science problem btw -- it encompasses physics too.
- Master_Odin 6y agoCoupled with a lot of academics viewing coding as an unfortunate requirement to their craft. I can probably count on one hand of the folks I've worked with who know what a linter even is, or even keep minimally abreast of new versions of the language they work in every day.
- lambdatronics 6y agoNot even a requirement -- some of the elderly scientists I've worked with get by on spreadsheets! I did a tutorial on Git for my lab group in grad school -- there was some code under SVN at the time, but most folks didn't really use version control at all. (One nerve-wracking instance, I had to revert some months-old changes to our instrument control code, with only my memory to go on, because a bug I'd introduced was holding up someone else's experiment.) 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.