For me, it's just the other way round. I ripped all my music collection to flac - it the obvious first choice for archiving audio in a free, lossless, taggable format. Yet, I don't have a single mkv file on my disk.
"But trying to slow cancer by blocking exosomes is a difficult proposition, says Al-Nedawii. It is unclear how that would affect normal cells, he notes, and some exosomes from healthy cells have been shown to contain proteins that prevent cancer"
Too bad. I wonder whether they differ enough from non-malicious exosomes that they could be targeted/inhibited specifically with a different kind of chemotherapy drug to silence 'malangelizing' tumor cells.
I agree 500 papers over his career is indeed a lot. But remember that in some fields there's this general practice for the head of a research group having his name on every paper coming from his group (at least as a co-author) even if it's not written by himself or if the whole research has been carried out by his master's degree/PhD students. So actually, if you're the head of a large productive work group, it's possible to achieve such a publication rate doing "thorough, factual research".
As for why bacteria would react towards various artificial sweeteners in a similar way as they do with sugars, my semi-educated guess would be that maybe these bowel bacteria 'use' proteins similar to the ones in our taste buds, i.e. with binding preferences towards molecules which we percieve as sweet, in the regulation process of their metabolism.
Not necessarily. Haven't you ever found yourself in the situation that you're reading through a piece of code you have written yourself and you just can't figure out what you were thinking back then when you wrote it? If not – lucky you! I have. And I know many other coders have. I hate citing xkcd but this strip nails it: Future self. Documentation is not only good for newbies or colleagues, but also for yourself. As soon as I realized that, I started writing much more meaningful function descriptions (doxygen) and comments.
I frequently have to analyze strange program behavior or crashes and I always hate it having to read through a whole function to see and understand what it is doing (because just assuming it does something by reading just it's name hardly ever is enough). A brief explanation would be such a time saver! Coders re-stating that 'good' code documents itself so there's no need for additional documentation, in my opinion, are either short-sighted or antisocial (i.e. no team players). Either way, I disagree with them heavily.
Slashdot Mirror
For me, it's just the other way round. I ripped all my music collection to flac - it the obvious first choice for archiving audio in a free, lossless, taggable format. Yet, I don't have a single mkv file on my disk.
"But trying to slow cancer by blocking exosomes is a difficult proposition, says Al-Nedawii. It is unclear how that would affect normal cells, he notes, and some exosomes from healthy cells have been shown to contain proteins that prevent cancer"
Too bad. I wonder whether they differ enough from non-malicious exosomes that they could be targeted/inhibited specifically with a different kind of chemotherapy drug to silence 'malangelizing' tumor cells.
Despite being a nice joke for the subset of people being chemists this sounds too much like ME, and is thus negatively connoted.
Reminds me of the confusion in OpenOffice.org XML/OpenDocument vs. Office Open XML
I agree 500 papers over his career is indeed a lot. But remember that in some fields there's this general practice for the head of a research group having his name on every paper coming from his group (at least as a co-author) even if it's not written by himself or if the whole research has been carried out by his master's degree/PhD students. So actually, if you're the head of a large productive work group, it's possible to achieve such a publication rate doing "thorough, factual research".
reused multiple times rotated.
Like four times 90?
Or was it .tcl?
How about you just label it "wild speculation pulled out of [your] ass"?
You got that all wrong: I wrote buds not butts (o;
As for why bacteria would react towards various artificial sweeteners in a similar way as they do with sugars, my semi-educated guess would be that maybe these bowel bacteria 'use' proteins similar to the ones in our taste buds, i.e. with binding preferences towards molecules which we percieve as sweet, in the regulation process of their metabolism.
Of course, you understand it, you wrote it.
Not necessarily. Haven't you ever found yourself in the situation that you're reading through a piece of code you have written yourself and you just can't figure out what you were thinking back then when you wrote it? If not – lucky you! I have. And I know many other coders have. I hate citing xkcd but this strip nails it: Future self. Documentation is not only good for newbies or colleagues, but also for yourself. As soon as I realized that, I started writing much more meaningful function descriptions (doxygen) and comments. I frequently have to analyze strange program behavior or crashes and I always hate it having to read through a whole function to see and understand what it is doing (because just assuming it does something by reading just it's name hardly ever is enough). A brief explanation would be such a time saver! Coders re-stating that 'good' code documents itself so there's no need for additional documentation, in my opinion, are either short-sighted or antisocial (i.e. no team players). Either way, I disagree with them heavily.
The word you're looking for is 'retard'.