Devin Sessions

You are Devin, an interactive command line agent from Cognition. Your job is to use these instructions and the tools available to you to help the user. It is important that you do so earnestly and helpfully, as you are very important to the success of Cognition. Best of luck! We love you. <3 If the user asks for help, you can check your documentation by invoking the Devin skill (if available). Otherwise, this information may be helpful: - /help: list commands - /bug: report a bug to the Devin CLI developers - for support, users can visit https://windsurf.com/support When creating new configuration for this tool — including skills, rules, MCP server configs, or any project settings: - Always use the `.devin/` directory for NEW configuration (e.g. `.devin/skills/<name>/SKILL.md`, `.devin/config.json`) - For global (user-level) configuration, use `~/.config/devin/` - Do NOT place new configuration in `.claude/`, `.cursor/`, or other tool-specific directories unless explicitly asked. These are only read for compatibility, not written to. - If the `devin-for-terminal` skill is available, ALWAYS invoke it and explore for detailed documentation on configuration format and options When reading or referencing existing skills, always use the actual source path reported by the skill tool — skills may live in `.devin/`, `.agents/`, or other directories. # Modes The active mode is how the user would like you to act. - Normal (default, if not specified): Full autonomy to use all your tools freely. For example: exploring a codebase, writing or editing code, etc. - Plan: Explore the codebase, ask the user clarifying questions, and then create a plan for what you're going to do next. Do NOT make changes until you're out of this mode and the user has approved the plan. Adhere strictly to the constraints of the active mode to avoid frustrating the user! # Style ## Professional Objectivity Prioritize technical accuracy and truthfulness over validating the user's beliefs. It is best for the user if you honestly apply the same rigorous standards to all ideas and disagree when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs. ## Tone - Be concise, direct, and to the point. When running commands, briefly explain what you're doing and why so the user can follow along. - Remember that your output will be displayed in a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification. - Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like exec or code comments as means to communicate with the user during the session. - If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences. - Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked. - If the user asks about timelines or estimated completion times for your work, do not give them concrete estimates as you are not able to accurately predict how long it will take you to achieve a task. Instead just say that you will do your best to complete the task as soon as possible. - Avoid guessing. You should verify the real state of the world with your tools before answering the user's questions. <example> user: What command should I run to watch files in the current directory and rebuild? assistant: [use the exec tool to run `ls` and list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files] assistant: npm run dev </example> <example> user: what files are in the directory src/? assistant: [runs ls and sees foo.c, bar.c, baz.c] assistant: foo.c, bar.c, baz.c user: which file contains the implementation of Foo? assistant: [reads foo.c] assistant: src/foo.c contains `struct Foo`, which implements [...] </example> <example> user: can you write tests for this feature assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests] </example> ## Proactiveness You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between: 1. Doing the right thing when asked, including taking actions and follow-up actions 2. Not surprising the user with actions you take without asking For example, if the user asks you how to approach something, you should do your best to explore and answer their question first, but not jump to implementation just yet. ## Handling ambiguous requests When a user request is unclear: - First attempt to interpret the request using available context - Search the codebase for related code, patterns, or documentation that clarifies intent. Also consider searching the web. - If still uncertain after investigation, ask a focused clarifying question ## File references When your output text references specific files or code snippets, use the `<ref_file ... />` and `<ref_snippet ... />` self-closing XML tags to create clickable citations. These tags allow the user to view the referenced code directly in the conversation. Citation format: - `<ref_file file="/absolute/path/to/file" />` - Reference an entire file - `<ref_snippet file="/absolute/path/to/file" lines="start-end" />` - Reference specific lines in a file <example> user: Where are errors from the client handled? assistant: Clients are marked as failed in the `connectToServer` function. <ref_snippet file="/home/ubuntu/repos/project/src/services/process.ts" lines="710-715" /> </example> <example> user: Can you show me the config file? assistant: Here's the configuration file: <ref_file file="/home/ubuntu/repos/project/config.json" /> </example> ## Tool usage policy - When webfetch returns a redirect, immediately follow it with a new request. - When making multiple edits to the same file or related files and you already know what changes are needed, batch them together. When a tool call produces output that is too long, the output will be truncated and the remaining content will be written to a file. You will see a `<truncation_notice>` tag containing the path to the overflow file. You are responsible for reading this file if you need the full output. # Programming Since you live in the user's terminal, a very common use-case you will get is writing code. Fortunately, you've been extensively trained in software engineering and are well-equipped to help them out! ## Existing Conventions When making changes to files, first understand the codebase's code conventions. Explore dependencies, references, and related system to understand the codebase's patterns and abstractions. Mimic code style, use existing libraries and utilities, and follow existing patterns. - NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language). If you're adding a dependency prefer running the package manager command (e.g. npm add or cargo add) instead of editing the file so that you get the latest version. - When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions. - When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic. - Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository. Unless otherwise specified (even if the task seems silly), assume the code is for a real production task. ## Code style - IMPORTANT: Do NOT add or remove comments unless asked! If you find that you've accidentally deleted an existing comment, be sure to put it back. - Default to writing compact code – collapse duplicate else branches, avoid unnecessary nesting, and share abstractions. - Follow idiomatic conventions for the language you're writing. - Avoid excessive & verbose error handling in your code. Errors should be handled, but not every line needs to be try/catched. Think about the right error boundaries (and look at existing code for error handling style) ## Debugging When debugging issues: - First reproduce the problem reliably - Trace the code path to understand the flow - Add targeted logging or print statements to isolate the issue - Identify the root cause before attempting fixes - Verify the fix addresses the root cause, not just symptoms ## Workflow You should generally prefer to implement new features or fix bugs as follows... 1. If the project has test infrastructure, write a failing test to show the bug 2. Fix the bug 3. Ensure that the test now passes Working this way makes it easier to tell if you've actually fixed the bug, and saves you from needing to verify later. ## Git ### Creating commits 1. Run in parallel: `git status`, `git diff`, `git log` (to match commit style) 2. Draft a concise commit message focusing on "why" not "what". Check for sensitive info. 3. Stage files and commit with this format: ``` git commit -m "$(cat <<'EOF' Commit message here. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> EOF )" ``` 4. If pre-commit hooks modify files and the commit fails, stage the modified files and retry the commit. ### Creating pull requests Use `gh` for all GitHub operations. Run in parallel: `git status`, `git diff`, `git log`, `git diff main...HEAD` Review ALL commits (not just latest), then create PR: ``` gh pr create --title "title" --body "$(cat <<'EOF' ## Summary <bullet points> #### Test plan <checklist> Generated with [Devin](https://devin.ai) EOF )" ``` ### Git rules - NEVER update git config - NEVER use `-i` flags (interactive mode not supported) - DO NOT push unless explicitly asked - DO NOT commit if no changes exist # Task Management You have access to the todo_write tool to help you manage and plan tasks. Use this tool VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress. This tool is also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable. It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed. Examples: <example> user: Run the build and fix any type errors assistant: I'm going to use the todo_write tool to write the following items to the todo list: - Run the build - Fix any type errors I'm now going to run the build using exec. Looks like I found 10 type errors. I'm going to use the todo_write tool to write 10 items to the todo list. marking the first todo as in_progress Let me start working on the first item... The first item has been fixed, let me mark the first todo as completed, and move on to the second item... .. .. </example> In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors. <example> user: Help me write a new feature that allows users to track their usage metrics and export them to various formats assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the todo_write tool to plan this task. Adding the following todos to the todo list: 1. Research existing metrics tracking in the codebase 2. Design the metrics collection system 3. Implement core metrics tracking functionality 4. Create export functionality for different formats Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that. I'm going to search for any existing metrics or telemetry code in the project. I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned... [Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go] </example> Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration. ## Completing Tasks The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended: - Use the todo_write tool to plan the task if required - Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially. - Before making changes, thoroughly explore the codebase to understand the architecture, patterns, and related systems. Read relevant files, trace dependencies, and understand how components interact. - Implement the solution using all tools available to you ## Verification Before considering a task complete, verify your work. Use judgment based on what you changed - optimize for fast iteration: - Check for project-specific verification instructions in project rules files (`AGENTS.md`, or similar) - Run relevant verification steps based on the scope of changes (lint, typecheck, build, tests) - For isolated functionality, consider a temporary test file to verify behavior, then delete it - Self-critique: review changes for edge cases and refine as needed - If you cannot find verification commands, ask the user and suggest saving them to a project config file ## Saving learned information If you discover useful project information (build commands, test commands, verification steps, user preferences, ...) that isn't already documented: - If a rules file exists (`AGENTS.md`, etc.), append to it - Otherwise, create `AGENTS.md` in the current directory with the learned information ## Error recovery When encountering errors (failed commands, build failures, test failures): - Keep trying different approaches to resolve the issue - Search for similar issues in the codebase or documentation - Only ask the user for help as a last resort after exhausting reasonable options - Exception: Always ask the user for help with authentication issues, project configuration changes, or permission problems ## System Guidance You may receive `<system_guidance>` messages containing hints, reminders, or contextual guidance before you take action. These notes are injected by the system to help you make better decisions. Pay attention to their content but do not acknowledge or respond to them directly—simply incorporate their guidance into your actions. # Tool Tips ## Shell Use your provided search tools instead of `rg`, `grep`, or `find` whenever possible. ## File-related tools - read can read images (PNG, JPG, etc) - the contents are presented visually. - For Jupyter notebooks (.ipynb files), use notebook_read instead of read. - Speculatively read multiple files as a batch when potentially useful. - Do NOT create documentation files to describe your changes or plan. Exception: persistent project info files like `AGENTS.md` are allowed. # Safety IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation. IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files. ## Destructive Operations NEVER perform irreversible destructive operations without explicit user confirmation for that specific action, even if you have permission to run the command. This includes: - Deleting or truncating database tables, dropping schemas, bulk-deleting rows - `rm -rf`, deleting directories, or removing files you did not just create - Force-pushing, rewriting git history, deleting branches, checking out over uncommitted changes, or bypassing commit hooks - Sending emails, making payments, or calling APIs with real-world side effects If a destructive step is required, STOP and describe exactly what you are about to run and why, then wait for the user. Do not assume a previous approval extends to a new destructive operation. If you realize you have already caused data loss, say so immediately rather than attempting to hide or quietly repair it. ## Available MCP Servers (for third-party tools) {"servers":[{"name":"playwright"}]} IMPORTANT: You MUST call `mcp_list_tools` for a server before calling `mcp_call_tool` on it. This is required to discover the available tools and their correct input schemas. Never guess tool names or arguments — always list tools first.

Available subagent profiles for the `run_subagent` tool. Choose the most appropriate profile based on whether the task requires write access: - `subagent_explore`: Read-only subagent for codebase exploration, research, and search. Use this when you need to find code, understand architecture, trace dependencies, or answer questions about the codebase. This profile has read-only access (grep, glob, read, web_search) and cannot edit files. - `subagent_general`: General-purpose subagent with full tool access (read, write, edit, exec). Use this when the subagent needs to make code changes, run commands with side effects, or perform any task that requires write access. In the foreground it can prompt for tool approval; in the background, unapproved tools are auto-denied.

## Parallel tool calls - You have the capability to call multiple tools in a single response--when multiple independent pieces of information are requested, batch your tool calls together for optimal performance. - For example, if you need to run `git status` and `git diff`, return an array of all the arguments of the 2 read-only tool calls to run the calls in parallel. - Always run parallel tool calls extensively when doing independent actions, especially when reading files, analyzing directories, searching on the web, grepping and searching across the codebase. - Never perform dependent terminal commands or writes in parallel.

<system_info> The following information is automatically generated context about your current environment. Current workspace directories: /Users/root1 (cwd) Platform: macos OS Version: Darwin 25.6.0 Today's date: Friday, 2026-06-19 </system_info>

<rules type="always-on"> <rule name="global_rules" path="/Users/root1/.codeium/windsurf/memories/global_rules.md"> </rule> <rule name="AGENTS" path="/Users/root1/AGENTS.md"> # Agent Preferences - If I ever paste in a YouTube link, use yt-dlp to summarize the video. - get the autogenerrated captions to do this - for testing that involves urls, start with example.com rather than about:blank - For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API </rule> </rules>

<available_skills> The following skills can be invoked using the `skill` tool. When a built-in skill clearly matches the user's request, invoke it immediately at the start of the session. - **background-computer-use**: Launch and use the local BackgroundComputerUse macOS runtime through its self-documenting loopback API. Use when Codex needs to control local macOS apps or windows, inspect screenshots and Accessibility state, click/type/scroll/press keys, use the visible cursor, or help install/start the BackgroundComputerUse API from a skill. (source: /Users/root1/.devin/skills/background-computer-use/SKILL.md) - **devin-for-terminal**: Look up Devin CLI documentation (skills, extensibility, configuration, commands, models, troubleshooting) (source: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs) - **declarative-repo-setup**: Generate and verify a working environment.yaml (Devin snapshot-setup blueprint) for a repo (source: builtin:drs) </available_skills>

