Spaced repetition for engineers

My working answer: yes for discrete, hard-won facts you rarely touch (a flag, a 2am config), and not for concepts you can re-derive. The rest I’m still chewing on.

I keep relearning the same things: a flag I used once, a config I debugged at 2am, a pattern I “knew” three years ago. Spaced repetition solved this for medical students and language learners. Why don’t more engineers run a deck for the hard-won, rarely-used stuff?

Open questions I’m chewing on:

• What earns a card, versus what’s better left as a searchable note?
• Does carding concepts work, or only discrete facts?
• How do you keep a deck from rotting as the tools change underneath it?

Seedling: mostly questions so far.