Skip to content

Instantly share code, notes, and snippets.

@guersam
guersam / reading-methodologies-for-software-plan-review-ko.md
Last active February 20, 2026 10:13
Reading Methodologies for Software Plan Review in Agentic Pair Programming

에이전틱 페어 프로그래밍에서 소프트웨어 설계 문서 리뷰를 위한 읽기 방법론

1. 서론

소프트웨어 설계 문서 — 아키텍처 문서, RFC, 기능 명세서, API 설계서 — 는 엔지니어링 팀이 생산하는 산출물 중 가장 밀도가 높습니다. 이러한 문서는 학술 논문, 법률 계약서, 안전 명세서와 구조적 특성을 공유합니다. 계층적 의존성, 암묵적 가정, 오해로 인한 높은 비용, 그리고 한 번 읽고 여러 번 실행하는 경향이 그것입니다.

구조적 읽기 방법론은 이러한 특성을 다루기 위해 수십 년간 발전해 왔습니다. SQ3R은 1940년대 군사 훈련을 위해 개발되었고, Fagan Inspection은 1976년 IBM에서 도입되었으며, Perspective-Based Reading은 1990년대 NASA 연구에서 탄생했습니다. 각 방법론은 복잡한 문서에서 의미를 추출하고, 빈틈을 찾아내며, 실행 가능한 판단을 도출하는 체계를 담고 있습니다.

에이전틱 LLM(대규모 언어 모델)은 이제 이러한 설계 문서를 리뷰하는 페어 프로그래밍 파트너로 활용되고 있습니다. 그러나 "이 설계를 리뷰해 줘"나 "어떻게 생각해?"같은 비구조적 프롬프팅은 피상적이고, 아첨적(sycophantic)이거나, 모드가 혼합된 응답을 유발합니다. LLM은 저자의 프레이밍에 동의하고, 그럴듯하지만 일반적인 관찰을 생성하며, 리뷰를 진정으로 가치 있게 만드는 구조적이거나 적대적인 통찰을 도출하지 못합니다.

@Dowwie
Dowwie / socratic_fp_learning.md
Created June 7, 2025 09:23
Following is a prompt for effective learning with an LLM. It uses the Socratic method to help the student build up their understanding from first principles. Replace the topic in the prompt and then in your follow-up prompt , specify the subject.

You are a teacher of algorithms and data-structures who specializes in the use of the socratic method of teaching concepts. You build up a foundation of understanding with your student as they advance using first principles thinking. Explain the subject that the student provides to you using this approach. By default, do not explain using source code nor artifacts until the student asks for you to do so. Furthermore, do not use analysis tools. Instead, explain concepts in natural language. You are to assume the role of teacher where the teacher asks a leading question to the student. The student thinks and responds. Engage misunderstanding until the student has sufficiently demonstrated that they've corrected their thinking. Continue until the core material of a subject is completely covered. I would benefit most from an explanation style in which you frequently pause to confirm, via asking me test questions, that I've understood your explanations so far. Particularly helpful are test questions related to sim

@jackrusher
jackrusher / webdav.clj
Last active June 18, 2025 20:13
A minimal webdav server/synthetic filesystem that works with JVM Clojure and babashka. See comments for instructions!
(ns webdav
(:require [clojure.string :as str]
[clojure.data.xml :as xml]
[org.httpkit.server :as hk-server]))
;; add the XML namespace that we'll use later
(xml/alias-uri 'd "DAV:")
(defn dissoc-in
"Should be in the standard library..."
@HugoGresse
HugoGresse / adbx
Last active November 27, 2022 11:19
Adb command to set proxy (WIP)
#!/bin/bash
usage() {
echo "Usage:"
echo " adbx proxy set"
echo " adbx proxy get"
echo " adbx proxy remove"
}
@hjertnes
hjertnes / doom.txt
Created April 6, 2018 08:28
Doom Emacs Cheatsheet
SPC
SPC: find file
, switch buffer
. browse files
: MX
; EX
< switch buffer
` eval
u universal arg
x pop up scratch
@bobrik
bobrik / README.md
Last active March 27, 2025 02:16
CFS hiccups
@KeithYeh
KeithYeh / Self-Signed SSL with SAN.md
Created October 14, 2017 13:12
Create self-signed SSL certificate with SubjectAltName(SAN)

How to create a self-signed SSL Certificate with SubjectAltName(SAN)

After Chrome 58, self-signed certificate without SAN is not valid anymore.

Step 1: Generate a Private Key

openssl genrsa -des3 -out example.com.key 2048

Step 2: Generate a CSR (Certificate Signing Request)

(ns blah
(:require [com.walmartlabs.lacinia.schema :as schema]
[com.walmartlabs.lacinia.util :refer [attach-resolvers]]
[com.walmartlabs.lacinia :as lacinia]))
(defn batch [ctx id]
(prn 'batch id)
(swap! (::loader ctx)
(fn [loader]
(if (contains? (:cache loader) id)
@reborg
reborg / rich-already-answered-that.md
Last active February 18, 2026 01:27
A curated collection of answers that Rich gave throughout the history of Clojure

Rich Already Answered That!

A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.

How to use:

  • The link in the table of content jumps at the copy of the answer on this page.
  • The link on the answer itself points back at the original post.

Table of Content