Schlagwort-Archiv: Uni

Machineration.

There's a time when the operation of the machine becomes so odious, makes you so sick at heart, that you can't take part. You can't even passively take part! And you've got to put your bodies upon the gears and upon the wheels, upon the levers, upon all the apparatus, and you've got to make it stop! And you've got to indicate to the people who run it, to the people who own it — that unless you're free, the machine will be prevented from working at all!

Mario Savio

Innovatinonsense.

Academic spamming has reached a new level when someone some bot suggest that you should patent a logic.

General Paper Lot.

The more sophisticated science becomes, the harder it is to communicate results. Papers today are longer than ever and full of jargon and symbols. They depend on chains of computer programs that generate data, and clean up data, and plot data, and run statistical models on data. These programs tend to be both so sloppily written and so central to the results that it’s contributed to a replication crisis, or put another way, a failure of the paper to perform its most basic task: to report what you’ve actually discovered, clearly enough that someone else can discover it for themselves.

James Somers: The Scientific Paper Is Obsolete

Viele Städte haben eine Universität.

Groningen is daarnaast vooral een studentenstad met ruim 57.000 studenten, van wie ongeveer 35.000 in de stad wonen.

nl.wikipedia.org: Groningen (stad)

Dankjewel.

It's been a blast.

Pledgeneering.

Citation

  • I will make explicit how to cite my software.
  • I will cite the software I used to produce my research results.
  • When reviewing, I will encourage others to cite the software they have used.

Careers

  • I will recognize software contributions in hiring and promotion within my institution, and encourage others in my institution to do the same.

Development and Use

  • I will develop software as open source from the start, whenever possible.
  • I will contribute to sustaining software I use and rely on.
  • I will match proposed software engineering practices to the actual needs and resources of the project.
  • I will help researchers improve the quality of their software without passing judgment.
  • I will publish the intellectual contributions of my research software.
  • I will document (including usage instructions, and input and output examples), package, release, and archive versions of my software.

 

Manifesto from Dagstuhl Perspectives Workshop 16252: Engineering Academic Software (https://doi.org/10.4230/DagMan.6.1.1)

聪明.

Sometimes all I understand is my own name.

Ältere Beiträge «