<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Pete and all,<div><br></div><div>Sorry I will miss tonight’s meeting as I am very interested in the topic. I look forward to watching the video of the session. I just got my first Oshpark board in the mail today so this is a timely topic. </div><div><br></div><div>I have one suggestion for a future meeting which I will call software engineering and then explain what I mean. As the sketches I write become more complex, I am running into some problems that may be of general interest:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- When should I take functionality from the main body of the program to a function? to a library?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- What is the best way to store and maintain the base functionality versus branches or forks. For example, I write a wireless sensor sketch with one implementation for a temperature sensor and another for an accelerometer?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- When there are several libraries that offer similar functionality, what is the best way to determine which to use? Don’t expect a strict protocol here but would be interested in rules of thumb.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- How do I handle the substitution of libraries for different target platforms. For example, I had to substitute the TinyWireM library for Wire when I moved to an ATTiny and needed an I2C library - a real pain.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Should I be using a repository like Github and, if so, how is Github best used?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Are there some things I should do to make my code more compact or efficient once I have it working as expected - something like readability vs efficiency in code?</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Also, in reading <a href="http://phys.org/news/2014-01-internet-poses.html">this article</a> about the security of embedded systems - are there some security best practices for Arduino?</div><div>If all this is too basic or has been covered, I apologize but wanted to throw out my suggestion in case there is a call for future agenda topics tonight.</div><div><br></div><div>I am sorry I will mis tonight’s meeting - I look forward to the next and thank you all again for your help and support.</div><div><br></div><div>Chip</div><div><br></div><div><br></div><div><br></div><div><br><div><div>On Jan 12, 2014, at 1:00 PM, <a href="mailto:triembed-request@triembed.org">triembed-request@triembed.org</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Send TriEmbed mailing list submissions to<br><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:triembed@triembed.org">triembed@triembed.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><span class="Apple-tab-span" style="white-space:pre"> </span>http://mail.triembed.org/mailman/listinfo/triembed_triembed.org<br>or, via email, send a message with subject or body 'help' to<br><span class="Apple-tab-span" style="white-space:pre"> </span>triembed-request@triembed.org<br><br>You can reach the person managing the list at<br><span class="Apple-tab-span" style="white-space:pre"> </span>triembed-owner@triembed.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of TriEmbed digest..."<br><br><br>Today's Topics:<br><br> 1. TriEmbed @ NCSU Monday January 13th @ 7pm (different<br> room/building) (Pete Soper)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 12 Jan 2014 08:48:15 -0500<br>From: Pete Soper <pete@soper.us><br>To: triembed@triembed.org, trianglerobotics@yahoogroups.com<br>Subject: [TriEmbed] TriEmbed @ NCSU Monday January 13th @ 7pm<br><span class="Apple-tab-span" style="white-space:pre"> </span>(different<span class="Apple-tab-span" style="white-space:pre"> </span>room/building)<br>Message-ID: <52D29D1F.4040703@soper.us><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>The next meeting of the Triangle Embedded computing interest group will <br>be in room 1021 of Engineering building TWO (note the change of building <br>and room) on Monday the 13th at 7-9pm.<br><br>The meeting will start with open announcements, followed by a short <br>presentation about designing and assembling custom PCBs, followed by the <br>usual discussions and show and tells. Help for beginners is available at <br>every meeting. Bring your gadgets and gizmos and cool ideas to share!<br><br>There's parking on Oval drive in front of the building as well as two <br>parking decks on Partner's Way.<br><br>Details and map links are here:<br><br>http://TriEmbed.org<br><br>This meeting room/building is booked through May and we'll hopefully be <br>able to book it through the summer this spring.<br><br>NCSU Students, Faculty and Staff: There is an urgent need for school <br>representatives. Volunteers only need to attend and be the designated <br>contact to satisfy NCSU requirements for a given meeting. If you can <br>help please drop me a line with your contact info and what month(s) you <br>can attend and represent the school.<br><br>If we can't meet this need it won't be possible to continue with <br>meetings at NCSU.<br><br>-Pete<br><br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>TriEmbed mailing list<br>TriEmbed@triembed.org<br>http://mail.triembed.org/mailman/listinfo/triembed_triembed.org<br><br><br>------------------------------<br><br>End of TriEmbed Digest, Vol 8, Issue 7<br>**************************************<br></blockquote></div><br></div></body></html>