I am a firm believer in the old saying: "A closed mouth gathers no foot." (I strive to be polite to others)
I have a fairly decent background in hands-on, electronics engineering technician work (over 30 years earning a paycheck and 12 years before that as a home hobbyist/student).

To a lesser degree, I have dabbled somewhat with programming; beginning with student work on the Commodore PET 16, then moving to the Apple II+ beginning with Apple BASIC, then Pascal, and then I taught myself assembly for the 6502, as there were no classes I could take, so I bought a book on Apple Assembly language and studied and experimented and made many mistakes and learned from them.

Beyond this, I've worked with assorted PLCs and Microchip's PIC16C54 and PIC16C57 for various assembly language driven projects.

Three years ago I became interested in the Arduino UNO Rev3 and have first, worked through the starter pack examples, then moved on to some solo mini projects on my own (self taught, with many goofs and blunders I made; but with self-application of extra "Skull-Sweat" to figure out on my own where I screwed up how to un-screw up my mistakes!).

Another old/new saying I apply to my haunted head: "When in doubt Read The Directions, Bonehead! aka RTFM, with try Google searching the matter".

I remain, always, a permanent student, a seeker of knowledge, a maker of mistakes who learns by doing, and a questioner who first asks myself, "Now where/how did I screw up THIS time?!?!"

Note: The second thing I ask myself (and sometimes other people) is, "Now what am I not seeing or overlooking in the mistake(s) I made??"

When faced with a complex problem (which includes Circuitry, programming, goals to be achieved, issues regarding safety concerns, etcetera) I believe in: "Break the problem up into smaller, more manageable chunks, and resolve each one of these smaller portions one by one. If any of these smaller portions still cause me troubles, see about breaking that one up into sub-sub-portions and work those out. Once this is accomplished, start putting them together slowly, with prove-out testing(s) along the way".