Podcasts about disable

Rosie interviews Dr Jeremy Walker following the recent Australian Senate Select Committee Inquiry on Information Integrity on Climate Change and Energy (2025), to which he presented both written and in person evidence. Dr Walker is Senior Lecturer in the School of Communications, Faculty of Arts and Social Sciences, University of Technology Sydney. He's a member and past director of the Climate Society and Environment Research Centre (C-SERC) at UTS, and a research fellow of the Whitlam Institute, Western Sydney University, and the International Climate Social Science Network based at Brown University, Rhode Island, USA. With two decades of research into the Atlas Network informing his submission, Dr. Walker sheds light on the secretive world of climate misinformation and disinformation. During the show we also discuss the rise of racism and Pauline Hanson; the extended disinformation and astroturfing against the Victoria to NSW Interconnecter (VNI) West and the Victorian ALP government; and the relationship of fossil fuel money and local Atlas Network linked groups to both. The links below are well worth a look: Link to Senate Select Committee on Information Integrity on Climate Change and Energy, with access to submissions, documents, Hansard and video: https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Information_Integrity_on_Climate_Change_and_Energy/ClimateIntegrityDr Jeremy Walker's submission is no. 243. Note that the “additional information” is archival evidence regarding the origin and early sponsorship of Australia's Centre for Independent Studies (CIS). The full report of the Senate Select Committee: https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Information_Integrity_on_Climate_Change_and_Energy/ClimateIntegrity/Report Video from the Senate committee's hearings on 16/02/2026Note that Jeremy Walker appears at 10.37 am (in between evidence from Meta and Coal Australia - well worth watching as well!):https://www.aph.gov.au/News_and_Events/Watch_Read_Listen/ParlView/video/4334923Hansard transcript of Jeremy Walker's testimony at the hearing is here:https://parlinfo.aph.gov.au/parlInfo/search/display/display.w3p;db=COMMITTEES;id=committees%2Fcommsen%2F29259%2F0002;query=Id%3A%22committees%2Fcommsen%2F29259%2F0000%22 The Senate inquiry gets great context and writeups by the ABC's Gareth Hutchens: https://www.abc.net.au/news/2026-01-26/atlas-network-mont-pelerin-society-neoliberal-think-tanks/105700628https://www.abc.net.au/news/2026-02-19/climate-disinformation-senate-committee-dr-karl-atlas-network/106350002https://www.abc.net.au/news/2026-03-29/senate-report-misinformation-climate-change-recommendations/106497978 Jeremy also spoke about the Australian Security Leaders Climate Group (ASLCG) and their report, The Climate Disinformation War: How to fight back for Australia's democracy and security.  

Franck Martin returns to the show to discuss the practical challenges of retiring IPv4 with hosts Ed, Nick, and Tom. Together they break down key strategies, how to work effectively with vendors, and how to mitigate potential outages during the transition. They also explore the cultural shifts necessary for successful IPv6 adoption and the importance... Read more »

Franck Martin returns to the show to discuss the practical challenges of retiring IPv4 with hosts Ed, Nick, and Tom. Together they break down key strategies, how to work effectively with vendors, and how to mitigate potential outages during the transition. They also explore the cultural shifts necessary for successful IPv6 adoption and the importance... Read more »

Franck Martin returns to the show to discuss the practical challenges of retiring IPv4 with hosts Ed, Nick, and Tom. Together they break down key strategies, how to work effectively with vendors, and how to mitigate potential outages during the transition. They also explore the cultural shifts necessary for successful IPv6 adoption and the importance... Read more »

