HamSCI Code Review
Code is important to our work at all stages, and well-written code might impact both our own accomplishments within teams, as well as how useful our work will be to the world in general. This is true for the Personal Space Weather Station, but also for so many of our projects, academic papers, and more. I therefore propose a regular code review session for the HamSCI community. Meeting and discussing code will help us improve our programming skills individually, and the quality of our work as a community.
Feel free to send along ideas (contact information is below).
When
weekly meetings of 1 hour
You are welcome to come to as many or as few code review meetings as you like.
Time tbd
Where
zoom, tentatively
Who
All experience levels are welcome.
Some help from those with more programming experience would be much appreciated, but those of us know are newer to programming still have a lot to offer and learn from each other!
You don't have to bring code to discuss to the session, though if you've been working on something lately, we'd encourage you to bring it.
No affliation with HamSCI is necessary (though you should come join us, it's fun!).
What code you can bring for discussion
You are welcome to bring code from any HamSCI project, or work that is of interest to the amateur radio or scientific communities and consistent with the objectives of HamSCI. Code in any programming language is welcome.
You must have the right to share and discuss the code you are presenting.
While everyone is welcome to make use of the general concepts and programming techniques discussed in other projects, being part of code review does not grant the other participants rights to the specific software being discussed. Participants agree to not use, distribute, or discuss the sofware in ways not explicitly granted by the code's presenter.
Bringing Code to the Review
First-come first-serve, though people may email me to request to be on the list for discussion
ordering will be at organizers' discretion preference will be given to newer programmers or those who haven't gotten floor time lately
You should have your code and any supporting files ready to share. You should also have prepared a copy of your code that you can share with the participants if necessarily.
You might come with a small number of specific questions you'd like to ask to the group, or you might ask for general feedback on your work.