Video · Cole Medin ·

The 4 Components of Every Successful AI Second Brain (Build These Now)

Cole Medin argues that an AI second brain should be dead simple—built from a handful of tools and a folder of markdown files—and claims it saves him 25 to 30 hours every week. He breaks the system into four components: Context, Connections, Capabilities, and Cadence. He argues that the underlying model doesn't matter, and points to a free Second Brain Starter template and Nate Herk's AIS-OS (the Four Cs) as references. He encourages viewers to either build a new second brain or audit an existing one.

Watch on YouTube The opening of the original, or for stories before 30 October 2026 an AI model's summary of it. Check the original before you rely on a detail.

More from Cole Medin

All stories

VideoCole Medin

AI Makes Us WAY Faster but Fries Our Focus (Here's What I Do About It)

In this video, developer Cole Medin reflects on how AI coding has made him faster than ever, but at a cost to his focus. He says he can no longer sit down and code for four hours straight with music on; instead he runs several agent sessions at once, dictates prompts all day, and switches between tasks every few minutes, which he finds tiring. He explains that the real problem is context switching, which keeps him from getting into flow, and that every improvement to his system makes the problem worse. He concludes that he is now investing in more autonomy rather than more sessions, and believes we are living in an 'in-between' period that will end.

VideoCole Medin

My AI Dark Factory Dream Is Dead (Here's What Actually Works)

Cole Medin explains why the 'AI dark factory' - the most autonomous form of agentic engineering, where agents are handed a high-level document for an epic or release and figure out how to build, validate, and ship software straight to production - does not work, even in a hypothetical AGI world. He argues that as LLMs improve they get much better at building software but not much better at understanding human intent, so the bottleneck is always communicating what you actually want; 'LLMs can't read our minds.' He also cites maintainability concerns, noting that coding agents sprawl and cannot maintain a codebase the way humans do, referencing Dex Horthy's talk 'Why Software Factories Fail.' His inspiration was Dan Shapiro's blog post on the five levels of autonomy for AI coding, with the dark factory being level five. He has therefore shifted to an 'AI software factory' that keeps humans in the loop: he plans each release up front, runs agents in parallel through the issues, and tests everything in staging before it ships.

VideoCole Medin

Is Learning to Build Software Still Worth It with AI? (My Honest Take)

Cole Medin argues that software-building skills remain valuable as AI agents take on complex tasks, because language models cannot read your mind and you must still communicate your intent and build a harness around the agent, including planning up front and validating the output at the end. He explains that the viral 'Reverse Engineer Anything' (REA) GitHub repo works so well specifically because the finished application already contains the intent, letting the agent validate its own output reliably, which is why it is not a fair example of agents being able to build anything. He warns against the 'meat proxy' trap of dumping a ticket into a coding agent and passing back whatever it returns without your own critical thinking, and offers a test for evaluating whether a skill is worth investing in: if the next model is twice as good, does the skill matter more or less.

VideoCole Medin

The BEST Jev Use Cases for AI Coding (Absolute Game Changers)

The speaker presents four practical use cases for Jev, a browser agent, in AI coding workflows: guarding a coding agent with a security hook, playtesting a game to catch bugs that unit tests miss, driving browser testing on a real app, and classifying GitHub issues and pull requests so that Archon workflows select the right steps and the right model. The speaker emphasizes that Jev never works alone—the LLM sets Jev up and acts on what it finds, while Jev makes fast and cheap decisions in between, which helps with token efficiency and rate limits. The speaker promotes a Dynamous workshop on Friday, October 2nd and links to the jev-ultrafast browser agent and the jev-use repository, which shows more examples of Jev working with an LLM.