From herrold at owlriver.com  Wed Feb 14 12:51:40 2018
From: herrold at owlriver.com (R P Herrold)
Date: Wed, 14 Feb 2018 12:51:40 -0500 (EST)
Subject: [carpe] meeting summary 2018 02 13 Herrold reaction and summary
Message-ID: <alpine.LRH.2.03.1802141209350.31048@bjyevire.pbz>


Thanks, @rubberduck203 //   Christopher J McClellan

pix at:
	https://twitter.com/Rubberduck203/status/963570871502860289

and there, a poke toward:
	https://christopherjmcclellan.wordpress.com/

working through:
	https://github.com/rubberduck203/avr-template


What a great whale of a great CARPE meeting ; thank you JEP 
for driving the group


At The Forge last night on TDD, C++, pair (really 'swarm' [1]) 
coding, all on an Arduino, as though it was an initial turn-up 
on pre-release hardware known only through its spec sheet.

By the end of the effort an hour and a half later, actually 
applying the code to a device [and seeing it do just what it 
should do, per the testing].


I'm really impressed that TDD and a chip specification PDF 
were enough to get there so quickly

Also it was nice ** not ** using the Arduino IDE (which sort 
of sux, but is ubiquitous [2])  but rather a GCC and makefile 
driven environment, and ... interesting to see the MSFT Visual 
Studio in action (which also knows C++ syntax, and what might 
be missing, mis-capitalized, etc) ... GUI pop up 
valid completions and the tab key could really speed things up


I think that Makefile can afford to always just run: 
	make clean

with each progressive make, as there is not a huge complex 
environment in play to rebuild, and the false economy of NOT 
running it, and then running: 
	make clean && make


is not worth the time it takes to think about whether one 
should, a second time .. just do it  ;)

-- Russ herrold

1. there was a keyboard driver who pretended to not know the
language, but did know C++ syntax, and the rest of the room
'talking through' test writing, Functions, Methods, and
refactoring

2. I feel a little embarrassed having presented at CARPE last 
August, in part about 'coddling' that environment [3], but I 
was really off solving problems as to the ESP8266 environment, 
and this was something I could send off, as I drove past 
problems getting an environment set up.  I filed one as to a 
three line test yesterday, of similar type: [4] bottom of 
Comment 13

along with the needed fix stanza for a SElinux issue 
on RHEL 7 ip6tables.  By filing it, I can now forget about it, 
as it is durably tracked, will be indexed by Google, and when 
I bump into it again, I filed enough detail of the error 
messages that it provoked that I can find it.  

See also: [5] Comment 1 I _found_ that solution because 
someone else had documented error noise (even if not then 
fixed [6]) a couple years ago

3. https://github.com/arduino/Arduino/issues/4581

4. https://bugzilla.redhat.com/show_bug.cgi?id=1486803#c13

5. https://bugzilla.redhat.com/show_bug.cgi?id=1544937

which overnight after being filed has already picked up a 
comment from the global lead at RHT in its comment 2

6. https://bugzilla.redhat.com/show_bug.cgi?id=1348434