<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Repl-Driven-Development on PlumePHP</title><link>https://plumephp.com/tags/repl-driven-development/</link><description>Recent content in Repl-Driven-Development on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 29 Sep 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/repl-driven-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Clojure REPL 驱动开发：nREPL、热重载与交互式工作流</title><link>https://plumephp.com/clojure-repl-driven-development/</link><pubDate>Tue, 29 Sep 2026 13:00:00 +0800</pubDate><guid>https://plumephp.com/clojure-repl-driven-development/</guid><description>&lt;p&gt;Clojure 的杀手锏不是「函数式」，而是 &lt;strong&gt;REPL 驱动开发（RDD）&lt;/strong&gt;——你写一个函数，立刻求值验证，再写下一个。相比「写一整天代码然后编译跑测试」，RDD 是「边写边验证」的即时反馈循环，把错误消灭在诞生时刻。本文讲透这套工作流：REPL 是什么、nREPL 协议怎么连、Clojure CLI 与 Leiningen 怎么启动、CIDER/Calva 怎么把编辑器变成 REPL 前台、热重载如何让代码「活」着演化、远程 REPL 调试线上、REPL 里的测试调试，最后给纪律与陷阱。掌握 RDD，你才算「会写 Clojure」。&lt;/p&gt;</description></item></channel></rss>