The Amp Hour Electronics Podcast

A weekly show about the trends in the electronic industry.

  • For Us
    • Donate
    • Link Here!
    • Suggest
      • Guest Suggestions
      • Story Suggestions
      • Feature My Workbench!
    • Advertising
  • For You
    • Episode Index
    • Guest Episodes
    • Buy Stuff
  • About
  • Email
  • Facebook
  • LinkedIn
  • RSS
  • Twitter
  • YouTube
You are here: Home / Radio Show / #460 – Rubber Ducking

#460 – Rubber Ducking

Play

Podcast: Play in new window | Download

Subscribe: Apple Podcasts | RSS

  • Chris has been reading “Zen and the Art of Motorcycle Maintenance”, among other things
  • Debugging with GDB
  • Jay Carlson on Embedded.fm
  • The Amazing $1 Microcontroller
  • EEVblog2 video with David, using volatile inside interrupt routines
  • Rubber ducking
  • Keeping notebooks
  • A scan of an engineer’s notebook from 1978 while designing the Atari 400 and 800
  • Grass Valley Group, later merged with Tek
  • Chuck Peddle interview
  • Dave’s video about engineering notebooks about a PC based logic analyzer
  • What are modern versions of lab notebooks? Evernote? One note?
  • Feature Phone from Germany (CCCamp)
  • The $8.70 “mystery item” was in fact a Process Meter (DMM with a constant source built in)
  • Boston Dynamics is now commercially selling their Spot robot
  • Buying industrial robot
  • Former guest James Bruton
  • Re-using stuff you know
  • Former guest Jeri Ellsworth is crowdfunding the Tilt5 project. She talked about this on episode 394, specifically how CastAR burned out and how she was buying the assets to restart as Tilt5.
  • Being disciplined during troubleshooting

Thanks to evarinaldiphotography for the rubber ducky photo

Comments

  1. Martin Hanks says

    September 30, 2019 at 9:18 am

    “Grass Valley” probably referred to Cyan Engineering in Grass Valley CA. GVG was in Grass Valley as well, and later moved to nearby Nevada City. GVG is still in the broadcast hardware business, owned by Belden.

    https://m.youtube.com/watch?v=bfFGrQLuY8s

    Cheers!

  2. Dentaku says

    September 30, 2019 at 11:53 am

    I have problems reading that notebook too.
    It’s probably easier for someone who was in the industry at that time and knows all the acronyms and older technology.

  3. john c says

    September 30, 2019 at 12:51 pm

    Be so very careful who you trust for mind control or so-called new age mentoring !
    sadly many hippies can end up in the gutter with a serious drug addiction.

  4. mark@badensteel.com says

    October 1, 2019 at 3:42 pm

    Factory Seconds ..you mentioned the wonky switch and jacks. So they dumped them and required name to be removed.

  5. ben says

    October 3, 2019 at 10:01 am

    Regarding Atari, there was a recent episode of the Choicelogy podcast (S04E02) where they interview one of the most successful Atari game developers (Howard Warshaw), and how resources (or lack-of) can cause poor decisions. The podcast is usually about behavioral-economics/finance, but anyone interested in Atari or designing on a tight schedule will appreciate it!

  6. Michael L Kornegay says

    October 13, 2019 at 8:40 am

    Chris, command line gdb is not very productive. A variety of ide support source level instead of line level debugging.

    When don’t need a full ide, I recommend cgdb. If you are not too intimidated by vi editor like commands, this is a great compromise that does not require graphical environments like x windows.

Copyright © 2023