Best Tech Podcasts This Week – 05/01/23
The Tech Tribune staff has compiled a list of the best new tech podcasts released in the last week (as of the time of writing):
“Sunny and Vinny are back to break down ChatGPT’s latest innovation: the Code Interpreter. They demonstrate its capabilities with two separate datasets on EVs in America and US Bank Failures (10:58) before discussing how platforms like ChatGPT will revolutionize organizational efficiency (31:19).”
“The FDA warns of a vulnerability affecting biomedical devices. Ransomware’s effects continue to trouble the US Marshals Service. The US Justice Department shifts how it deals with large scale cybercrime. Fresh phish from the GRU. Caleb Barlow looks at unicorns and zombiecorns. Our guest Manoj Sharma from Symantec explains the differences between Zero Trust and SASE. And KillNet runs an ask-me-anything session.”
“SpaceX’s recent Starship test flight, the first during which it flew with its Super Heavy orbital booster, was a bit more of a mess than it even appeared when it ended with a large explosion.”
“Hyperswitch is like the adapter pattern for payments, Austin Henley writes about the future of programming by summarizing recent research papers, Thoughtworks published their 28th volume of their Tech Radar, the team at General Products reminds devs to scan our technical writing for words such as “easy”, “painless”, “straightforward”, “trivial”, “simple” and “just” & we finish with a lightning round of cool tools.”
“Softbank’s chip designer Arm has confidentially filed to go public, seeking a valuation of $30 billion to $70 billion in what is shaping up to be the biggest IPO of the year. Could it be the key to thawing a frozen IPO pipeline? Plus, investor Brad Gerstner lit into Sundar Pichai for losing Google’s AI lead to OpenAI, leaving investors questioning whether he can get tough on the issue.”
“Bug reporting hasn’t changed since the 1990’s. Despite all the technological advancements we’ve made in the rest of software development, the way we handle bugs has stayed the same.
It is common practice for non technical teams to provide bug reports that are missing vital information for developers to identify and quickly fix code, such as: network requests, console logs, HAR file, device information, video or screenshot replication, and more.
Providing a comprehensive bug report requires logging into many tools and time spent context switching, creating an environment where people are less likely to report bugs, which is not an ideal scenario for any founder or builder.”
“Gurman says the big Apple Watch OS overhaul is nigh. I can already tell you what the biggest tech IPO of 2023 is going to be. Are there signs tech earnings have turned or a corner, or, at least, have bottomed out? And why the AI revolution is behind the potential of a major labor strike in Hollywood.”
“We’ve all experienced the creepiness of modern data trafficking, but that kind of daily annoyance is the surface of a much bigger issue: Big Tech companies such as Amazon & Microsoft are lobbying policymakers to veto laws that harm their business, and often hide their lobbying behind industry coalitions or organizations with names that are vague and seemingly harmless. Will current and future privacy laws actually protect your information, or will they protect the companies collecting your information?”
“On this week’s episode of the Android Central Podcast, Shruti Shekar, Jerry Hildenbrand, Derrek Lee, and Nick Sutrich discuss the Google I/O 2023 program, Fairphone’s sustainability model, review Motorola’s Rizr & ThinkPhone, debate whether they’d ditch Android for $10,000, and more!”
“I work at a startup that makes embedded devices and the software that runs on them. Everyone on the tech team does both. We recently hired someone to lead the tech team to give the CTO more time for other duties. My new boss is incredibly experienced with hardware design and embedded systems and has been in the industry for a long time (40+ years). However, they are not familiar with modern software practices like version control. They will frequently ask us to do things like delete all copies of a broken version of software. When we try to explain how git works they will ask us to make a new repo with the now working version of the software even if the fix was a 1 line change. How can I politely explain that they just don’t understand how this works and correct them without being rude?”