Tips to software consultants/contractors. A thread. I like to work in VMs, such as Ubuntu.

When using a single VM across multiple clients, I create a unique login/user for each client.

"Matthew Eshleman ClientA"
"Matthew Eshleman ClientB"
etc

Many firmware devs are working on very small teams, often solo.

This means potentially bad habits may have been formed, which have negative impacts on a team based software project. Here are some habits to avoid, even when working solo: Uncontrolled dev environment.

Developers likely created a host PC dev environment piecemeal over time. Works great for one person! (sort of... well...maybe..not really)

Document every thing needed to install/setup in a wiki.

And also learn about Docker or VM approaches.

So, we still use a traditional antenna to watch broadcast TV. We are fans of our local PBS station (WNPT), which is currently broadcasting in low power mode.

I noticed that when I plugged in my iPhone Xs to charge, we would immediately lose the PBS signal.

So... (thread) I started up my MESA spectrum analyzer (reiusa.net/rf-detection/m…) to check the signal.

This is great. The only time I get to see code like this is typically under NDA while under development or while under a court protective order.

First review note: traditional older style C code, but looks professional. Some encoding issues in the comments...

https://twitter.com/mbeddedartistry/status/1245476560758427650

HMI code is c++ though. Appears to be custom framework, not sure yet.
French comments I believe.
Visual Studio Code is handling the code fairly well.
Qt Creator IDE use will need effort.
References to Keil and Borland.