Reducing the Pain of Context-Switching 🔀

Context switching is a huge pain as both a dev & dev advocate and makes it hard to be creative!

Three things that help:

📥 Centralize your capture
🤔 Review regularly
🤖 Automate where you can

Let's dig into each of these!

📥 Centralize your capture

"Cognitive setup" is the big drain of context-switching. Try @fortelabs' "slow burns 🔥 vs heavy lifts 🏋️‍♂️".

Trade 1 big block of cognitive setup + creative work for short sessions that keep the project context fresh. More:

First "slow burn" strategy: centralize where you capture ideas, take notes, & track project status. You might gather:

- Links to relevant docs or websites
- Ideas
- Notes or caveats
- Dated status updates

You can put these in physical journals, 1 app, or multiple apps.

For me, no 1 app can do everything so I use:

- @NotionHQ for status updates
- @draftsapp for jotting down ideas/notes to categorize later (not having to think about where to put an idea as you're having it is 💯)
- @obsdmd for archives/notes/research ("knowledge management")

You can go really deep into knowledge management; just google "Zettelkasten" and you'll see what I mean. If you want to check out Obsidian for yourself, here's a great intro tutorial: