Andreessen Horowitz has a message for up-and-coming tech talent: Don’t drop out of school to start a company; come do school with us instead. The venture-capital firm is investing $35 million in an unaccredited two-year alternative to traditional college.

Andy Burnham will tell the Labour Party faithful next week that he’s the leader who’ll deliver the hope and change they want. The underlying message is more nuanced: stick with me because things might get worse before they get better.

and @assafbar @nuri_chang @barrey_ben @JustinoMolinaro @perryraskin @theleafnode @ajaysurie @KeithKakadia @thekhoatran @vedantshah2001 @ItsAlexStarr @EmanFT_ @kouroshbaloo @LandonH @Vasu_ai123 @GiovanniZanette @ChristianSextl @tobias_pfuetze @gambrill @ogrikuu @evannewman0 @kiowasean @hamarshehmhmd @Dweldonb @ScottShapiroUXD @kidneycryptodoc @shtse8 @JohnKlacynski @AgentRevenueLab @benridler @iamnotkookie @nit33sh @argupta @vladciurca @thatdrewgilliam @aarifkhan4u @archvalmiki @iserflott @abe238 @SpenxerM @larsjaner @stan522 @SimplyColeB @SurfingPigment @NavSha @tylerwillis @trevin @shuv1337 @ivankqw @trung_rta

Andrej Karpathy just gave one of the clearest explanations I’ve heard for how people should be thinking about their Hermes agents. Not one agent. All of them. “Remove yourself as the bottleneck.” That line is much bigger than better prompting. Karpathy is talking about arranging your agents so they can operate with less human intervention, keep work moving longer, and accomplish far more from the relatively small amount of direction you give them. That should be the direction you’re pushing every Hermes agent you build. Your research agent shouldn’t need you to tell it what to search next every five minutes. Your monitoring agent shouldn’t depend on you remembering to check something. Your content agent shouldn’t stop after step one when the rest of the workflow is already known. Your development agent shouldn’t need you sitting there approving every tiny action. That doesn’t mean blindly making everything autonomous. It means deliberately looking at every place where you are still unnecessarily sitting in the loop. Give the agent a clear objective. Give it the tools it needs. Give it the right Skills, memory, files and project context. Define the boundaries. Define what success looks like. Give it a reason to start working, whether that’s a schedule, an event, a recurring task or another agent handing work off to it. Most importantly, define what it can handle itself and what actually requires you. That’s the shift. You’re no longer just building something you can chat with. You’re building an operating workflow that can continue doing useful work after you walk away. Karpathy later puts the goal even more directly: get “more agents running for longer periods of time without your involvement.” That might be one of the best north stars you can use for a serious Hermes setup. Because the number of agents you have means almost nothing by itself. You can have 20 Hermes agents and still personally drive every single action. Or you can have five well-designed agents researching, monitoring, organizing, building and reporting while your attention is somewhere else. So instead of asking: How many Hermes agents can I build? Start asking this about every agent you already have: What am I still doing that this agent could be doing without me? That’s where the leverage starts.