Hiring only senior engineers is killing companies (News)

What up, nerds? Shabikes. I'm Jared, and this is changelog news for the week of Monday, 09/29/2025. It's official. Robots are invading Major League Baseball. Starting with the 2026 season, MLB will implement a challenge system for balls and strikes to, quote, usher in the era of robot umpiring. Human umpires aren't going anywhere anytime soon, but the rioting is on the wall. This makes me sad. Sure. Robots will make a higher percentage of correct calls, but they'll also be able to throw harder, hit further, and run faster someday. And that doesn't mean I want to watch them compete. Oh, well. Let's get into this week's news. Hiring only senior engineers is killing companies. In the last three months, Andrew Churchill interviewed 134 engineers. His main takeaway, there is a huge pool of exceptional junior engineers that most companies won't even consider. In this post, Andrew outlines why he loves working with juniors, fresh energy, unshackled by prior experience, loyalty, and more. How to hire the right juniors, fill up her mindset, home assignments, test with and without AI, etcetera, and how to make it work after the hire. Invest in mentoring, be patient, measure right, etcetera. His call to action, quote, investing your time in passionate junior developers will pay off in the long run. The question is whether you'll start now or wait until everyone else figures it out. Introducing Chrome Dev Tools MCP. Now in public preview, Chrome's Dev Tools now connects AI agents like Cursor, Cloud Code, and Gemini CLI to its automation and debugging capabilities. The end result, quote, your AI helper can not only write code, but actually run it in a real browser, inspect what's happening, and even fix issues based on real feedback from the page, end quote. Chrome Dev Tools MCP acts as a bridge between an AI model and a real Chrome browser instance, which means that your model can now open pages, click buttons, read the DOM slash CSS, capture performance metrics, read console logs, and much more, all autonomously as if a human developer were using Chrome DevTools. GitHub's plan for a more secure NPM supply chain. NPM has been getting hammered by attackers recently, so much so that I've struggled to track and contextualize all the events. So so we're having our friend, Farasabuka DJ, from socket security on the show Friday to help make sense of it all. GitHub, as the owners and hosts of NPM, are at the center of the platform, hears what they're doing about it. Quote, to address token abuse and self replicating malware, we will be changing authentication and publishing options in the near future to only include one, local publishing with required two factor auth, two, granular tokens, which will have a limited lifetime of seven days, and three, trusted publishing. Links to the details of all three of those things are in the show notes. In addition to these changes, GitHub provides a list of actions NPM …