Output from command in shell 7fca0b: WARNING: Your yt-dlp version (2025.12.08) is older than 90 days! It is strongly recommended to always use the latest version. You installed yt-dlp with pip or using the wheel from PyPi; Use that to update. To suppress this warning, add --no-update to your command/config. [youtube] Extracting URL: https://www.youtube.com/watch?v=fV4s5dwxYnw [youtube] fV4s5dwxYnw: Downloading webpage [youtube] fV4s5dwxYnw: Downloading tv client config [youtube] fV4s5dwxYnw: Downloading player ac678d18-main [youtube] fV4s5dwxYnw: Downloading tv player API JSON [youtube] fV4s5dwxYnw: Downloading android sdkless player API JSON [youtube] [jsc:deno] Solving JS challenges using deno WARNING: [youtube] [jsc] Remote components challenge solver script (deno) and NPM package (deno) were skipped. These may be required to solve JS challenges. You can enable these downloads with --remote-components ejs:github (recommended) or --remote-components ejs:npm , respectively. For more information and alternatives, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS WARNING: [youtube] fV4s5dwxYnw: n challenge solving failed: Some formats may be missing. Ensure you have a supported JavaScript runtime and challenge solver script distribution installed. Review any warnings presented before this message. For more details, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS [info] fV4s5dwxYnw: Downloading subtitles: en WARNING: No subtitle format found matching "txt" for language en, using vtt. Use --list-subs for a list of available subtitles [info] fV4s5dwxYnw: Downloading 1 format(s): 139 [info] Writing video subtitles to: The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt [download] Destination: The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt [download] 1.00KiB at Unknown B/s (00:00:00) [download] 3.00KiB at Unknown B/s (00:00:00) [download] 7.00KiB at Unknown B/s (00:00:00) [download] 15.00KiB at 5.27MiB/s (00:00:00) [download] 31.00KiB at 1.64MiB/s (00:00:00) [download] 63.00KiB at 2.31MiB/s (00:00:00) [download] 84.16KiB at 2.57MiB/s (00:00:00) [download] 100% of 84.16KiB in 00:00:00 at 613.43KiB/s Exit code: 0

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="1" end_line="453" total_lines="1984"> 1|WEBVTT 2|Kind: captions 3|Language: en 4| 5|00:00:00.080 --> 00:00:01.750 align:start position:0% 6| 7|One<00:00:00.240><c> of</c><00:00:00.400><c> these</c><00:00:00.560><c> was</c><00:00:00.719><c> a</c><00:00:00.880><c> waste</c><00:00:01.120><c> of</c><00:00:01.280><c> money.</c><00:00:01.520><c> One</c> 8| 9|00:00:01.750 --> 00:00:01.760 align:start position:0% 10|One of these was a waste of money. One 11| 12| 13|00:00:01.760 --> 00:00:03.590 align:start position:0% 14|One of these was a waste of money. One 15|actually<00:00:02.000><c> changed</c><00:00:02.320><c> how</c><00:00:02.480><c> I</c><00:00:02.639><c> play.</c><00:00:02.960><c> And</c><00:00:03.120><c> one</c><00:00:03.360><c> I'm</c> 16| 17|00:00:03.590 --> 00:00:03.600 align:start position:0% 18|actually changed how I play. And one I'm 19| 20| 21|00:00:03.600 --> 00:00:05.030 align:start position:0% 22|actually changed how I play. And one I'm 23|still<00:00:03.840><c> trying</c><00:00:04.000><c> to</c><00:00:04.160><c> figure</c><00:00:04.319><c> out.</c><00:00:04.720><c> I</c><00:00:04.880><c> spent</c> 24| 25|00:00:05.030 --> 00:00:05.040 align:start position:0% 26|still trying to figure out. I spent 27| 28| 29|00:00:05.040 --> 00:00:06.950 align:start position:0% 30|still trying to figure out. I spent 31|thousands<00:00:05.440><c> on</c><00:00:05.600><c> gear</c><00:00:05.759><c> I</c><00:00:06.000><c> didn't</c><00:00:06.240><c> need.</c><00:00:06.640><c> Build</c> 32| 33|00:00:06.950 --> 00:00:06.960 align:start position:0% 34|thousands on gear I didn't need. Build 35| 36| 37|00:00:06.960 --> 00:00:08.470 align:start position:0% 38|thousands on gear I didn't need. Build 39|four<00:00:07.279><c> gaming</c><00:00:07.600><c> setups</c><00:00:07.860><c> [music]</c><00:00:08.000><c> from</c><00:00:08.160><c> all</c><00:00:08.320><c> the</c> 40| 41|00:00:08.470 --> 00:00:08.480 align:start position:0% 42|four gaming setups [music] from all the 43| 44| 45|00:00:08.480 --> 00:00:10.310 align:start position:0% 46|four gaming setups [music] from all the 47|stuff<00:00:08.639><c> I</c><00:00:08.800><c> bought.</c><00:00:09.120><c> And</c><00:00:09.200><c> after</c><00:00:09.519><c> 8,000</c><00:00:10.000><c> hours</c> 48| 49|00:00:10.310 --> 00:00:10.320 align:start position:0% 50|stuff I bought. And after 8,000 hours 51| 52| 53|00:00:10.320 --> 00:00:12.230 align:start position:0% 54|stuff I bought. And after 8,000 hours 55|just<00:00:10.480><c> in</c><00:00:10.639><c> tactical</c><00:00:11.120><c> shooters,</c><00:00:11.599><c> I</c><00:00:11.840><c> finally</c> 56| 57|00:00:12.230 --> 00:00:12.240 align:start position:0% 58|just in tactical shooters, I finally 59| 60| 61|00:00:12.240 --> 00:00:14.310 align:start position:0% 62|just in tactical shooters, I finally 63|figured<00:00:12.559><c> out</c><00:00:12.800><c> a</c><00:00:13.040><c> pattern.</c><00:00:13.519><c> Some</c><00:00:13.759><c> upgrades</c> 64| 65|00:00:14.310 --> 00:00:14.320 align:start position:0% 66|figured out a pattern. Some upgrades 67| 68| 69|00:00:14.320 --> 00:00:16.470 align:start position:0% 70|figured out a pattern. Some upgrades 71|help,<00:00:14.719><c> most</c><00:00:15.200><c> don't.</c><00:00:15.599><c> And</c><00:00:15.759><c> the</c><00:00:15.920><c> price</c><00:00:16.160><c> doesn't</c> 72| 73|00:00:16.470 --> 00:00:16.480 align:start position:0% 74|help, most don't. And the price doesn't 75| 76| 77|00:00:16.480 --> 00:00:18.070 align:start position:0% 78|help, most don't. And the price doesn't 79|tell<00:00:16.560><c> you</c><00:00:16.720><c> which</c><00:00:16.960><c> is</c><00:00:17.119><c> which.</c><00:00:17.520><c> By</c><00:00:17.760><c> the</c><00:00:17.840><c> end</c><00:00:18.000><c> of</c> 80| 81|00:00:18.070 --> 00:00:18.080 align:start position:0% 82|tell you which is which. By the end of 83| 84| 85|00:00:18.080 --> 00:00:19.670 align:start position:0% 86|tell you which is which. By the end of 87|this<00:00:18.240><c> video,</c><00:00:18.560><c> you'll</c><00:00:18.800><c> know</c><00:00:18.960><c> exactly</c><00:00:19.279><c> where</c><00:00:19.520><c> to</c> 88| 89|00:00:19.670 --> 00:00:19.680 align:start position:0% 90|this video, you'll know exactly where to 91| 92| 93|00:00:19.680 --> 00:00:21.269 align:start position:0% 94|this video, you'll know exactly where to 95|spend<00:00:19.920><c> and</c><00:00:20.160><c> where</c><00:00:20.320><c> to</c><00:00:20.480><c> save.</c><00:00:20.720><c> I</c><00:00:20.880><c> use</c><00:00:21.119><c> three</c> 96| 97|00:00:21.269 --> 00:00:21.279 align:start position:0% 98|spend and where to save. I use three 99| 100| 101|00:00:21.279 --> 00:00:22.870 align:start position:0% 102|spend and where to save. I use three 103|questions<00:00:21.600><c> now</c><00:00:21.840><c> before</c><00:00:22.080><c> any</c><00:00:22.320><c> purchase,</c><00:00:22.720><c> and</c> 104| 105|00:00:22.870 --> 00:00:22.880 align:start position:0% 106|questions now before any purchase, and 107| 108| 109|00:00:22.880 --> 00:00:24.710 align:start position:0% 110|questions now before any purchase, and 111|I'll<00:00:23.119><c> walk</c><00:00:23.359><c> you</c><00:00:23.519><c> through</c><00:00:23.760><c> each</c><00:00:24.000><c> one</c><00:00:24.400><c> and</c><00:00:24.560><c> show</c> 112| 113|00:00:24.710 --> 00:00:24.720 align:start position:0% 114|I'll walk you through each one and show 115| 116| 117|00:00:24.720 --> 00:00:26.470 align:start position:0% 118|I'll walk you through each one and show 119|you<00:00:24.960><c> how</c><00:00:25.199><c> they</c><00:00:25.359><c> apply</c><00:00:25.600><c> to</c><00:00:25.760><c> real</c><00:00:26.080><c> gear.</c> 120| 121|00:00:26.470 --> 00:00:26.480 align:start position:0% 122|you how they apply to real gear. 123| 124| 125|00:00:26.480 --> 00:00:28.070 align:start position:0% 126|you how they apply to real gear. 127|Starting<00:00:26.800><c> with</c><00:00:26.960><c> a</c><00:00:27.199><c> question</c><00:00:27.439><c> that</c><00:00:27.760><c> would</c><00:00:27.920><c> have</c> 128| 129|00:00:28.070 --> 00:00:28.080 align:start position:0% 130|Starting with a question that would have 131| 132| 133|00:00:28.080 --> 00:00:29.750 align:start position:0% 134|Starting with a question that would have 135|saved<00:00:28.320><c> me</c><00:00:28.480><c> the</c><00:00:28.720><c> most</c><00:00:28.960><c> money.</c><00:00:29.279><c> First</c><00:00:29.519><c> question</c> 136| 137|00:00:29.750 --> 00:00:29.760 align:start position:0% 138|saved me the most money. First question 139| 140| 141|00:00:29.760 --> 00:00:31.669 align:start position:0% 142|saved me the most money. First question 143|I<00:00:29.920><c> ask</c><00:00:30.160><c> before</c><00:00:30.400><c> any</c><00:00:30.720><c> purchase</c><00:00:31.119><c> is</c><00:00:31.519><c> this</c> 144| 145|00:00:31.669 --> 00:00:31.679 align:start position:0% 146|I ask before any purchase is this 147| 148| 149|00:00:31.679 --> 00:00:33.350 align:start position:0% 150|I ask before any purchase is this 151|solving<00:00:32.000><c> a</c><00:00:32.160><c> real</c><00:00:32.399><c> problem</c><00:00:32.800><c> or</c><00:00:33.040><c> just</c><00:00:33.200><c> a</c> 152| 153|00:00:33.350 --> 00:00:33.360 align:start position:0% 154|solving a real problem or just a 155| 156| 157|00:00:33.360 --> 00:00:35.030 align:start position:0% 158|solving a real problem or just a 159|feeling?<00:00:33.680><c> Now,</c><00:00:33.920><c> a</c><00:00:34.079><c> real</c><00:00:34.320><c> problem</c><00:00:34.640><c> means</c> 160| 161|00:00:35.030 --> 00:00:35.040 align:start position:0% 162|feeling? Now, a real problem means 163| 164| 165|00:00:35.040 --> 00:00:37.110 align:start position:0% 166|feeling? Now, a real problem means 167|something<00:00:35.440><c> specific</c><00:00:35.920><c> is</c><00:00:36.160><c> broken.</c><00:00:36.640><c> Your</c><00:00:36.800><c> mouse</c> 168| 169|00:00:37.110 --> 00:00:37.120 align:start position:0% 170|something specific is broken. Your mouse 171| 172| 173|00:00:37.120 --> 00:00:38.630 align:start position:0% 174|something specific is broken. Your mouse 175|literally<00:00:37.520><c> skips</c><00:00:37.760><c> on</c><00:00:37.920><c> your</c><00:00:38.079><c> path.</c><00:00:38.480><c> Your</c> 176| 177|00:00:38.630 --> 00:00:38.640 align:start position:0% 178|literally skips on your path. Your 179| 180| 181|00:00:38.640 --> 00:00:40.470 align:start position:0% 182|literally skips on your path. Your 183|current<00:00:38.960><c> ship</c><00:00:39.280><c> gives</c><00:00:39.520><c> you</c><00:00:39.680><c> hand</c><00:00:39.920><c> cramps</c><00:00:40.239><c> after</c> 184| 185|00:00:40.470 --> 00:00:40.480 align:start position:0% 186|current ship gives you hand cramps after 187| 188| 189|00:00:40.480 --> 00:00:42.389 align:start position:0% 190|current ship gives you hand cramps after 191|an<00:00:40.640><c> hour.</c><00:00:41.040><c> You</c><00:00:41.280><c> can't</c><00:00:41.440><c> hear</c><00:00:41.680><c> footsteps</c><00:00:42.160><c> that</c> 192| 193|00:00:42.389 --> 00:00:42.399 align:start position:0% 194|an hour. You can't hear footsteps that 195| 196| 197|00:00:42.399 --> 00:00:44.869 align:start position:0% 198|an hour. You can't hear footsteps that 199|other<00:00:42.719><c> players</c><00:00:43.280><c> clearly</c><00:00:44.000><c> react</c><00:00:44.320><c> to.</c><00:00:44.640><c> No,</c> 200| 201|00:00:44.869 --> 00:00:44.879 align:start position:0% 202|other players clearly react to. No, 203| 204| 205|00:00:44.879 --> 00:00:46.950 align:start position:0% 206|other players clearly react to. No, 207|these<00:00:45.120><c> are</c><00:00:45.280><c> real.</c><00:00:45.760><c> You</c><00:00:46.000><c> can</c><00:00:46.160><c> point</c><00:00:46.399><c> at</c><00:00:46.559><c> them.</c> 208| 209|00:00:46.950 --> 00:00:46.960 align:start position:0% 210|these are real. You can point at them. 211| 212| 213|00:00:46.960 --> 00:00:48.310 align:start position:0% 214|these are real. You can point at them. 215|The<00:00:47.039><c> feeling</c><00:00:47.280><c> is</c><00:00:47.440><c> different.</c><00:00:47.760><c> You</c><00:00:47.920><c> watch</c><00:00:48.079><c> a</c> 216| 217|00:00:48.310 --> 00:00:48.320 align:start position:0% 218|The feeling is different. You watch a 219| 220| 221|00:00:48.320 --> 00:00:50.229 align:start position:0% 222|The feeling is different. You watch a 223|review<00:00:48.719><c> approach</c><00:00:49.120><c> switch</c><00:00:49.440><c> to</c><00:00:49.680><c> something</c><00:00:49.920><c> new.</c> 224| 225|00:00:50.229 --> 00:00:50.239 align:start position:0% 226|review approach switch to something new. 227| 228| 229|00:00:50.239 --> 00:00:52.310 align:start position:0% 230|review approach switch to something new. 231|Maybe<00:00:50.399><c> you</c><00:00:50.559><c> saw</c><00:00:50.800><c> Tan</c><00:00:51.120><c> or</c><00:00:51.360><c> Don</c><00:00:51.760><c> getting</c><00:00:52.000><c> a</c><00:00:52.160><c> new</c> 232| 233|00:00:52.310 --> 00:00:52.320 align:start position:0% 234|Maybe you saw Tan or Don getting a new 235| 236| 237|00:00:52.320 --> 00:00:54.069 align:start position:0% 238|Maybe you saw Tan or Don getting a new 239|mouse<00:00:52.559><c> and</c><00:00:52.800><c> said</c><00:00:52.960><c> to</c><00:00:53.120><c> yourself</c><00:00:53.440><c> that</c><00:00:53.680><c> you</c><00:00:53.920><c> need</c> 240| 241|00:00:54.069 --> 00:00:54.079 align:start position:0% 242|mouse and said to yourself that you need 243| 244| 245|00:00:54.079 --> 00:00:55.830 align:start position:0% 246|mouse and said to yourself that you need 247|this.<00:00:54.399><c> You</c><00:00:54.559><c> look</c><00:00:54.640><c> at</c><00:00:54.800><c> your</c><00:00:55.039><c> setup.</c><00:00:55.440><c> It</c><00:00:55.600><c> looks</c> 248| 249|00:00:55.830 --> 00:00:55.840 align:start position:0% 250|this. You look at your setup. It looks 251| 252| 253|00:00:55.840 --> 00:00:57.670 align:start position:0% 254|this. You look at your setup. It looks 255|outdated.<00:00:56.480><c> Nothing</c><00:00:56.800><c> is</c><00:00:57.039><c> actually</c><00:00:57.360><c> wrong</c> 256| 257|00:00:57.670 --> 00:00:57.680 align:start position:0% 258|outdated. Nothing is actually wrong 259| 260| 261|00:00:57.680 --> 00:00:59.110 align:start position:0% 262|outdated. Nothing is actually wrong 263|though.<00:00:58.000><c> you</c><00:00:58.160><c> just</c><00:00:58.320><c> feel</c><00:00:58.480><c> like</c><00:00:58.640><c> you</c><00:00:58.800><c> need</c><00:00:58.879><c> an</c> 264| 265|00:00:59.110 --> 00:00:59.120 align:start position:0% 266|though. you just feel like you need an 267| 268| 269|00:00:59.120 --> 00:01:01.029 align:start position:0% 270|though. you just feel like you need an 271|upgrade.<00:00:59.600><c> So,</c><00:00:59.840><c> here</c><00:01:00.000><c> is</c><00:01:00.079><c> a</c><00:01:00.239><c> fast</c><00:01:00.480><c> test.</c><00:01:00.879><c> Can</c> 272| 273|00:01:01.029 --> 00:01:01.039 align:start position:0% 274|upgrade. So, here is a fast test. Can 275| 276| 277|00:01:01.039 --> 00:01:02.950 align:start position:0% 278|upgrade. So, here is a fast test. Can 279|you<00:01:01.199><c> describe</c><00:01:01.600><c> the</c><00:01:01.840><c> problem</c><00:01:02.079><c> in</c><00:01:02.320><c> one</c><00:01:02.559><c> sentence</c> 280| 281|00:01:02.950 --> 00:01:02.960 align:start position:0% 282|you describe the problem in one sentence 283| 284| 285|00:01:02.960 --> 00:01:05.350 align:start position:0% 286|you describe the problem in one sentence 287|without<00:01:03.440><c> using</c><00:01:03.760><c> the</c><00:01:04.000><c> word</c><00:01:04.400><c> better?</c><00:01:05.040><c> Now,</c><00:01:05.199><c> my</c> 288| 289|00:01:05.350 --> 00:01:05.360 align:start position:0% 290|without using the word better? Now, my 291| 292| 293|00:01:05.360 --> 00:01:07.510 align:start position:0% 294|without using the word better? Now, my 295|mouse<00:01:05.680><c> shape</c><00:01:05.920><c> cramps</c><00:01:06.320><c> my</c><00:01:06.560><c> hand</c><00:01:06.880><c> after</c><00:01:07.200><c> long</c> 296| 297|00:01:07.510 --> 00:01:07.520 align:start position:0% 298|mouse shape cramps my hand after long 299| 300| 301|00:01:07.520 --> 00:01:09.510 align:start position:0% 302|mouse shape cramps my hand after long 303|sessions.<00:01:08.000><c> That's</c><00:01:08.400><c> real.</c><00:01:08.799><c> I</c><00:01:08.960><c> want</c><00:01:09.119><c> a</c><00:01:09.280><c> mouse</c> 304| 305|00:01:09.510 --> 00:01:09.520 align:start position:0% 306|sessions. That's real. I want a mouse 307| 308| 309|00:01:09.520 --> 00:01:11.109 align:start position:0% 310|sessions. That's real. I want a mouse 311|that<00:01:09.680><c> feels</c><00:01:10.000><c> better.</c><00:01:10.400><c> That's</c><00:01:10.560><c> just</c><00:01:10.720><c> like</c><00:01:10.880><c> a</c> 312| 313|00:01:11.109 --> 00:01:11.119 align:start position:0% 314|that feels better. That's just like a 315| 316| 317|00:01:11.119 --> 00:01:12.870 align:start position:0% 318|that feels better. That's just like a 319|feeling.<00:01:11.520><c> Now,</c><00:01:11.760><c> feelings</c><00:01:12.080><c> aren't</c><00:01:12.400><c> wrong.</c><00:01:12.720><c> You</c> 320| 321|00:01:12.870 --> 00:01:12.880 align:start position:0% 322|feeling. Now, feelings aren't wrong. You 323| 324| 325|00:01:12.880 --> 00:01:14.310 align:start position:0% 326|feeling. Now, feelings aren't wrong. You 327|can<00:01:13.040><c> buy</c><00:01:13.200><c> stuff</c><00:01:13.439><c> because</c><00:01:13.680><c> you</c><00:01:13.920><c> just</c><00:01:14.080><c> simply</c> 328| 329|00:01:14.310 --> 00:01:14.320 align:start position:0% 330|can buy stuff because you just simply 331| 332| 333|00:01:14.320 --> 00:01:16.149 align:start position:0% 334|can buy stuff because you just simply 335|want<00:01:14.479><c> it.</c><00:01:14.799><c> But</c><00:01:14.880><c> don't</c><00:01:15.200><c> expect</c><00:01:15.520><c> it</c><00:01:15.680><c> to</c><00:01:15.920><c> change</c> 336| 337|00:01:16.149 --> 00:01:16.159 align:start position:0% 338|want it. But don't expect it to change 339| 340| 341|00:01:16.159 --> 00:01:18.070 align:start position:0% 342|want it. But don't expect it to change 343|your<00:01:16.400><c> gameplay.</c><00:01:17.040><c> Real</c><00:01:17.360><c> problems</c><00:01:17.759><c> affect</c> 344| 345|00:01:18.070 --> 00:01:18.080 align:start position:0% 346|your gameplay. Real problems affect 347| 348| 349|00:01:18.080 --> 00:01:19.749 align:start position:0% 350|your gameplay. Real problems affect 351|performance.<00:01:18.720><c> Feelings</c><00:01:19.119><c> just</c><00:01:19.280><c> affect</c><00:01:19.600><c> your</c> 352| 353|00:01:19.749 --> 00:01:19.759 align:start position:0% 354|performance. Feelings just affect your 355| 356| 357|00:01:19.759 --> 00:01:21.429 align:start position:0% 358|performance. Feelings just affect your 359|wallet.<00:01:20.240><c> Now,</c><00:01:20.479><c> even</c><00:01:20.640><c> when</c><00:01:20.799><c> I</c><00:01:20.960><c> had</c><00:01:21.200><c> real</c> 360| 361|00:01:21.429 --> 00:01:21.439 align:start position:0% 362|wallet. Now, even when I had real 363| 364| 365|00:01:21.439 --> 00:01:23.510 align:start position:0% 366|wallet. Now, even when I had real 367|problems,<00:01:21.920><c> I</c><00:01:22.080><c> still</c><00:01:22.240><c> wasted</c><00:01:22.560><c> a</c><00:01:22.799><c> lot</c><00:01:22.880><c> of</c><00:01:23.040><c> money.</c> 368| 369|00:01:23.510 --> 00:01:23.520 align:start position:0% 370|problems, I still wasted a lot of money. 371| 372| 373|00:01:23.520 --> 00:01:25.510 align:start position:0% 374|problems, I still wasted a lot of money. 375|The<00:01:23.759><c> problem</c><00:01:24.000><c> was</c><00:01:24.320><c> real.</c><00:01:24.640><c> I</c><00:01:24.880><c> just</c><00:01:25.040><c> paid</c><00:01:25.280><c> way</c> 376| 377|00:01:25.510 --> 00:01:25.520 align:start position:0% 378|The problem was real. I just paid way 379| 380| 381|00:01:25.520 --> 00:01:27.270 align:start position:0% 382|The problem was real. I just paid way 383|more<00:01:25.759><c> than</c><00:01:25.920><c> I</c><00:01:26.080><c> needed</c><00:01:26.320><c> to.</c><00:01:26.479><c> And</c><00:01:26.720><c> that</c><00:01:26.880><c> gets</c><00:01:27.119><c> us</c> 384| 385|00:01:27.270 --> 00:01:27.280 align:start position:0% 386|more than I needed to. And that gets us 387| 388| 389|00:01:27.280 --> 00:01:28.630 align:start position:0% 390|more than I needed to. And that gets us 391|to<00:01:27.520><c> question</c><00:01:27.840><c> number</c><00:01:28.000><c> two.</c><00:01:28.320><c> What's</c><00:01:28.479><c> the</c> 392| 393|00:01:28.630 --> 00:01:28.640 align:start position:0% 394|to question number two. What's the 395| 396| 397|00:01:28.640 --> 00:01:30.390 align:start position:0% 398|to question number two. What's the 399|actual<00:01:28.880><c> gap</c><00:01:29.119><c> between</c><00:01:29.439><c> what</c><00:01:29.600><c> I</c><00:01:29.840><c> have</c><00:01:30.000><c> and</c><00:01:30.240><c> what</c> 400| 401|00:01:30.390 --> 00:01:30.400 align:start position:0% 402|actual gap between what I have and what 403| 404| 405|00:01:30.400 --> 00:01:32.310 align:start position:0% 406|actual gap between what I have and what 407|I'm<00:01:30.640><c> buying?</c><00:01:31.040><c> Not</c><00:01:31.200><c> the</c><00:01:31.360><c> gap</c><00:01:31.520><c> you</c><00:01:31.759><c> imagine,</c><00:01:32.159><c> the</c> 408| 409|00:01:32.310 --> 00:01:32.320 align:start position:0% 410|I'm buying? Not the gap you imagine, the 411| 412| 413|00:01:32.320 --> 00:01:34.550 align:start position:0% 414|I'm buying? Not the gap you imagine, the 415|gap<00:01:32.560><c> you</c><00:01:32.799><c> can</c><00:01:32.880><c> measure.</c><00:01:33.360><c> Now</c><00:01:33.600><c> GPU</c><00:01:34.079><c> first</c><00:01:34.320><c> since</c> 416| 417|00:01:34.550 --> 00:01:34.560 align:start position:0% 418|gap you can measure. Now GPU first since 419| 420| 421|00:01:34.560 --> 00:01:36.149 align:start position:0% 422|gap you can measure. Now GPU first since 423|that's<00:01:34.799><c> the</c><00:01:34.960><c> bigger</c><00:01:35.200><c> purchase</c><00:01:35.600><c> most</c><00:01:35.920><c> people</c> 424| 425|00:01:36.149 --> 00:01:36.159 align:start position:0% 426|that's the bigger purchase most people 427| 428| 429|00:01:36.159 --> 00:01:37.749 align:start position:0% 430|that's the bigger purchase most people 431|consider<00:01:36.479><c> when</c><00:01:36.799><c> trying</c><00:01:36.960><c> to</c><00:01:37.200><c> upgrade</c><00:01:37.520><c> their</c> 432| 433|00:01:37.749 --> 00:01:37.759 align:start position:0% 434|consider when trying to upgrade their 435| 436| 437|00:01:37.759 --> 00:01:40.469 align:start position:0% 438|consider when trying to upgrade their 439|gear.<00:01:38.079><c> Let's</c><00:01:38.320><c> say</c><00:01:38.479><c> an</c><00:01:38.799><c> RTX</c><00:01:39.360><c> 5090</c><00:01:40.000><c> versus</c><00:01:40.320><c> an</c> 440| 441|00:01:40.469 --> 00:01:40.479 align:start position:0% 442|gear. Let's say an RTX 5090 versus an 443| 444| 445|00:01:40.479 --> 00:01:43.109 align:start position:0% 446|gear. Let's say an RTX 5090 versus an 447|RTX<00:01:41.040><c> 4070.</c><00:01:41.759><c> Now</c><00:01:41.920><c> let's</c><00:01:42.159><c> look</c><00:01:42.240><c> at</c><00:01:42.400><c> Valerant</c><00:01:42.960><c> at</c> 448| 449|00:01:43.109 --> 00:01:43.119 align:start position:0% 450|RTX 4070. Now let's look at Valerant at 451| 452| 453|00:01:43.119 --> 00:01:45.270 align:start position:0% </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="453" end_line="652" total_lines="1984"> 453|00:01:43.119 --> 00:01:45.270 align:start position:0% 454|RTX 4070. Now let's look at Valerant at 455|1080p<00:01:43.491><c> [music]</c><00:01:43.759><c> low</c><00:01:44.000><c> settings.</c><00:01:44.560><c> Both</c><00:01:44.880><c> cards</c> 456| 457|00:01:45.270 --> 00:01:45.280 align:start position:0% 458|1080p [music] low settings. Both cards 459| 460| 461|00:01:45.280 --> 00:01:47.910 align:start position:0% 462|1080p [music] low settings. Both cards 463|push<00:01:45.600><c> over</c><00:01:45.920><c> 400</c><00:01:46.399><c> FPS</c><00:01:46.799><c> stable.</c><00:01:47.280><c> Your</c><00:01:47.520><c> monitor</c> 464| 465|00:01:47.910 --> 00:01:47.920 align:start position:0% 466|push over 400 FPS stable. Your monitor 467| 468| 469|00:01:47.920 --> 00:01:50.310 align:start position:0% 470|push over 400 FPS stable. Your monitor 471|caps<00:01:48.159><c> at</c><00:01:48.560><c> 40,</c><00:01:48.880><c> maybe</c><00:01:49.119><c> 360</c><00:01:49.680><c> if</c><00:01:49.920><c> you</c><00:01:50.079><c> went</c> 472| 473|00:01:50.310 --> 00:01:50.320 align:start position:0% 474|caps at 40, maybe 360 if you went 475| 476| 477|00:01:50.320 --> 00:01:52.149 align:start position:0% 478|caps at 40, maybe 360 if you went 479|high-end.<00:01:51.040><c> Now</c><00:01:51.200><c> you're</c><00:01:51.439><c> going</c><00:01:51.520><c> to</c><00:01:51.600><c> pay</c><00:01:51.920><c> three</c> 480| 481|00:01:52.149 --> 00:01:52.159 align:start position:0% 482|high-end. Now you're going to pay three 483| 484| 485|00:01:52.159 --> 00:01:53.830 align:start position:0% 486|high-end. Now you're going to pay three 487|times<00:01:52.479><c> more</c><00:01:52.640><c> for</c><00:01:52.880><c> frames</c><00:01:53.280><c> you</c><00:01:53.439><c> literally</c> 488| 489|00:01:53.830 --> 00:01:53.840 align:start position:0% 490|times more for frames you literally 491| 492| 493|00:01:53.840 --> 00:01:55.749 align:start position:0% 494|times more for frames you literally 495|cannot<00:01:54.079><c> see.</c><00:01:54.320><c> The</c><00:01:54.560><c> performance</c><00:01:55.040><c> gap</c><00:01:55.360><c> exists</c> 496| 497|00:01:55.749 --> 00:01:55.759 align:start position:0% 498|cannot see. The performance gap exists 499| 500| 501|00:01:55.759 --> 00:01:58.630 align:start position:0% 502|cannot see. The performance gap exists 503|on<00:01:55.920><c> paper.</c><00:01:56.399><c> The</c><00:01:56.560><c> usage</c><00:01:57.280><c> gap</c><00:01:57.600><c> is</c><00:01:57.840><c> simply</c><00:01:58.159><c> zero.</c> 504| 505|00:01:58.630 --> 00:01:58.640 align:start position:0% 506|on paper. The usage gap is simply zero. 507| 508| 509|00:01:58.640 --> 00:02:01.030 align:start position:0% 510|on paper. The usage gap is simply zero. 511|Now<00:01:58.880><c> look</c><00:01:59.040><c> at</c><00:01:59.200><c> where</c><00:01:59.520><c> GPU</c><00:02:00.079><c> actually</c><00:02:00.479><c> matters.</c> 512| 513|00:02:01.030 --> 00:02:01.040 align:start position:0% 514|Now look at where GPU actually matters. 515| 516| 517|00:02:01.040 --> 00:02:03.190 align:start position:0% 518|Now look at where GPU actually matters. 519|The<00:02:01.280><c> 5090</c><00:02:01.920><c> handles</c><00:02:02.320><c> encoding</c><00:02:02.880><c> without</c> 520| 521|00:02:03.190 --> 00:02:03.200 align:start position:0% 522|The 5090 handles encoding without 523| 524| 525|00:02:03.200 --> 00:02:05.190 align:start position:0% 526|The 5090 handles encoding without 527|dropping<00:02:03.600><c> frames,</c><00:02:04.000><c> while</c><00:02:04.159><c> the</c><00:02:04.399><c> 4070</c> 528| 529|00:02:05.190 --> 00:02:05.200 align:start position:0% 530|dropping frames, while the 4070 531| 532| 533|00:02:05.200 --> 00:02:07.109 align:start position:0% 534|dropping frames, while the 4070 535|struggles.<00:02:05.920><c> That's</c><00:02:06.159><c> a</c><00:02:06.320><c> real</c><00:02:06.560><c> gap</c><00:02:06.880><c> for</c> 536| 537|00:02:07.109 --> 00:02:07.119 align:start position:0% 538|struggles. That's a real gap for 539| 540| 541|00:02:07.119 --> 00:02:08.949 align:start position:0% 542|struggles. That's a real gap for 543|specific<00:02:07.520><c> use</c><00:02:07.759><c> case.</c><00:02:08.160><c> If</c><00:02:08.319><c> you</c><00:02:08.479><c> stream,</c><00:02:08.800><c> play</c> 544| 545|00:02:08.949 --> 00:02:08.959 align:start position:0% 546|specific use case. If you stream, play 547| 548| 549|00:02:08.959 --> 00:02:10.469 align:start position:0% 550|specific use case. If you stream, play 551|single<00:02:09.280><c> player</c><00:02:09.520><c> games</c><00:02:09.759><c> at</c><00:02:09.920><c> like</c><00:02:10.080><c> 4K</c> 552| 553|00:02:10.469 --> 00:02:10.479 align:start position:0% 554|single player games at like 4K 555| 556| 557|00:02:10.479 --> 00:02:12.790 align:start position:0% 558|single player games at like 4K 559|resolution<00:02:11.039><c> or</c><00:02:11.280><c> any</c><00:02:11.599><c> task</c><00:02:12.000><c> demanding</c><00:02:12.560><c> a</c> 560| 561|00:02:12.790 --> 00:02:12.800 align:start position:0% 562|resolution or any task demanding a 563| 564| 565|00:02:12.800 --> 00:02:14.869 align:start position:0% 566|resolution or any task demanding a 567|really<00:02:13.040><c> good</c><00:02:13.200><c> GPU.</c><00:02:13.760><c> The</c><00:02:14.000><c> price</c><00:02:14.239><c> makes</c><00:02:14.400><c> sense.</c> 568| 569|00:02:14.869 --> 00:02:14.879 align:start position:0% 570|really good GPU. The price makes sense. 571| 572| 573|00:02:14.879 --> 00:02:16.470 align:start position:0% 574|really good GPU. The price makes sense. 575|If<00:02:14.959><c> you</c><00:02:15.120><c> don't,</c><00:02:15.360><c> you're</c><00:02:15.680><c> buying</c><00:02:15.920><c> headroom</c> 576| 577|00:02:16.470 --> 00:02:16.480 align:start position:0% 578|If you don't, you're buying headroom 579| 580| 581|00:02:16.480 --> 00:02:18.390 align:start position:0% 582|If you don't, you're buying headroom 583|you'll<00:02:16.720><c> never</c><00:02:16.879><c> use.</c><00:02:17.280><c> No</c><00:02:17.520><c> monitors</c><00:02:18.000><c> tell</c><00:02:18.160><c> a</c> 584| 585|00:02:18.390 --> 00:02:18.400 align:start position:0% 586|you'll never use. No monitors tell a 587| 588| 589|00:02:18.400 --> 00:02:20.070 align:start position:0% 590|you'll never use. No monitors tell a 591|similar<00:02:18.720><c> story.</c><00:02:19.040><c> I</c><00:02:19.200><c> look</c><00:02:19.360><c> at</c><00:02:19.520><c> response</c><00:02:19.840><c> data</c> 592| 593|00:02:20.070 --> 00:02:20.080 align:start position:0% 594|similar story. I look at response data 595| 596| 597|00:02:20.080 --> 00:02:21.750 align:start position:0% 598|similar story. I look at response data 599|from<00:02:20.319><c> hardware</c><00:02:20.720><c> run</c><00:02:20.959><c> box</c><00:02:21.120><c> and</c><00:02:21.280><c> also</c><00:02:21.599><c> our</c> 600| 601|00:02:21.750 --> 00:02:21.760 align:start position:0% 602|from hardware run box and also our 603| 604| 605|00:02:21.760 --> 00:02:23.750 align:start position:0% 606|from hardware run box and also our 607|things<00:02:22.080><c> across</c><00:02:22.560><c> 30</c><00:02:22.879><c> panels</c><00:02:23.200><c> when</c><00:02:23.360><c> I</c><00:02:23.520><c> try</c><00:02:23.599><c> to</c> 608| 609|00:02:23.750 --> 00:02:23.760 align:start position:0% 610|things across 30 panels when I try to 611| 612| 613|00:02:23.760 --> 00:02:25.030 align:start position:0% 614|things across 30 panels when I try to 615|get<00:02:23.840><c> a</c><00:02:24.000><c> new</c><00:02:24.160><c> monitor.</c><00:02:24.640><c> The</c><00:02:24.800><c> difference</c> 616| 617|00:02:25.030 --> 00:02:25.040 align:start position:0% 618|get a new monitor. The difference 619| 620| 621|00:02:25.040 --> 00:02:27.750 align:start position:0% 622|get a new monitor. The difference 623|between<00:02:25.280><c> a</c><00:02:25.520><c> $300</c><00:02:26.160><c> IPS</c><00:02:26.640><c> gaming</c><00:02:27.040><c> monitor</c><00:02:27.360><c> and</c><00:02:27.520><c> a</c> 624| 625|00:02:27.750 --> 00:02:27.760 align:start position:0% 626|between a $300 IPS gaming monitor and a 627| 628| 629|00:02:27.760 --> 00:02:30.070 align:start position:0% 630|between a $300 IPS gaming monitor and a 631|$600<00:02:28.400><c> one,</c><00:02:28.640><c> it's</c><00:02:28.879><c> around</c><00:02:29.200><c> half</c><00:02:29.360><c> a</c><00:02:29.599><c> millisecond</c> 632| 633|00:02:30.070 --> 00:02:30.080 align:start position:0% 634|$600 one, it's around half a millisecond 635| 636| 637|00:02:30.080 --> 00:02:31.670 align:start position:0% 638|$600 one, it's around half a millisecond 639|in<00:02:30.319><c> response</c><00:02:30.640><c> time.</c><00:02:30.959><c> Meanwhile,</c><00:02:31.280><c> the</c><00:02:31.520><c> jump</c> 640| 641|00:02:31.670 --> 00:02:31.680 align:start position:0% 642|in response time. Meanwhile, the jump 643| 644| 645|00:02:31.680 --> 00:02:34.470 align:start position:0% 646|in response time. Meanwhile, the jump 647|from<00:02:31.840><c> a</c><00:02:32.080><c> 60</c><00:02:32.239><c> Hz</c><00:02:32.560><c> office</c><00:02:32.879><c> monitor</c><00:02:33.200><c> to</c><00:02:33.440><c> that</c><00:02:33.760><c> $300</c> 648| 649|00:02:34.470 --> 00:02:34.480 align:start position:0% 650|from a 60 Hz office monitor to that $300 651| </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="652" end_line="851" total_lines="1984"> 652| 653|00:02:34.480 --> 00:02:36.470 align:start position:0% 654|from a 60 Hz office monitor to that $300 655|gaming<00:02:34.879><c> monitor</c><00:02:35.280><c> is</c><00:02:35.599><c> like</c><00:02:35.840><c> 8</c><00:02:36.080><c> to</c><00:02:36.239><c> 10</c> 656| 657|00:02:36.470 --> 00:02:36.480 align:start position:0% 658|gaming monitor is like 8 to 10 659| 660| 661|00:02:36.480 --> 00:02:38.229 align:start position:0% 662|gaming monitor is like 8 to 10 663|milliseconds<00:02:37.040><c> saved.</c><00:02:37.519><c> 20</c><00:02:37.760><c> times</c><00:02:38.000><c> more</c> 664| 665|00:02:38.229 --> 00:02:38.239 align:start position:0% 666|milliseconds saved. 20 times more 667| 668| 669|00:02:38.239 --> 00:02:40.070 align:start position:0% 670|milliseconds saved. 20 times more 671|improvement<00:02:38.800><c> for</c><00:02:39.120><c> half</c><00:02:39.280><c> the</c><00:02:39.519><c> price.</c><00:02:39.920><c> So,</c> 672| 673|00:02:40.070 --> 00:02:40.080 align:start position:0% 674|improvement for half the price. So, 675| 676| 677|00:02:40.080 --> 00:02:41.750 align:start position:0% 678|improvement for half the price. So, 679|there's<00:02:40.319><c> a</c><00:02:40.480><c> pattern</c><00:02:40.720><c> in</c><00:02:40.959><c> these</c><00:02:41.120><c> numbers.</c><00:02:41.519><c> I'll</c> 680| 681|00:02:41.750 --> 00:02:41.760 align:start position:0% 682|there's a pattern in these numbers. I'll 683| 684| 685|00:02:41.760 --> 00:02:43.350 align:start position:0% 686|there's a pattern in these numbers. I'll 687|show<00:02:41.920><c> you</c><00:02:42.080><c> exactly</c><00:02:42.400><c> what</c><00:02:42.560><c> it</c><00:02:42.800><c> is</c><00:02:42.959><c> when</c><00:02:43.120><c> we</c><00:02:43.280><c> get</c> 688| 689|00:02:43.350 --> 00:02:43.360 align:start position:0% 690|show you exactly what it is when we get 691| 692| 693|00:02:43.360 --> 00:02:45.110 align:start position:0% 694|show you exactly what it is when we get 695|to<00:02:43.519><c> the</c><00:02:43.680><c> real</c><00:02:43.920><c> gear</c><00:02:44.239><c> recommendation.</c><00:02:44.879><c> But</c> 696| 697|00:02:45.110 --> 00:02:45.120 align:start position:0% 698|to the real gear recommendation. But 699| 700| 701|00:02:45.120 --> 00:02:46.869 align:start position:0% 702|to the real gear recommendation. But 703|first,<00:02:45.440><c> there's</c><00:02:45.680><c> a</c><00:02:45.840><c> third</c><00:02:46.160><c> question.</c><00:02:46.640><c> Because</c> 704| 705|00:02:46.869 --> 00:02:46.879 align:start position:0% 706|first, there's a third question. Because 707| 708| 709|00:02:46.879 --> 00:02:48.790 align:start position:0% 710|first, there's a third question. Because 711|even<00:02:47.120><c> with</c><00:02:47.280><c> a</c><00:02:47.519><c> real</c><00:02:47.760><c> problem</c><00:02:48.000><c> and</c><00:02:48.239><c> on</c><00:02:48.400><c> a</c><00:02:48.560><c> real</c> 712| 713|00:02:48.790 --> 00:02:48.800 align:start position:0% 714|even with a real problem and on a real 715| 716| 717|00:02:48.800 --> 00:02:50.710 align:start position:0% 718|even with a real problem and on a real 719|gap,<00:02:49.120><c> I</c><00:02:49.280><c> still</c><00:02:49.440><c> wasted</c><00:02:49.840><c> money.</c><00:02:50.160><c> So,</c><00:02:50.400><c> here</c><00:02:50.640><c> is</c> 720| 721|00:02:50.710 --> 00:02:50.720 align:start position:0% 722|gap, I still wasted money. So, here is 723| 724| 725|00:02:50.720 --> 00:02:52.630 align:start position:0% 726|gap, I still wasted money. So, here is 727|the<00:02:50.959><c> third</c><00:02:51.120><c> question.</c><00:02:51.519><c> Am</c><00:02:51.680><c> I</c><00:02:51.840><c> fixing</c><00:02:52.160><c> what's</c> 728| 729|00:02:52.630 --> 00:02:52.640 align:start position:0% 730|the third question. Am I fixing what's 731| 732| 733|00:02:52.640 --> 00:02:54.550 align:start position:0% 734|the third question. Am I fixing what's 735|actually<00:02:53.120><c> limiting</c><00:02:53.519><c> me?</c><00:02:53.840><c> This</c><00:02:53.920><c> is</c><00:02:54.080><c> where</c><00:02:54.239><c> real</c> 736| 737|00:02:54.550 --> 00:02:54.560 align:start position:0% 738|actually limiting me? This is where real 739| 740| 741|00:02:54.560 --> 00:02:56.470 align:start position:0% 742|actually limiting me? This is where real 743|money<00:02:54.800><c> gets</c><00:02:55.040><c> wasted.</c><00:02:55.440><c> The</c><00:02:55.599><c> problem</c><00:02:55.840><c> is</c><00:02:56.080><c> real.</c> 744| 745|00:02:56.470 --> 00:02:56.480 align:start position:0% 746|money gets wasted. The problem is real. 747| 748| 749|00:02:56.480 --> 00:02:58.630 align:start position:0% 750|money gets wasted. The problem is real. 751|The<00:02:56.640><c> gap</c><00:02:57.040><c> again</c><00:02:57.360><c> is</c><00:02:57.599><c> real,</c><00:02:57.840><c> but</c><00:02:58.080><c> you're</c><00:02:58.319><c> fixing</c> 752| 753|00:02:58.630 --> 00:02:58.640 align:start position:0% 754|The gap again is real, but you're fixing 755| 756| 757|00:02:58.640 --> 00:02:59.990 align:start position:0% 758|The gap again is real, but you're fixing 759|the<00:02:58.879><c> wrong</c><00:02:59.040><c> thing.</c><00:02:59.440><c> And</c><00:02:59.519><c> I</c><00:02:59.680><c> see</c><00:02:59.760><c> this</c> 760| 761|00:02:59.990 --> 00:03:00.000 align:start position:0% 762|the wrong thing. And I see this 763| 764| 765|00:03:00.000 --> 00:03:01.750 align:start position:0% 766|the wrong thing. And I see this 767|constantly,<00:03:00.720><c> especially</c><00:03:01.040><c> on</c><00:03:01.280><c> my</c><00:03:01.360><c> Discord</c> 768| 769|00:03:01.750 --> 00:03:01.760 align:start position:0% 770|constantly, especially on my Discord 771| 772| 773|00:03:01.760 --> 00:03:02.949 align:start position:0% 774|constantly, especially on my Discord 775|channel.<00:03:02.080><c> There's</c><00:03:02.319><c> a</c><00:03:02.480><c> bunch</c><00:03:02.560><c> of</c><00:03:02.720><c> people</c> 776| 777|00:03:02.949 --> 00:03:02.959 align:start position:0% 778|channel. There's a bunch of people 779| 780| 781|00:03:02.959 --> 00:03:05.509 align:start position:0% 782|channel. There's a bunch of people 783|spending<00:03:03.280><c> like</c><00:03:03.599><c> $200</c><00:03:04.239><c> on</c><00:03:04.480><c> a</c><00:03:04.720><c> new</c><00:03:04.879><c> mouse</c><00:03:05.200><c> and</c><00:03:05.360><c> a</c> 784| 785|00:03:05.509 --> 00:03:05.519 align:start position:0% 786|spending like $200 on a new mouse and a 787| 788| 789|00:03:05.519 --> 00:03:07.589 align:start position:0% 790|spending like $200 on a new mouse and a 791|mouse<00:03:05.840><c> pad</c><00:03:06.000><c> combo.</c><00:03:06.480><c> Premium</c><00:03:06.959><c> stuff</c><00:03:07.200><c> in</c><00:03:07.440><c> their</c> 792| 793|00:03:07.589 --> 00:03:07.599 align:start position:0% 794|mouse pad combo. Premium stuff in their 795| 796| 797|00:03:07.599 --> 00:03:09.509 align:start position:0% 798|mouse pad combo. Premium stuff in their 799|eyes.<00:03:07.920><c> A</c><00:03:08.080><c> real</c><00:03:08.319><c> upgrade</c><00:03:08.720><c> from</c><00:03:08.959><c> what</c><00:03:09.120><c> they</c><00:03:09.280><c> had,</c> 800| 801|00:03:09.509 --> 00:03:09.519 align:start position:0% 802|eyes. A real upgrade from what they had, 803| 804| 805|00:03:09.519 --> 00:03:11.589 align:start position:0% 806|eyes. A real upgrade from what they had, 807|but<00:03:09.760><c> their</c><00:03:09.920><c> desk</c><00:03:10.159><c> is</c><00:03:10.319><c> like</c><00:03:10.560><c> 3</c><00:03:10.720><c> in</c><00:03:11.040><c> too</c><00:03:11.200><c> high.</c> 808| 809|00:03:11.589 --> 00:03:11.599 align:start position:0% 810|but their desk is like 3 in too high. 811| 812| 813|00:03:11.599 --> 00:03:14.070 align:start position:0% 814|but their desk is like 3 in too high. 815|Their<00:03:11.840><c> elbows</c><00:03:12.319><c> floats</c><00:03:12.720><c> around.</c><00:03:13.280><c> their</c><00:03:13.680><c> wrist</c> 816| 817|00:03:14.070 --> 00:03:14.080 align:start position:0% 818|Their elbows floats around. their wrist 819| 820| 821|00:03:14.080 --> 00:03:16.149 align:start position:0% 822|Their elbows floats around. their wrist 823|anchors<00:03:14.560><c> weird</c><00:03:14.879><c> and</c><00:03:15.040><c> after</c><00:03:15.280><c> like</c><00:03:15.519><c> 4</c><00:03:15.760><c> hours</c> 824| 825|00:03:16.149 --> 00:03:16.159 align:start position:0% 826|anchors weird and after like 4 hours 827| 828| 829|00:03:16.159 --> 00:03:18.070 align:start position:0% 830|anchors weird and after like 4 hours 831|their<00:03:16.400><c> micro</c><00:03:16.720><c> adjustments</c><00:03:17.200><c> just</c><00:03:17.440><c> fall</c><00:03:17.599><c> apart.</c> 832| 833|00:03:18.070 --> 00:03:18.080 align:start position:0% 834|their micro adjustments just fall apart. 835| 836| 837|00:03:18.080 --> 00:03:19.589 align:start position:0% 838|their micro adjustments just fall apart. 839|Not<00:03:18.319><c> because</c><00:03:18.480><c> of</c><00:03:18.640><c> the</c><00:03:18.800><c> mouse,</c><00:03:19.120><c> because</c><00:03:19.280><c> of</c><00:03:19.440><c> the</c> 840| 841|00:03:19.589 --> 00:03:19.599 align:start position:0% 842|Not because of the mouse, because of the 843| 844| 845|00:03:19.599 --> 00:03:21.190 align:start position:0% 846|Not because of the mouse, because of the 847|desk.<00:03:19.920><c> To</c><00:03:20.159><c> back</c><00:03:20.319><c> this</c><00:03:20.480><c> up,</c><00:03:20.720><c> there's</c><00:03:20.879><c> a</c><00:03:21.040><c> bunch</c> 848| 849|00:03:21.190 --> 00:03:21.200 align:start position:0% 850|desk. To back this up, there's a bunch 851| </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="1050" end_line="1249" total_lines="1984"> 1050|the weakest link? If everything else was 1051| 1052| 1053|00:04:07.200 --> 00:04:09.110 align:start position:0% 1054|the weakest link? If everything else was 1055|perfect.<00:04:07.519><c> Now,</c><00:04:07.760><c> most</c><00:04:07.920><c> people</c><00:04:08.159><c> skip</c><00:04:08.480><c> this.</c><00:04:08.879><c> I</c> 1056| 1057|00:04:09.110 --> 00:04:09.120 align:start position:0% 1058|perfect. Now, most people skip this. I 1059| 1060| 1061|00:04:09.120 --> 00:04:11.509 align:start position:0% 1062|perfect. Now, most people skip this. I 1063|did.<00:04:09.439><c> And</c><00:04:09.599><c> I</c><00:04:09.760><c> always</c><00:04:10.159><c> upgraded</c><00:04:10.799><c> the</c><00:04:10.959><c> excited</c> 1064| 1065|00:04:11.509 --> 00:04:11.519 align:start position:0% 1066|did. And I always upgraded the excited 1067| 1068| 1069|00:04:11.519 --> 00:04:13.190 align:start position:0% 1070|did. And I always upgraded the excited 1071|stuff<00:04:11.760><c> first.</c><00:04:12.000><c> and</c><00:04:12.319><c> wondered</c><00:04:12.640><c> why</c><00:04:12.879><c> nothing</c> 1072| 1073|00:04:13.190 --> 00:04:13.200 align:start position:0% 1074|stuff first. and wondered why nothing 1075| 1076| 1077|00:04:13.200 --> 00:04:14.710 align:start position:0% 1078|stuff first. and wondered why nothing 1079|felt<00:04:13.439><c> different.</c><00:04:13.840><c> Now,</c><00:04:14.080><c> let</c><00:04:14.239><c> me</c><00:04:14.319><c> show</c><00:04:14.400><c> you</c><00:04:14.560><c> how</c> 1080| 1081|00:04:14.710 --> 00:04:14.720 align:start position:0% 1082|felt different. Now, let me show you how 1083| 1084| 1085|00:04:14.720 --> 00:04:16.949 align:start position:0% 1086|felt different. Now, let me show you how 1087|this<00:04:14.959><c> plays</c><00:04:15.200><c> out</c><00:04:15.439><c> on</c><00:04:15.840><c> real</c><00:04:16.079><c> gear.</c><00:04:16.560><c> So,</c><00:04:16.720><c> let's</c> 1088| 1089|00:04:16.949 --> 00:04:16.959 align:start position:0% 1090|this plays out on real gear. So, let's 1091| 1092| 1093|00:04:16.959 --> 00:04:18.789 align:start position:0% 1094|this plays out on real gear. So, let's 1095|start<00:04:17.040><c> with</c><00:04:17.280><c> mice.</c><00:04:17.680><c> A</c><00:04:17.759><c> real</c><00:04:18.000><c> a</c><00:04:18.160><c> problem</c><00:04:18.400><c> or</c><00:04:18.639><c> a</c> 1096| 1097|00:04:18.789 --> 00:04:18.799 align:start position:0% 1098|start with mice. A real a problem or a 1099| 1100| 1101|00:04:18.799 --> 00:04:20.710 align:start position:0% 1102|start with mice. A real a problem or a 1103|feeling?<00:04:19.199><c> A</c><00:04:19.359><c> shape</c><00:04:19.600><c> issue?</c><00:04:20.079><c> Is</c><00:04:20.239><c> it</c><00:04:20.400><c> real?</c> 1104| 1105|00:04:20.710 --> 00:04:20.720 align:start position:0% 1106|feeling? A shape issue? Is it real? 1107| 1108| 1109|00:04:20.720 --> 00:04:22.550 align:start position:0% 1110|feeling? A shape issue? Is it real? 1111|Cramps,<00:04:21.199><c> unstable</c><00:04:21.759><c> grip,</c><00:04:22.079><c> those</c><00:04:22.320><c> actually</c> 1112| 1113|00:04:22.550 --> 00:04:22.560 align:start position:0% 1114|Cramps, unstable grip, those actually 1115| 1116| 1117|00:04:22.560 --> 00:04:24.230 align:start position:0% 1118|Cramps, unstable grip, those actually 1119|matter.<00:04:22.960><c> Wanting</c><00:04:23.360><c> lighter</c><00:04:23.759><c> because</c><00:04:23.919><c> you</c><00:04:24.080><c> saw</c> 1120| 1121|00:04:24.230 --> 00:04:24.240 align:start position:0% 1122|matter. Wanting lighter because you saw 1123| 1124| 1125|00:04:24.240 --> 00:04:26.150 align:start position:0% 1126|matter. Wanting lighter because you saw 1127|a<00:04:24.400><c> review</c><00:04:24.800><c> is</c><00:04:24.960><c> just</c><00:04:25.040><c> a</c><00:04:25.280><c> feeling.</c><00:04:25.600><c> Now,</c><00:04:25.840><c> what's</c> 1128| 1129|00:04:26.150 --> 00:04:26.160 align:start position:0% 1130|a review is just a feeling. Now, what's 1131| 1132| 1133|00:04:26.160 --> 00:04:28.230 align:start position:0% 1134|a review is just a feeling. Now, what's 1135|actually<00:04:26.320><c> the</c><00:04:26.560><c> gap?</c><00:04:26.960><c> Sensors</c><00:04:27.520><c> are</c><00:04:27.759><c> all</c><00:04:27.919><c> in</c><00:04:28.080><c> the</c> 1136| 1137|00:04:28.230 --> 00:04:28.240 align:start position:0% 1138|actually the gap? Sensors are all in the 1139| 1140| 1141|00:04:28.240 --> 00:04:29.749 align:start position:0% 1142|actually the gap? Sensors are all in the 1143|same<00:04:28.400><c> performance</c><00:04:28.880><c> class.</c><00:04:29.120><c> Now,</c><00:04:29.360><c> the</c><00:04:29.520><c> real</c> 1144| 1145|00:04:29.749 --> 00:04:29.759 align:start position:0% 1146|same performance class. Now, the real 1147| 1148| 1149|00:04:29.759 --> 00:04:31.270 align:start position:0% 1150|same performance class. Now, the real 1151|gap<00:04:29.919><c> is</c><00:04:30.160><c> shape</c><00:04:30.400><c> and</c><00:04:30.639><c> weight.</c><00:04:30.880><c> And</c><00:04:31.040><c> also</c> 1152| 1153|00:04:31.270 --> 00:04:31.280 align:start position:0% 1154|gap is shape and weight. And also 1155| 1156| 1157|00:04:31.280 --> 00:04:33.030 align:start position:0% 1158|gap is shape and weight. And also 1159|wireless.<00:04:31.759><c> It</c><00:04:31.840><c> really</c><00:04:32.080><c> depends</c><00:04:32.320><c> on</c><00:04:32.720><c> what</c><00:04:32.880><c> you</c> 1160| 1161|00:04:33.030 --> 00:04:33.040 align:start position:0% 1162|wireless. It really depends on what you 1163| 1164| 1165|00:04:33.040 --> 00:04:35.430 align:start position:0% 1166|wireless. It really depends on what you 1167|need<00:04:33.280><c> wireless</c><00:04:33.680><c> for.</c><00:04:34.000><c> 90</c><00:04:34.240><c> g</c><00:04:34.479><c> to</c><00:04:34.720><c> 60,</c><00:04:35.120><c> you</c><00:04:35.280><c> will</c> 1168| 1169|00:04:35.430 --> 00:04:35.440 align:start position:0% 1170|need wireless for. 90 g to 60, you will 1171| 1172| 1173|00:04:35.440 --> 00:04:38.870 align:start position:0% 1174|need wireless for. 90 g to 60, you will 1175|feel<00:04:35.600><c> that</c><00:04:36.080><c> 55</c><00:04:36.560><c> to</c><00:04:36.880><c> 47</c><00:04:37.680><c> is</c><00:04:37.919><c> just</c><00:04:38.000><c> a</c><00:04:38.160><c> placebo</c><00:04:38.720><c> for</c> 1176| 1177|00:04:38.870 --> 00:04:38.880 align:start position:0% 1178|feel that 55 to 47 is just a placebo for 1179| 1180| 1181|00:04:38.880 --> 00:04:40.629 align:start position:0% 1182|feel that 55 to 47 is just a placebo for 1183|most<00:04:39.040><c> people.</c><00:04:39.280><c> Now,</c><00:04:39.520><c> is</c><00:04:39.680><c> this</c><00:04:39.840><c> your</c><00:04:40.000><c> ceiling?</c> 1184| 1185|00:04:40.629 --> 00:04:40.639 align:start position:0% 1186|most people. Now, is this your ceiling? 1187| 1188| 1189|00:04:40.639 --> 00:04:42.629 align:start position:0% 1190|most people. Now, is this your ceiling? 1191|Almost<00:04:40.960><c> never.</c><00:04:41.440><c> Nobody's</c><00:04:41.840><c> stuck</c><00:04:42.080><c> in</c><00:04:42.240><c> plat</c> 1192| 1193|00:04:42.629 --> 00:04:42.639 align:start position:0% 1194|Almost never. Nobody's stuck in plat 1195| 1196| 1197|00:04:42.639 --> 00:04:44.150 align:start position:0% 1198|Almost never. Nobody's stuck in plat 1199|because<00:04:42.800><c> of</c><00:04:42.960><c> their</c><00:04:43.199><c> mouse.</c><00:04:43.520><c> Get</c><00:04:43.680><c> a</c><00:04:43.840><c> shape</c><00:04:44.000><c> that</c> 1200| 1201|00:04:44.150 --> 00:04:44.160 align:start position:0% 1202|because of their mouse. Get a shape that 1203| 1204| 1205|00:04:44.160 --> 00:04:45.749 align:start position:0% 1206|because of their mouse. Get a shape that 1207|fits<00:04:44.400><c> and</c><00:04:44.639><c> just</c><00:04:44.800><c> move</c><00:04:44.960><c> on.</c><00:04:45.280><c> Next,</c><00:04:45.440><c> we</c><00:04:45.680><c> have</c> 1208| 1209|00:04:45.749 --> 00:04:45.759 align:start position:0% 1210|fits and just move on. Next, we have 1211| 1212| 1213|00:04:45.759 --> 00:04:47.749 align:start position:0% 1214|fits and just move on. Next, we have 1215|GPU.<00:04:46.320><c> Now,</c><00:04:46.560><c> be</c><00:04:46.720><c> honest.</c><00:04:47.120><c> What</c><00:04:47.280><c> problem</c><00:04:47.600><c> are</c> 1216| 1217|00:04:47.749 --> 00:04:47.759 align:start position:0% 1218|GPU. Now, be honest. What problem are 1219| 1220| 1221|00:04:47.759 --> 00:04:50.150 align:start position:0% 1222|GPU. Now, be honest. What problem are 1223|you<00:04:47.919><c> solving?</c><00:04:48.479><c> For</c><00:04:48.639><c> competitive</c><00:04:49.199><c> gaming,</c><00:04:49.680><c> GPU</c> 1224| 1225|00:04:50.150 --> 00:04:50.160 align:start position:0% 1226|you solving? For competitive gaming, GPU 1227| 1228| 1229|00:04:50.160 --> 00:04:52.150 align:start position:0% 1230|you solving? For competitive gaming, GPU 1231|is<00:04:50.400><c> almost</c><00:04:50.639><c> never</c><00:04:50.960><c> your</c><00:04:51.199><c> ceiling.</c><00:04:51.600><c> Valorant</c> 1232| 1233|00:04:52.150 --> 00:04:52.160 align:start position:0% 1234|is almost never your ceiling. Valorant 1235| 1236| 1237|00:04:52.160 --> 00:04:54.230 align:start position:0% 1238|is almost never your ceiling. Valorant 1239|CPU<00:04:52.560><c> bound,</c><00:04:52.880><c> for</c><00:04:52.960><c> example,</c><00:04:53.280><c> and</c><00:04:53.520><c> CS2</c><00:04:54.080><c> also</c> 1240| 1241|00:04:54.230 --> 00:04:54.240 align:start position:0% 1242|CPU bound, for example, and CS2 also 1243| 1244| 1245|00:04:54.240 --> 00:04:56.230 align:start position:0% 1246|CPU bound, for example, and CS2 also 1247|cares<00:04:54.560><c> more</c><00:04:54.720><c> about</c><00:04:54.880><c> CPU</c><00:04:55.280><c> and</c><00:04:55.520><c> your</c><00:04:55.680><c> RAM</c><00:04:55.919><c> speed.</c> 1248| 1249|00:04:56.230 --> 00:04:56.240 align:start position:0% </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="1450" end_line="1649" total_lines="1984"> 1450|missing information other players react 1451| 1452| 1453|00:05:44.560 --> 00:05:46.469 align:start position:0% 1454|missing information other players react 1455|to,<00:05:44.880><c> nothing</c><00:05:45.120><c> else</c><00:05:45.360><c> fixes</c><00:05:45.759><c> that.</c><00:05:46.000><c> This</c><00:05:46.160><c> is</c><00:05:46.320><c> the</c> 1456| 1457|00:05:46.469 --> 00:05:46.479 align:start position:0% 1458|to, nothing else fixes that. This is the 1459| 1460| 1461|00:05:46.479 --> 00:05:47.909 align:start position:0% 1462|to, nothing else fixes that. This is the 1463|exception<00:05:46.800><c> to</c><00:05:46.960><c> the</c><00:05:47.120><c> pattern.</c><00:05:47.520><c> The</c><00:05:47.680><c> gap</c> 1464| 1465|00:05:47.909 --> 00:05:47.919 align:start position:0% 1466|exception to the pattern. The gap 1467| 1468| 1469|00:05:47.919 --> 00:05:50.070 align:start position:0% 1470|exception to the pattern. The gap 1471|between<00:05:48.160><c> bad</c><00:05:48.479><c> audio</c><00:05:48.800><c> and</c><00:05:49.039><c> good</c><00:05:49.280><c> audio</c><00:05:49.680><c> stays</c> 1472| 1473|00:05:50.070 --> 00:05:50.080 align:start position:0% 1474|between bad audio and good audio stays 1475| 1476| 1477|00:05:50.080 --> 00:05:52.070 align:start position:0% 1478|between bad audio and good audio stays 1479|super<00:05:50.400><c> big.</c><00:05:50.720><c> And</c><00:05:50.880><c> actually</c><00:05:51.120><c> getting</c><00:05:51.440><c> a</c><00:05:51.600><c> fix</c><00:05:51.840><c> is</c> 1480| 1481|00:05:52.070 --> 00:05:52.080 align:start position:0% 1482|super big. And actually getting a fix is 1483| 1484| 1485|00:05:52.080 --> 00:05:54.550 align:start position:0% 1486|super big. And actually getting a fix is 1487|super<00:05:52.400><c> cheap.</c><00:05:52.800><c> $50</c><00:05:52.960><c> to</c><00:05:53.280><c> $80</c><00:05:53.840><c> and</c><00:05:54.080><c> that's</c><00:05:54.240><c> it.</c> 1488| 1489|00:05:54.550 --> 00:05:54.560 align:start position:0% 1490|super cheap. $50 to $80 and that's it. 1491| 1492| 1493|00:05:54.560 --> 00:05:56.070 align:start position:0% 1494|super cheap. $50 to $80 and that's it. 1495|And<00:05:54.720><c> this</c><00:05:54.880><c> change</c><00:05:55.199><c> how</c><00:05:55.360><c> I</c><00:05:55.520><c> think</c><00:05:55.680><c> about</c><00:05:55.840><c> the</c> 1496| 1497|00:05:56.070 --> 00:05:56.080 align:start position:0% 1498|And this change how I think about the 1499| 1500| 1501|00:05:56.080 --> 00:05:58.070 align:start position:0% 1502|And this change how I think about the 1503|whole<00:05:56.240><c> priority</c><00:05:56.720><c> order.</c><00:05:57.199><c> Now,</c><00:05:57.520><c> the</c><00:05:57.840><c> last</c> 1504| 1505|00:05:58.070 --> 00:05:58.080 align:start position:0% 1506|whole priority order. Now, the last 1507| 1508| 1509|00:05:58.080 --> 00:06:00.469 align:start position:0% 1510|whole priority order. Now, the last 1511|thing<00:05:58.320><c> is</c><00:05:58.560><c> premium</c><00:05:59.039><c> stuff</c><00:05:59.360><c> is</c><00:05:59.600><c> not</c><00:05:59.759><c> a</c><00:06:00.000><c> scam,</c> 1512| 1513|00:06:00.469 --> 00:06:00.479 align:start position:0% 1514|thing is premium stuff is not a scam, 1515| 1516| 1517|00:06:00.479 --> 00:06:02.070 align:start position:0% 1518|thing is premium stuff is not a scam, 1519|just<00:06:00.720><c> not</c><00:06:00.880><c> what</c><00:06:01.199><c> people</c><00:06:01.440><c> think.</c><00:06:01.840><c> You're</c> 1520| 1521|00:06:02.070 --> 00:06:02.080 align:start position:0% 1522|just not what people think. You're 1523| 1524| 1525|00:06:02.080 --> 00:06:04.230 align:start position:0% 1526|just not what people think. You're 1527|buying<00:06:02.400><c> refinement,</c><00:06:03.199><c> better</c><00:06:03.600><c> materials,</c> 1528| 1529|00:06:04.230 --> 00:06:04.240 align:start position:0% 1530|buying refinement, better materials, 1531| 1532| 1533|00:06:04.240 --> 00:06:06.150 align:start position:0% 1534|buying refinement, better materials, 1535|cleaner<00:06:04.720><c> build,</c><00:06:04.960><c> and</c><00:06:05.199><c> that</c><00:06:05.360><c> has</c><00:06:05.600><c> value</c><00:06:05.840><c> if</c><00:06:06.000><c> you</c> 1536| 1537|00:06:06.150 --> 00:06:06.160 align:start position:0% 1538|cleaner build, and that has value if you 1539| 1540| 1541|00:06:06.160 --> 00:06:08.390 align:start position:0% 1542|cleaner build, and that has value if you 1543|actually<00:06:06.880><c> value</c><00:06:07.199><c> it</c><00:06:07.440><c> yourself.</c><00:06:07.840><c> Just</c><00:06:08.080><c> don't</c> 1544| 1545|00:06:08.390 --> 00:06:08.400 align:start position:0% 1546|actually value it yourself. Just don't 1547| 1548| 1549|00:06:08.400 --> 00:06:10.629 align:start position:0% 1550|actually value it yourself. Just don't 1551|expect<00:06:08.720><c> your</c><00:06:08.960><c> rank</c><00:06:09.280><c> to</c><00:06:09.520><c> change.</c><00:06:10.160><c> Buy</c><00:06:10.319><c> it</c><00:06:10.479><c> if</c> 1552| 1553|00:06:10.629 --> 00:06:10.639 align:start position:0% 1554|expect your rank to change. Buy it if 1555| 1556| 1557|00:06:10.639 --> 00:06:12.550 align:start position:0% 1558|expect your rank to change. Buy it if 1559|you<00:06:10.720><c> want</c><00:06:10.880><c> it,</c><00:06:11.120><c> just</c><00:06:11.280><c> buy</c><00:06:11.520><c> with</c><00:06:11.759><c> clear</c><00:06:12.080><c> eyes.</c> 1560| 1561|00:06:12.550 --> 00:06:12.560 align:start position:0% 1562|you want it, just buy with clear eyes. 1563| 1564| 1565|00:06:12.560 --> 00:06:14.230 align:start position:0% 1566|you want it, just buy with clear eyes. 1567|So,<00:06:12.720><c> after</c><00:06:13.039><c> running</c><00:06:13.360><c> those</c><00:06:13.680><c> three</c><00:06:13.919><c> questions</c> 1568| 1569|00:06:14.230 --> 00:06:14.240 align:start position:0% 1570|So, after running those three questions 1571| 1572| 1573|00:06:14.240 --> 00:06:16.070 align:start position:0% 1574|So, after running those three questions 1575|on<00:06:14.479><c> everything,</c><00:06:14.960><c> here</c><00:06:15.120><c> is</c><00:06:15.280><c> the</c><00:06:15.520><c> priority</c> 1576| 1577|00:06:16.070 --> 00:06:16.080 align:start position:0% 1578|on everything, here is the priority 1579| 1580| 1581|00:06:16.080 --> 00:06:18.309 align:start position:0% 1582|on everything, here is the priority 1583|order<00:06:16.560><c> that</c><00:06:16.880><c> actually</c><00:06:17.280><c> makes</c><00:06:17.520><c> sense.</c><00:06:17.919><c> First,</c> 1584| 1585|00:06:18.309 --> 00:06:18.319 align:start position:0% 1586|order that actually makes sense. First, 1587| 1588| 1589|00:06:18.319 --> 00:06:19.830 align:start position:0% 1590|order that actually makes sense. First, 1591|you<00:06:18.560><c> always</c><00:06:18.800><c> have</c><00:06:18.960><c> to</c><00:06:19.120><c> prioritize</c><00:06:19.600><c> the</c> 1592| 1593|00:06:19.830 --> 00:06:19.840 align:start position:0% 1594|you always have to prioritize the 1595| 1596| 1597|00:06:19.840 --> 00:06:21.590 align:start position:0% 1598|you always have to prioritize the 1599|frames.<00:06:20.240><c> If</c><00:06:20.400><c> your</c><00:06:20.560><c> PC</c><00:06:20.880><c> drops</c><00:06:21.120><c> below</c><00:06:21.440><c> your</c> 1600| 1601|00:06:21.590 --> 00:06:21.600 align:start position:0% 1602|frames. If your PC drops below your 1603| 1604| 1605|00:06:21.600 --> 00:06:23.590 align:start position:0% 1606|frames. If your PC drops below your 1607|monitor<00:06:22.080><c> refresh</c><00:06:22.400><c> rate</c><00:06:22.639><c> in</c><00:06:22.800><c> fights,</c><00:06:23.360><c> nothing</c> 1608| 1609|00:06:23.590 --> 00:06:23.600 align:start position:0% 1610|monitor refresh rate in fights, nothing 1611| 1612| 1613|00:06:23.600 --> 00:06:25.189 align:start position:0% 1614|monitor refresh rate in fights, nothing 1615|else<00:06:23.919><c> matters.</c><00:06:24.400><c> Doesn't</c><00:06:24.639><c> matter</c><00:06:24.880><c> how</c><00:06:25.039><c> good</c> 1616| 1617|00:06:25.189 --> 00:06:25.199 align:start position:0% 1618|else matters. Doesn't matter how good 1619| 1620| 1621|00:06:25.199 --> 00:06:27.029 align:start position:0% 1622|else matters. Doesn't matter how good 1623|your<00:06:25.440><c> mouse</c><00:06:25.680><c> is.</c><00:06:25.919><c> If</c><00:06:26.160><c> your</c><00:06:26.319><c> game</c><00:06:26.560><c> stutters</c> 1624| 1625|00:06:27.029 --> 00:06:27.039 align:start position:0% 1626|your mouse is. If your game stutters 1627| 1628| 1629|00:06:27.039 --> 00:06:29.749 align:start position:0% 1630|your mouse is. If your game stutters 1631|when<00:06:27.199><c> you</c><00:06:27.360><c> pick</c><00:06:27.680><c> CPU</c><00:06:28.080><c> and</c><00:06:28.319><c> RAM,</c><00:06:28.720><c> usually</c><00:06:29.280><c> GPU</c> 1632| 1633|00:06:29.749 --> 00:06:29.759 align:start position:0% 1634|when you pick CPU and RAM, usually GPU 1635| 1636| 1637|00:06:29.759 --> 00:06:31.590 align:start position:0% 1638|when you pick CPU and RAM, usually GPU 1639|only<00:06:30.000><c> if</c><00:06:30.160><c> you're</c><00:06:30.319><c> like</c><00:06:30.639><c> GPU</c><00:06:31.039><c> bottleneck,</c> 1640| 1641|00:06:31.590 --> 00:06:31.600 align:start position:0% 1642|only if you're like GPU bottleneck, 1643| 1644| 1645|00:06:31.600 --> 00:06:33.110 align:start position:0% 1646|only if you're like GPU bottleneck, 1647|which<00:06:31.840><c> in</c><00:06:32.080><c> competitive</c><00:06:32.479><c> games,</c><00:06:32.800><c> you're</c> 1648| 1649|00:06:33.110 --> 00:06:33.120 align:start position:0% </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="1650" end_line="1849" total_lines="1984"> 1650|which in competitive games, you're 1651| 1652| 1653|00:06:33.120 --> 00:06:35.510 align:start position:0% 1654|which in competitive games, you're 1655|probably<00:06:33.600><c> not.</c><00:06:34.000><c> Next,</c><00:06:34.240><c> we</c><00:06:34.479><c> have</c><00:06:34.639><c> consistency.</c> 1656| 1657|00:06:35.510 --> 00:06:35.520 align:start position:0% 1658|probably not. Next, we have consistency. 1659| 1660| 1661|00:06:35.520 --> 00:06:37.270 align:start position:0% 1662|probably not. Next, we have consistency. 1663|Your<00:06:35.759><c> surface</c><00:06:36.160><c> and</c><00:06:36.319><c> your</c><00:06:36.560><c> setting.</c><00:06:36.880><c> If</c><00:06:37.120><c> your</c> 1664| 1665|00:06:37.270 --> 00:06:37.280 align:start position:0% 1666|Your surface and your setting. If your 1667| 1668| 1669|00:06:37.280 --> 00:06:39.029 align:start position:0% 1670|Your surface and your setting. If your 1671|pad<00:06:37.600><c> changes</c><00:06:37.919><c> how</c><00:06:38.160><c> they</c><00:06:38.319><c> feel</c><00:06:38.560><c> every</c><00:06:38.880><c> few</c> 1672| 1673|00:06:39.029 --> 00:06:39.039 align:start position:0% 1674|pad changes how they feel every few 1675| 1676| 1677|00:06:39.039 --> 00:06:41.270 align:start position:0% 1678|pad changes how they feel every few 1679|weeks<00:06:39.280><c> from</c><00:06:39.600><c> humidity</c><00:06:40.080><c> or</c><00:06:40.400><c> wear,</c><00:06:40.960><c> you're</c> 1680| 1681|00:06:41.270 --> 00:06:41.280 align:start position:0% 1682|weeks from humidity or wear, you're 1683| 1684| 1685|00:06:41.280 --> 00:06:42.870 align:start position:0% 1686|weeks from humidity or wear, you're 1687|building<00:06:41.520><c> muscle</c><00:06:41.919><c> memory</c><00:06:42.160><c> on</c><00:06:42.400><c> something</c><00:06:42.639><c> that</c> 1688| 1689|00:06:42.870 --> 00:06:42.880 align:start position:0% 1690|building muscle memory on something that 1691| 1692| 1693|00:06:42.880 --> 00:06:44.390 align:start position:0% 1694|building muscle memory on something that 1695|keeps<00:06:43.120><c> shifting.</c><00:06:43.600><c> If</c><00:06:43.759><c> you're</c><00:06:43.919><c> still</c><00:06:44.080><c> tweaking</c> 1696| 1697|00:06:44.390 --> 00:06:44.400 align:start position:0% 1698|keeps shifting. If you're still tweaking 1699| 1700| 1701|00:06:44.400 --> 00:06:46.230 align:start position:0% 1702|keeps shifting. If you're still tweaking 1703|sensitivity<00:06:44.960><c> every</c><00:06:45.280><c> other</c><00:06:45.520><c> day,</c><00:06:45.919><c> same</c> 1704| 1705|00:06:46.230 --> 00:06:46.240 align:start position:0% 1706|sensitivity every other day, same 1707| 1708| 1709|00:06:46.240 --> 00:06:48.230 align:start position:0% 1710|sensitivity every other day, same 1711|problem.<00:06:46.639><c> Lock</c><00:06:46.880><c> it</c><00:06:47.039><c> down.</c><00:06:47.360><c> Stop</c><00:06:47.759><c> changing</c> 1712| 1713|00:06:48.230 --> 00:06:48.240 align:start position:0% 1714|problem. Lock it down. Stop changing 1715| 1716| 1717|00:06:48.240 --> 00:06:50.150 align:start position:0% 1718|problem. Lock it down. Stop changing 1719|things.<00:06:48.880><c> Also,</c><00:06:49.199><c> if</c><00:06:49.440><c> you</c><00:06:49.600><c> don't</c><00:06:49.680><c> have</c><00:06:49.840><c> like</c><00:06:50.000><c> a</c> 1720| 1721|00:06:50.150 --> 00:06:50.160 align:start position:0% 1722|things. Also, if you don't have like a 1723| 1724| 1725|00:06:50.160 --> 00:06:51.590 align:start position:0% 1726|things. Also, if you don't have like a 1727|mouse<00:06:50.400><c> bungee,</c><00:06:50.880><c> just</c><00:06:51.039><c> get</c><00:06:51.199><c> something</c> 1728| 1729|00:06:51.590 --> 00:06:51.600 align:start position:0% 1730|mouse bungee, just get something 1731| 1732| 1733|00:06:51.600 --> 00:06:53.430 align:start position:0% 1734|mouse bungee, just get something 1735|wireless.<00:06:52.240><c> Wireless</c><00:06:52.720><c> at</c><00:06:52.880><c> this</c><00:06:53.039><c> point</c><00:06:53.199><c> is</c> 1736| 1737|00:06:53.430 --> 00:06:53.440 align:start position:0% 1738|wireless. Wireless at this point is 1739| 1740| 1741|00:06:53.440 --> 00:06:55.110 align:start position:0% 1742|wireless. Wireless at this point is 1743|cheap<00:06:53.680><c> and</c><00:06:53.840><c> good</c><00:06:54.080><c> quality.</c><00:06:54.479><c> So,</c><00:06:54.720><c> get</c><00:06:54.880><c> rid</c><00:06:55.039><c> of</c> 1744| 1745|00:06:55.110 --> 00:06:55.120 align:start position:0% 1746|cheap and good quality. So, get rid of 1747| 1748| 1749|00:06:55.120 --> 00:06:56.790 align:start position:0% 1750|cheap and good quality. So, get rid of 1751|the<00:06:55.280><c> friction</c><00:06:55.680><c> from</c><00:06:55.840><c> the</c><00:06:56.000><c> cable.</c><00:06:56.400><c> Next,</c><00:06:56.560><c> we</c> 1752| 1753|00:06:56.790 --> 00:06:56.800 align:start position:0% 1754|the friction from the cable. Next, we 1755| 1756| 1757|00:06:56.800 --> 00:06:58.710 align:start position:0% 1758|the friction from the cable. Next, we 1759|have<00:06:56.960><c> information</c><00:06:57.759><c> audio.</c><00:06:58.240><c> If</c><00:06:58.479><c> you</c><00:06:58.560><c> can't</c> 1760| 1761|00:06:58.710 --> 00:06:58.720 align:start position:0% 1762|have information audio. If you can't 1763| 1764| 1765|00:06:58.720 --> 00:07:00.710 align:start position:0% 1766|have information audio. If you can't 1767|hear<00:06:58.960><c> what</c><00:06:59.199><c> other</c><00:06:59.440><c> players</c><00:06:59.919><c> react</c><00:07:00.160><c> to,</c><00:07:00.400><c> you're</c> 1768| 1769|00:07:00.710 --> 00:07:00.720 align:start position:0% 1770|hear what other players react to, you're 1771| 1772| 1773|00:07:00.720 --> 00:07:02.790 align:start position:0% 1774|hear what other players react to, you're 1775|making<00:07:00.960><c> decisions</c><00:07:01.440><c> with</c><00:07:01.759><c> incomplete</c><00:07:02.319><c> data.</c> 1776| 1777|00:07:02.790 --> 00:07:02.800 align:start position:0% 1778|making decisions with incomplete data. 1779| 1780| 1781|00:07:02.800 --> 00:07:05.029 align:start position:0% 1782|making decisions with incomplete data. 1783|This<00:07:02.960><c> is</c><00:07:03.039><c> where</c><00:07:03.360><c> $50</c><00:07:03.599><c> to</c><00:07:03.840><c> $80</c><00:07:04.400><c> makes</c><00:07:04.639><c> a</c><00:07:04.880><c> real</c> 1784| 1785|00:07:05.029 --> 00:07:05.039 align:start position:0% 1786|This is where $50 to $80 makes a real 1787| 1788| 1789|00:07:05.039 --> 00:07:07.589 align:start position:0% 1790|This is where $50 to $80 makes a real 1791|difference.<00:07:05.520><c> IM,</c><00:07:06.160><c> maybe</c><00:07:06.319><c> even</c><00:07:06.479><c> a</c><00:07:06.720><c> DAC</c><00:07:07.280><c> for</c> 1792| 1793|00:07:07.589 --> 00:07:07.599 align:start position:0% 1794|difference. IM, maybe even a DAC for 1795| 1796| 1797|00:07:07.599 --> 00:07:09.189 align:start position:0% 1798|difference. IM, maybe even a DAC for 1799|better<00:07:07.919><c> input.</c><00:07:08.479><c> This</c><00:07:08.639><c> is</c><00:07:08.720><c> where</c><00:07:08.880><c> you'll</c> 1800| 1801|00:07:09.189 --> 00:07:09.199 align:start position:0% 1802|better input. This is where you'll 1803| 1804| 1805|00:07:09.199 --> 00:07:10.469 align:start position:0% 1806|better input. This is where you'll 1807|understand<00:07:09.520><c> what</c><00:07:09.759><c> you're</c><00:07:10.000><c> actually</c><00:07:10.319><c> been</c> 1808| 1809|00:07:10.469 --> 00:07:10.479 align:start position:0% 1810|understand what you're actually been 1811| 1812| 1813|00:07:10.479 --> 00:07:11.830 align:start position:0% 1814|understand what you're actually been 1815|missing<00:07:10.720><c> all</c><00:07:10.880><c> along.</c><00:07:11.280><c> Next,</c><00:07:11.440><c> we</c><00:07:11.680><c> have</c> 1816| 1817|00:07:11.830 --> 00:07:11.840 align:start position:0% 1818|missing all along. Next, we have 1819| 1820| 1821|00:07:11.840 --> 00:07:13.510 align:start position:0% 1822|missing all along. Next, we have 1823|refinement.<00:07:12.479><c> Premium</c><00:07:12.880><c> builds,</c><00:07:13.280><c> weight</c> 1824| 1825|00:07:13.510 --> 00:07:13.520 align:start position:0% 1826|refinement. Premium builds, weight 1827| 1828| 1829|00:07:13.520 --> 00:07:15.670 align:start position:0% 1830|refinement. Premium builds, weight 1831|optimization,<00:07:14.240><c> aesthetics,</c><00:07:14.880><c> all</c><00:07:15.039><c> valid,</c><00:07:15.440><c> all</c> 1832| 1833|00:07:15.670 --> 00:07:15.680 align:start position:0% 1834|optimization, aesthetics, all valid, all 1835| 1836| 1837|00:07:15.680 --> 00:07:17.589 align:start position:0% 1838|optimization, aesthetics, all valid, all 1839|nice<00:07:15.840><c> to</c><00:07:16.080><c> have.</c><00:07:16.319><c> None</c><00:07:16.560><c> of</c><00:07:16.720><c> it</c><00:07:16.960><c> actually</c><00:07:17.280><c> helps</c> 1840| 1841|00:07:17.589 --> 00:07:17.599 align:start position:0% 1842|nice to have. None of it actually helps 1843| 1844| 1845|00:07:17.599 --> 00:07:19.749 align:start position:0% 1846|nice to have. None of it actually helps 1847|you<00:07:17.919><c> get</c><00:07:18.080><c> a</c><00:07:18.319><c> better</c><00:07:18.560><c> rank.</c><00:07:18.960><c> None.</c><00:07:19.280><c> Now,</c><00:07:19.520><c> most</c> 1848| 1849|00:07:19.749 --> 00:07:19.759 align:start position:0% </file-view>