This show has been flagged as Clean by the host. Hello, again. This is Trey. Welcome to part 8 in my Cheap Yellow Display (CYD) Project series. If you wish to catch up on earlier episodes, you can find them on my HPR profile page https://www.hackerpublicradio.org/correspondents/0394.html It is hard to believe that I started this project and the HPR series to document it more than a year ago. Time flies. Life happens. I spent the last 8 months so focused on work related activities that I had to set the project aside. And once I set it aside, it was difficult to get back to again. The one time I tried, I found that my son's old Windows laptop, which I had commandeered to use for the project, was once and truly dead. We live in a different world now than we did when I began this project. Today, everything is about AI – how it is changing our world, increasing efficiencies, and even displacing certain types of jobs. "Vibe coding" is transforming the way we make software, and now everyone is a developer. Within my organization, we are all being strongly encouraged to learn more about AI and apply it in our daily work. We are blessed to have access to a wide range of training and to powerful tools which support the process. Several colleagues within my organization and outside my organization have recommended Claude Code -- for development, for organization, for brainstorming, and for much more. My role is not that of a developer, and I have had no need for Claude Code at work. There are plenty of other tools for me to use. But at home, I thought... I could install Claude Code at home to experiment with and to learn. And then it hit me. I wonder if I could use Claude Code to help me with my stalled CYD project. "Hello, my name is Trey, and I am a fraud." OK. I don't think I am a fraud, but having never used such a powerful tool to help me code, I feel a little bit like a fraud, with Claude doing the work for me. Let's talk through what we did. As I mentioned, I was unable to use the laptop on which I created the original GUI code. But no worries, because It was all on GitHub, right? So, I began by trying to install Claude Code on one of my Ubuntu machines. That failed miserably, and all the instructions I found online recommended running it on Windows. So I transitioned to installing Claude Code on a freshly built Windows 10 system using some old hardware which will not support Windows 11. Surprisingly, It seems that Claude wants to run within Ubuntu on Windows Subsystem for Linux (WSL). Once I went through all the hoops for installing and setting up my basic subscription, I got to work. I created a new directory to use for all my project files, and another one for Claude to write all its output files to. Everything I have read and heard about using Claude Code for a project like this recommended beginning by using Claude to create the project plan. So my first prompt was as follows: "I am building a project using an ESP32 cheap yellow display. The final goal is to have a device with a graphical user interface which will allow me store several text messages, each assigned to their own specific button. Then, when one of the buttons is pressed, the message will be converted into morse code, and the message will be sent by blinking an onboard LED. I already have the initial design for the GUI coded in my github repository. Please construct a detailed step by step plan for building this application" I wanted to keep it simple at the beginning, so even though I plan to use an opto-isolated relay for the output, I am starting out using the built in LED. Claude asked me for the URL for my Github repository, and I provided it. After thinking for a bit, it produced a project plan. CYD Morse Sender — Step-by-Step Build Plan What You Already Have - 3 fully designed LVGL screens (Send, Config, Keyboard) - 7 send buttons with green styling on the Send Screen - Speed slider (5–30 WPM) and program slot dropdown on Config Screen - Text area + LVGL keyboard widget on Keyboard Screen - Display driver and touchscreen hardware initialized (but touch read was stubbed out) --- Phase 1: Fix Touchscreen Input Initialize the XPT2046 on VSPI, replace the hardcoded touched = false with real touch data, calibrate raw ADC coordinates to screen pixels, and verify all three nav buttons transition screens correctly. Phase 2: Persistent Message Storage Use Preferences.h / NVS to store 7 messages ("msg0" – "msg6") that survive power cycles. Load on boot and populate send button labels. Phase 3: Config Screen — Slot Selection & Speed Wire the Program dropdown to g_selectedSlot, wire the Speed slider to g_wpm with a live WPM label, and wire the Set button to clear the text area and navigate to the Keyboard Screen. Phase 4: Keyboard Screen — Capture and Save Text On keyboard OK (LV_EVENT_READY): read the text area, save to NVS, update the send button label, navigate back. On Cancel: navigate back without saving. Phase 5: Morse Code Engine Build morse.h with the full A–Z / 0–9 lookup table, a textToMorse() converter, and Paris-standard timing (unit_ms = 1200 / wpm). Phase 6: Non-Blocking LED Transmission State machine (IDLE / LED_ON / LED_OFF) driven by millis() in a morseUpdate() function called every loop — no delay(). LED on GPIO 17 (blue). Phase 7: Wire the Send Buttons Each button calls startMorse(getMessage(slot)) if not already transmitting. Disable all send buttons during TX; re-enable when the state machine reaches the end. Phase 8: Integration & Polish Stop button, WPM persistence, empty-slot guard, serial debug output, final touch calibration, end-to-end test checklist. --- Recommended order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 This was wild! Claude determined exactly how far along I was in the project, and also alerted me to the fact that the "touch read was stubbed out". Ugh. This means that the files I had uploaded to GitHub were my original GUI files (Episode 05 – HPR4532 - https://hackerpublicradio.org/eps/hpr4532/index.html ) and not the ones that I finally got working properly (Episode 07 – HPR4624 - https://hackerpublicradio.org/eps/hpr4624/index.html ). That was my own fault. Did I mention that I don't get Git? I REALLY need to learn to properly use Git! But, we have a plan, broken down by eight numbered phases. And they seem to address all the functionality I wanted with a few additional things I had not thought about. Interestingly, even though these phases are sequentially numbered, Claud recommended that we approach them in a bizarre order: Phase 1 → 2 → 7 (partial) → 5 → 6 → 7 (full) → 3 → 4 → 8 . Alright. Let's see what we can do. The first phase is to fix the touchscreen input. Claude took me through it step-by-step, asking as it needed to read specific project files. Finally, it wrote a new ui.ino code file to my speficied output directory for me to test. I copied it into the correct file location, said a quick prayer, compiled in Arduino IDE, and downloaded to the CYD. Well, that is... interesting. The display looked nothing like it was supposed to. There were vertical green bars with smaller dashed green vertical stripes in them. I will include a picture in the show notes so that you can see what it looked like and why it was so difficult to describe. I spent the next hour or so trying to explain what I was seeing to a chat bot. Claude recommended potential fixes which either did nothing or made the situation worse. I began questioning whether this was a good idea, how people actually gained efficiencies talking to a bot, and even several life choices. Then I had a thought. I prompted Claude: If I were to take a picture of the screen on the cheap yellow display and copy it into the output folder, would you be able to analyze it to better determine what is wrong and how to fix it? Shockingly, Claude answered in the affirmative, and told me to copy the picture to the output folder and let it know when to proceed. It analyzed the picture and more of the supporting files it had copied from my GitHub, asking each time if it could access that file. It determined that my original code was written for a flavor of LVGL version 8 and I was now using LVGL 9.5. It recommended changes, and then asked permission to make those changes, file by file. .h files & .c files, Finally, I just gave it permission to edit the files in the project folder without asking for permission for each file each time. Claude was still explaining each change, showing me exactly what would be changed, and asking for permission, so that I could review all of the changes. But now it was not asking additional permission to write to each of the impacted files. Next, Code compiled and downloaded. Different screen, but not right. Again, I took a picture and gave it to Claude to analyze. So, Claude paused and altered the code to generate a specific test pattern overtop of the GUI. The test pattern was supposed to cover the entire rectangular screen. But parts of the pattern were in a square on the screen and parts were not. Another photograph and analysis, told Claude that there were some rotation/screensize issues. We repeated this several times. Some resulted in improvement, and others did not. This is the point where I noticed something interesting. Not about Claude, specifically, or about the app. But I noticed something interesting about myself and about the process. Previously, when I was working through some of these challenges without Claud, I found myself becoming more and more stressed, frustrated, and angry, until I found a solution. Then another problem would repeat the cycle. Success in the end was great, but the emotional extremes during the process were not always pleasant. Now, I was effectively managing the project, and relaying information to the resource responsible for fixing the problems -- a very different experience. But I also ran into another issue. Claude became absolutely certain that the problem revolved around the device not accurately knowing where the 4 corners of the screen were. But in reality, the output of the test pattern was rotated 90 degrees from the actual screen. It took several iterations of me insisting that the problem had to do with screen orientation and not corner coordinates. It was interesting to experience the tool doubling down on an obvious mistake, but we finally resolved that. Again, while it was frustrating, it was much less stressful. We proceeded to Phase 2: Persistent Message Storage where we ensured that the button labels on the send screen were stored in the devices persistent storage, so that, when they are edited to contain the message they should send, that information would survive a reboot. Next, we combined elements of Phase 5: Morse Code Engine , Phase 6: Non-Blocking LED Transmission , and Phase 7: Wire the Send Buttons together. Building the morse code engine was an area I had been thinking about for a while. I already had working parts of something similar in the Arduino practice oscillator I have referenced a few times in this series. The code for the practice oscillator may be found on my GitHub, but it was all based on original code from jmharvey1, with my only contribution being making pin assignments variables so that the code could easily be ported to different devices. So, I was happy that we were building the morse code engine directly. The code for it may be found in morse.h, which uses a constant character lookup table to define each character. Without any specific direction from me, Claude used the PARIS timing methods I have already described within Episode 6 of this series. It defines timing for DOT, DASH, LETTER_GAP, and WORD_GAP, and all are based on a simple calculation of 1200 ms / the number of words per minute (WPM) we wish to transmit. Along the way, we discovered that, if we tried to use the delay() function, it would crash the program due to a conflict with the LVGL timer used for touchscreen inputs. Claude altered all the delays accordingly. Then, Phase 3: Config Screen — Slot Selection & Speed allowed us to configure the WPM we wished to use in addition to selecting a specific Send button to reconfigure. This forced us to work on Phase 4: Keyboard Screen — Capture and Save Text which is used to type the entries for each Send button. At this point, I also decided that we would want to also use the Keyboard Screen to send ad hoc morse as we typed it. During this phase we discovered several bugs which seemed to cause random freezes. Careful troubleshooting with messages output to the Arduino IDE's serial console helped us narrow down the causes and remedy them. Finally all the tests worked and I am able to merrily pre-configure macro buttons with custom messages and use the CYD to send the morse code for those messages to the on-board LED at whichever rate I specify. I have noticed in my presentation of this narrative that I repeatedly slip into the first person plural terms "we" and "us" instead of the first person singular terms "I" and "me". I have unconsciously personified Claud and recognized it as an integral part of my (formerly one person) development team. I finally configured Claude to connect to my GitHub repo and upload all the files and documentation. We additionally created a CYD-Narrative.md file which describes in more detail all the work which was done on the project. I still do not 100% get git, but we are successfully using it. You can find all these files in my GitHub repo ( https://github.com/jttrey3/CYD_MorseSender ) where they are shared under a GPL 3.0 license. There are still several additional steps I plan to complete in the next few months. 1. I will be integrating an opto-isolated relay which will allow me to plug the device into the straight key input on any amateur radio. This will require a battery power source, charge controller, and more hardware. I... make that "We" (Claude & I) will be modifying the code to support an audio side tone through an attached speaker when sending code We will add an output selection switch to the config page to choose any combination of speaker, relay, or LED as output. We will develop a downloadable firmware which I hope to share with the Cheap Yellow Display community. If you can think of any additional features you would like to see integrated, please drop me an email using the address in my HPR profile. I may also work with a friend to attempt to 3d print a case for the entire contraption, and I will be sure to record additional episodes sharing the process. I have learned so much throughout this project, about the CYD, ESP32, GUIs, Claude Code, GitHub, and most of all, about myself. Does using AI to develop this code make me a fraud? It still feels like it in some ways. Does it make me more productive? ABSOLUTELY! I made consistent forward progress when I only had 30-60 minutes each day to work on it, and everything discussed in this episode was completed in less than a week. If I had been able to work on it for a few hours uninterrupted, it may have only taken me 3-5 hours. Does it empower and inspire me to do more projects like this? 100% I feel like I had support working with me the whole way. I was less stressed overall, and it had less of an impact on the amount of and quality of time I spent with my family. I will be wrapping up this series soon, without any more 6 month gaps, I hope. Until next time... Provide feedback on this episode.

