Worth Knowing

US Govt stake in AI? #ai #ainews

OpenAI’s proposals to US govt. let’s see where that goes.

How AI would release would be changed? Should that be a case? #ai #news

US government is changing the rules of AI release. Would that make playing field more uneven?

Anthropic accuses Alibaba. #ai # news #shorts

AI war heating up and its getting quite political.

#openai new model GPT 5.6 Sol #ai #ainews

Ai software now as restricted technology, deepen the gap of haves and haves not.

OpenAI’s #newest and #hottest AI chip, Jelopeno. #openai #ai #aishorts

Silicon Valley has new AI Problem #ai #openai #anthropic #meta #gemini

Google lost $225 Billion in market value. Know who is responsible. #ai #ainews #stockmarket

How to use code review graph: Episode 4: Use Blast Radius

I extracted the key points from your slideshow: hook, demo change, prompt, interpretation, validation checklist, and next episode teaser. Most developers review the diff. But the dangerous part of a code change is often everything the diff silently affects. In Episode 4 of the Code Review Graph Series, we look at blast radius analysis before merging code. The demo uses a tiny change in OpenCue: Changing the default wordsPerMinute value from 150 to 180. That looks like a simple one line diff, but it can affect playback speed, prompter UI, saved scripts, settings, storage, user experience, and tests. In this episode, you will learn how to use Code Review Graph to find: • Direct impact • Indirect impact • Affected files and functions • Callers and callees • User facing flows • Related tests • Missing test coverage • High risk areas before merge Prompt used in the video: Use code-review-graph to find the blast radius of this change. I changed the default wordsPerMinute value in PromptSettings from 150 to 180. I want to know what files, functions, flows, tests, and modules may be affected beyond the changed file. Highlight anything with high risk, especially playback behavior, saved script behavior, shared settings, user facing flows, hub nodes, and bridge nodes. This prompt forces AI to move beyond the changed files and ask: What can this change break? The diff tells you what changed. The graph tells you what is affected. After finding the blast radius, ask AI for a minimum automated test plan and manual validation plan before merge. Validation checklist from this episode: • Create a new script and confirm default WPM is 180 • Check playback scroll speed • Load old saved scripts and confirm values are preserved • Verify settings UI behavior • Run related tests • Add missing tests if needed #CodeReview #AI #SoftwareEngineering #DeveloperTools #Programming #GitHub #PullRequest #CodeQuality #SeniorEngineer #TechLead #CodeReviewGraph

Where #AI going after Fable 5 and Mythos 5 ban. #ainews

How to use Code Review Graph EP3: Stop Asking AI for Shallow Code Reviews

Most AI code reviews are too shallow. They look at the diff, give generic advice, and often miss the real risk hiding in the codebase. In this episode of the Code Review Graph series, I show a practical workflow for getting your first useful AI code review using a real Swift and SwiftUI macOS app: OpenCue. Instead of asking AI to simply “review this diff,” we use Code Review Graph to update the repo graph, detect changes, inspect impact, and ask AI for a senior-level review focused on risk, tests, affected flows, and merge safety. In this episode, you’ll learn how to: * Update your Code Review Graph after local changes * Detect changed files and review impact * Ask AI for a context-aware code review * Find missing tests and risky dependencies * Turn AI output into useful PR review comments * Review code more like a senior engineer, not a linter This workflow is especially useful when working with AI coding tools like Claude Code, Cursor, GitHub Copilot, Windsurf, Codex, or any assistant connected to your repo context. The goal is simple: stop asking AI for shallow code reviews. Give it the map, the changed files, the affected flows, and the risk context so it can produce feedback that actually helps before merge. Watch the full Code Review Graph series to learn how to make AI understand your codebase instead of guessing. #CodeReviewGraph #aicodereview #aifordevelopers #SwiftUI #Swift #macOSDevelopment #DeveloperTools #CursorAI #ClaudeCode #githubcopilot #softwareengineering #CodeReview #WorthKnowingTV #copilot #copilotcli

How to use GitHub Copilot CLI Natively Inside Xcode 27

In this episode, I’ll show you how to use GitHub Copilot CLI natively inside Xcode 27 by setting it up as an ACP Agent in Xcode’s new Intelligence Agents workflow. This is a quick practical setup for iOS developers, Swift developers, and anyone experimenting with agentic coding inside Xcode. We’ll install or update the GitHub Copilot CLI, verify the Copilot executable path, add it as an ACP agent in Xcode 27, pass the --acp argument, and confirm that Copilot is responding directly from Xcode. This opens up a new dimension for Xcode agentic coding, where GitHub Copilot CLI can work inside the IDE instead of only from the terminal. I’ll also show the quick verification steps and a few troubleshooting tips if Xcode does not connect correctly. Important note: this requires Xcode 27 or newer, and based on my first impression, this feature can use a lot of tokens, so use it responsibly. If you are building iOS apps with Swift, SwiftUI, Xcode, GitHub Copilot, or AI coding agents, this setup is worth knowing. #Xcode27 #GitHubCopilot #CopilotCLI #SwiftUI #iOSDevelopment #SwiftDeveloper #Xcode #AICoding #AgenticCoding #GitHub #DeveloperTools #AIForCoding

CRG Series Episode 2: Smarter AI Setup

