CodeRefinery
We are the https://coderefinery.org project and provide training and e-Infrastructure for research software development.
We are the https://coderefinery.org project and provide training and e-Infrastructure for research software development.
There is one more day of #CodeRefinery tomorrow! This is one of the best days, and as usual anyone can drop by and watch the #livestream:
- at 9:00 CET, #SoftwareTesting which connects many things we have done before.
- And at ~11:00, "Modular code development type-along", where you'll see real steps you can take starting with #Jupyter data analysis turning into a #ReproducibleResearch tool using everything we have learned.
https://coderefinery.github.io/2023-03-21-workshop/ #RSEng #RSE #OpenScience #SciComp
Day 5 has started already! #Juptyer (bit of basics + plenty of tricks) and #Documentation (basics, comments, #readme:s, hands-on with #Sphinx, #GithubPages).
Now: jupyter
~1.25 hr from now: Documentation
#CodeRefinery is live for week 2. Last week we talked about version control (#git) a lot, now we show got git can be used to make #ReproducibleResearch, #documentation, #testing, and other things you need for #OpenScience. Yes, you can join for week 2 if you weren't here for week 1:
Livestream starting in 5 minutes:
https://twitch.tv/coderefinery
https://coderefinery.github.io/2023-03-21-workshop/
@scottmatter Good question! The point isn't number of questions; the reason for posting is to show how we get around "larger/online = no interaction". I think that live voice isn't the most important (and it keeps shy people quiet), most important is short loop "feedback → instructors discuss". This works very well for that, keeps it live, and makes it feel like a group while also not biasing towards extroverts.
Our blog post on our style says more: https://coderefinery.org/blog/2022/10/24/parallel-chat/
Apologies in advance if this is totally irrelevant, but…
Is volume of interactions an important metric in this case related to some other learning objective? What’s the relative value of a large number of questions in chat vs a smaller number in verbal interaction? What are the qualitative differences in learner (and teacher) experience? Is the intention for a whole lot of individual learning experiences or a shared learning experience as a group? If volume is important, could this live event have been a bulletin board instead?
Is online more or less interactive?
35 minutes of teaching, 30 questions in our @hedgedoc parallel chat so far. Hedgedoc performance holding up with ~250 viewers. Livestream interaction works and gets us far more questions than we could any other way - and this all will be posted on the webpage for reference this afternoon!
We started for the day! git-intro all day
- now: motivation
- soon: basics of making a repository, committing changes
- later on: branching
This thread will be used for #CodeRefinery 2023 March schedule updates. #teaching #livestream #RSEng #git #VersionControl #OpenScience #SciComp
https://twitch.tv/coderefinery
https://coderefinery.github.io/2023-03-21-workshop/
look ⬇️
How to attend #CodeRefinery?
Good question: the last years have shown that teaching can be free, and we see no reason to stop!
- Everyone (yes, that means you) can watch our #livestream at https://www.twitch.tv/coderefinery
- Some partners have in-person exercise help
- Or make your own team "watching party"
- Q&A access for those who register
- Review materials and videos later
Events limited by place or time is so 2019, join us for the future tomorrow! Info ⬆️ thread. #RSEng #AcademicMastadon
> If someone had just show me this, I could have saved 3 months from my #PhD. — someone ~2015 (not about #CodeRefinery)
There is no better investment than saving your future time. Is this week's minor deadline more important than your future career? aybe ask your supervisor and their answer might surprise you.
Attend the #CodeRefinery workshop this week and next, look ⬆️ thread to see more.
#RSEng #SciComp #git #github #openscience #ResearchSoftware #AcademicMastodon
https://coderefinery.github.io/2023-03-21-workshop/
What is this #CodeRefinery thing we've been talking about, and why might you attend?
- Workshop, for scientists, not about programming but the skills to use it well for #SciComp and #DataScience
- If you, or someone you know, has to use programming to do your work, but you know you could be more efficient - come!
> This was the best course I ever had, just make up something and say I said it. -- participant, ~2019
Starts Tue, online&in-person at partners: https://coderefinery.github.io/2023-03-21-workshop/
Our #CodeRefinery workshop is next week, and we are getting close to 500 registrations. We are especially happy how we can cater to so many different learning styles and ways of attending - we aren't a typical online course!
CodeRefinery teaches to practical tools for developing #ResearchSoftware, targeted to scientists. Either join yourself, or join and help make a local breakout/exercise session for your own community:
https://coderefinery.github.io/2023-03-21-workshop/ #RSEng #OpenScience #FAIR #AcademicMastodon
@coderefinery Nice. I am trying to send scientists your way.
We currently experience 0.2 registrations/minute and this is the best news of the day for us.
Our workshop starts in two weeks and you can still join:
Our workshop starts in two weeks and you can still join: https://coderefinery.github.io/2023-03-21-workshop/ - first 3 half-days will focus on Git commands and workflows: https://coderefinery.github.io/git-intro/reference/
#training #git #inclusive #softwarepractices #versioncontrol #free #online
Everyone knows your code needs documentation. As a #researcher, you probably also know that most code doesn't need perfect #documentation. #README files are good enough for most case! Read our suggestions/hands-on for how to make a good one for your projects. What do you do?
https://coderefinery.github.io/documentation/writing-readme-files/
(to be honest, this isn't our best page since it's rarely taught in #CodeRefinery workshops. Any suggestions?)
#RSEng #ResearchSoftware #git #SciComp #CodeRefinery #TipsAndTricks
It's #CodeRefinery time! CodeRefinery is one our main #training courses for #scientists, covering all the skills such as #VersionControl (#git), #documentation, #ReproducibleResearch, #testing, and more
Free to attend to anyone in the world: 21-23 & 28-30 March, EU mornings: https://coderefinery.github.io/2023-03-21-workshop/
We recommend everyone attend this course at least once.
#RSEng #HPC #SciComp #Research #AcademicMastodon #phdstudents #ResearchSoftware #OpenScience
![[caption contains additional info]
Core CodeRefinery lessons
Also see all of our online lessons: Lesson index
These are the lessons which are included in the "standard" CodeRefinery workshop, and what we believe that every computational scientist (even those with very small amounts of computation) should know.
- Introduction to version control (day 1) [git, basics and solo work]
- Collaborative distributed version control (day 3) [How to work together with git and github]
- Documentation (day 5) [in-code, readmes, Sphinx]
- Jupyter notebooks (day 5) [basics + intermediate tricks to help people get on the same page]
- Automated testing (day 6) [how to make your code more reliable]
- Social coding and open software (day 4) [what does it take to share and reuse, and why?]
- Reproducible research (day 4) [How to make your work reusable - either by yourself in a few weeks, or others]
- Modular code development type-along (day 6) [Put it all together and see how we make a real code fit together]](https://cdn.fosstodon.org/media_attachments/files/109/908/400/951/904/222/original/52d6814c6816ae60.png "[caption contains additional info]
Core CodeRefinery lessons
Also see all of our online lessons: Lesson index
These are the lessons which are included in the \"standard\" CodeRefinery workshop, and what we believe that every computational scientist (even those with very small amounts of computation) should know.
- Introduction to version control (day 1) [git, basics and solo work]
- Collaborative distributed version control (day 3) [How to work together with git and github]
- Documentation (day 5) [in-code, readmes, Sphinx]
- Jupyter notebooks (day 5) [basics + intermediate tricks to help people get on the same page]
- Automated testing (day 6) [how to make your code more reliable]
- Social coding and open software (day 4) [what does it take to share and reuse, and why?]
- Reproducible research (day 4) [How to make your work reusable - either by yourself in a few weeks, or others]
- Modular code development type-along (day 6) [Put it all together and see how we make a real code fit together]")
@mattasdata Yes, we have a remote-first mindset for #CodeRefinery. And then add back some in-person interaction, since that way around is relatively easy.
- Livestream to everyone in the world. Free but we don't promise much support for non-Nordic. Someone local could, though.
- Clear break times for exercises and discussion
- Collaborative notes for large-scale simultaneous discussion
- Watching parties as possible, either organized yourself or through a partner.
More: https://coderefinery.org/workshops/teaching-style/
Check out our crash course on minimum interactive #CommandLine #shell for scientists: https://scicomp.aalto.fi/scicomp/shell/
Are you a scientist who has to connect programs together or run some stuff on a #Linux cluster (#HPC)? You should know a few basic command line commands - maybe not everything, but you'll definitely see some around. Check out those curated tutonial based on what people really need.
The next CodeRefinery workshop is soon - March 21-23&28-30, online&in-person ! https://coderefinery.github.io/2023-03-21-workshop/
#Coderefinery is the bridge between academic courses and practical #ScientificComputing - all the stuff you need to know but aren't taught. And it's like an intermediate-level #Carpentries workshop if that's your thing.
It changes people's careers. Topics include #git, #ReproducibleResearch, #documentation, #testing, modular code development, and more.