Episode 254: Microsoft Cuts 4,800 Jobs, Meta Faces a $1.4 Trillion Lawsuit, Apple Loses in Europe, and the iPhone Ultra NearsJay and Karl discuss another turbulent week across big tech, AI, gaming, and consumer hardware. Microsoft announces another round of layoffs that hits Xbox particularly hard, Meta finds itself fighting legal battles on multiple fronts, and Apple loses an important appeal over the App Store in Europe.We also look at Meta's continued investment in mixed reality hardware, fresh evidence that Nvidia's long-rumoured RTX 50 Super cards may finally be on the way, and the latest reports suggesting Apple's iPhone Ultra could launch in extremely limited numbers.Also available on:Apple Podcasts | YouTubeIn This EpisodeNewsMicrosoft cuts 4,800 jobs and shrinks Xbox in 'significant restructure'Microsoft announces another major restructuring, with significant impacts across Xbox and other divisions.Meta is facing $1.4 trillion in state lawsuits over social media addictionUS states continue legal action against Meta over the impact of its platforms on younger users.Disable autoplay and infinite scroll or risk massive fines, EU tells MetaEuropean regulators increase pressure on Meta to redesign key engagement features.Apple loses legal fight over its App Store 'gatekeeper' status in EuropeApple's appeal fails, meaning it remains subject to the EU's Digital Markets Act requirements.Meta reaffirms work on multiple next-generation headsetsMeta confirms several future VR and mixed reality devices remain in active development.RTX 5080 Super, RTX 5070 Ti Super and RTX 5070 Super appear in PSU calculatorNew evidence suggests Nvidia's refreshed RTX 50 Series GPUs could arrive sooner than expected.RumoursReport: iPhone Ultra to have incredibly limited availability at launch, may ship slightly laterApple's premium iPhone Ultra could be difficult to buy at launch if the latest reports prove accurate.Say hello:@WeeklyTechRant | @weeklytechrant.bs

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Tonya Edmonds.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Tonya Edmonds.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Tonya Edmonds.

Doug and Rob Allen talk about Identity, EDR, Your Great Aunt Ida Meets some hot firefighters, and more. Segment Resources: Qilin and Warlock Ransomware Use Vulnerable Drivers to Disable 300+ EDR Tools: https://thehackernews.com/2026/04/qilin-and-warlock-ransomware-use.html This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn-591

Doug and Rob Allen talk about Identity, EDR, Your Great Aunt Ida Meets some hot firefighters, and more. Segment Resources: Qilin and Warlock Ransomware Use Vulnerable Drivers to Disable 300+ EDR Tools: https://thehackernews.com/2026/04/qilin-and-warlock-ransomware-use.html This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Show Notes: https://securityweekly.com/swn-591

Doug and Rob Allen talk about Identity, EDR, Your Great Aunt Ida Meets some hot firefighters, and more. Segment Resources: Qilin and Warlock Ransomware Use Vulnerable Drivers to Disable 300+ EDR Tools: https://thehackernews.com/2026/04/qilin-and-warlock-ransomware-use.html This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Visit https://www.securityweekly.com/swn for all the latest episodes! Show Notes: https://securityweekly.com/swn-591

Doug and Rob Allen talk about Identity, EDR, Your Great Aunt Ida Meets some hot firefighters, and more. Segment Resources: Qilin and Warlock Ransomware Use Vulnerable Drivers to Disable 300+ EDR Tools: https://thehackernews.com/2026/04/qilin-and-warlock-ransomware-use.html This segment is sponsored by ThreatLocker. Visit https://securityweekly.com/threatlocker to learn more about them! Show Notes: https://securityweekly.com/swn-591

Referências do EpisódioUnpatched Langflow Flaw CVE-2026-5027 Exploited for Unauthenticated RCEExpanded JDY IoT and SOHO botnet enables rapid vulnerability exploitationCVE-2026-0274 Cortex XSOAR: Improper Validation of Credentials in CommvaultSecurityIQ integrationWho Runs the Ransomware Group ‘The Gentlemen?'GitHub to Disable npm Install Scripts by Default to Stop Supply Chain AttacksRoteiro e apresentação: Carlos CabralEdição de áudio: Paulo Arruzzo Narração de encerramento: Bianca Garcia

Reid Davenport (he/him) is an award-winning documentary filmmaker and he is an Unapologetically Black Unicorn. Reid talks about disability rights, medical ableism and the things that shape how society values disabled lives. They talk about Reid's powerful film “Life After” and the issues it raises about the value of a person's autonomy, the intersectionality of race and disability and the supports people need to live meaningful lives. To learn more about Reid Davenport visit: https://www.reiddavenport.com/   The National Suicide Prevention Lifeline is now: 988 Suicide and Crisis Lifeline Contact the show: UBU@UnapologeticallyBlackUnicorns.info Transcripts are available on Apple Podcasts.