Before AI can review your code properly, it needs a map. In this episode, I show you how to install Code Review Graph, connect it to your AI coding tool, build a graph for your repository, and check that everything is working. Code Review Graph helps your AI coding assistant understand your codebase before it starts guessing from a small diff or random files. Instead of asking AI to review code with limited context, you can give it a structured map of your repo so it can reason better about files, functions, dependencies, and impact areas. In this video, we cover: • Installing Code Review Graph • Checking the CLI setup • Running the MCP install command • Connecting Code Review Graph to AI coding tools • Building the local repo graph • Checking graph status • Restarting your AI coding tool • Running the first repo understanding prompt Commands used in this episode: pipx install code-review-graph code-review-graph --help code-review-graph install code-review-graph build code-review-graph status First prompt after setup: Before helping me with this repository, use code-review-graph to understand the repo structure. Start with the minimal context tool, then tell me what kind of project this is, which areas look important, and which tool you would use next if I ask for a review, debugging help, or architecture analysis. This is Episode 2 in the Code Review Graph series. In the next episode, we will use this setup for a real pull request style AI code review and see how much better AI performs when it has repo context. Comment below which AI coding tool you want me to test next: Cursor, Claude Code, GitHub Copilot, Codex, Windsurf, or something else? Subscribe to Worth Knowing for practical AI coding workflows, developer tools, productivity systems, and real world software engineering tips. #CodeReviewGraph #AICoding #AICodeReview #CursorAI #ClaudeCode #GitHubCopilot #Codex #Windsurf #MCP #AIWorkflow #DeveloperTools #SoftwareEngineering #CodingTools #AIForCoding #WorthKnowing

Elgato Wave:3 Mic Unboxing and First Impression

#ElgatoWave3 #YouTubeSetup #CreatorGear I finally unboxed the Elgato Wave:3 microphone for my YouTube creator setup, and in this video I share my first impression, what comes inside the box, the build quality, the desk setup feel, and whether it looks like a good microphone for creators, streamers, podcasters, and anyone making videos from home. This is not a long term review yet. This is my honest first look after opening the Elgato Wave:3 and checking how it fits into a real creator workflow. I talk about the design, packaging, microphone quality, setup experience, and why I picked this mic for improving my YouTube audio. If you are thinking about buying the Elgato Wave:3 for YouTube videos, streaming, podcasting, Zoom calls, voiceovers, or content creation, this video should help you get a quick practical look before you decide. In future videos, I will test the audio quality, compare it with other microphones, and see whether it actually improves my creator setup. 👍 Like the video if it helped 🔔 Subscribe for more tech, creator tools, productivity gear, and practical AI content 💬 Comment below: What microphone are you using right now? #ElgatoWave3 #ElgatoWave #MicrophoneUnboxing #MicUnboxing #YouTubeSetup #CreatorSetup #ContentCreator #YouTubeCreators #StreamingSetup #PodcastMicrophone #BestMicForYouTube #TechUnboxing #FirstImpression #CreatorGear #WorthKnowingTV

How to Use Code Review Graph Ep 1: AI Code Reviews Are Missing the Bigger Picture: Intro to the CRG

Most AI code reviews are shallow because AI usually reviews the diff without understanding the full codebase. In this kickoff episode, I introduce Code Review Graph, a tool that gives AI coding assistants a local structural map of your repository before they review your code. Instead of only looking at changed lines, AI can understand relationships between files, functions, tests, flows, dependencies, and architecture risk. This is important if you use tools like Cursor, Claude Code, GitHub Copilot, Codex, Windsurf, Zed, Gemini CLI, or any AI coding workflow. Better AI coding is not just about better prompts. It is about better context. In this series, we will go step by step through Code Review Graph, including setup, MCP integration, first review, blast radius analysis, missing tests, architecture risk, and a practical daily AI code review workflow. In this video: 00:00 Problem Statement 00:45 Intro 01:20 What are the values? 01:59 How Code Review Graph helps AI understand your codebase 02:38 What It solves? 3:35 Tool and its help to AI 4:23 Setup instructions 5:15 What will be covered in the list If you use AI for software development, this is one tool worth knowing. Code Review Graph: https://code-review-graph.com/ Subscribe to Worth Knowing for practical videos on AI, software engineering, coding tools, productivity, and better workflows. #AI #AICoding #CodeReview #SoftwareEngineering #CursorAI #GitHubCopilot #ClaudeCode #Codex #Windsurf #DeveloperTools #Programming #MCP #AIWorkflow #CodingTools #WorthKnowing

The MX Creative Console Is Not What I Expected

I bought the Logitech MX Creative Console because I was looking for a better productivity tool for my creator and coding workflow. After unboxing it, testing it, and trying to make it fit into my daily setup, I realized something important: this product is not for everyone. In this video, I share my honest experience with the MX Creative Console, why I decided to return it, and what creators should know before buying it. The product itself is not bad, but it feels heavily focused on Adobe workflows. If you use apps like Premiere Pro, Photoshop, Lightroom, or Illustrator every day, this may still be useful for you. But if your workflow includes video editing, coding, content planning, research, browser work, and multiple non Adobe tools, the limitations become much more obvious. I also talk about the display keys, limited icon customization, the dial controls, the included Adobe Creative Cloud value, and why I think a proper macro pad may be a better fit for my workflow. This is not a hate review. It is a real world creator plus coder review after actually using the MX Creative Console. In this video Logitech MX Creative Console review Why I returned the MX Creative Console Is the MX Creative Console worth it MX Creative Console for creators MX Creative Console for coding workflow Adobe focused productivity tools Best productivity tools for creators Macro pad vs MX Creative Console My honest verdict The MX Creative Console may be useful for heavy Adobe users, but for my workflow, it is too narrow. I need something more flexible, more customizable, and more useful across all the apps I use every day. Watch next Check out my MX Creative Console unboxing video to see my first impression before I actually tested it in my workflow. #LogitechMXCreativeConsole #MXCreativeConsole #Logitech #ProductivityTools #CreatorWorkflow #TechReview #YouTubeCreatorTools #MacroPad #AdobeCreativeCloud #CodingWorkflow