WorkPace

Most AI tools now let you choose between a few different models — and it can feel a bit like ordering off a menu in a language you don't speak. The good news: you only need to know three tiers and what each one is good at. Here's the simple version. ## The three tiers (and how to think about them) Most AI providers offer something like a small/medium/large lineup. Anthropic's Claude family is a clean example: **Haiku** (small and fast), **Sonnet** (the balanced default), and **Opus** (the heavy-hitter). OpenAI, Google, and others follow a similar pattern. Pick based on how hard your task actually is — not on which model sounds fanciest. ## The fast, lightweight model (e.g. Claude Haiku) **Best for:** quick tasks, high-volume work, anything where speed and cost matter more than raw brainpower. **Strengths:** very fast responses, much cheaper, great for simple summaries, classification, drafting short messages, answering FAQs, or processing lots of inputs at once. **Weaknesses:** struggles with long, multi-step reasoning. Don't ask it to debug a tricky race condition or design complex architecture — it'll get there, but slowly and with more mistakes. **Reach for it when:** you need to triage support tickets, summarize a meeting, draft a quick email, or run something thousands of times in a loop. ## The balanced default (e.g. Claude Sonnet) **Best for:** about 90% of what most people actually do with AI. **Strengths:** strong reasoning, solid coding ability, reliable tool use, and fast enough to feel snappy in a chat. It's the model most AI tools (including Claude Code) use by default for a reason — it hits the sweet spot between quality and cost. **Weaknesses:** the very hardest reasoning problems — novel research, deeply ambiguous tasks, multi-hour autonomous work — will occasionally trip it up. **Reach for it when:** you're writing, coding, analyzing data, building something, or having a meaningful conversation. Start here by default. ## The heavy-hitter (e.g. Claude Opus) **Best for:** the genuinely hard stuff. **Strengths:** deep reasoning, complex multi-step planning, careful code reviews, novel problem-solving, and long autonomous tasks. It's the model you want when a small mistake costs a lot. **Weaknesses:** slower and more expensive — often 5x the cost of the mid-tier model. Overkill for everyday work. **Reach for it when:** you're debugging something nasty, doing a final code review before shipping, working through a research problem, or tackling something where you need it done right the first time. ## A simple rule of thumb Start with the **mid-tier** model. If it nails your task, you're done. If it struggles, **upgrade to the flagship** for that one job. If you're running the same simple task hundreds of times, **drop down to the fast tier** to save time and money. That's really it. Match the model to the task, not the other way around. ## Bonus: it's not just Claude The same logic applies across providers. OpenAI has a similar small/medium/large split, as do Google's Gemini models. Whichever ecosystem you're in, the principle is the same — fast and cheap for volume, balanced for daily work, flagship for the hard problems. ## Wrapping up You don't need to memorize benchmarks or chase the latest release. Pick a default, know when to step up, and know when to step down. Do that, and you'll get better results without burning time (or budget) on the wrong tool.

# How to Install Claude Code and Start Using It Claude Code is Anthropic's command-line tool that lets you delegate real coding tasks to Claude — straight from your terminal. It can read your files, write new ones, run commands, and work through entire features while you watch (or grab a coffee). Here's how to get it set up and run your first task. > **Quick note:** Claude Code is a separate tool from the Claude desktop chat app. The desktop app is for conversations; Claude Code lives in your terminal and works directly with your codebase. You'll use the terminal for this guide. ## Before you start You'll need a paid Claude plan (Pro, Max, Team, or Enterprise) or an Anthropic Console account with API credits. The free Claude.ai plan doesn't include Claude Code access. ## Step 1: Install Claude Code The native installer is the recommended path — no Node.js, no package manager drama, and it auto-updates in the background. **macOS or Linux** — open your terminal and run: ```bash curl -fsSL https://claude.ai/install.sh | bash ``` **Windows** — open PowerShell (not CMD) and run: ```powershell irm https://claude.ai/install.ps1 | iex ``` Once it finishes, close and reopen your terminal so it picks up the new `claude` command. ## Step 2: Verify the install Run this to confirm everything's wired up: ```bash claude --version ``` You should see a version number print out. If you want a deeper health check, run `claude doctor` — it'll flag anything off about your setup. ## Step 3: Log in Navigate into a project folder and start Claude Code: ```bash cd ~/your-project claude ``` The first time you run it, your browser will open for a one-time OAuth login. Sign in with the Anthropic account tied to your subscription, paste the code back into the terminal if prompted, and you're in. ## Step 4: Try your first task Now the fun part. Just type what you want in plain English. A few starter ideas: - "Explain what this codebase does." - "Find the bug in `auth.js` and fix it." - "Add a dark mode toggle to the settings page." - "Write tests for the `parseInput` function." Claude Code will read the relevant files, propose changes, and ask before writing or running anything destructive. You stay in control of every step. ## Where the desktop app fits in If you're using the Claude desktop app for chat, think of it as the planning room and Claude Code as the workshop. A common workflow: brainstorm an approach in the desktop app, then drop into your terminal and let Claude Code actually build it. The two are separate tools, but they pair nicely. ## Wrapping up That's really all there is to it — one install command, one login, and you've got an AI collaborator working alongside you in your codebase. Start with a small, low-stakes task on a real project. You'll feel the difference within minutes.

