In This Episode: Dealing with change and making it an adventure.
This week the TEH Podcast is hosted by Leo Notenboom, the “Chief Question Answerer” at Ask Leo!, and Gary Rosenzweig, the host and producer of MacMost, and mobile game developer at Clever Media.
(You’ll find longer Bios on the Hosts page.)
Top Stories
- GR: Change…
- Some things you can stop from changing. For instance: Furniture
- Other things rarely change, but when they do you can’t do anything about it. For instance: traffic light nearby
- Some things will change more often (restaurants and stores nearby)
- Software and hardware are fluid and always changing.
- Often hear this: If it isn’t broke, don’t fix it
-
- Things can “break” without you realizing it or even experiencing it.
- You are not the only customer
-
- My approach: Embrace Change. Love it. Look at it as an adventure. Something new to explore.
Ain’t it Cool
-
- LN: Deep Fakes
- LN: Free cool sounds. https://notificationsounds.com/
- GR: Fake Famous (HBO).
- … and Tiktok
Leo, you brought up some great points about the ease of technology creating indistinguishable fakes. I think it is human nature to want to trust other people and what we are told. Advertising and marketing depend on being able to develop a level of trust quickly. NPR’s “All Things Considered” had a segment this past week, April 22nd, 2021, which highlighted how India’s election process is trying to reign in disinformation spread through social media, essentially by getting targeted messages out preemptively. I wonder if our American education system should include some curriculum about disinformation? (https://www.npr.org/2021/04/22/989938941/how-india-is-confronting-disinformation-on-social-media-ahead-of-elections)
I worked for several software development companies over my career and had experience as a programmer in my early career. I have often said I would have enjoyed programming more if it just wasn’t for end-users using what I wrote. Everything about getting a commercial application out the door was about compromises between what could be developed in what time to satisfy which customers. Even as an “insider” who knew more than a little about the structure of the source code it was hard for me to get the development team to make even the smallest of changes to support my customers.
Thanks for the podcasts. I enjoy listening to the banter between you and Gary. I also relate to Gary’s need to read and sometimes comment on public forums such as Reddit.com.