On this week's show a listener asks for some help with keeping his audio in sync with his video. We also discuss how to turn off the ACR on your Smart TV. But first we read your emails and take a look at the week's news. News: Here's What's Coming in the 2026 Apple TV Roku's Howdy Streaming Service Reaches an Estimated 1 Million Users Deal Alert! 65" TV for $238 Audio Sync in a Home Theater Byron's request for answers to some specific questions on audio sync: I'd appreciate it if you guys could provide some "guiding principles" on syncing audio in a home theater setup. I have four questions: 1. Should the AVR be the ONLY place to mess with syncing settings (when everything runs through it, including ARC)? Yes, in most cases—this is the recommended approach. Start with AVR settings at zero or Auto, enable Auto Lip Sync if available, and adjust the manual audio delay there. Avoid adjusting on the TV or sources unless you have a specific reason like a stubborn source that bypasses the AVR. Changing multiple devices creates conflicts and makes troubleshooting harder. 2. If AVR is the main adjustment point, do sources automatically stay in sync after setting it once?  Often yes, especially with Auto Lip Sync enabled and consistent sources. The AVR's delay setting (or per-input memory) applies across similar content. However: Different video formats, resolutions, SDR vs. HDR/Dolby Vision,  60Hz vs. 24p or processing modes can introduce varying delays. Some AVRs store audio delay per input, so one good setting per source/input often suffices.  3. For Fire TV Sticks, Apple TV, etc.: Do sync settings apply across all apps, or per-app? Fire TV Stick: The AV Sync Tuning (under Settings > Display & Sounds > Audio) is generally a device-wide offset. It should hold across apps for the HDMI output. Individual apps might have minor internal variations, but a global tweak usually covers most cases. Reboot the stick if sync drifts. Apple TV: No built-in manual per-app delay slider in standard settings. There's a Wireless Audio Sync calibration that uses the iPhone for measurement, which is more global. Different apps (e.g., Netflix vs. others) can sometimes show varying sync due to their decoding/processing—users often report needing AVR tweaks when switching apps. Match Frame Rate and consistent audio formats help stability.  In both cases, rely on the AVR for the heavy lifting. 4. Do higher-end AVRs allow different sync settings per input? Yes! Many mid-to-high-end models store audio delay/lip sync per input source. Examples include Denon models with "Master Audio Delay" or similar, where you can set and recall different ms offsets (often 0–500ms) for each HDMI input. This is a big convenience for multiple devices. Check your AVR manual for "Audio Delay," "Lip Sync," or "per input" settings. Additional Best Practices Minimize variables: Disable unnecessary video processing (motion smoothing, noise reduction) on the TV and AVR to reduce video latency. Use "Game" or "Pure Direct" modes where possible for lower lag. HDMI/ARC specifics: Ensure high-quality HDMI cables. eARC is better than ARC for bandwidth and sync negotiation. Power cycle everything (unplug) after big changes. Order of troubleshooting: AVR Auto Lip Sync → Manual AVR delay → Source device tweaks → TV audio delay (last). Test tools: Use built-in sync tests on your devices or YouTube "lip sync test" videos. The Most Effective ways to Circumvent Smart TV Spying Last week we talked about how your TV was spying on what you are watching. This week we discuss how to prevent that from happening. The following are the most effective ways to circumvent smart TV spying and related data collection, ranked from easiest/quickest to most thorough. These also help limit proxy network enrollment in shady apps. 1. Disable ACR Directly in TV Settings (Quickest First Step) Most brands let you turn off Automatic Content Recognition (and related ad/personalization features) without losing core picture quality. Do this on every TV: Samsung: Home button → Sidebar menu → Privacy Choices → Terms & Conditions / Privacy Policy → Uncheck Viewing Information Services (and Interest-Based Ads if present). LG: Settings → General → System → Additional Settings (or Advanced) → Turn Live Plus OFF → Also enable Limit Ad Tracking. Sony: Settings → Initial Setup → Disable Samba Interactive TV. Vizio: System → Reset & Admin → Turn Viewing Data OFF. Roku TV / Roku-based: Settings → Privacy → Smart TV Experience → Uncheck Use Info from TV Inputs. Hisense / TCL: Settings → System or Privacy → Disable Smart TV Experience or Use Info from TV Inputs. Amazon Fire TV: Preferences → Privacy Settings → Turn off data tracking options. After changing, restart the TV. Check the setting again after any software update, as it can reset. Also disable voice assistants, microphones, and cameras (cover them physically if needed). 2. Block Internet Access to the TV (Highly Effective) The simplest long-term fix: Prevent the TV from phoning home at all. Don't connect it to Wi-Fi or Ethernet in the first place. Or, on your router: Create a guest Wi-Fi just for the TV, then use firewall rules, parental controls, or MAC address blocking to stop all outbound internet traffic (while allowing local network access if you stream from a NAS/Plex/Jellyfin). Advanced: Use a tool like Pi-hole or AdGuard Home on your network to block known tracking domains. Pro tip: Many people report the TV works fine (or even faster) for HDMI inputs and local streaming when fully offline. External streaming devices handle all internet needs. 3. Use the TV as a "Dumb" Display Only Treat your smart TV like a big monitor: Connect all content via HDMI from a more private device (never use the TV's built-in apps). Recommended external boxes (in order of privacy-friendliness): Apple TV — Clean interface, minimal tracking, no aggressive ads. NVIDIA Shield or other local-media-focused devices.  Raspberry Pi or HTPC running Kodi/Plex for full local control. This bypasses the TV's OS almost entirely. 4. Go Fully "Dumb" (Most Private Long-Term Solution) Buy a true dumb TV or large computer monitor (no smart features, no Wi-Fi, no ACR). Options exist in smaller sizes or from brands like Westinghouse for basic panels. Pair it with an external streamer or your own computer/laptop via HDMI. Many privacy-focused users prefer this setup over any "smart" panel. Important reality check: Disabling ACR and blocking internet stops most viewing-data collection, but no method is 100% foolproof against every firmware trick or future update. The nuclear option—keeping the TV completely offline and HDMI-only—remains the gold standard for privacy.  

We are talking abou the Malmstrom "UFO" incident.Please support the show.Patreon

Reid Davenport (he/him) is an award-winning documentary filmmaker and he is an Unapologetically Black Unicorn. Reid talks about disability rights, medical ableism and the things that shape how society values disabled lives. They talk about Reid's powerful film “Life After” and the issues it raises about the value of a person's autonomy, the intersectionality of race and disability and the supports people need to live meaningful lives. To learn more about Reid Davenport visit: https://www.reiddavenport.com/   The National Suicide Prevention Lifeline is now: 988 Suicide and Crisis Lifeline Contact the show: UBU@UnapologeticallyBlackUnicorns.info Transcripts are available on Apple Podcasts.

Running Oracle Database@AWS is most effective when you have full visibility and control over your environment.   In this episode, hosts Lois Houston and Nikita Abraham are joined by Rashmi Panda, who explains how to monitor performance, track key metrics, and catch issues before they become problems. Later, Samvit Mishra shares key best practices for securing, optimizing, and maintaining a resilient Oracle Database@AWS deployment.   Oracle Database@AWS Architect Professional: https://mylearn.oracle.com/ou/course/oracle-databaseaws-architect-professional/155574 Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ X: https://x.com/Oracle_Edu   Special thanks to Arijit Ghosh, Anna Hulkower, Kris-Ann Nansen, Radhika Banka, and the OU Studio Team for helping us create this episode. ------------------------------------------------------ Episode Transcript: 00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Welcome to the Oracle University Podcast! I'm Nikita Abraham, Team Lead: Editorial Services with Oracle University, and with me is Lois Houston, Director of Communications and Adoption with Customer Success Services  Lois: Hello again! Last week's discussion was all about how Oracle Database@AWS stays secure and available. Today, we're joined by two experts from Oracle University. First, we'll hear from Rashmi Panda, Senior Principal Database Instructor, who will tell you how to monitor and log Oracle Database@AWS so your environment stays healthy and reliable. Nikita: And then we're bringing in Samvit Mishra, Senior Manager, CSS OU Cloud Delivery, who will break down the best practices that help you secure and strengthen your Oracle Database@AWS deployment. Let's start with you, Rashmi. Is there a service that allows you to monitor the different AWS resources in real time? Rashmi: Amazon CloudWatch is the cloud-native AWS monitoring service that can monitor the different AWS resources in real time. It allows you to collect the resource metrics and create customized dashboards, and even take action when certain criteria is met. Integration of Oracle Database@AWS with Amazon CloudWatch enables monitoring the metrics of the different database resources that are provisioned in Oracle Database@AWS. Amazon CloudWatch collects raw data and processes it to produce near real-time metrics data. Metrics collected for the resources are retained for 15 months. This facilitates analyzing the historical data to understand and compare the performance, trends, and utilization of the database service resources at different time intervals. You can set up alarms that continuously monitor the resource metrics for breach of user-defined thresholds and configure alert notification or take automated action in response to that metric threshold being reached. 02:19 Lois: What monitoring features stand out the most in Amazon CloudWatch? Rashmi: With Amazon CloudWatch, you can monitor Exadata VM Cluster, container database, and Autonomous database resources in Oracle Database@AWS. Oracle Database@AWS reports metrics data specific to the resource in AWS/ODB namespace of Amazon CloudWatch. Metrics can be collected only when the database resource is an available state in Oracle Database@AWS. Each of the resource types have their own metrics defined in AWS/ODB namespace, for which the metrics data get collected.  02:54 Nikita: Rashmi, can you take us through a few metrics? Rashmi: At Exadata database VM Cluster, there is CPU utilization, memory utilization, swap space storage file system utilization metric. Then there is load average on the server, what is the node status, and the number of allocated CPUs, et cetera. Then for container database, there is CPU utilization, storage utilization, block changes, parse count, execute count, user calls, which are important elements that can provide metrics data on database load. And for Autonomous Database metrics data include DB time, CPU utilization, logins, IOPS and IO throughput, RedoSize, parse, execute, transaction count, and few others. 03:32 Nikita: Once you've collected these metrics and analyzed database performance, what tools or services can you use to automate responses or handle specific events in your Oracle Database@AWS environment? Rashmi: Then there is Amazon EventBridge, which can monitor events from AWS services and respond automatically with certain actions that may be defined. You can monitor events from Oracle Database@AWS in EventBridge, which sends events data continuously to EventBridge at real time. Eventbridge forwards these events data to target AWS Lambda and Amazon Simple Notification Service to perform any actions on occurrence of certain events. Oracle Database@AWS events are structured messages that indicate changes in the life cycle of the database service resource. Eventbridge can filter events based on your defined rules, process them, and deliver to one or more targets. Event Bus is the router that receives the events, optionally transform them, and then delivers the events to the targets. Events from Oracle Database@AWS can be generated by two means: they can be generated from Oracle Database@AWS in AWS, and they can also be generated directly from OCI and received by EventBridge in AWS. You can monitor Exadata Database and Autonomous Database resource events. Ensure that the Exadata infrastructure status is an available state. You can configure how the events are handled for these resources. You can define rules in EventBridge to filter the events of interest and the target, who is going to receive and process those events. You can filter events based on a pattern depending on the event type, and apply this pattern using Amazon EventBridge put-rule API, with the default event bus to route only those matching events to targets. 05:13 Lois: And what about events that AWS itself generates? Rashmi: Events that are generated in AWS for the Oracle Database@AWS resources are delivered to the default event bus of your AWS account. These events that are generated in AWS for Oracle Database@AWS resources include lifecycle changes of the ODB network. The different network events are successful creation or failure of the creation of the ODB network, and successful deletion or failure in deletion of the ODB network. When you subscribe to Oracle Database@AWS, then an event bus with prefix aws.partner/odb is created in your AWS account. All events generated in OCI for the Oracle Database@AWS resources are then received in this event bus. When you are creating filter pattern using Amazon EventBridge put-rule API, you must set the event bus name to this event bus. Make sure you do not delete this event bus. Events generated in OCI and received into event bus are extensive. They include events of Oracle Exadata infrastructure, VM Cluster, container, and pluggable databases. 06:14 Lois: If you want to look back at what's happened in your environment, like who made the changes or accessed resources, what's the best AWS service for logging and auditing all that activity? Rashmi: Amazon CloudTrail is a logging service in AWS that records the different actions taken by a user or roles, or an AWS service. Oracle Database@AWS is integrated with Amazon Cloud Trail. This enables logging of all the different events on Oracle Database@AWS resources.  Amazon Cloud Trail captures all the API calls to Oracle Database@AWS as events. These API calls include calls from the Oracle Database@AWS console, and code calls to Oracle Database@AWS API operations. These log files are delivered to Amazon S3 bucket that you specify. These logs determine the identity of the caller who made the call request to Oracle Database@AWS, their IP from which the call originated, the time of the call, and some additional details.  CloudTrail event history stores immutable record of the past 90 days of management events in an AWS region. You can view, search, and download these records from CloudTrail Event History. You can access CloudTrail when you create an AWS account that automatically gives you the access to CloudTrail. Event history. If you would like to retain the logs for a longer period of time beyond 90 days, you can create CloudTrail trails or CloudTrail Lake event data store.  Management events in AWS provide information about management operations that are performed on the resources in your AWS account. Management operations are also called control plane operations. Thus, the control plane operations in Oracle Database@AWS are logged as management events in CloudTrail logs.  07:59 Are you a MyLearn subscriber? If so, you're automatically a member of the Oracle University Learning Community! Join millions of learners, attend exclusive live events, and connect directly with Oracle subject matter experts. Enjoy the latest news, join challenges, and share your ideas. Don't miss out! Become an active member today by visiting mylearn.oracle.com. 08:25 Nikita: Welcome back! Samvit, let's talk best practices. What should teams keep in mind when they're setting up and securing their Oracle Database@AWS environment?  Samvit: Use IAM roles and policies with least privilege to manage Oracle Database@AWS resources. This ensures only authorized users can provision or modify DB resources, reducing the risk of accidental or malicious changes.  Oracle Data Safe monitors database activity, user risk, and sensitive data, while AWS CloudTrail records all AWS API calls. Together, they give full visibility across the database and cloud layers. Autonomous Database supports Oracle Database Vault for enforcing separation of duties. Exadata Database Service can integrate with Audit Vault and Database Firewall to prevent privileged users from bypassing security controls. Enable multifactor authentication for AWS IAM users managing Oracle Database@AWS. This adds a strong second layer of protection against stolen credentials.  Always deploy your Oracle Database@AWS in private subnets without public IPs. Use AWS security groups and NACLs to strictly limit inbound and outbound traffic, allowing access only from trusted applications. Exadata Database Service supports integration with Oracle Vault for key lifecycle management. And in case of Autonomous Database, the transparent data encryption keys are automatically managed. But you can bring your own keys with OCI Vault. Key rotation ensures compliance and reduces risk of key compromise. Oracle Database@AWS enforces encrypted connections by default. Ensure clients connect with TLS 1.2 or 1.3 to protect data in transit from interception or tampering.  Use Oracle Data Safe's user assessment features to detect dormant users or excessive privileges. Disable unused accounts and rightsize permissions to reduce insider threats and security gap. Export database audit logs to Oracle Data Safe Audit Vault or AWS S3 with object lock for immutability. This prevents lock tampering and ensures audit evidence is preserved for compliance.  11:25 Lois: OK, that covers security. Do you have any tips for making sure your Oracle Database@AWS setup is reliable and resilient? Samvit: Start with clear recovery objectives. Define how much downtime and data loss each workload can tolerate. These targets drive your HADR architecture and backup strategy.  Implement business continuity measures to deliver maximum uptime for your databases. As a best practice, you must configure disaster recovery environment for your critical databases so that, in the event of any disaster affecting the primary database, applications can be immediately failed over to the DR environment, ensuring least application downtime and zero or minimal data loss. With Oracle Database@AWS, you can automate the creation and management of DR environment for your database services using different deployment capabilities. You can opt to configure either cross-availability zone DR in the same region or configure cross-region DR. Since cross-availability zone can only provide site failure protection, you must also configure a cross-region DR to protect against regional failure. A DR plan is only effective if tested. Regular failover and switchover drills validate that people, processes, and systems can recover as designed.  For Exadata Database, Autonomous Recovery Service provides automated backup validation, recovery guarantees, and protection against accidental data loss or corruption.  Oracle-managed backups are fully managed by OCI. When you create your Oracle Exadata Database, you can enable automatic backups by choosing Enable Automatic Backups in the OCI Console. When you do that, you can select Amazon S3 or OCI Object Storage or Autonomous Recovery Service as the backup destination. Don't just take backups. You also need to test them. Regularly restore backups into non-production environment to validate integrity and recovery time.  Plan beyond just the database. Map application and middleware dependencies to ensure end-to-end business resilience. A database failover is useless if dependent apps can't reconnect. 14:09 Nikita: Another area of interest is performance and cost. What practices help teams balance the two? Samvit: Autonomous Database automatically scales CPU and storage as workloads grow. This ensures performance during peaks while avoiding overprovisioning. So you should enable ADB auto-scaling.  Monitor CPU, memory, and IO metrics with AWS CloudWatch to rightsize your compute. Scale up or down based on actual utilization instead of static provisioning. Autonomous databases continuously evaluate and creates indexes automatically. This improves query performance without requiring manual tuning.  Use connection pooling in your applications to optimize database connections. Minimizing round-trip reduces latency and improves throughput. Apply AWS tags to database and related resources for cost allocation and chargeback. Tagging also helps with governance and cost visibility.  Choose between bring your own license and license-included models for Oracle Database@AWS. The right model depends on your existing license portfolio and cost strategy. Not all workloads need long backup retention. Adjust retention policies based on business needs to balance compliance with storage costs.  Exadata Database supports Oracle multitenant with pluggable databases. Consolidating databases reduces infrastructure footprint and licensing costs. Performance tuning isn't just technical. Align metrics with business KPIs. correlating DB performance to user experience and revenue impact helps prioritize optimizations.  16:20 Lois: Before we wrap up, Samvit, let's look at operational efficiency. What advice do you have for making day-to-day operations more efficient? Samvit: Use infrastructure as code tools like Terraform or AWS CloudFormation to automate provisioning. This ensures consistent, repeatable deployments with minimal manual errors.  For Autonomous Database, enable auto-start/stop to optimize costs by running databases only when needed. This is ideal for dev test or seasonal workloads. Exadata Database Service provides fleet maintenance to patch multiple systems consistently. This reduces downtime and simplifies lifecycle management.  Integrate AWS CloudWatch for performance monitoring and EventBridge for event-driven automation. This helps detect issues early and trigger automated workflows. Oracle Data Safe provides ready-to-use audit and compliance reports. Use these to streamline governance and reduce the effort of manual compliance tracking.  For Autonomous databases, Performance Hub simplifies monitoring while Exadata users benefit from AWR and ASH reports. Together, they give deep insights into performance trends. Automated tagging policies and change management workflows help maintain governance. They ensure resources are tracked properly and changes are auditable.  Monitor storage consumption and growth patterns using AWS CloudWatch and the ADB Console. Proactive tracking helps avoid capacity issues and unexpected costs. Send CloudTrail logs into EventBridge to trigger automated incident responses. This shortens response time and builds operational resilience.  18:36 Nikita: Samvit and Rashmi, thanks for spending time with us today. Your insights always help bring the bigger picture into focus. Lois: They definitely do. And if you'd like to go deeper into everything we covered, head over to mylearn.oracle.com and look up the Oracle Database@AWS Architect Professional course. Until next time, this is Lois Houston… Nikita: And Nikita Abraham, signing off! 19:03 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

In this episode, Tyler demonstrates how to disable Hot Corners on macOS.Hot Corners are areas of the screen that perform a specified action when the mouse pointer is hovered over them. As a VoiceOver user who doesn't use the mouse, you might want to configure them to do nothing, so you don't inadvertently cause an action to be performed if you accidentally brush your fingers against the trackpad or use trackpad gestures to control VoiceOver. To do this, go to System Settings > Desktop & Dock > Hot Corners, and make sure the popup menu for each screen corner is set to hyphen (-) rather than any of the actions in the menu.TranscriptDisclaimer: This transcript was generated by AI Note Taker – VoicePen, an AI-powered transcription app. It is not edited or formatted, and it may not accurately capture the speakers' names, voices, or content.Tyler: Hey, AppleVis-ers. Tyler here with a quick tip for how to disable hot corners on macOS. Hot corners are areas of the screen that, when hovered over with the mouse pointer, cause certain functions to be performed, such as locking the screen, starting screensaver, or creating a quick note.Tyler: If you're a voiceover user who doesn't use the mouse, you may want to disable these so you don't inadvertently trigger them in the course of using your Mac, say, if you accidentally brush your fingers on the trackpad or if you use trackpad gestures to control voiceover. To do this, you go into System Settings, Desktop and Dock, click the Hot Corners button, and make sure each of the four corners is set not to perform any action. And I'm going to demonstrate that now on my Mac.VoiceOver: Menu bar Apple. Apple, system settings. System settings. T7, volume, systems, general, window, sidebar.Tyler: D for desktop and dock.VoiceOver: Desktop and dock. Desktop and dock, scroll area.Tyler: Interact with scroll area.VoiceOver: Desktop and dock, scroll area. 77 up.Tyler: And because the Hot Corners button is located near the bottom, I'm going to jump to the bottom of VL Globe, right?VoiceOver: Help button.Tyler: VL left.VoiceOver: Hot Corners button.Tyler: Hot Corners.VoiceOver: Dialog hyphen top left Hot Corner pop-up button.Tyler: Here we are. So at the top of the dialog, VLGlobe left arrow. Okay, so that's hyphen. And that means that there is nothing, no action bound to that hot corner. But if I go into the pop-up menu. Mission control. Application windows. Desktop. Notification center. Apps. Quick note. Start screensaver. Disable screensaver.Tyler: And hyphen, which is do nothing. So if that corner, the top left corner on your Mac is set to do something else and you don't want it to do that, just change it to hyphen. And if you go VL right, bottom left, same deal.VoiceOver: Choose hyphen.Tyler: And top right is hyphen. Hyphen, bottom right. So if all of these are set to hyphen,Tyler: there will be no actions performed when moving the mouse to the corners of the screen. So no hot corner is active. And when you're done, just feel right again, hit done. Hot corners button. And here you are back in system settings. So that's a quick tip for how to disable hot corners on Mac OS. It's a quick set it and forget it task that can help if you…

   While the left works hard to find any little thing that looks bad for ICE or our current enforcement of immigration, the man in charge turns out to be a real human with a real heart.  Wait until you hear the story Tom Homan told at a conference about the victims of our open borders.    According to a report by the Topeka Cap Journal, democrats approved all kinds of voter packets to be sent to Kansans that never requested them.  This is a huge scam.    We have the information you need to disable that start/stop button on your car.  Ron DeSantis hammers NYC over the Mayor's new budget as it's bigger than the entire state of Florida budget.    In sports, no Jerome Tang spells success for KSU as they get a win.  The Royals take batting practice with the new ball/strike computer system on at Surprise Stadium.  It happened on a day the leader of the player's union resigned in a sex scandal.    And a self proclaimed "woke bit__" skating for team USA had a little too much Trump hate in her heart and flamed out on the ice and then embarrassed us all as a total baby balling her eyes out.  Ughh.    Tiger Woods is in the news and our Final Final is a beautiful message about Jesse Jackson.

PREVIEW FOR LATER TODAY Guest: Henry Sokolski. Sokolski explains a three-stage strategy to disable enemies via information warfare and alliance disruption, noting U.S. military containment strategies remain outdated.1930

She Made Fun Of A Disable SWAT Husband While Meeting Boss at Hotel And The Feds Found HerBecome a supporter of this podcast: https://www.spreaker.com/podcast/true-cheating-wives-and-girlfriends-stories-2026-true-cheating-stories-podcast--5689182/support.

She Made Fun Of A Disable SWAT Husband While Meeting Boss at Hotel And The Feds Found HerBecome a supporter of this podcast: https://www.spreaker.com/podcast/true-cheating-wives-and-girlfriends-stories-2026-true-cheating-stories-podcast--5689182/support.

PREVIEW Guest: Henry Sokolski. Sokolski describes a new warfare tactic piloted by Russia that utilizes non-nuclear strategic weapons to disable critical infrastructure nodes, such as electricity and communications. While China is actively building these intercontinental systems to force surrender without nuclear fallout, the U.S. currently lacks a coherent response to this specific threat.

Hackers Weaponize Windows Hyper-V to Hide Linux VM and Evade EDR Detection

Division. It's the one word that captures the pain and problems America is facing right now. Tragedy should unite us, but in recent history, moments of violence have only fueled greater division — even among believers.In this message, Pastor Sam Grosso approaches this cultural moment not as a reporter or politician, but through a biblical lens.What does true peace and unity look like in the body of Christ, and is peace even possible in a time like this?

As part of the 2025 Developmental Disabilities Conference, Dr. Elysa Marco talks about various biological approaches to therapy. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40623]