Notion is a flexible workspace where notes, tasks, docs, and databases all live in one place. The blank canvas can feel intimidating at first — but you only need a few basics to get going. ## Step 1: Create your account Head to [notion.so](https://notion.so) and sign up with your email or Google account. The free plan is plenty for personal use. ## Step 2: Learn the one rule Everything in Notion is a **page**. Pages can hold text, to-do lists, tables, images, or other pages nested inside them. That's it — once you get that, the rest clicks. ## Step 3: Try the basics Type `/` anywhere on a page to pull up the menu of blocks you can add — headings, checklists, toggles, databases, and more. Play around for five minutes and you'll have the feel of it. ## Step 4: Start with a template The fastest way to get value out of Notion is to skip the blank page entirely. Grab my template here to get a ready-made setup you can start using today: 👉 https://www.notion.so/sammy-elsherif/Home-SRT-Framework-34a2861133b58006a16dd4977e6ef464?source=copy_link Just click **Duplicate** in the top-right corner and it'll drop straight into your workspace. ## Wrapping up Don't overthink it. Sign up, duplicate the template, and start using it. You'll learn more in a week of actually using Notion than in any tutorial.

# How to Duplicate a Workspace in Notion (The Easy Way) Ever spent hours building the perfect Notion setup — only to wish you had a copy you could reuse for your next project, team, or client? Good news: you can duplicate your workspace's content and save yourself from rebuilding it block by block. Here's how to do it in just a few minutes. ## Why duplicate a workspace? Duplicating gives you a ready-made blueprint for recurring projects, a safe sandbox for onboarding new teammates, and a way to keep branding consistent across multiple teams. Think of it as cloning your favorite playbook so you can hit the ground running every time. ## Step 1: Create a new "container" page In the workspace that holds the content you want to copy, head to the sidebar and click **+ New page**. This page will act as a container — a single home for everything you're about to duplicate, which makes the process way faster than moving pages one at a time. ## Step 2: Drag your pages into the container From your sidebar, drag every page you want to duplicate into the new container page you just created. All sub-pages will come along for the ride automatically, so you only need to grab the top-level ones. ## Step 3: Move it to your destination workspace Click the **•••** menu next to your container page (or right-click it) and choose **Move to**. At the bottom of the menu, open the dropdown next to your current workspace's name and select the destination workspace. Confirm with **I understand, duplicate**, and Notion will copy everything over. > **Moving to a different account instead?** Open the container page, click **Share**, and invite the other account's email with **Full access**. Then log into that account and use the same Move to → Duplicate flow. ## Step 4: Do a final walkthrough Pop into your new workspace and check that everything landed where it should. Pay extra attention to links, database relations, and permissions — these can occasionally break during duplication. Keep your original content untouched until you're sure the copy is solid. ## A heads-up before you start Notion doesn't currently let you clone an entire workspace with one click — what you're really doing is bulk-duplicating pages from one workspace into another. It's the closest thing to a true workspace duplicate, and for most people it does the job perfectly. ## Wrapping up Once you've got the hang of it, duplicating workspaces becomes a serious productivity move. Build a master setup once, clone it whenever you need to, and never reinvent the wheel again. Happy duplicating!