-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce yourself! #3
Comments
So I guess I will start: my background is in bioinformatics and I currently work on women's diseases (omics). I am also a regular JupyterLab contributor. I would like to see more research papers with well documented repositories, but I understand that until this is a universal requirement, a researcher asked to do so may decide as well go to another journal. I would like to help researchers to annotate their repositories and make exploring repositories of others easier. I can contribute by writing Python, JavaScript/TypeScript or other code as needed, and by sharing some stories of badly organised repositories I found in the wild. |
Hi 👋 I'm Marcel, I'm a computational neuroscientist and now officially in the role of a software research engineer, working on tools for neural simulations (and some data analysis, etc.). My main work is in Python (with a bit of Cython/C/C++/CUDA sprinkled on top), I'm quite familiar with many of the more boring infrastructure tasks (automatic documentation builds, GitHub Actions for CI, ...) and I can write some basic JavaScript. I also have some experience in the realm of code review via initiatives such as codecheck.org.uk/ or https://rescience.github.io/ , and like everyone trying to reproduce results from publications, I have run into my fair share of badly organized repositories :) |
Welcome @mstimberg! Thanks for the link to ReScience C - I did not know this one. I looked at the FAQ and had a chuckle when I saw this one:
Concise! And of course a good explanation follows. |
Please feel welcome to write a bit about yourself in here. It would be ideal if we could chat more during the breaks and on Slack; in the meantime let's keep this issue as a quick way of introducing ourselves in an asynchronous way. Please try to mention what is your background, what you think you can contribute, and what you think about the project idea :)
The text was updated successfully, but these errors were encountered: