Update wiki/operation-optimization.md
bb5db187fc33 harrisonqian 2026-04-12 1 file
index 34b652e..00572ca 100644
@@ -25,21 +25,12 @@ these check-ins are the operational version of [[zooming-out]] — applied to yo
## self-improvement experiments
things i've tried:
-- circadian lights, morning routine, no-eating blocks, wind-down routine
- structured first hour, unstructured second hour
- 10% of time on crazy ideas (from [[startup-workflow]]'s 80-15-5 rule)
- voice to text for coding (see [[vibe-coding]])
some of these stuck, some didn't. the meta-lesson: run experiments, but don't expect all of them to work. and don't keep running experiments that aren't working just because you spent time setting them up.
-## discipline vs. scaffolding
-
-a recurring question: should you train raw discipline (willpower, push-through capacity) or build scaffolding (apps, routines, systems, atomic habits)?
-
-i lean toward discipline. scaffolding can become a crutch — when the app breaks or the routine gets disrupted, you're left with nothing. raw discipline transfers across contexts. see [[perseverance]].
-
-but scaffolding has value for getting started. the sequence: scaffolding to build the habit → gradually remove scaffolding → raw discipline maintains it.
-
## wasted setup time
"wasted a lot of time on setup that didn't matter — ditching them feels so good." operation optimization sometimes means undoing previous optimization attempts. if a system isn't serving you, kill it. don't maintain complexity out of sunk cost.