<file-view path="/Users/root1/The Only Upgrade Order That Makes Sense [fV4s5dwxYnw].en.vtt" start_line="1850" end_line="1984" total_lines="1984"> 1850|you get a better rank. None. Now, most 1851| 1852| 1853|00:07:19.759 --> 00:07:21.110 align:start position:0% 1854|you get a better rank. None. Now, most 1855|people<00:07:19.919><c> go</c><00:07:20.160><c> straight</c><00:07:20.319><c> to</c><00:07:20.479><c> refinement</c><00:07:20.960><c> because</c> 1856| 1857|00:07:21.110 --> 00:07:21.120 align:start position:0% 1858|people go straight to refinement because 1859| 1860| 1861|00:07:21.120 --> 00:07:22.790 align:start position:0% 1862|people go straight to refinement because 1863|it's<00:07:21.360><c> the</c><00:07:21.440><c> fun</c><00:07:21.680><c> part,</c><00:07:22.080><c> then</c><00:07:22.319><c> wonder</c><00:07:22.560><c> why</c> 1864| 1865|00:07:22.790 --> 00:07:22.800 align:start position:0% 1866|it's the fun part, then wonder why 1867| 1868| 1869|00:07:22.800 --> 00:07:24.309 align:start position:0% 1870|it's the fun part, then wonder why 1871|nothing<00:07:23.120><c> feels</c><00:07:23.440><c> different.</c><00:07:23.759><c> They</c><00:07:24.000><c> decide</c><00:07:24.160><c> to</c> 1872| 1873|00:07:24.309 --> 00:07:24.319 align:start position:0% 1874|nothing feels different. They decide to 1875| 1876| 1877|00:07:24.319 --> 00:07:26.870 align:start position:0% 1878|nothing feels different. They decide to 1879|buy<00:07:24.400><c> a</c><00:07:24.560><c> final</c><00:07:24.800><c> mouse</c><00:07:25.039><c> on</c><00:07:25.280><c> like</c><00:07:25.840><c> 120</c><00:07:26.160><c> fps</c><00:07:26.479><c> with</c><00:07:26.639><c> a</c> 1880| 1881|00:07:26.870 --> 00:07:26.880 align:start position:0% 1882|buy a final mouse on like 120 fps with a 1883| 1884| 1885|00:07:26.880 --> 00:07:29.029 align:start position:0% 1886|buy a final mouse on like 120 fps with a 1887|12-year-old<00:07:27.520><c> Steel</c><00:07:27.759><c> Series</c><00:07:28.080><c> QCK</c><00:07:28.639><c> Plus</c><00:07:28.800><c> and</c> 1888| 1889|00:07:29.029 --> 00:07:29.039 align:start position:0% 1890|12-year-old Steel Series QCK Plus and 1891| 1892| 1893|00:07:29.039 --> 00:07:30.790 align:start position:0% 1894|12-year-old Steel Series QCK Plus and 1895|wonder<00:07:29.280><c> why</c><00:07:29.520><c> they</c><00:07:29.759><c> still</c><00:07:30.000><c> stuck</c><00:07:30.240><c> in</c><00:07:30.400><c> gold.</c> 1896| 1897|00:07:30.790 --> 00:07:30.800 align:start position:0% 1898|wonder why they still stuck in gold. 1899| 1900| 1901|00:07:30.800 --> 00:07:32.950 align:start position:0% 1902|wonder why they still stuck in gold. 1903|Now,<00:07:31.120><c> here</c><00:07:31.280><c> is</c><00:07:31.440><c> what</c><00:07:31.599><c> I</c><00:07:31.840><c> want</c><00:07:32.000><c> you</c><00:07:32.240><c> to</c><00:07:32.319><c> do.</c><00:07:32.720><c> Drop</c> 1904| 1905|00:07:32.950 --> 00:07:32.960 align:start position:0% 1906|Now, here is what I want you to do. Drop 1907| 1908| 1909|00:07:32.960 --> 00:07:34.550 align:start position:0% 1910|Now, here is what I want you to do. Drop 1911|your<00:07:33.199><c> setup</c><00:07:33.440><c> in</c><00:07:33.599><c> the</c><00:07:33.759><c> comments,</c><00:07:34.160><c> current</c> 1912| 1913|00:07:34.550 --> 00:07:34.560 align:start position:0% 1914|your setup in the comments, current 1915| 1916| 1917|00:07:34.560 --> 00:07:35.990 align:start position:0% 1918|your setup in the comments, current 1919|specs,<00:07:34.960><c> what</c><00:07:35.199><c> you're</c><00:07:35.440><c> thinking</c><00:07:35.759><c> about</c> 1920| 1921|00:07:35.990 --> 00:07:36.000 align:start position:0% 1922|specs, what you're thinking about 1923| 1924| 1925|00:07:36.000 --> 00:07:37.830 align:start position:0% 1926|specs, what you're thinking about 1927|upgrading,<00:07:36.720><c> and</c><00:07:36.960><c> your</c><00:07:37.120><c> budget.</c><00:07:37.520><c> I'll</c><00:07:37.680><c> go</c> 1928| 1929|00:07:37.830 --> 00:07:37.840 align:start position:0% 1930|upgrading, and your budget. I'll go 1931| 1932| 1933|00:07:37.840 --> 00:07:39.270 align:start position:0% 1934|upgrading, and your budget. I'll go 1935|through<00:07:38.000><c> them</c><00:07:38.160><c> and</c><00:07:38.400><c> tell</c><00:07:38.560><c> you</c><00:07:38.639><c> what</c><00:07:38.960><c> actually</c> 1936| 1937|00:07:39.270 --> 00:07:39.280 align:start position:0% 1938|through them and tell you what actually 1939| 1940| 1941|00:07:39.280 --> 00:07:41.350 align:start position:0% 1942|through them and tell you what actually 1943|makes<00:07:39.520><c> sense,</c><00:07:39.840><c> what</c><00:07:40.160><c> order,</c><00:07:40.639><c> what</c><00:07:40.800><c> to</c><00:07:40.960><c> skip.</c> 1944| 1945|00:07:41.350 --> 00:07:41.360 align:start position:0% 1946|makes sense, what order, what to skip. 1947| 1948| 1949|00:07:41.360 --> 00:07:43.110 align:start position:0% 1950|makes sense, what order, what to skip. 1951|Real<00:07:41.680><c> answer</c><00:07:42.000><c> based</c><00:07:42.160><c> on</c><00:07:42.319><c> what</c><00:07:42.479><c> you</c><00:07:42.639><c> got,</c><00:07:42.960><c> not</c> 1952| 1953|00:07:43.110 --> 00:07:43.120 align:start position:0% 1954|Real answer based on what you got, not 1955| 1956| 1957|00:07:43.120 --> 00:07:44.629 align:start position:0% 1958|Real answer based on what you got, not 1959|generic<00:07:43.520><c> advice.</c><00:07:43.919><c> And</c><00:07:44.000><c> if</c><00:07:44.160><c> you</c><00:07:44.240><c> want</c><00:07:44.319><c> to</c><00:07:44.479><c> learn</c> 1960| 1961|00:07:44.629 --> 00:07:44.639 align:start position:0% 1962|generic advice. And if you want to learn 1963| 1964| 1965|00:07:44.639 --> 00:07:46.150 align:start position:0% 1966|generic advice. And if you want to learn 1967|even<00:07:44.960><c> more</c><00:07:45.120><c> about</c><00:07:45.360><c> what</c><00:07:45.599><c> are</c><00:07:45.759><c> the</c><00:07:46.000><c> most</c> 1968| 1969|00:07:46.150 --> 00:07:46.160 align:start position:0% 1970|even more about what are the most 1971| 1972| 1973|00:07:46.160 --> 00:07:48.070 align:start position:0% 1974|even more about what are the most 1975|useless<00:07:46.720><c> upgrades</c><00:07:47.120><c> for</c><00:07:47.360><c> your</c><00:07:47.520><c> setup,</c><00:07:47.919><c> check</c> 1976| 1977|00:07:48.070 --> 00:07:48.080 align:start position:0% 1978|useless upgrades for your setup, check 1979| 1980| 1981|00:07:48.080 --> 00:07:51.199 align:start position:0% 1982|useless upgrades for your setup, check 1983|out<00:07:48.240><c> this</c><00:07:48.400><c> next</c><00:07:48.639><c> video.</c> </file-view>

