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: https://t.co/BW0XjTudAi
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: https://t.co/sl7AVEAYvF
🤔 Review regularly

The most overlooked & underrated thing that helps with context-switching is reviewing projects & notes regularly. It:

- Helps us notice patterns
- Clears the junk from our heads
- Helps us understand our true capacity

More: https://t.co/9vE7lgVQyk
I review my projects in Notion about once a week & add comments about the last thing I was working on & my next action.

I do some "digital gardening" in Drafts & Obsidian each day; I'll review my Drafts inbox & move to Obsidian or clean up my notes on whatever I'm working on.
🤖 Automate where you can

Automation can be a rabbit hole, but the place to prioritize is reducing your likelihood of getting distracted. Like when you head to Chrome to Google something & then come to your senses an hour later while deep in the @dog_rates timeline 🐕.
Take advantage of all the ways technology can help you, whether shell scripts or tools like @zapier & @integromat. I rely on @keyboardmaestro & @TextExpander to insert snippets, launch collections of apps, etc. Here's how I use KM w/screencasting: https://t.co/ZUfhQx9Brq
I also learned a trick from @MacSparky on how to use KM to create "context palettes" of shortcuts. I hit "ctrl-cmd-opt-B" to bring up a bunch of business shortcuts to launch sites, open repos in @code, or open a Notion project. Here's how to do it: https://t.co/nGbvHMVIL8
Start slow with automation; notice where you're getting distracted & gradually build automations that save you steps.

It's easy to over-engineer something complicated & then ditch the whole thing out of frustration.

To really nerd out on this, check out @automatorsfm 🤓
I've found this combo of centralizing capture, regular review, & automation to be extremely powerful even when I only get it right 70% of the time. The slow burn 🔥 significantly reduces the amount of time I need to get creative work done.
If you found this helpful, you'd probably also like my Developer Microskills newsletter! Each week, I send out a practical, actionable way to improve as a dev & dev advocate. Last week's issue was an expanded version of this thread!

Join 1090+ other devs: https://t.co/V2TzZmX1F5

More from Productivity

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
And here they are...

THE WINNERS OF THE 24 HOUR STARTUP CHALLENGE

Remember, this money is just fun. If you launched a product (or even attempted a launch) - you did something worth MUCH more than $1,000.

#24hrstartup

The winners 👇

#10

Lattes For Change - Skip a latte and save a life.

https://t.co/M75RAirZzs

@frantzfries built a platform where you can see how skipping your morning latte could do for the world.

A great product for a great cause.

Congrats Chris on winning $250!


#9

Instaland - Create amazing landing pages for your followers.

https://t.co/5KkveJTAsy

A team project! @bpmct and @BaileyPumfleet built a tool for social media influencers to create simple "swipe up" landing pages for followers.

Really impressive for 24 hours. Congrats!


#8

SayHenlo - Chat without distractions

https://t.co/og0B7gmkW6

Built by @DaltonEdwards, it's a platform for combatting conversation overload. This product was also coded exclusively from an iPad 😲

Dalton is a beast. I'm so excited he placed in the top 10.


#7

CoderStory - Learn to code from developers across the globe!

https://t.co/86Ay6nF4AY

Built by @jesswallaceuk, the project is focused on highlighting the experience of developers and people learning to code.

I wish this existed when I learned to code! Congrats on $250!!