I have been involved in TB research for many years, knew the scientists who were locally fighting with whatever means were at their disposal - look up Georgies Mode - and this makes me sad and incredibly angry.

I grew up in a communist country. Say what you will, at least your blacklist is transparent and you know about its existence ;-D But seriously, this is awful.

My take is that I write code for others. It should be as clear and understandable as possible, even at the cost of efficiency, elegance or cleverness. This is why I think mixing Python with R makes sense in packages (under the hood so to speak) but not in analysis scripts or pipelines.

Zależy gdzie w Niemczech.

I don't even

Nie stać mnie niestety na rysunek, ale powiem, że kopertę z własnoręczną adnotacją w której przyszedł kalendarz pod choinkę lojalnie zachowałem ;-)

A to się całkiem zgadzam. Wogle to mam wrażenie że ta tuba którą wyguglalem na szybko to nie było to samo nagranie które słyszałem w dwójce.

Care to elaborate?

Shame to say, I never learned that. To a certain extent, I sometimes think that it sunk my career

I'd say always put arguments to grep in quotes. Single by default, double if you grep for variables.

Precisely. Ggplot is for more advanced cases. I still use plot(x, y) when I need to quickly see the results.

Except that "couple of clicks" is anything but reproducible.

Here is a book I wrote with markdown/Quarto (my chapters, that is): ccpress.pl/jak-powstalo...

I create my own BibTex files and nvim for editing. I use the completion mechanism of nvim to insert references, and simple text searching to find them. I used Zotero for a while but I found it not worth the effort.

Actually, I use it for all my writing. I wrote books (at least, my chapters in the books) in markdown and used quarto to format bibliography, footnotes etc. and produce Word. Advantages: (i) you can use github (ii) you can use your fav editor (iii) you can always switch to Word later if necessary.

Also, my camera is dirty (and will remain so)