Widget Wednesday: Breadboard Basics

As much as I lost my heart to -- and built my first Arduino project on -- Adafruit's Trinket, the game-changer (for me) was stumbling across the chip-on-board form-factor.  That form-factor is not unique to the Arduino universe, where it's sometimes called "Boarduino."  We'll get to that in a later post.  For now, however, I want to focus on the mechanics of the breadboard itself.  Because [extremely schmoozy voice] that's where the magic happens [/extremely schmoozy voice]

First things first:  What is it good for?  "Prototyping" is the obvious answer.  But, chez fivechimera, there's also a long -- and sometimes even honourable -- history of prototypes being "good enough" for literal years of full-time use. Until they're not and the parts go back into their Cabela's tackle-boxes for next time.

This is not a novel concept: "Breadboarding" gets its name from the days of yore -- by which I mean literally a hundred years ago -- when you wired up your project by literally pounding nails into a breadboard (or any wide slab of wood), and winding copper wire around them to create a circuit.  Homebrew ("cat's whisker") radios were a Very Big Deal.  (See also: https://www.mikeselectronicparts.com/wp-content/uploads/building-a-crystal-radio.pdf)  

But, doubtless, one big selling point in those pre-Radio Shack days, was that once that project's usefulness ended, one could always pry loose the widgets, un-string the wire for later use (copper is expensive, y'all!), and pull the nails from the breadboard to restore it to its blank-canvas state.

And so reusability is the main reason I prefer the Boarduino form-factor.  Assuming that you're working w/in certain constraints, reducing project footprint is the second-best reason.  Assuming, of course, that the project can live inside certain limitations:

1. Current limitations:  Each small hole (a.k.a. "tie point," a.k.a. "pin") on a solderless breadboard should never carry more than 500mA, or 1/2 of an Amp. of current through it.  Theoretically, they can take up to one Amp.  Just don't.  Most especially projects that will be up and running for awhile.  It's not worth the risk.
2. Voltage limitations:  Stick to 5 volts DC.  Again, you want to stay well within the safety zone.  
3. Pin spacing:  If the widgets you're planning to plug into your breadboard don't have pins 2.5mm (or 0.1 inch) apart, you're going to need to make other wiring arrangements.  We'll get to those options in a subsequent post.
4. "Stupid-proofing":  Nothing in a breadboard's construction limits current polarity.  By which I mean, if you mix up positive and ground, the breadboard will not step in to save you.  At best, your project just won't work.  A short can melt the breadboard plastic.  (Ask me how I know.)  You also risk frying any widget connected to the faulty wiring -- up to and including the microcontroller.
5. Layout limitations:  Do you have enough room on the breadboard for the microcontroller chip (a.k.a. MCU) and all your widgets?  If not, how are you going to work around that when your project is up and running in the real world?

Which brings me to breadboard sizes and their features (or lack thereof).  There might be a few exotic outliers, but here's the range I've stumbled over through the last few years:

I would say that they come in all shapes and sizes, except that the shape is limited to rectangular.

Half-size (top left):  In my experience, this is usually the optimal size for a Boarduino projects. The holes ("pins") come in two flavours.  

• The two rows that run (horizontally) along the long edges of each side are often referred to as "power rails."  Traditionally, red is connected to the positive end of the power source and runs, uninterrupted from one end to the other.  Ground is wired into blue.  By default, the power rails on each side are independent of each other.
•  If we consider the power rails to be "rows," then the other flavour of pins can be considered "columns."  These run perpendicular to the rails.  The five pins of each column -- highlighted in neon green -- are connected to each other.  They are not, however, connected to the column on the other side of the trench that runs between them.  

Full size (right):  Similar to the half-size with more "tie points" and often more flexibility.  Depending on the manufacturer, you might need to bridge the two halves of the power-rails.  Or not, depending on your project layout.

Mini (middle left):  In this case, there are no power-rails "rows"; only "columns" of five interconnected pins.  You will have to use one column for a positive rail and one for the negative.  Which brings one big no-no:  Never, EVER wire positive and negative into the same column.  Even for the simplest project.