As part of the 2025 Developmental Disabilities Conference, Dr. Elysa Marco talks about various biological approaches to therapy. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40623]

As part of the 2025 Developmental Disabilities Conference, Dr. Elysa Marco talks about various biological approaches to therapy. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40623]

Axon, a company that makes policing equipment, developed new software called Draft One that takes recordings from police cameras and uses artificial intelligence to summarize them into incident reports. Many police departments trying out the tool are not disclosing that they're using AI to write reports, according to a Mother Jones investigation. That potentially leaves both prosecutors and defense attorneys in the blind — despite safeguards Axon built into its software to prevent this very scenario, and to remove errors or AI hallucinations. Marketplace's Nova Safo spoke with investigative journalist Tekendra Parmar who reported the story for Mother Jones.

Axon, a company that makes policing equipment, developed new software called Draft One that takes recordings from police cameras and uses artificial intelligence to summarize them into incident reports. Many police departments trying out the tool are not disclosing that they're using AI to write reports, according to a Mother Jones investigation. That potentially leaves both prosecutors and defense attorneys in the blind — despite safeguards Axon built into its software to prevent this very scenario, and to remove errors or AI hallucinations. Marketplace's Nova Safo spoke with investigative journalist Tekendra Parmar who reported the story for Mother Jones.

