Create a clean, professional, 2D animated explainer video...

Create a clean, professional, 2D animated explainer video about how clean code is created through rewriting and refactoring. Use the narration exactly as provided below. Do not rewrite, shorten, expand, correct, paraphrase, or add any narration. Visual style: modern hand-drawn whiteboard mixed with minimal code-editor visuals. Use smooth object reveals, code transformations, arrows, highlights, strike-throughs, and before-versus-after comparisons. Keep the visuals simple, intelligent, and directly connected to each narration line. Avoid generic developers sitting at computers, unnecessary decorative elements, 3D visuals, stock-photo style scenes, and excessive text. Visualise the narration in this sequence: Start with a large messy function containing multiple responsibilities. Gradually separate it into smaller functions, each performing one clear task. Show abstraction levels as stacked layers, with code moving into the correct layer. When the narration says nobody writes clean code on the first try, show a blank code editor rapidly filling with rough, unorganised code. Compare this process with writing a rough essay draft on paper. Visualise nested loops, meaningless variable names, long argument lists, and duplicated code as separate visible problems inside the code. Make the code look crowded and difficult to understand. When the narration says this is completely fine, soften the visual tone and show a green test suite protecting the code. Display tests passing while the messy code remains functional. During the refactoring section, visually split large functions, rename unclear variables, shorten argument lists, and remove duplicated code. Show each change happening step by step without changing the output of the program. Show the code becoming progressively cleaner with every iteration. Use repeated transformation cycles such as messy code → test → refactor → cleaner code. For the final statement, remove the messy version and reveal a clean, well-structured codebase. End with the sentence “Clean code isn’t written. It’s rewritten.” as the strongest visual moment. Then briefly reveal “Principles coming next.” Narration: “Functions should be small. They should do one thing. They should operate at one level of abstraction. We’ve discussed these rules. Honestly, nobody writes clean code on the first try. Writing code is like writing an essay. We get our thoughts down first—messy and disorganized, with nested loops, names that mean nothing, long argument lists, and duplicated code everywhere. And that’s completely fine. As long as we have tests, we can refactor it with confidence. We split functions, find better names, and eliminate duplication. Iteration by iteration, the code starts following every rule. Clean code isn’t written. It’s rewritten. Principles coming next.”