[TangerineSDR] [EXTERNAL] Re: Code Review

[Engelke, Bill]

Aiden – I don’t wish to be uncooperative, but this could be a significant increase in scope; so I will not be participating in any code reviews until directed to do so by the UA Principal Investigator (Dr. Travis Atkinson). If you want to pursue this, please go thru the chain of command, i.e., ask Nathaniel (chief PI) to pass this new requirement to our team thru Dr. Atkinson.   -73- Bill AB4EJ

From: TangerineSDR <tangerinesdr-bounces at lists.tapr.org> On Behalf Of Aidan Montare via TangerineSDR
Sent: Sunday, August 30, 2020 11:03 AM
To: hamsci at googlegroups.com; TAPR TangerineSDR Modular Software Defined Radio <tangerinesdr at lists.tapr.org>
Cc: Aidan Montare <aam141 at case.edu>
Subject: [EXTERNAL] Re: [TangerineSDR] Code Review

Dear all,

Thanks everyone for sharing your thoughts on my proposal for hamsci code review sessions! I really appreciate the feedback.

Please fill out the form (https://forms.gle/uiEHCqMG9v1BaQiW7) by this Thursday if you haven't already so that I can schedule a time. My college semester just began this week, so I mostly know my own schedule and can pick a time.

Also, I wanted to provide some comments that will hopefully clarify a few things:

The code review sessions are intended to be pretty informal. I want a space for people to talk about programming in our projects, get help on topics they would like to discuss, and polish the aspects of their work they'd like to polish.

As Kristina pointed out, "code review" is a bit of a reserved word in certain groups, and often means a specific thing. I'm not trying to be so formal (perhaps I should have called them by a different name). I don't expect that anyone has to follow any of the recommendations they get at any of the sessions. And I don't expect that all code written in HamSCI has to go through code review.

Also, these sessions are half for the benefit of our projects, and half for everyone's individual benefit. Part of my motivation is the desire to personally improve my own abilities, and I hope that others will learn things as well. I appreciate the sentiment that not all good ideas might be implemented now, but some might be worth remembering for the future. If someone decides that we can't implement an idea now, but learns something that can be applied in their future projects, I'd consider that a success.

Finally, I'm a bit of a nerd, and I do personally enjoy learning about things like programming standards. But my intent of code review is not to propose any coding standard or style guide.

I hope that makes my thoughts a bit clearer. I continue to appreciate the feedback, and enjoy the discussions. Hearing from everyone’s different experiences is one of my favorite parts of hamsci!

--
Sincerely,

Aidan Montare
CWRU Class of 2021
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20200830/93407a60/attachment-0001.html>