As part of the 2025 Developmental Disabilities Conference, Emily Hill talks about how sibling support can be a catalyst for family empowerment. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40622]

As part of the 2025 Developmental Disabilities Conference, Emily Hill talks about how sibling support can be a catalyst for family empowerment. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40622]

As part of the 2025 Developmental Disabilities Conference, Emily Hill talks about how sibling support can be a catalyst for family empowerment. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40622]

As part of the 2025 Developmental Disabilities Conference, Judy Mark, Vivian Do, Miguel Lugo, all from Disability Voices United, talk about supported decision-making in healthcare. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40611]

As part of the 2025 Developmental Disabilities Conference, Judy Mark, Vivian Do, Miguel Lugo, all from Disability Voices United, talk about supported decision-making in healthcare. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40611]

As part of the 2025 Developmental Disabilities Conference, Judy Mark, Vivian Do, Miguel Lugo, all from Disability Voices United, talk about supported decision-making in healthcare. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40611]

As part of the 2025 Developmental Disabilities Conference, Dr. Raul Gutierrez, Associate Professor of Pediatrics at San Francisco General Hospital, talks about supporting immigrant children. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40619]

As part of the 2025 Developmental Disabilities Conference, Dr. Raul Gutierrez, Associate Professor of Pediatrics at San Francisco General Hospital, talks about supporting immigrant children. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40619]

