bryan escherize

DIY DML Flat-Panel Speakers + Subwoofer — Complete Build Guide

A 2.1 hi-fi system built around DML (Distributed Mode Loudspeaker) flat panels for the mids/highs and a powered subwoofer for the bottom end. Two exciters turn two flat panels into full-range-ish speakers; a small Class-D amp drives them and feeds the sub.

Budget: ~$660 total
Difficulty: Beginner-friendly (no crossover math, no soldering required)
Use case: Music-first listening in a small/medium room
Time: An afternoon

name	linear-project-workflow
description	Opinionated end-to-end workflow for a small multi-dev project (design → grill → issues → build+capture → verify → retro). The thin hub that names the phases and their gates, delegating each to a focused spoke skill. Use when kicking off, running, or wrapping a multi-person project in Linear.

Linear project workflow — the hub

This is a thin orchestrator: it owns the phase flow and the gates between phases, and delegates each phase to a focused spoke. It deliberately does NOT repeat the spokes' content — a monolith that inlines everything dilutes the instructions and rots. The hub stays small so it never becomes the coupling bottleneck.

Every rule was retrofitted from a real project (Native 2FA) where the code shipped in ~90 minutes but key security invariants were designed in commit messages with no durable home, caught only by adversarial review. The workflow's job is to make that catch systematic.

name	linear-project-workflow
description	Opinionated end-to-end Linear workflow for a small multi-dev project (design → decisions → issues → build → capture → retro). Use when kicking off, running, or wrapping a multi-person project in Linear that wants a design doc, a decision log, mid-flight knowledge capture, and a retro. Delegates issue/branch/PR mechanics to the linear-workflow and linear-cli skills.

Linear project workflow (small team, fast + accurate)

The execution layer (issues, branches, status, PRs) is owned by linear-workflow and linear-cli — this skill does not repeat it. This is the layer above: how a project is shaped in Linear so a few devs move fast without losing the decisions and discoveries that only surface mid-build.

Every rule here was retrofitted from a real project (Native 2FA, 2026-07) where the code shipped in ~90 minutes but key security invariants (challenge-token jti consumption, replay ratcheting, a 401-vs-400 convention) were designed in commit message

Summary

Loving correction of children is biblically commanded, distinguishes instructive pain from damaging abuse, and finds its resolution in the gospel — where Jesus removes the shame that sin produces.

Situation: Every parent must correct their children, but fears doing harm in the process.
Complication: Fear of damage leads many to withhold necessary discipline, despite Scripture's clear commands.
Question: How should Christian parents correct their children biblically?
Answer: Use measured consequences that teach right from wrong, never out of anger, always pointing to Jesus who removes shame and offers forgiveness.

1. Correction is commanded and loving, not optional

Canyon Springs — Recent Sermon Summaries

May 17 – June 21, 2026 · For Bryan & Sarah

Overview

A six-week run through James, Proverbs, and Deuteronomy — moving from planning & patience into a sustained focus on parenting, teaching our children, and training for godliness.

| Date | Text | Theme |

Use the pyramid-principle skill whenever you write executive-facing prose; it pays for itself there and nowhere else.

Situation. You write memos, docs, PR descriptions, reports - things a busy reader must grasp fast.

Complication. LLMs (and most writers) default to context-first: setup, reasoning, conclusion buried last. Reader hits paragraph 4 before the point. "Be concise" and "be MECE" don't fix it - vague advice doesn't change model behavior.

Question. Is a structured skill worth the overhead over just writing?

Answer. Yes for executive writing, no for casual chat or code - three reasons below.

Toward a biff.fx-Style Effects Architecture in Metabase

Date: 2026-06-17
Source: Analysis of biff.fx by Jacob O'Bryant, applied to the Metabase codebase
Artifacts: biff.fx source (~150 LOC)

The Idea

PR #75333 Review: Replace H2 with SQLite for Sample Data

PR: metabase/metabase#75333 Author: @bgrabow Date reviewed: 2026-06-15 Scope: 47 files changed, +1479/-356 Labels: no-backport, PR-Env, .Team/Graphy

	;; ============================================================================
	;; Static Clojure — starter .clj-kondo/config.edn
	;;
	;; Companion to RULES.md (100 rules, each tagged KONDO: YES/HOOK/ANALYSIS/NO).
	;; This file is the executable half of the guide. It covers the 28 rules
	;; tagged KONDO: YES — everything clj-kondo can enforce with configuration
	;; alone, zero custom hook code.
	;;
	;; PURPOSE AND PHILOSOPHY
	;;

	#!/usr/bin/env bash
	# ============================================================================
	# setup-kid-omarchy.sh
	# ---------------------------------------------------------------------------
	# Turn an Omarchy (Arch Linux + Hyprland) machine into a reasonably
	# kid-safe box. Layered approach, because there is no single "Google Family
	# Link" equivalent on Linux — you stack a few small tools and each one
	# closes a different hole:
	#
	# LAYER TOOL WHAT IT STOPS