Laurence Chen humorless

Dev Workflow

After editing source files, use brepl to require the changed namespace with :reload and test interactively, rather than relying solely on curl or bb test.

Call handlers directly — Ring handlers are pure functions (request map → response map). Test them in brepl without going through HTTP or middleware: (handlers/home-handler {}), (handlers/inspect-handler {}). Inspect response structure with (keys resp) before dumping the full body.
Verify routes with Reitit — Use reitit.core/match-by-path to check route matching interactively without a browser: (reitit.core/match-by-path (reitit.ring/router app-routes/routes) "/"). Useful for verifying newly added routes before integration testing.
Compose and inspect HoneySQL queries — Build queries incrementally as data and preview the generated SQL with (honey.sql/format query {:quoted true}) before sending to the database. This lets you verify correctness without executing a

chmod -R 777 /tmp/kestra-wd/tmp

layout-component (ornament fn)
- handle CSS part
- leverage query syntax to assign CSS to child structure
widget-component (ornament fn)
- small, reusable, and self-contained UI elements)
presenter-fn (ordinary fn)
- handle pure html structure (withouth CSS)
- example: fail-page
container-fn (ordinary fn)
- handle the data && logic behavior

如何在 neovim 裡註冊一個新的 filetype

如果建立了一個新的 neovim plugin，比方說，叫做 conjure-piglet-client
該 plugin 用 fnl 寫多數的邏輯。

	;; Example of using
	;;
	;; - #{...}
	;; - "&:not()"
	;; - "&:has()"

	(o/defstyled form :form
	...
	[#{:input :textarea :select} ["&:not([type=checkbox])"
	:w-full :mb-3]]

	## 假設您將書分成三個部分（Part 1, Part 2, Part 3），這是您給第一個部分（Part 1）的提示：

	```
	以下是一本專業書的第${n}部分。請你閱讀這段內容，並幫助我分析這段文字所預設的「隱含讀者」（implied reader）是什麼樣的人？

	具體來說，請你從以下幾個方面來描述：
	1. 讀者的背景知識：這位讀者可能具備哪些專業知識？是初學者、中級學習者還是該領域的專家？
	2. 讀者的學習目標：這位讀者想從書中獲得什麼？是想解決特定問題、學習新技能還是獲取宏觀知識？
	3. 讀者的思維模式與偏好：讀者可能習慣什麼樣的論證方式？是喜歡條列式說明、圖表輔助還是需要大量實例？
	4. 基於以上分析，請你綜合描述這位「隱含讀者」的完整輪廓。