As part of the 2025 Developmental Disabilities Conference, Allen Friedland, Terri Hancharick and Jack Jadach talk about a collaborative approach to enhancing health in fitness centers. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40613]

As part of the 2025 Developmental Disabilities Conference, Allen Friedland, Terri Hancharick and Jack Jadach talk about a collaborative approach to enhancing health in fitness centers. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40613]

Friday, August 8. The seven stories you need to know today.Read today's briefing.If you're not a subscriber, click here to start.

As part of the 2025 Developmental Disabilities Conference, Dr. Mary Dubon of Harvard Medical School talk about adaptive and para sports for youth with physical and developmental disabilities. Series: "Developmental Disabilities Update" [Health and Medicine] [Show ID: 40617]

In this episode of Building Better Developers with AI, Rob Broadhead and Michael Meloche revisit a popular question: What Happens When Software Fails? Originally titled When Coffee Hits the Fan: Developer Disaster Recovery, this AI-enhanced breakdown explores real-world developer mistakes, recovery strategies, and the tools that help turn chaos into control. Whether you're managing your first deployment or juggling enterprise infrastructure, you'll leave this episode better equipped for the moment when software fails. When Software Fails and Everything Goes Down The podcast kicks off with a dramatic (but realistic) scenario: CI passes, coffee is in hand, and then production crashes. While that might sound extreme, it's a situation many developers recognize. Rob and Michael cover some familiar culprits: Dropping a production database Misconfigured cloud infrastructure costing hundreds overnight Accidentally publishing secret keys Over-provisioned “default” environments meant for enterprise use Takeaway: Software will fail. Being prepared is the difference between a disaster and a quick fix. Why Software Fails: Avoiding Costly Dev Mistakes Michael shares an all-too-common situation: connecting to the wrong environment and running production-breaking SQL. The issue wasn't the code—it was the context. Here are some best practices to avoid accidental failure: Color-code terminal environments (green for dev, red for prod) Disable auto-commit in production databases Always preview changes with a SELECT before running DELETE or UPDATE Back up databases or individual tables before making changes These simple habits can save hours—or days—of cleanup. How to Recover When Software Fails Rob and Michael outline a reliable recovery framework that works in any team or tech stack: Monitoring and alerts: Tools like Datadog, Prometheus, and Sentry help detect issues early Rollback plans: Scripts, snapshots, and container rebuilds should be ready to go Runbooks: Documented recovery steps prevent chaos during outages Postmortems: Blameless reviews help teams learn and improve Clear communication: Everyone on the team should know who's doing what during a crisis Pro Tip: Practice disaster scenarios ahead of time. Simulations help ensure you're truly ready. Essential Tools for Recovery Tools can make or break your ability to respond quickly when software fails. Rob and Michael recommend: Docker & Docker Compose for replicable environments Terraform & Ansible for consistent infrastructure GitHub Actions, GitLab CI, Jenkins for automated testing and deployment Chaos Engineering tools like Gremlin and Chaos Monkey Snapshot and backup automation to enable fast data restoration Michael emphasizes: containers are the fastest way to spin up clean environments, test recovery steps, and isolate issues safely. Mindset Matters: Staying Calm When Software Fails Technical preparation is critical—but so is mindset. Rob notes that no one makes smart decisions in panic mode. Having a calm, repeatable process in place reduces pressure when systems go down. Cultural and team-based practices: Use blameless postmortems to normalize failure Avoid root access in production whenever possible Share mistakes in standups so others can learn Make local environments mirror production using containers Reminder: Recovery is a skill—one you should build just like any feature. Think you're ready for a failure scenario? Prove it. This week, simulate a software failure in your development environment: Turn off a service your app depends on Delete (then restore) a local database from backup Use Docker to rebuild your environment from scratch Trigger a mock alert in your monitoring tool Then answer these questions: How fast can you recover? What broke that you didn't expect? What would you do differently in production? Recovery isn't just theory—it's a skill you build through practice. Start now, while the stakes are low. Final Thought Software fails. That's a reality of modern development. But with the right tools, smart workflows, and a calm, prepared team, you can recover quickly—and even improve your system in the process. Learn from failure. Build with resilience. And next time something breaks, you'll know exactly what to do. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources System Backups – Prepare for the Worst Using Dropbox To Provide A File Store and Reliable Backup Testing Your Backups – Disaster Recovery Requires Verification Virtual Systems On A Budget – Realistic Cloud Pricing Building Better Developers With AI Podcast Videos – With Bonus Content

