Switching Guides
Short, scannable references for the first week after you switch platforms or tools. Each guide is a two-column table mapping what you used to do to what you do now — no marketing, no feature tours, just the everyday actions and where they moved.
Switching guides
-
Switching from Windows to Mac
File Explorer to Finder, Task Manager to Activity Monitor, Ctrl to Cmd, plus the friction points nobody warns you about. 23 rows.
-
Chrome to Safari
Bookmarks, sync, extensions, tab groups, passwords, privacy and downloads — where each one moved. 20 rows.
Practice guides
Same two-column format, applied to habits rather than platforms: the instinct on the left, the principle that should replace it on the right.
-
Test Automation Principles
The test pyramid and what belongs at each layer, then 24 principles on flakiness, mocking, selectors, suite runtime and ownership.
Planned
-
Mac to Windows Planned
The reverse trip: Finder to Explorer, Spotlight to Windows Search, and re-learning the modifier keys.
-
Android to iPhone Planned
Moving contacts, photos and messages, plus the gestures and settings that changed names.
-
Gmail to Outlook Planned
Labels to folders, filters to rules, and where search syntax differs.
-
Excel to Google Sheets Planned
Formula gaps, macros to Apps Script, and the shortcuts that don't carry over.
-
Slack to Microsoft Teams Planned
Channels, threads, huddles and notification settings, mapped side by side.
-
VS Code to JetBrains Planned
Keymaps, extensions to plugins, and how projects and run configs differ.
-
Photoshop to Figma Planned
Layers to frames, artboards to pages, and what to stop expecting.
-
Jira to Linear Planned
Issues, workflows, sprints to cycles, and migrating without losing history.
Adding a guide
Copy an existing folder under /guides/, keep the same page skeleton
(header, h1, intro paragraph, [data-filter-mount] div,
table.compare inside a .table-scroll wrapper, callout,
footer), and add a card to the list above. No build step, no dependencies.