Scrimba Guide Blog, Reviews, Tips, and Career Advice for Developers

Agentic coding means you hand an AI agent a goal, not a list of steps. You say "make the failing user test pass" and the agent works out how: it reads the code, edits files, runs the commands, reads the errors, and tries again until the goal is met or it hits a limit. The word agentic marks the two things a plain chat window lacks, tools and its own decisions. A human still reviews the result. That last part is the part that matters for anyone learning to code, and October 2026 shipped real evidence for it.

Install the newest 3.14.x today: as of 2026-10-09 that is Python 3.14.8, released 2026-09-30. Python 3.15.0 final is scheduled to land today, 2026-10-09, after a one-week slip, and either one is fine for learning. Check what you already have with python --version, and ignore any tutorial panic about 3.15 breaking beginner code.

Hacktoberfest 2026 no longer counts pull requests; organizers announced this on 2026-08-19. You can still make your first pull request in October: find a repo with a good-first-issue label, read its contributing guide, fork it, branch, commit, push, open the PR against the original repo, and answer review yourself.

MCP is a JSON-RPC 2.0 standard that lets an AI app (the host) call your code through a server exposing tools, resources and prompts, a typed API the model discovers at runtime. The 2026-07-28 revision made it stateless: no initialize handshake, no sessions. If you know APIs, the model and a STDIO server still hold; new code uses SDK v2.

React 19.3.0 shipped 2026-09-09 and npm has tagged it latest since. It is a minor release that adds features and removes nothing, so a React 19 course still teaches current React. Install whatever npm create vite@latest gives you, which resolves to 19.3.0, and keep react and react-dom on the exact same version.

A good Scrimba Explain prompt names the topic, the audience, and the slides you want. I ran the same RAG prompt through three teaching styles, attached a Markdown file, and built a three-lesson playlist, seven explainers in total. Professor was not noticeably deeper than Standard, which suggests the prompt text, not the picker, sets the depth.

If you do not know what Explain is yet, the reference page covers entry points and quotas, and the full review covers whether the output is any good. This post is only about the web composer at scrimba.com/explain↗ (opens in a new tab): what to type, which style to pick, and which clicks cost you an explainer.

Scrimba Explain exposes two MCP endpoints: one for your own agent session, one for pull requests. Claude Code connects to either with one command or one JSON file, reads your repository or diff, and streams a narrated video lesson into Scrimba. Drafts cost nothing until someone opens and claims the link. I ran both endpoints against a public Anthropic repo and a merged pull request, and this post is what came back, including the parts that went wrong.

Every Scrimba lesson has an EXPLAIN button in its header. Pause, type a question, and Scrimba builds a short narrated video from that lesson: its files, your highlighted code, and the teacher's narration to that point. It costs one explainer from your allowance, 10 for life on Free or 100 a month on Pro, and stays attached to the lesson.

Tested with a Pro account on the "Chunking text from documents" lesson in Learn RAG, Guil Hernandez's 94-minute course on retrieval-augmented generation, September 2026.

I pressed the button once, with a deliberately picky prompt, to see what it sends and what it builds. Here is what got sent, what came back, and the three moments in a course where it earns its cost.

Scrimba Explain turns a typed question into a narrated video with code, diagram and quiz slides in about ten seconds. NotebookLM Video Overviews turn documents already sitting in a notebook into a narrated slideshow that can take over 30 minutes. Pick Explain for a coding concept or a piece of code, NotebookLM for a video summary of your own PDFs or notes.

I generated every Explain result in this comparison myself, on a Pro account: the explainers, the transcripts, the quizzes. NotebookLM sat behind a corporate sign-in on the machine I had, so its side of the table comes from Google's own help pages and blog posts, linked where it appears, and anything Google does not document is marked unverified.

Learn DevOps in this order: Linux, Git, Docker, a real deployment, environment variables and secrets, then continuous integration. Kubernetes comes last, and only if you want the DevOps job title rather than the ability to ship your own work. Before you start, spend ten minutes with the free roadmap at roadmap.sh/devops so you can see how those pieces depend on each other. Every stage below has a good free resource and a good paid one: the free route costs you time and assembly, the paid route costs money and buys both back.