Micro (bottom left, shown top and bottom):  For grins, I'm throwing this one in.  And, no, I have no idea what's going on with those "Lego-bumps" on the underside except to guess that they allow the breadboard to be glued/screwed into place from the underside of some project???  Again, I have no idea.

Now.  All of the above assumes that you have some basic understanding of how circuits work.  If you're still new to the concepts and/or hesitant to play with live electricity, you can "practice" your wiring skills virtually. 

Most electronics prototyping/visualisation software is geared for PCBs -- printed circuit boards.  That's both an intermediate/advanced move as well as one more or less alien to this feature's "Boarduino" focus.  If you're serious about electronics design, you will need to learn how to "think" in PCB.  For now, don't worry about it.  In practice, that leaves two non-trivial options:

TinkerCad is "free" in the sense that you can give AutoDesk your email address -- be sure to use the "spam" one -- and play around in the "Electronics" section to see what I mean.  

• Pros:  It's "free" in the sense that you're giving a large company your email address and the user interface is quite intuitive.  Also, it's online, so no PC-vs.-Mac-vs.-Linux issues to worry about
  
• Cons:  AutoDesk offers shockingly small range of "widgets" to plug into the breadboard.   
  

Fritzing is payware.  (Normally, I'm more than happy to trade money-for-value...until that money is processed by [spits] Paypal.)

• Pros:  A much, much broader variety of widgets.  Some vendors (wisely) contribute to the Fritzing project; others don't.  But you can normally find something "close enough."
• Cons:  A slightly steeper -- if unsurprising -- learning-curve because there are more features.  (Pro tip:  Save yourself a bunch of grief and learn how to "lock" main widgets like the breadboard in place.  Otherwise, it's far, far too reminiscent of the mayhem of resizing and image in Microsoft Word.)
  

Of the two, I personally prefer the features-vs.-complexity balance of Fritzing.  If you're not sure that you're going to stick with this hobby (or don't have access to a payment method that [spits] Paypal will accept), TinkerCad should be more than enough to get a feel for breadboard circuitry.

That' about all I have for this installment.  An excellent deep-dive into the construction of breadboards can be found here: https://protosupplies.com/guide-to-solderless-breadboards.

Next time, I'm planning on going through the often-overlooked mechanics of creating circuits, with, of course, a particular emphasis on breadboards.

Until then, Tchein ton siault d'beluets!

- - - - -

Credit where it's due:  Dennis Freeberg, for the square-on photo of the half-size breadboard.

Widget Wednesday: Multi-meters Matter!

First things first:  What is it good for?  The short answer is measuring voltage (for our immediate purposes, DC voltage) and resistance and, hopefully, amperage.  The longer answer is that, if you don't make your multi-meter part of your tinkering/debugging, you are (in the immortal phrasing of South Park) gonna have a bad time.

Regardless of what kinds of widgets you intend to tinker with, your first purchase should be a multi-meter.  I'm serious here.  Like, Global Thermonuclear Armageddon levels of serious.  When you're first tinkering, a multi-meter is mainly useful for checking voltage levels and verifying whether current is flowing where you intend it to flow...and in the direction you intend it to flow.  A short-circuit can be an, ahem!, highly unpleasant surprise -- even without damaged equipment/widgets.  A multi-meter will ultimately, easily pay for itself in visits that you don't receive from The Magic Smoke Fairy.  

In addition to its money-saving graces, a multi-meter will not only give you more time to "play," it will also make that time more enjoyable.  What do I mean by that?  Well, I'm a programmer by trade.  So my first instinct is to blame my own code when I connect all the wires and [sad trombone] the project doesn't work. I've wasted entire evenings on wonky jumper-wires.

But in this hobby, I'm usually working with inexpensive, no-name widgets -- the kind shipped by the cargo-container-load.  These are most certainly not UL-rated, much less ranked in Consumer Reports.  (This includes power supplies, which is a whole 'nuther subject for a whole 'nuther post.) 

Also, unlike programming for full-size computers, debugging options are pretty thin on the ground.  I'm not at a point where I can justify the cost of an oscilloscope.  Often, a voltage level (or lack thereof) is my only way of seeing what's going on inside the wires.  

I was naive when I bought my first multi-meter; I was casing out the "Electrical" aisle at the small Home Hardware franchise, saw this model, and thought, "Oh, hey!  I'm gonna want one of those!"  Turns out, it doesn't measure amperage.  That's mostly an inconvenience; rarely do I need anything besides DC voltage:   

• "Is this supposedly-recharged battery ready for the 'special' recycling box?"
• "Is this jumper-wire borked?"
• "Did I screw up my voltage-divider math (again)?"

That being said...get yourself one that measures amperage alongside DC voltage, AC voltage, and resistance.

Also make sure that you have more than one way to attach the red and black tips of your multimeter to whatever it's measuring.  Like I said, I was pretty naive; my model only came with the probe-style leads.  For checking battery voltage, that'll do ya: 

 

One important note about the colour-coding here:  

• Red == Positive voltage, noted by the "plus-sign" on your battery or DC power source.
  
• Black == Ground voltage, noted as the "minus-sign" on your battery or DC power-source.  There's technically a difference between "negative" and "ground" voltage.  That's (once again) another topic for a later time.
  

 "What is it good for?" Verdict:  This battery is freshly charged.  (Note:  AA and AAA Alkaline batteries -- i.e. the throwaway non-rechargeable ones -- are expected to put out 1.5 volts in their prime.  Their rechargeable counterparts?  Only 1.2 volts.  And I will go to my heckin' grave wanting to wedgie every last corporate moron responsible for that travesty...)

 But for most other purposes, probe-type leads are useless.  Even if you had enough hands to hold the leads to the positive and negative wires in your project's circuitry, we all can understand what a spectacularly, gawdawfully BAD IDEA that would be.  Even with the relatively low voltages/currents of battery packs.

That's where "alligator cords" come in.  Checking the voltage of bunch of batteries in a pack looks like this: 

 

"What is it good for" Verdict?  We have three AA rechargeable batteries in series, with the expectation that they will add up to ~3.6V.  So, yeah, these are pretty freshly charged.  

My Gentle Reader will notice that, again, colour-coding comes into play.  When you buy a handful of alligator-cords, they are colour-coded.  Stick to the formula:  Red is for positive voltages; black is for ground/negative.  We'll talk about other colours at a later date.

But what if you're measuring voltage/current/resistance in-circuit?  For instance, how can we objectively know that the 3mm LED in this circuit is operating at something close to the optimal voltage:

Even accounting for the artificial lighting under which this photo was taken, that green LED looks a tad pale.  Going by experience, that is usually a symptom of low voltage.  But, checking the LED's datasheet, we know that the LED's operating-range voltage is 3.0V-3.6V -- a tad under the 3.72 voltage of the battery-pack.

Now, because the "Intro to Electronics" tutorials say that we're supposed to add a resistor to the LED's circuit to keep the voltage under the 3.06V maximum, and also the operating current under 20mA (a.k.a. 0.02 Amperes).  The kit came with 220-Ohm resistors for this kind of circuit, and I popped in one of those to make sure that the LED doesn't pop because -- dude! -- those things can be LOUD when they blow out.  Ask me how I know. :~/

So let's see what the multi-meter has to say about the voltage.  We do that by splicing the multi-meter into the circuit with the alligator cords and a couple extra jumper-wires (the latter of which we'll address in a future blog-post):

 

 

To splice the multi-meter into the circuit, notice how we add a red ("positive") jumper-wire ahead of the LED and a black ("ground") jumper-wire behind the LED.  And how we patch each jumper-wire into the appropriately-coloured multi-meter lead via jumper-wire.  We are essentially making the multi-meter the "middle-man" in the circuit to measure the total amount of voltage.  We could do the same for resistance.  Or -- with a more sophisticated multi-meter -- the amperage.  (But, with Ohm's Law, you only need two out of the three values to compute the other.)

"What is it good for?" Verdict:  Turns out that we were right about the voltage (and by the math of Ohm's Law, current):  That LED is, basically, running too cool.  (The upshot -- again, something that will be covered shortly -- is that we can afford to adjust the value of the resistor used in the circuit.  Downward, in fact.

That's a good place to start/end with multi-meters.  When "Widget Wednesday" covers trimpots and rheostats and the like, measuring resistance will come back into play.  But for now, the intent is to give My Gentle Reader enough tooling to figure out whether or not the magic electron-juice is flowing through a given set of wires...and whether it's too little or (worse!) too much for the widgets in its path.

Until next time, Tchein ton siault d'beluets! 

- - - - -

Credits where they're due:

• Dennis, for taking the first photograph while my hands were busy keeping the battery from rolling away from the multi-meter's leads.
• Nicole, for "rehoming" her electonics supplies and gear with me, including the alligator-cords.  One can never have too many alligator-cords. :~)
  
• BJW Electronics, for soldering leads onto the wire of the battery-pack to make it breadboard-friendly.
  

Introducing "Widget Wednesday"

I'm kicking off a regular feature that digresses more than a little from the usual focus on programming as a vocation and a business.  

I've been faffing about with Arduino since January of 2015 and failing my way into micro-controller programming every since.  To date, I've done far more personal tinkering than professional work.  And while I've learned whole new skills throughout the last seven years, the lesson that hit hardest was how the overlap between folks who understand circuitry and folks who can write code for micro-controllers is surprisingly thin.  

That said, the RaspberryPi and, to a greater extent, Arduino (and the ecosystem it spawned) have been nothing short of game-changing.  Correspondingly, an abundance of inexpensive, usually breadboard-friendly electronics (what I'm going to call "widgets" from here on out) has mushroomed.  Which puts both those ecosystems into something of a virtuous cycle.

Mostly, I play for Team Arduino.  My use-case for the RaspberryPi has largely involve running tiny, specialised web servers inside a network.  In this context, I adore the Pi.  But for what's generally known as "physical computing"?  It's a sub-optimal form-factor.  Now, for all I know, this might have changed with later models.  But the earlier Pi iterations offered a laughably low amount of current to any 3rd party widgets connected to them.  I'm talking about hooking up three 3mm LEDs and powering them at ~80% capacity.  From a board that requests a 2-Amp power supply (enough to power 100 of these LEDs)?  Yeah, laughable.

Additionally, my experience with the Pi (thus far) is that it's Global Thermonuclear Armageddon(TM) levels of overkill when it comes to the computing power it takes to process these widgets' input and output.  Mainly because whatever's controlling the widget often only needs to know "Is it on or is it off right at this very microsecond/nanosecond?" Or, "Does this widget need to be on or off at this very nanosecond/millisecond?"  Or, if we start to get fancy, "Is it outputting a current somewhere between 0V and 5V right now?"  

For that purpose, the Arduino's 8-bit processor and trivial storage space are more than adequate.  Face it:  8-bit computing ran the original Space Shuttles.  And I'm more interested in the Space Shuttle, vs. the number-crunching IBM beasties that computed its trajectories/orbits Back In The Day(TM).

Now.  For a 21st-century web programmer who takes 64-bit processing with gigabytes of memory/storage for granted, there was for sure some Getting-Used-To(TM) involved.  But I was lucky enough to stumble into Programming School(TM) in the 1990s when C/C++ was still used to flush out the posers.  (Hello, bit-shifting and bit-masking!)  Then stuff like StackOverflow happened and embedded computing stopped being such a High Priesthood.

But as much as I manage to fumble and faff my way through circuit-diagrams, I will always, always see things through a coding lens.  Alas, that's not the best perspective from which to learn - much less presume to coach anyone else in learning -- this topic.  I personally know at least a half-dozen folks who have legit. forgotten more circuitry than I will ever know.  But they come to me for code.  And there lies the rub.

So on those occasions when I'm asked to teach Arduino, I am fully, cringingly, aware of the huge disservice I'm doing by skimming through the bare-bones concepts of, say, Ohm's law or how to calculate resistor values.  Or what to look for in a datasheet.  Yadayadayada.

Because the reality is that if you're already a programmer, learning the Arduino API is literally the least of your concerns.   That's even true when you get bored with the API and branch out into the pure C/C++ code beneath the surface...or (gasp!) the snippets of Assembly language that can be spliced in when performance matters.  No, it's the hardware (not to mention the electromagnetic branch of physics) that will hose you from Hell to breakfast and back again.  So you'd better get used to the idea before you get cocky.  There's coding for the hermetically-sealed walled garden of a web browser or smartphone.  And then there's the messy real world.  Where allllllllll sorts of things can go wrong.

The upshot is that, while I might have to screen-shot snippets of code from time to time, right now I really can't see needing anything like a Git repository.  Maybe for the datasheets?  I dunno -- I guess we're going to find out together.

Specifically, I will be focusing on electronics components that I have used -- or for which I have a designated project.  In reality, a lot of this will be an exercise in me thinking out loud, to some degree organising a meandering reference manual for my own sweet sake.  Documenting things, even things I already know, forces me to understand them at a deeper level.  Writing, even as a moderately fast typist, slows me down.  That's a good thing.  I have no option but to question how, exactly, I actually came to know what I think I know.  Sometimes that's a rude awakening.  But again, this is a good thing.  

Thus, this series/feature will start off pretty basic and hew fairly close to the proverbial metal:  Elemental generic components to start, progressing to inexpensive, breadboard-friendly "breakout boards."  Again, we can thank the Pi/Arduino ecosystems for the absolute embarrassment of riches we now enjoy here.  Limor Fried's Adafruit (and similar businesses like Sparkfun) has reaped the dividends of the education they've sown (in tandem with making these boards affordable enough to take a lot of the risk out of tinkering).  Explaining basic concepts like "What is a circuit?"  "How are Current, Resistance, and Voltage related?" in a way that doesn't make anyone feel condescended-to is an invaluable service to beginners who might not have access to formal education.  

Additionally, Adafruit and Sparkfun, like the Digikey-/Mouser-scale suppliers, are good about providing datasheets/specs.  (WIDGET SHOPPING COMMANDMENT #1:  Thou shalt not add a widget to thine cart without downloading its datasheet.)  Datasheets exist to splash some cold reality on the idea you had in this morning's shower.  E.g.: This widget won't (reliably) work if the ambient temperature is below the freezing point.  Or:  This widget operates at a different voltage than the microcontroller.

But, helpful as tutorials and datasheets both are -- and you always read them both, riiiiiiiiight??? -- someone stepping beyond the "Hello, World!" winky-blinky LED phase of embedded electronic development is left to fend for themselves on their first non-trivial project.  That can leave a newbie on the proverbial horns of a dilemma:

• A widget's datasheet will tell you the min./max.voltages/currents/temperatures/etc. of where it will and won't work.  But it's hardly inspiring.  
• A project found on the web may have a given widget in its parts-list but give no clue about what makes that particular widget a good fit for that particular project.  (So screw your project, amirite?)
  

"Widget Wednesday" aims to fill that gap.  So when a given widget is profiled, the first thing covered is "What is it good for?" Then we'll address things like constraints, limitations, tolerances, reliability, etc..  Like I said, I've been doing this for several years; I have a few war-stories to share.  Elsewhere, I've only been half-joking when I've said that the most toe-curling five words in the English Language are "Ask me how I know."  Stick with me, and you'll find out.

Until next time, Tchein ton siault d'beluets!

Frivolous Friday, 2021.01.15, the Stan Rogers edition

I'm not sure how, but we're apparently All About the sea-shanties this week,  So here's a double-barrelled middle finger to the January 6th Capitol Hill terrorists, courtesy of a U.S. expat living in Maritimes Canada.  (Note:  All the Stan Rogers versions seem to be locked up by YouTube or Reddit, but this is a lovely, lively cover:  https://vimeo.com/182341839)

Oh, the year was twenty and twenty-one --
How I wish I was employable now! --
When viral tweets from the tangerine King
Riled the scummiest rabble I'd ever seen:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

When four red states flipped over to blue --
How I wish I was employable now! --
The Murdochs & Mercers & alt-right hive
Swore that two plus two added up to five:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

The "patriot" crowd was a sickening sight --
How I wish I was employable now! --
Some came armed with zip-ties or horns or bombs,
And the half of them driven there by their Moms
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

The Ellipse spiels were the opening act --
How I wish I was employable now! --
Rudy and fail-sons and Papa, too
Each blessed the mayhem we came to do:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

We swarmed the building with the big white dome --
How I wish I was employable now! --
We smashed glass and doors, maybe foiled some locks
But quick-witted aides saved the ballot-box:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

I prowled the halls spoiling for a fight --
How I wish I was employable now! --
A trial-by-combat with Pelosi
Or a best-two-out-of-three versus AOC:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

We snapped our selfies without a mask --
How I wish I was employable now! --
We took our trophies and set out for home,
Not one of us packing a burner-phone:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

My name was added to the No-Fly List --
How I wish I was employable now! --
Tho' I was down with Capitol Police,
I was doxxed to the G-men by my teenaged niece:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

President Harris is the Anti-Christ --
How I wish I was employable now! --
I'll sign off now before I wake me Mom--
Click 'Like' and donate to my Patreon:
Hell-ban them all! I was told,
We'd take back votes that the Democrats stole,
Wave our guns, drink lib'ral tears.
Now I'm a D-list player in the Vlog-o-sphere
The last of Donald's Privateers.

May I have a word?

I suppose the multi-week gap between project completion and project installation was a chance to check for "drift" on the two DS-3231 real-time clocks (RTCs) that went into "Mark II" of the Office Finches' overhead lighting.  Small mercies 'n all...

For those folks just tuning in, I added a shelf to the corner of their corner of the office a couple summers ago.  The overhang blocks the already-not-abundant natural lighting of a NE-facing window.  The "Mark I" was extremely prototype-y.  Like, 5mm-LEDs-in-breadboards prototype-y.  I wish I were making that up.  (Moral of the story:  Never underestimate the longevity of V1.0.)  The "Mark II"'s design supercedes that at the cost of some duplication, yet with fewer components overall.  What's shown above is mirrored by a twin just 30cm or so to the right.

Anyhoo, Adafruit -- the Great-Grand-Godmother of every winky-blinky cosplay project on the planet, or so it seems -- batched their NeoPixels into a handy ring.  And, to their credit, each of these 12 itty-bitty-winky-blinkies punches well above its weight @18mA a pop.  The office walls are mostly a darker green, so I was initially disappointed in the lighting levels.  But after the (white) table, (white) cages, and (mostly-white) cover-cloth were all back in place, I had nothing to complain about.  And that's just with 24 pixels.

They also massively streamline the design overall:  Base (white) lighting, rotating RGB (to vary the light-spectrum), motion-activated night-lighting, and a top-of-the-hour "disco" light-show to keep an eye on the RTC drift is now handled with just six wires instead of a couple dozen.  So, good job, Adafruit:  I'm sorry I didn't realise that the PixelRings I bought were knock-offs.  I'll know to check next time.

Importantly, this project cemented my affection for the "Boarduino" form-factor -- by which I mean an Arduino project running from an Atmega328P-PU chip plugged into a full- or half-size breadboard.  (You can do the same with smaller chips like the ATTiny 24/25/44/45/84/85 chips, if you're willing to make certain trade-offs in computing power and features.)  The flexibility (from a wiring standpoint) is pretty much unbeatable.

But there's another kind of flexibility I've lost my heart to, and that's just the pure freedom from a particular MCU form-factor.

Don't get me wrong:  For the initial coding/debugging, the full-size UNO is my trusty go-to.  Mainly because, even with ZIF sockets, toggling between the "programmer" breadboard and the actual project breadboard is a PITA.  Also, plugging a Trinket into a baby-breadboard and wiring it up to all the other widgets has the satisfying feel of solving a puzzle. 

That being said, I kind of live in Perpetual Prototype mode with these projects.  (Off the top of my head, I can already think of at least three things I'm smacking myself upside the head for not doing differently -- most notably, using bigger screw-sizes.)  And, when all's said and done, I can.  Everything about this project is generic and re-usable.  Even the PLA 3D-printed offsets used to mount stuff onto the underside of the shelf can be recycled by melting and re-extruding.

Part of me cringes at condemning the waste I see in the name of hands-on technical education.  Yes, learners should feel free to make mistakes, up to and including the dreaded "magic smoke" that is a rite of passage in electronics.  But trashing a new toothbrush to make a bristle-bot that will end up in the ocean as soon as the coin-cell battery wears out (or it ceases to be amusing -- whichever comes first) also makes me grind my heckin' teeth.  Because the unintended lesson taught is obsolescence.  Any child will inevitably pick up that lesson many times over in modern society without any lesson-plan, spank you very much. :~/

The DIY folks I follow seem to delight in passing around upcycling hacks.  E.g. the boy who repurposed a computer fan to charge his phone while bicycling to school.  Or the girl who hacked together a foot-powered washing machine to power through that chore in less time.  Or even the junkyard/repair-shop trade in salvaged parts...the kind of place where you bring your own box and pay in cash (and/or beer).  Love 'em all.  Really, I do.

But I'm talking about something slightly different, something that we in the First World(TM) are typically privileged to do, and that's make stuff with brand-new (or gently used) parts.  Maybe it would help if we had a more generic term than "Boarduino,"  something that encapsulates the ethic of intentional re-use. For now, I'm going to have to roll as a soi-dissant "perpetual prototyper" (in lieu of "maker" or "hacker"), but I'm definitely in the market for something better.  And the nanosecond I find a better badge, I will wear it proudly.  Heck, if it's on-fleek enough, I might even get the tattoo.

Silly Saturday, 2018.11.24, the Kenny Rogers edition

On a late Sunday evenin',
At a start-up out of runway,
I sat next to The Greybeard,
We were both too tired to weep.
So we took turns a-sighin'
As the errors rolled from Jenkins,
'Til ennui overtook him
And he began to speak.

He said, "Grrl, I've made a life
Out of savin' founders' bacon,
Smellin' trouble brewin'
'Fore the pinks slips start to fly.
By the green hue of your skin-tone,
I can see you called your options
If you'll walk me down the hall-way,
I'll give you some advice."

So we headed to the break-room
And he kicked my butt at foos-ball,
Then opened up the drink-'fridge
And slammed a Mountain Dew.
Then the place got almost quiet
Once we set our phones to "vibrate."
He said, "If you wanna make the rent, grrl,
This is what you got to do."

[Chorus]
"You got to know when to ship it,
Know when to slip it,
Know when to refactor,
When to let things stand.
You never work ev'ry weekend
If the CEO's not there, too.
There'll be time enough for workin'
When the Round A lands."

"Now, ev'ry Greybeard knows,
That the secret to the pay-off
Is knowin' that ideas mean jack
When your team can't see them through.
'Cause every app. is Facebook
And every app. is Friendster,
And the best that you can hope for
Is your VCs know it, too."

And when he'd finished speakin'
He ordered up an Uber,
Buffed his LinkedIn resume,
Tossed his work-badge in the trash.
And once at his next start-up,
The Greybeard hit the jackpot.
But in his parting words I'd found
Advice that I could cash.

[Repeat chorus three times]

How to go from Dunning-Krueger* to Imposter Syndrome in 3 weeks or less

This past February, the (ahem!) "illuminati" of the Moncton User Group had a problem:  No speaker lined up for March.  Now, I had already started a spiel on basic AVR microcontroller programming.  Problem was, it was intended for more of a Makerspace crowd.  Alas, the local Makerspace has been in a lull for awhile now, which left a half-finished outline languishing in a folder alongside a bunch of transition slide images.  But I figured that if I tossed out the hardware-oriented "What is a Circuit?" bits and amped up the code samples, it could be made to work...in a "niche" sort of way.

It's been roughly a year and a half since I stood up in front of my MUG colleagues to bang on about my latest nerdery.  So I knew that I was basically out of shape as a presenter.  Still, I had a bit over three weeks to finish the outline and turn it into slides, but no big deal because it's really only the bare-bones basics, plus I totally know where I'm going with it and, anyway, the Arduino presentation was so long ago that nobody will realise that I'm poaching half the image files and honestly it's not like anyone here will be starting out from scratch with a C-like programming language anyway, right???

Boy howdy, did that beastie hand ever me my head -- more than any other presentation I've given.  It was pretty humbling, even before I was regaling my shower-door with the soundtrack for the slide-deck.  :~/   I half-expected at least one of my coaches/mentors from UWEC Forensics to show up and administer a well-deserved smack upside the head.  A sampling of mistakes:

• Not verbalising sections as I finished them.  (The first few run-throughs always sound absolutely dreadful; better to break that much dreadful into smaller chunks.)
• Trying to cram too much into single slides/sections.  The last-minute right-sizing set me back to square one for the most difficult (and crucial) part of the whole thing.
• The demo. part should have been chucked overboard.  The idea was to pull everything together and mop up the important nitty-gritties that weren't covered by the basic examples.  But even contrived and oversimplified, it was too much for a fatigued group of people, smart as they are.
• Procrastinating until almost too late on wiring up an actual breadboard with the demo. project and trying to upload my sample code.  Rookie mistakes that egregious on the Friday before a Tuesday presentation is nothing short of speaker malpractice, IMLTHO.
• Procrastinating until too late for actually timing the whole presentation.  It ran close to 90 minutes end-to-end,  I figure that 75 minutes was pushing the limits of people's patience.  My last minute cuts never actually made it all the way out the door b/c of nerves.  Bad, BAD me.
• Overconfidence in how quickly I could translate my extremely n00b understanding of a subject into something that could be understood by someone coming into the subject fresh.  (Arduino has made huge inroads into the AVR space for a reason, fam!)
• And the great-grand-matriarch of all the other mistakes:  Having precisely zero practical experience before volunteering.  Don't get me wrong:  I'm a huge fan of learning by teaching, but this skirted dangerously close to the proverb about the blind leading the lame.

From the standpoints of sound and flow, it wasn't horrible -- that much, at least, can be said without relying on charity.  I learned decades ago how to fake confidence.  Despite the nerves (or maybe because of them), my ex-coaches would certainly have approved of both the volume and variety of hand-gestures and body language.  With, by the bye, no reading directly off slides (the cardinal sin of any presentation).  There were a couple of small stumbles, one slide-transition hiccup -- nothing that fazed me, even in front of my peers (a.k.a. my betters).

But there was a ominous lack of response when I ended every section/subsection with "Any questions about that?"  Uh-oh.  Which tells me that, at best, I bored just over 20 very talented people who have better things to do on a Tuesday night.  At worst, I made them lose whatever interest they might have had in AVR programming.

Cold comfort, I suppose, that I don't crawl out of the rubble entirely empty-handed.  Quite apart part from the obvious perks of thoroughly understanding the material and having a sweet set of references all in one place, nat'cherly.  And an even greater appreciation for everything that the Arduino ecosystem has accomplished. No, my personal takeaway from this three weeks of scrambling is where I need to turn my attention next.  And next.  And next.  And so on.  (Respectively, those "nexts" are Serial I/O, timers, pulse-width modulation, I2C and SPI communication, and then whatever I don't recognise while I'm tripping through all that.)

It goes (almost) without saying that I will certainly leave room in my brain for the lessons (and humility) acquired after  ear-bashing my I/T colleagues.  In another year or two, I'll be back up in front of the room.  And it's not so much a matter of living down this talk as it is living up to the standards set by the other presenters who generously share their time and knowledge (and war-stories) with us. 

- - - - - -

* The Dunning-Krueger Effect is the inability of a newbie to correctly assess her/his abilities in a new area of competence.