Real risk is incorporating other’s code without understanding or testing it. It doesn’t matter who wrote it, bad code is bad code. But let’s not point at a group and say “don’t write code”, let’s help everyone to write better code.
-
-
এই থ্রেডটি দেখানধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
I think you probably mean a different John MacFarlane?
-
Yes, this one: https://johnmacfarlane.net/ ... sorry!
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
I completely agree. Academia needs to do more to support full time paid scientific programmers, and scientists responsible for maintaining high quality software packages should get far more credit than they do.
-
The caveat, of course, is that as
@jakevdp pointed out in a very prescient post, it's incredibly difficult for academia to compete with tech companies for talented scientific programmers. -
It may be easier than you think. Academia has meaningful work on offer, and there may be an audience for that. But it requires real collaboration between reseachers and s/w engineers, for the latter are also looking for options to better themselves...
-
Few universities have permanent (ie, staff scientist) positions in the first place, and even fewer have staff positions for full time scientific programmers. Offering people term limited contracts when they could make 5 or 6x in the private sector is insulting.
-
This is precisely what the
@ResearchSoftEng movement aims to fix. By creating RSE groups, we can provide those all important permanent contracts. -
You guys are doing awesome work :)
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
There's academics writing code as a matter of passion and because they know what they do (Knuth). Then, there's "look, I've done something so I can write a paper about it" abandonware. More of the first, less of the second.
-
YES! Exactly. Thank you for making the point. I have seen a lot of crapware out there. But writing good code is not teached and you need passion and the insight that good code is good scientific practice...
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
I cannot fathom the alternative: researchers not writing code. Discouraging them is counter-productive to
#OpenScience and#ReproducibleResearch. Sure we might write some garbage code (that no one is obliged to use) along the way but the alternative is much much worse. -
Anyone doing analysis should use a CLI. Whether their code is a record of what they did or a fully functional package with all the bells and whistles is irrelevant to good science. Reproducibility is key. Then there’s something there at least if the “experts” want to build on it.
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
Both statements can be, and absolutely are, true.https://twitter.com/zakdavid/status/1018302195375202305?s=21 …
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
For as long as I get academics' VMs of the size of 60GB, and being an image of the researcher's laptop hard drive, I am with Zach.
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।