For the 2015 RuGMetabolism & Nutrition course, 25% of the final grade is determined by an editorial I have to write with 3 other students. Scratch that; one of them is no longer enrolled. Good for me! The less, the merrier! The remaining two students in group C with the same subject—metabolic regulation—are: Jesse E. Kuindersma and Vera E. Otten. Based on the editorial, we also have to prepare a presentation.
Janine Kruit explained today that the editorial has to be in the style typical of scientific editorials that promote a scientific article. So, it might be a good idea to look at a few published editorials for inspiration. One important feature she mentioned is that the editorial has to be positive about the study. Of course, the results can be negative, such as in [my example]: “dieting does not lead to long term weight loss”. She did suggest putting a positive spin on results such as these; e.g.: “There’s no need to force yourself to stick to some diet; dieting doesn’t work anyway.” 😉
The editoral has to be 800–1000 words long and is meant to highlight the most important results from a study and place them in a broader context that is applicable to the audience. The audience are the co-enrolled students who will witness the presentation and who will be able to access the editorial through the course’s Nestor environment.
One schematic illustration (of some metabolic pathway) is expected to accompany the text of the editoral. I’m guessing the presentation may contain more figures.
The presenation should take ± 20 minutes. Before the presentation, a concept-editoral has to be handed in by our group. Our presenation will be on Friday, March 27, sometime between 11:00–13:00, during the tutorial [Tutorial 6] in room 3111.0017A.
Update March 31: We just handed in the finished editorial.
One day, some day long ago, I said to Jeroen Dekker, a photographer friend of mine, who was still learning to program at the time: “Programming is talking to the future.” He thought it was a good quote. Coming across it again now, so do I. It’s good because it’s true, which everybody who has ever debugged some old code—be it their own or someone else’s—can attest to.
As for testing it, my knowledge (\(K()\)) of MathML (\(M\)) is pretty much nonexistant, while I’m quite comfortable with LaTeX (\(L\)) math exations, which is why I’m typing the LaTeX code “K(M) \ll K(L)” to generate the following simple equation:
Anyway, I am one of those people who randomly generates his (often overly long) passwords, which I store in a strongly encrypted file, but the article provided a great reminder that I should do the same for my answers to ‘security’ questions.
Some Oct 2 2012 wisdom from SlashDot user fuzzyfuzzyfungus: “Dubai is an example of the glorious harmony between (middle) east and west! A city that wraps the middle east’s robust traditions of rule of law and enlightenment liberalism and the west’s values of sober financial honesty in the civic-planning expertise of Vegas developers on PCP… Truly, an example for us all.”
Judging by the following notes in my ~/jot directory, I was inspired two years ago (Oct 23, 2013) by a TEDx talk by Josh Kaufman on learning:
Josh’s advice boils down to 4 major points:
Deconstruct the skill.
Learn enough to self-correct (don’t procrastinate by reading text-books).
Remove practice barriers (distractions).
Practice for at least 20 hours. [This is the gist of his talk, but I guess it is a complitely arbitrary out-of-his-ass thing.]
Perhaps I could apply this approach to figuring out which statistical model(s) to use for the peat moss fluorescence data which I’ve been struggling with these past few weeks. Since I don’t have a statistics text-book, I can’t exercise my love of text-book-aided procrastination, a shortcoming which I’ve compensated by my old debugging procrastination strategy—just fiddling around until something useful happens. Sadly, it is becoming apparent to me that with statistics, nothing useful is learned if you don’t understand what you’re doing and why. :'(
This link to The Architecture of Open Source Applications book was gathering dust somewhere in my ~/jot directory. In true free software spirit, it is released under a Creative Commons licence and the individual chapters are readable online. Each chapter about the architecture of a particular open source software project is written by the (co-)author of that respective project.
[…] In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program’s major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think.
When a Linux Mint release goes out of support, together with the Ubuntu release on which it is based, the Ubuntu packages become unavailable. This can be annoying for old fossils like me who stubbornly contue to use a release that has gone out of support, as I’m doing with Mint 14 (Nadia), based on Ubuntu 12.10, (Quantal Quetzal). (“Yeah, yeah; I’ll upgrade soon; I promise.”) Luckily, the out-of-support packages remain available in a different location.
So, in /etc/apt/source.list, I could simply replace all instances of archive.ubuntu.com with old-releases.ubuntu.com, so that my /etc/apt/source.list now look like this:
deb http://packages.linuxmint.com/ nadia main upstream import
deb http://old-releases.ubuntu.com/ubuntu/ quantal main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ quantal-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ quantal-security main restricted universe multiverse
In July 2013, I noticed that somehow the settings of the wp-page-numbers plugin for this blog had reset, which sucked donkey balls. I had fixed it then, but a while ago, the problem again raised its ugly head, so I had to fix it again. Weird.
Copyleft: These days everything you can think of is copyrighted, patented, protected or otherwise made into someone's imaginary intellectual property. I have a lot of imagination but not enough to pretend that I have some divine right to share things with you without giving you the right to share it further. That would be childish. So, everything here is licensed under a Creative Commons Attribution-Noncommercial-Share Alike license. That means that you can bloody well do anything you like with my content as long as you tell that it's from me (or the respective author). Only if you want to make money from my content do you have to ask me permission first. (As if I could be bothered to sue.) Oh, and you can't redistribute your derivative content under more restrictive terms. Share the love.
Colophon: This weblog is powered by a WordPress installation running on PHP5 and MySQL, hosted by NearlyFreeSpeech.Net's outstanding FreeBSD hosting platform. The markup for this WP theme is my own and should usually validate as some sort of XHTML concoction. So should the CSS. I've actually blogged about this theme.