In Season 25, Episode 10 of the "Building Better Developers with AI" podcast, Rob Broadhead and Michael Meloche revisit one of their most practical episodes: decluttering your code and digital life. However, this time, they utilize AI tools like ChatGPT to elevate the conversation and provide even more actionable ways to streamline your workflow, sharpen focus, and enhance developer productivity. Why Developers Should Declutter—and Level Up Developer clutter goes far beyond messy code. It creeps into your tabs, your file system, your brain, and your workflow. Rob and Michael explore how revisiting the original topic through the lens of AI created deeper, more structured insights. AI not only confirmed their past advice—it elevated it. As Rob puts it: “Clutter doesn't show up in your IDE, but it absolutely shows up in your performance.” AI helped them reframe the conversation into clear action steps that help you level up your development workflow by decluttering at every level—from code to cognition. Clean Code Is Smart Code: Use AI to Level Up Your Refactoring A central theme of the episode is simple: Great developers delete code. Michael and Rob walk through common bad habits—commented-out code, legacy logic, stale TODOs—and how they quietly accumulate technical debt. They recommend using tools like ESLint, Prettier, or Flake8 to automatically flag issues. More importantly, they encourage developers to make cleanup a weekly routine, not a once-a-year emergency. AI Tip: Utilize ChatGPT to refactor lengthy methods, rename ambiguous variables, or break down complex classes into more manageable components. It's a quick way to make your code easier to read, test, and maintain. Optimize Your Tools: Streamline and Standardize Your Workspace If you want to level up your development workflow truly, decluttering extends beyond the codebase. Your workspace setup—browser tabs, IDE extensions, terminal scripts—can either streamline your productivity or sabotage it. Rob's key practices: Limit browser tabs to 10 or fewer Disable unused plugins and extensions Stick to a consistent folder structure Use shell scripts, makefiles, or Git aliases to speed up routine tasks Michael reinforces the idea with his “kitchen sink” app concept—a reusable codebase that acts as both a portfolio and a best-practices toolkit. Silence the Noise: Declutter Your Developer Brain Clutter isn't just digital—it's cognitive. Rob and Michael emphasize how context-switching kills focus and creativity. To combat this, they recommend: Turning off nonessential notifications (on phone, desktop, and wearables) Using time boxing (e.g., Pomodoro technique) Auditing your calendar weekly Creating interruption-free zones for deep work Pro Tip: Play white noise or ambient focus tracks to drown out distractions and stay locked in. These habits allow you to protect your most important asset as a developer—your attention. Make Decluttering a Weekly Habit and Watch Your Workflow Level Up Don't wait for a meltdown to clean house. Rob and Michael suggest building decluttering directly into your dev rhythm—especially at the end of each sprint or workweek. Their weekly checklist: Archive stale Git branches Delete unused files and TODOs Refactor one file for clarity Restart your system Review your inbox and calendar Even a 15-minute Friday cleanup session can give you a cleaner slate and a sharper mind going into Monday. Bonus: Fewer Tools, More Flow Tool overload is another form of workflow clutter. Michael recommends consolidating everything into one platform—whether it's GitHub, Jira, or Notion. “Let the business be disorganized,” he says. “You bring the order.” Rob echoes this with a challenge: Take one week to migrate everything from your old tools into your primary stack. You'll save time and reduce friction moving forward. Final Thoughts: Use AI to Clean, Simplify, and Level Up Decluttering isn't just about tidiness—it's about creating space to do your best work. And with AI now in your toolkit, you can automate, refactor, and optimize like never before. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Balance Your Time in a Busy World: Tools and Techniques Boost Your Developer Efficiency: Automation Tips for Developers Code Refactoring: Maintaining Clean, Efficient Code Cleaning Your Task List Building Better Developers With AI Podcast Videos – With Bonus Content

The NYPD is asking the White House for authorization to intercept and disable potentially hostile drones flying over New York City. Meanwhile, a city commission is recommending that borough presidents get new authority over land use decisions, allowing them a decisive vote if the City Council rejects rezoning or development plans. And New York's baseball stars shine: Mets shortstop Francisco Lindor and Yankees slugger Aaron Judge have been named starters for this year's MLB All-Star Game.

Galatians 5:13-15 Thanks to everyone who supports TMBH at patreon.com/thetmbhpodcast You're the reason we can all do this together! Discuss the episode here Music by Jeff Foote

Nina Polshakova is a software engineer at Solo.io, where she's worked on Istio and API Gateway projects. She's been part of the Kubernetes release team since v1.27 and is currently serving as the Release Lead for v1.33.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod - bluesky: @kubernetespodcast.com   News of the week 229 new things Google announced at Next 25 MCO: Multi-Cluster Orchestrator Golden Kubestronaut Cloud Native Platform Engineering Associate The kube-scheduler-simulator K0s and k0smotron are now CNCF Sandbox projects   Links from the interview Nina Polshakova Kubernetes Deprecation Policy Kubernetes Dev Google Group solo.io Istio API Gateway (General concept, linking to K8s Gateway API) Kubernetes Release Team GitHub Istio revisions Working in Public by Nadia Eghbal (Link to publisher's site about the book) Kubernetes Maintainers Read Mean Comments (KubeCon EU 2024) Kubernetes 1.33 release blog (Link to release announcement blog) Kubernetes Enhancement Proposals (KEPs) Sidecar Containers Multiple Service CIDR support (KEP link) Dynamic Resource Allocation (DRA) DRA support for partitioned devices (KEP link) DRA device taints and tolerations (KEP link) DRA: Prioritized Alternatives in Device Requests (KEP link) Kubernetes 1.33 sneak peak (Link to pre-release highlights) EndpointSlices API Kubernetes Gateway API node.status.nodeInfo.kubeProxyVersion is a lie (issue) KEP-4004: Deprecate the kubeProxyVersion field of v1.Node #4005 (KEP link) Kubelet Removal: Host network support for Windows pods (KEP link) Containerd SIG Windows HostProcess Containers (Windows) Removal: KEP-5040: Disable git_repo volume driver (KEP link) User Namespaces (Beta, Enabled by Default) CRI-O Runc In-place Resource Resize for Pods (Link to the alpha announcement, but now beta) Vertical Pod Autoscaler (VPA) KEP-5080: Ordered Namespace Deletion PyTorch Linkerd Terry Pratchett's Discworld series Tiffany Aching series Guards! Guards! Going Postal Kubernetes Slack New Contributor Orientation  

06 Ram AFM Misfire how to fix using oil system cleaner? 11 Suburban Hard Cold Start fix. 02 K3500 Brake light fix. 20 Ram AFM DOD Disable? 71 GMC Sprint El Camino Stored over a decade getting it running. 12 Nissan Altima bad fuel mileage fix. 97 F250 Trans front seal leaking fix 2010 Kia Soul Belt squeal? 97 Tahoe cold start clatter fix? 06 Mustang hard to press shifter button 18 Kia Forte leaks water on floorboard how to leak test? 06 Ram and old tractors when to change oil when used very little? 08 Cobalt low power uphill When to change oil on new Duramax 3.0 diesel? Subaru random mis due to carbon on valves. 2013 GMC Sierra disabling AFM the right way or not?