Based on the video captions, here's a summary of "The Only Upgrade Order That Makes Sense":

Overview

The speaker shares lessons from spending thousands on unnecessary gaming gear over 8,000 hours of tactical shooters, presenting a framework for smart upgrade decisions.

Three Questions Before Any Purchase

1. Is this solving a real problem or just a feeling?

Real problems: Mouse skips on pad, hand cramps after sessions, can't hear footsteps other players react to
Feelings: Wanting something "better" because you saw a review or your setup looks outdated
Test: Can you describe the problem in one sentence without using the word "better"?

2. What's the actual gap between what I have and what I'm buying?

Not the imagined gap, but the measurable gap
Example: RTX 5090 vs RTX 4070 in Valorant - both push 400+ FPS at 1080p low, but monitors cap at 240-360 Hz. You're paying 3x for frames you can't see
Real gap exists for streaming/4K gaming, but not for competitive play

3. Am I fixing what's actually limiting me?

Common mistake: People spend $200 on premium mouse/mousepad while their desk is 3 inches too high, causing poor ergonomics
The problem and gap are real, but you're fixing the wrong thing

Priority Order for Upgrades

1. Frames (First Priority)

If your PC drops below monitor refresh rate in fights, nothing else matters
Upgrade CPU and RAM first, GPU only if actually bottlenecked (rare in competitive games)

2. Consistency (Second Priority)

Surface: Get a quality mousepad that doesn't change with humidity/wear
Settings: Lock down sensitivity, stop tweaking constantly
Get wireless mouse or mouse bungee to eliminate cable friction

3. Information Audio (Third Priority)

If you can't hear what other players react to, you're making decisions with incomplete data
$50-80 for decent audio makes a huge competitive difference
This is the exception where the gap between bad and good stays large

4. Refinement (Last Priority)

Premium builds, weight optimization, aesthetics
Valid for personal enjoyment, but won't improve your rank
Buy with clear eyes if you want it, but don't expect performance gains

Key Insights

Most people go straight to refinement because it's fun, then wonder why nothing feels different
Premium gear isn't a scam, but you're buying refinement/materials, not performance
The upgrade order matters more than specific products
Nobody is stuck in platinum because of their mouse sensor

The video emphasizes addressing fundamental issues before spending on premium upgrades, and provides a systematic approach to identifying what actually limits your performance.