DEV Community: Leon Wong 282

The Beginner's Guide to Raycast: Replace Spotlight in 15 Minutes

Leon Wong 282 — Fri, 07 Nov 2025 13:23:56 +0000

The Beginner's Guide to Raycast: Replace Spotlight in 15 Minutes

You've probably used Spotlight thousands of times. ⌘Space, type an app name, press Enter. It works, but it's like using a bicycle when you could be driving a race car.

What if I told you there's a free Mac app that's faster than Spotlight, remembers everything you copy, lets you manage windows with your keyboard, and has 1,300+ extensions? And you can set it up in 15 minutes?

That app is Raycast, and in this beginner's guide, I'll show you exactly how to replace Spotlight and unlock productivity features you didn't know you needed. No technical skills required — just follow along.

What is Raycast? (And Why Should You Care?)

Raycast is a blazingly fast, extendable launcher for macOS. Think "Spotlight on steroids" — same basic idea, but 10x more powerful. It's built specifically for keyboard-first workflows and is completely free with a privacy-focused approach (your data stays on your Mac).

The key insight: Raycast does everything Spotlight does, plus dozens of features you'll wonder how you lived without.

Installing Raycast

Download and Install

The fastest way to install Raycast is via Homebrew. If you already have Homebrew:

brew install --cask raycast

Don't have Homebrew? No problem:

Visit raycast.com
Click "Download for Mac" (requires macOS 13+)

Tip: Remember Grant Permissions.

Replacing Spotlight (The Most Important Step)

Here's the critical decision: Don't try to use both Spotlight and Raycast. You'll split your muscle memory and never build the habit. Replace Spotlight completely.

How to Replace Spotlight:

Step 1: Disable Spotlight's hotkey

Open System Settings → Keyboard → Keyboard Shortcuts
Click "Spotlight" in the sidebar
Uncheck "Show Spotlight search" (⌘Space)

Step 2: Set Raycast to ⌘Space

Open Raycast
Press ⌘, (comma) to open Preferences
Go to General → Raycast Hotkey
Click the field and press ⌘Space
Save

Why ⌘Space is critical: Your fingers already know this shortcut from years of Spotlight. Using it for Raycast means zero retraining.

Your First 5 Minutes with Raycast

Open Raycast (⌘Space) and try these right now:

1. Launch Apps (Just Like Spotlight)

Type "chrome" → Google Chrome appears instantly

Type "mail" → Mail app

Type "vs" → VS Code (partial matching works!)

Key insight: Raycast learns your patterns. The apps you use most will show up after typing just 1-2 letters.

2. Find Files

In File Search. Type "bill" → Finds the file anywhere on your system

3. Do Calculations

Type "250 0.08" → 20* (instant result)

Type "50 USD to EUR" → Live currency conversion

Type "10 miles to km" → Unit conversion

No need to open Calculator ever again.

4. Understanding the Action Panel (⌘K)

Press ⌘K on any result to see all available actions. The Action Panel is context-sensitive — it shows different options depending on what you've selected.

On an app → Open, Quit, Show in Finder, Copy Path
On a file → Open, Open With, Move to Trash, Copy

Game-Changing Features You Can Set Up Right Now

Feature 1: Clipboard History

The problem: You copy something important, then accidentally copy over it. It's gone forever.

The solution: Raycast remembers everything you copy for 3 months.

You're writing an email and need to paste 5 different pieces of information (addresses, names, numbers). Normally, you'd copy-paste-switch-copy-paste 5 times. With clipboard history: Copy all 5 things first, then paste them in any order.

Feature 2: Text Snippets

The problem: You type the same things over and over — email signatures, addresses, greetings.

The solution: Type a short keyword and it expands to full text automatically.

Usage: Type ;sparkle anywhere (email, documents, chat) → it instantly expands to your full signature.

Feature 3: Window Management

The problem: Arranging windows by dragging is slow and imprecise.

The solution: Keyboard shortcuts that snap windows into place instantly.

Installing Your First Extension

Extensions are plugins that add new commands to Raycast. There are over 1,300 available — GitHub integration, Notion search, Spotify controls, and more.

How to browse extensions:

Open Raycast → type "store"
Press Enter to open Extension Store
Browse by category or search

Let's install Color Picker (useful for everyone):

Search for "Color Picker" in the Store
Click Install
Usage: ⌘Space → type "color picker" → click anywhere on your screen to grab that color

Other beginner-friendly extensions:

Emoji — Search and insert emoji faster than Character Viewer
Calendar — View today's schedule without opening Calendar app
Spotify — Control music without switching windows

Many extensions require API keys or account connections. Don't worry — each extension guides you through setup with clear instructions.

You're Now a Raycast User

In the last 15 minutes, you've transformed your Mac into a productivity powerhouse.

The bottom line: You've spent 15 minutes that will save you hours every month. Raycast isn't just a better Spotlight — it's a complete rethinking of how you interact with your Mac.

Once Raycast feels natural (give it a week), explore advanced features like Script Commands, AI integration (Raycast Pro), and custom themes.

What's your favorite Raycast feature so far? Drop a comment below — I'm genuinely curious which feature clicked for you first. For me, it was clipboard history. I recovered important text I'd accidentally copied over, and I was sold forever.

If this guide helped you discover Raycast, share it with a friend who's still using plain Spotlight. They'll thank you for the productivity upgrade.

Related Resources

Official Raycast Manual — Comprehensive documentation
Raycast Extension Store — Browse all 1,300+ extensions

Welcome to the world of keyboard-driven productivity. You're going to love it here. ⚡️

Installing MySQL 8.0 on macOS with Homebrew: A Complete Guide

Leon Wong 282 — Thu, 06 Nov 2025 11:32:14 +0000

Installing MySQL 8.0 on macOS with Homebrew: A Complete Guide

Introduction

Recently, I needed to set up a development environment on my Mac and chose to use Homebrew to install MySQL 8.0. The process was smoother than expected, so I'm sharing the complete installation steps and some practical tips here.

Prerequisites

Make sure Homebrew is already installed on your system. If not, run this command in Terminal:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Installation Steps

1. Update Homebrew

First, update Homebrew to the latest version:

brew update

2. Install MySQL 8.0

Run the following command to install MySQL 8.0:

brew install mysql@8.0

The installation process will automatically download and configure MySQL, usually taking a few minutes. Homebrew automatically handles environment variable configuration, so you can use the mysql command directly after installation.

3. Start MySQL Service

There are two ways to start the MySQL service:

Option 1: Start immediately (without auto-start on boot)

brew services start mysql@8.0

Option 2: Manual start

mysql.server start

4. Security Configuration

Run MySQL's security configuration script:

mysql_secure_installation

This script will guide you through the following configurations:

Set root password
Remove anonymous users
Disallow root login remotely
Remove test database
Reload privilege tables

It's recommended to select "Yes" for all options to enhance security.

Verify Installation

Log into MySQL

Enter the password you just set to log in.

mysql -u root -p

Option: DataGrip config

If you prefer to operate the database using a GUI tool, you can configure the DataGrip connect MySQL.

Common Commands

Service Management

# Start service
brew services start mysql@8.0

# Stop service
brew services stop mysql@8.0

# Restart service
brew services restart mysql@8.0

# Check service status
brew services list

Connect to MySQL

# Connect as root user
mysql -u root -p

# Connect to specific database
mysql -u root -p database_name

# Specify host and port
mysql -h localhost -P 3306 -u root -p

Uninstalling MySQL

If you need to uninstall:

# Stop service
brew services stop mysql@8.0

# Uninstall
brew uninstall mysql@8.0

# Delete data (optional)
rm -rf /opt/homebrew/var/mysql

Conclusion

Installing MySQL 8.0 with Homebrew is very straightforward - the entire process requires just a few commands. Homebrew automatically handles dependencies and configuration, making it much easier than manual installation. Remember to complete the security configuration after installation, and you're ready to start using MySQL!

I hope this tutorial helps! Feel free to share in the comments if you encounter any other issues.

What I Wish I Knew About Homebrew Before Wasting 2 Hours Troubleshooting

Leon Wong 282 — Sat, 25 Oct 2025 04:01:26 +0000

What I Wish I Knew About Homebrew Before Wasting 2 Hours Troubleshooting

Last Tuesday, I decided to finally install Homebrew on my new MacBook to create a testing environment for writing blog posts. I'd heard it was the "must-have" tool for Mac developers. The installation looked simple enough—copy a command, paste it into Terminal, wait a few minutes. Easy, right?

Thirty minutes later, I was staring at brew: command not found errors. An hour after that, I'd accidentally broken my entire setup with sudo and was desperately Googling "how to fix Homebrew permissions." By hour two, I was questioning every life choice that led me to this moment.

The frustrating part? Every single issue I hit was completely preventable. They're mistakes that thousands of beginners make every day, and they all have simple fixes—if you know what to look for.

If you just installed Homebrew and it's not working, or you're stuck in troubleshooting hell right now, this guide will save you hours. I'm sharing the 5 critical mistakes I made so you don't have to make them too.

Mistake #1: Not Adding Homebrew to Your PATH

The symptom: You successfully install Homebrew, but typing brew install git gives you brew: command not found.

This is the #1 issue beginners face, and it's especially common if you have an Apple Silicon Mac (M1, M2, M3, or M4).

Why it happens:

On Intel Macs, Homebrew installs to /usr/local/bin, which is already in your system's PATH. Your Terminal knows to look there for commands, so everything works automatically.

On Apple Silicon Macs, Homebrew installs to /opt/homebrew/bin instead. This location is not in your PATH by default. When you type brew, your Terminal has no idea where to find it.

During installation, Homebrew displays a message telling you to add it to your PATH. But it's buried in a wall of installation text that most people skim past. I know I did.

The 2-minute fix:

Copy these two lines into your Terminal and press Enter after each:

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

What this does: The first line adds Homebrew to your shell configuration file permanently. The second line activates it immediately without restarting Terminal.

Verify it worked:

brew --version

If you see Homebrew 4.x.x, you're golden. If not, close Terminal completely (Command + Q) and open it again.

Pro tip: This is only needed on Apple Silicon Macs. If you have an older Intel Mac and brew isn't working, the problem is something else—jump to Mistake #2.

Mistake #2: Using `sudo` with Homebrew (The Fatal Error)

The symptom: You see "Permission denied" errors and decide to add sudo to your command. It seems to work... until everything breaks.

This is the mistake I regret most. It took me an hour to undo the damage.

Why beginners do this:

On Linux, when you see permission errors, you typically add sudo to run commands as administrator. It's muscle memory for anyone with a bit of Unix experience.

So when Homebrew shows a permission error, your instinct is: "Ah, I need admin privileges. Let me try sudo brew install git."

Why this is catastrophic:

Homebrew is designed to run without sudo. When you use sudo, you create files and directories owned by root (the superuser) instead of your user account.

Now your Homebrew installation is partly owned by you and partly owned by root. Future Homebrew commands fail because they can't modify root-owned files. And the errors snowball from there.

I spent 45 minutes fixing permission issues because of one sudo brew command.

The iron-clad rule:

# ❌ NEVER do this:
sudo brew install git
sudo brew update
sudo anything-with-brew

# ✅ ALWAYS do this:
brew install git
brew update

If you already used sudo, here's how to fix it:

sudo chown -R $(whoami) /opt/homebrew/*

This resets ownership of all Homebrew files back to your user account. Then run brew doctor (more on that in Mistake #3) to verify everything is fixed.

What I wish I knew: Homebrew manages its own permissions elegantly. If you see permission errors, it means something is already wrong with your setup—not that you need sudo. The correct first step is always brew doctor, not sudo.

Mistake #3: Ignoring `brew doctor` Warnings

The symptom: Homebrew works sometimes but gives weird errors. Software installs but doesn't run correctly. You're not sure if things are actually broken or just quirky.

Why it happens:

Most beginners don't know that Homebrew includes a built-in diagnostic tool. They only discover brew doctor after Googling errors for 30 minutes.

Even when you run it and see warnings, it's tempting to ignore them if things seem to be working. I did this. The warnings felt like suggestions, not requirements.

They're not suggestions.

The preventive fix:

brew doctor

This single command diagnoses 90% of Homebrew issues. It checks your installation, identifies problems, and tells you exactly how to fix them.

What you might see:

Warning: "You have unlinked kegs in your Cellar"

What it means: A package is installed but not accessible in your PATH
Fix: brew link <package-name>

Warning: "You have not agreed to the Xcode license"

What it means: Apple's Command Line Tools need license acceptance
Fix: sudo xcodebuild -license then type "agree"

Warning: "Config scripts exist outside your system"

What it means: You have conflicting installations from other package managers
Fix: Follow the specific instructions Homebrew provides

When to run brew doctor:

Immediately after installing Homebrew
After installing any complex package (like Python or Node.js)
Any time something doesn't work as expected
Monthly, as part of your maintenance routine

If brew doctor says "Your system is ready to brew," you're good. If not, read every warning and fix them in order. Don't skip any.

What I wish I knew: Running brew doctor before I tried random Stack Overflow fixes would've pointed me directly to the PATH issue and saved me two hours.

Mistake #4: Not Understanding Formulae vs Casks

The symptom: Error: No available formula with the name "visual-studio-code" even though you know VSCode is available through Homebrew.

Or you install something and can't figure out where it went or how to launch it.

Why it happens:

Homebrew has two types of packages:

Formulae are command-line tools that get compiled and installed. Think: git, python, wget, node.

Casks are GUI applications that get downloaded as pre-built apps. Think: visual-studio-code, firefox, slack, zoom.

The command syntax is different, and beginners constantly forget the --cask flag.

The fix:

For command-line tools (formulae):

brew install git
brew install python
brew install wget

For GUI applications (casks):

brew install --cask visual-studio-code
brew install --cask firefox
brew install --cask slack

How to check which type you need:

brew search visual-studio-code

The output shows whether it's in "Formulae" or "Casks." If it says Casks, you need the --cask flag.

Rule of thumb: If you want something with a graphical interface that normally lives in your Applications folder, you almost always need --cask. Command-line tools never need it.

What I wish I knew: I wasted 15 minutes trying to install VSCode without --cask, convinced the package name was wrong. A quick brew search would've told me exactly what I needed.

Mistake #5: Skipping the Caveats

The symptom: Software installs successfully, but when you try to use it, nothing happens. Or it works but not the way you expected.

Why it happens:

After installing a package, Homebrew displays "Caveats"—important post-installation instructions. These often include:

Commands to add the tool to your PATH
How to start services (like databases)
Configuration steps required before first use
Version-specific warnings

Beginners see a wall of text, assume it's optional, and close Terminal. Or they don't scroll back up to read what was printed 50 lines ago.

Example caveat that breaks things if ignored:

==> Caveats
To start mysql now and restart at login:
  brew services start mysql

Or, if you don't want to run it as a service:
  mysql.server start

If you don't run one of these commands, MySQL is installed but not running. You'll get "connection refused" errors and think the installation failed.

The fix:

After every installation, scroll back and read the caveats. Actually read them, word by word. If they tell you to run a command, run it.

Viewing caveats later:

brew info <package-name>

This shows the package information including all caveats, even if you closed Terminal hours ago.

What I wish I knew: Those caveats aren't suggestions or nice-to-know tips. They're required steps to make the software actually work. Treat them like installation instructions, not optional reading.

Bonus Mistake: Forgetting to Update

The symptom: Packages you know exist show "formula not found" errors. Or you install outdated versions with known security issues.

Why it happens:

Homebrew's package definitions live in a Git repository. Over time, they get stale on your local machine. New packages aren't visible, and version information gets outdated.

The fix:

brew update

Run this before installing anything new. It takes 5-30 seconds and updates Homebrew itself plus all package definitions.

Make it a habit: Update weekly as part of your maintenance routine:

brew update && brew upgrade && brew cleanup

This updates definitions, upgrades all installed packages, and removes old versions to free disk space.

The 5-Minute Troubleshooting Checklist

When Homebrew isn't working, run these commands in order:

# 1. Is Homebrew in your PATH?
which brew

# 2. What's wrong?
brew doctor

# 3. Are your package definitions current?
brew update

# 4. Is the specific package available?
brew search <package-name>

# 5. Check ownership (Apple Silicon)
ls -la /opt/homebrew | head

90% of the time, brew doctor identifies the exact problem and tells you how to fix it.

Key Takeaways

Two hours of troubleshooting taught me what five minutes of preparation could have prevented:

Add Homebrew to your PATH (Apple Silicon Macs require manual setup)
Never use sudo with Homebrew commands (it breaks permissions permanently)
Run brew doctor first, Google second (diagnostics before desperation)
Use --cask for GUI apps (VSCode, Firefox, Slack need this flag)
Read the caveats every time (they're required steps, not optional)

The pattern is always the same: skip the setup instructions, ignore the warnings, spend hours troubleshooting what could've been prevented in minutes.

Next steps:

Run brew doctor right now (even if things seem to work)
Bookmark this guide for when you hit issues
Read the official Homebrew documentation for deeper understanding

What was your biggest Homebrew mistake? I'd love to hear if you've hit these same issues or discovered other gotchas I missed. Drop a comment below.

Related Resources

How I Stopped Manually Installing Software on Mac (And You Should Too) — Complete Homebrew tutorial for beginners
Why Your Mac Software Installation is Broken (And How to Fix It in 10 Minutes) — Why package managers matter
Homebrew Official Documentation — Full command reference and guides

Why Your Mac Software Installation is Broken (And How to Fix It in 10 Minutes)

Leon Wong 282 — Fri, 24 Oct 2025 06:18:20 +0000

Why Your Mac Software Installation is Broken (And How to Fix It in 10 Minutes)

Last Saturday, I watched my friend spend four hours setting up his new MacBook Pro. Four. Hours.

He wasn't doing anything complicated. Just installing the basics: Chrome, Slack, VSCode, Zoom, Docker, Git — maybe 20 apps total. The same apps he had on his old machine.

But each one required the same painful ritual: Google the name, hope the first result isn't malware, download, wait, open the DMG, drag to Applications, eject, delete the installer. Then do it all over again.

By hour three, he looked at me and asked: "There has to be a faster way to do this, right?"

The truth is, there is. And the fact that most Mac users don't know about it reveals something most people never realize: your Mac's software installation process is fundamentally broken.

It's not your fault. Apple designed it this way. But here's what they won't tell you: you're probably wasting 30+ hours per year on software installation and updates. Hours you could spend doing literally anything else.

In the next 7 minutes, I'll show you exactly what's broken about how you install software, why it's costing you time and creating security risks, and a 10-minute fix that solves it permanently.

What "Normal" Installation Actually Costs You

Let's talk about what you're really doing when you install software the "normal" way.

Problem 1: The Security Roulette Game

Every time you Google "install [app name]," you're playing Russian roulette with malware.

Type "download Chrome" into Google right now. You'll see ads for chrome-download.com, downloadchrome.com, and a dozen other sites that aren't Google. Some are legitimate mirrors. Others bundle adware. Some are straight-up malware.

My friend learned this the hard way last month. Downloaded "Chrome" from what looked like an official site. Got Chrome plus three browser extensions he didn't ask for and a "system optimizer" that was actually spyware.

The hidden cost: 10+ minutes per app verifying you're on the real website, plus the risk of spending hours cleaning up malware if you guess wrong.

Problem 2: The Dependency Black Hole

Some software needs other software to work. But they won't tell you this upfront.

Try installing Python from python.org. It'll work. Then you try to use it and get an error about missing Xcode Command Line Tools. So you Google that, find a 500MB download, wait 20 minutes for it to install, and finally Python works.

Or try installing ffmpeg manually. I'll wait. You'll need 12+ dependencies, each with its own website, download, installation process, and cryptic README file explaining which other dependencies you need first.

The hidden cost: 1-2 hours minimum troubleshooting "why doesn't this work?" and hunting down dependencies.

Problem 3: The Update Nightmare

Quick question: When was the last time you updated all your software?

Chrome nags you with a red dot every week. VSCode shows a badge. Slack slides in a banner. But Git? Node? Python? They just sit there, silently outdated, with security vulnerabilities piling up.

Each app updates differently:

Some auto-update in the background
Some require you to download a new installer and repeat the whole process
Some don't tell you updates exist at all

The hidden cost: 20-30 minutes every month clicking through individual app updaters, or running old, insecure software because updating is too annoying.

Problem 4: The Version Chaos

Pop quiz: Which version of Python is installed on your Mac right now?

If you said "I don't know" or "There's more than one?!", you're not alone. Most Mac users have multiple versions of the same software scattered around their system, with no idea which one runs when they double-click.

Three Python versions in different locations. Old apps forgotten in the Applications folder. Adobe trials you installed once in 2019. No way to track what you actually have or which versions conflict with each other.

The hidden cost: 15+ minutes diagnosing "it worked yesterday" problems when version conflicts break things.

Problem 5: The Downloads Folder Graveyard

Check your Downloads folder right now. I'll bet you $20 there are .dmg and .pkg files in there from software you installed six months ago.

Firefox 118.dmg. VSCode-darwin.zip. Docker.dmg. Zoom.pkg. Each one is 50-500MB. You're never going to use them again, but they're just sitting there, wasting gigabytes of disk space.

You have two choices: spend an hour manually cleaning them out, or live with eternal clutter.

The hidden cost: Wasted disk space and mental clutter from a folder that looks like a software graveyard.

These aren't edge cases. This is the standard Mac experience. But here's what most people don't know...

The Tool Mac Should've Included (But Didn't)

If you've ever used Linux, you know about package managers. Type apt install firefox or yum install git and boom — software installs automatically, with all dependencies, from verified sources.

Windows doesn't have a great package manager either. But at least they're working on one (winget).

macOS? You get the Mac App Store. Which is fine for consumer apps, but it's missing 90% of the software developers use and doesn't give you control over versions or updates.

What's a Package Manager?

Think of it like an App Store, but:

It has everything (not just what Apple approves)
It's controllable from your keyboard (no clicking through GUIs)
It handles updates all at once (not app-by-app)
It tracks versions and dependencies automatically

Here's the secret every Mac developer knows: there's been a free, open-source package manager for Mac since 2009. It's called Homebrew, it's maintained by thousands of contributors, and it solves every problem I just described.

Why haven't you heard of it?

Because it requires using Terminal. And Terminal scares people.

But here's the truth: you don't need to be a developer to use it. If you can copy and paste, you can fix your installation process forever.

How to Never Manually Download Software Again

Let me show you what Homebrew actually does.

Before Homebrew:

Google → Find website → Download → Wait → Open installer → Drag to Applications → Eject → Delete installer → Repeat × 20

After Homebrew:

Type brew install firefox → Press Enter → Done.

That's it. One command. From verified sources. With all dependencies. In seconds.

Real numbers from my friend's setup:

Installing 15 apps manually: 1 hour 45 minutes
Installing 15 apps with Homebrew: 2 minutes 30 seconds

Here's how to set it up in 10 minutes.

The 10-Minute Setup

Step 1: Open Terminal (1 minute)

Press Command + Space, type "Terminal", press Enter.

A window with a black background will open. Don't panic — you're just going to copy and paste two things. That's literally it.

Step 2: Install Homebrew (3 minutes)

Copy this command and paste it into Terminal:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Press Enter. It'll ask for your Mac password (the one you use to log in). Type it and press Enter again.

You'll see text scrolling by. That's normal. It's downloading and installing Homebrew. Takes 2-3 minutes.

Important: If you have an M1, M2, M3, or M4 Mac (Apple Silicon), Terminal will show you one more command to copy at the end. It looks like this:

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

Copy and paste that too. This adds Homebrew to your system's PATH so it actually works.

Step 3: Verify It Works (1 minute)

Type this and press Enter:

brew doctor

If you see "Your system is ready to brew", you're golden. If not, the error message will tell you exactly how to fix it.

Step 4: Install Your First Apps (5 minutes)

Now for the fun part.

To install GUI applications (the ones you're used to):

brew install --cask firefox
brew install --cask visual-studio-code
brew install --cask slack

To install command-line tools:

brew install git
brew install wget

Want to install multiple apps at once?

brew install --cask firefox google-chrome visual-studio-code slack zoom rectangle

What just happened:

You installed 6 applications in about 60 seconds. All from official sources. No clicking through installers. No dragging to Applications. No Downloads folder mess.

When my friend saw this, his exact words were: "You're telling me I could've done this in 5 minutes instead of 4 hours?"

Yes. Yes, I am.

The Commands You'll Actually Use

You don't need to memorize 50 commands. Here are the five that cover 90% of daily use:

Search for software:

brew search chrome

Install software:

brew install --cask firefox

Update everything at once:

brew update        # Updates Homebrew itself
brew upgrade       # Upgrades all your apps

Remove software:

brew uninstall firefox

Clean up old versions (free disk space):

brew cleanup

My weekly routine (takes 2 minutes):

brew update && brew upgrade && brew cleanup

That's it. One command, once a week, and everything stays updated.

Compare that to clicking through 20 individual app updaters.

What This Actually Fixes

Let's do a reality check on what just changed:

Security: Homebrew only downloads from official sources. No more sketchy download sites, no more wondering if you're getting malware.

Dependencies: Installing ffmpeg? Homebrew automatically installs all 12 dependencies in the right order. You just get working software.

Updates: One command updates everything. Not Chrome's updater, then VSCode's, then Slack's. One command. Two minutes. Weekly.

Versions: Homebrew tracks everything. Type brew list and see exactly what's installed. No more mystery software lurking in your Applications folder.

Disk Space: No installer pile-up in Downloads. Homebrew cleans up automatically with brew cleanup.

Last week I got a new MacBook. Using Homebrew, I installed everything I needed in 8 minutes. My colleague doing it the "normal" way took 3 hours. We installed the same 25 apps.

But here's the bigger win: It's not just about speed.

It's about confidence. No more wondering if you downloaded from the right site. No more mystery errors about missing dependencies. No more update anxiety.

The 10 Minutes That Saves You 30 Hours

Let's be honest about what we're talking about here:

Before: Hours of downloading, clicking, dragging, deleting. Repeated every time you get a new machine or need new software.

After: One command per app. Updates in 2 minutes weekly. Setup that works forever.

Time saved: 30+ hours per year. That's not an exaggeration — that's adding up 5 minutes per app across 20 apps, plus monthly updates, plus troubleshooting dependencies.

I know what you're thinking: "But I'm not technical..."

Here's the thing: Neither was I when I started. And you're already doing harder things. Manually managing 20+ apps with different update mechanisms and dependency requirements is objectively more complex than typing brew install firefox.

The only skill you need is copy-paste.

The real question isn't "Should I learn this?"

It's "Why didn't anyone tell me this existed?"

Key Takeaways

Mac's default installation process wastes hours and creates security and dependency risks
Package managers like Homebrew solve this completely and automatically
Setup takes 10 minutes and works forever
This isn't just for developers — it's for anyone who installs software

Ready to fix this?

Open Terminal right now (5 seconds)
Go to brew.sh and copy the installation command
Paste it and press Enter
In 10 minutes, you'll wonder why you waited this long

Now I'm curious: What's the first app you'll install with Homebrew? And how long did it take you to install it the old way? Drop a comment below — I want to hear your horror stories about manual installation.

Related Posts:

How I Stopped Manually Installing Software on Mac (And You Should Too) — Complete Homebrew tutorial with more examples

Resources:

Official Homebrew Website — Installation and documentation
Homebrew Package Search — Browse 6,000+ available packages

The Complete Beginner's Guide to Cloudflare R2 Image Hosting (2025)

Leon Wong 282 — Thu, 23 Oct 2025 09:44:40 +0000

The Complete Beginner's Guide to Cloudflare R2 Image Hosting (2025)

Are you paying $15-30 per month for image hosting? Or worse—relying on free services that might delete your images without warning?

I spent months testing image hosting solutions for my blog. Some were too expensive. Others were unreliable. A few just disappeared overnight, taking my images with them.

Then I discovered Cloudflare R2.

R2 gives you 10GB of storage, unlimited bandwidth, and global CDN delivery—completely free. No credit card required. No hidden fees. No bandwidth charges that spiral out of control when your blog gets popular.

In this guide, I'll walk you through setting up R2 step-by-step, even if you've never touched cloud storage before. By the time you finish reading, you'll have professional-grade image hosting running—the same infrastructure big companies pay thousands for.

15 minutes from now, your images will be hosted globally and loading fast for readers anywhere in the world.

What Makes R2 Different (And Why It Matters for Your Blog)

Let's start with the basics. Cloudflare R2 is object storage—think of it as a hard drive in the cloud that's accessible via web URLs.

When you upload an image to R2, you get a permanent URL you can use anywhere: your blog, GitHub documentation, social media, forum posts. The image loads fast because Cloudflare's global CDN (Content Delivery Network) automatically caches it at edge servers worldwide.

Here's what makes R2 special for bloggers:

✅ Free tier is genuinely generous

✅ Zero bandwidth costs

✅ Global CDN included

✅ No coding required

✅ Professional-grade reliability

How R2 Compares to Alternatives

Service	Free Tier	Stability	Bandwidth Costs
Imgur	Unlimited	May delete images	Free
AWS S3	5GB (12 months)	Excellent	$$$ Expensive
Google Drive	15GB	Good	Slow, not designed for this
Cloudflare R2	10GB forever	Excellent	$0 (unlimited)

Convinced? Let's set it up.

Prerequisites (Don't Worry—It's Easier Than You Think)

Before we dive in, here's what you'll need:

1. A Cloudflare account (free—I'll show you how to create one)

2. A custom domain (optional but recommended—any domain you own works)

3. 10 minutes of your time

Don't have a domain yet? No problem. You can start with R2's default URLs and add a custom domain later. The free tier works either way.

Never used Cloudflare before? Perfect. This guide assumes zero prior knowledge. I'll explain everything as we go.

Setting Up Your R2 Image Hosting (The Complete Walkthrough)

Step 1: Create Your Cloudflare Account

Head to cloudflare.com and click Sign Up in the top right corner.

Enter your email and create a password. Cloudflare will send you a verification email—click the link to activate your account.

That's it. No credit card required. No trial period that converts to a paid plan.

Step 2: Enable R2

Once you're logged in, look at the left sidebar. Scroll down and click R2.

You'll see a button that says "Purchase R2 Plan" or "Get Started." Don't panic—the free plan is actually free. Cloudflare just uses confusing terminology.

Click the button. Add payment information.

You now have R2 enabled on your account.

Step 3: Create Your First Bucket

In R2 terminology, a bucket is like a folder in the cloud. It holds all your images.

Click Create bucket in the R2 dashboard.

Choose a bucket name. This needs to be unique globally (across all Cloudflare users), lowercase, with no spaces. Use hyphens for readability.

Examples:

my-blog
leonwong282-cdn
techblog-assets

Select a location. Choose Automatic unless you have a specific reason to pick a region. Cloudflare will optimize placement for performance.

Click Create bucket.

🎉 Your bucket is live. Now let's make it accessible from the web.

Step 4: Connect a Custom Domain (Optional but Recommended)

This step makes your images accessible at clean URLs like images.yourdomain.com/photo.jpg instead of ugly default URLs.

If you don't have a domain yet, skip this step for now. You can always add it later.

If you have a domain:

In your bucket settings, click the Settings tab
Scroll to Public Access and click Connect Domain
Enter a subdomain—I recommend images.yourdomain.com or cdn.yourdomain.com
Click Connect domain

Cloudflare automatically handles everything:

Creates the DNS records
Provisions an SSL certificate (HTTPS)
Enables CDN caching

Wait 2-5 minutes for DNS to propagate worldwide. Grab a coffee.

Why custom domains matter:

Professional appearance
You control the URLs (if you switch providers, you keep your domain)
Better for SEO (search engines see your domain, not Cloudflare's)

Alternative: R2 provides default .[r2.dev](http://r2.dev) URLs that work immediately if you just want to test.

Getting Images Into R2 (Three Easy Methods)

Your R2 bucket is ready. Now let's upload images.

Method 1: Dashboard Upload (Simplest)

This is perfect if you're just getting started or uploading occasionally.

Go to your bucket in the R2 dashboard
Click the Upload button
Drag and drop images (or click to browse)

Your files are instantly available at:

https://images.yourdomain.com/filename.jpg

Like this:

That's it. No processing time. No compression. Instant.

Best for: Beginners, one-off uploads, testing

Method 2: Using an Upload Tool (Recommended for Regular Use)

If you blog regularly, manually visiting the dashboard gets tedious fast. Upload tools solve this.

Example: PicGo

These tools add a keyboard shortcut to your system. Take a screenshot, press the hotkey, and the image uploads automatically to R2. The URL copies to your clipboard instantly.

Best for: Regular bloggers, Markdown writers, content creators

I'll write a separate guide on configuring these tools with R2. For now, just know they exist.

Method 3: Command Line (Advanced—Skip if Intimidated)

Developers can use Cloudflare's Wrangler CLI to upload images from the terminal or automate uploads with scripts.

If you're not comfortable with command-line tools, ignore this method entirely. Methods 1 and 2 handle 99% of use cases.

Best for: Developers who want automation

How to Actually Use Your Images (In Blogs, Markdown, HTML)

Now that your images are uploaded, here's how to use them everywhere.

In Markdown:

![Description of image]([https://images.yourdomain.com/my-photo.jpg](https://images.yourdomain.com/my-photo.jpg))

In HTML:

<img src="[https://images.yourdomain.com/my-photo.jpg](https://images.yourdomain.com/my-photo.jpg)" alt="Description">

In WordPress, Ghost, or Medium:

Just paste the image URL when adding an image block. The platform fetches it automatically.

Organization Tips

As your image library grows, folders keep things sane.

Create folders in your bucket using forward slashes in filenames:

/blog/2025/january/screenshot.jpg
/social/twitter-banner.jpg
/thumbnails/post-01.jpg

Your URLs become:

https://images.yourdomain.com/blog/2025/january/screenshot.jpg

💡

Pro tip: Name your images descriptively. Use homebrew-terminal-screenshot.png instead of IMG_0234.png. It's better for SEO, and future you will thank present you when searching for a specific image.

How to Stay Within the Free Tier (And When You'd Ever Need to Pay)

Let's talk about limits. The R2 free tier includes:

✅ 10GB storage = ~10,000 typical blog images (assuming 1MB each)

✅ Unlimited downloads = Seriously. No bandwidth charges. Ever.

✅ 1 million upload operations per month = Unless you're uploading thousands of images daily, you'll never hit this.

Real-World Cost Examples

Small blog (1,000 visitors/month):

Cost: $0

Medium blog (10,000 visitors/month):

Cost: $0

Large blog (100,000 visitors/month):

Cost: Still probably $0

You'd only pay if you exceed 10GB of storage. Even then, it's only $0.015 per GB per month—incredibly cheap.

For context: a typical blog screenshot is 200-500KB. A high-quality photo is 2-3MB. You'd need to upload thousands of images to hit 10GB.

Most bloggers never pay a cent.

Conclusion: Your Images Are Now Hosted Professionally

In just 15 minutes, you've set up image hosting that would cost $15-30 per month elsewhere—completely free.

Key takeaways:

✅ R2 gives you 10GB of free storage and unlimited bandwidth

✅ Setup takes 10-15 minutes with no coding required

✅ Works with any blog platform, Markdown editor, or website

✅ Professional-grade reliability backed by Cloudflare's global infrastructure

Start uploading your images to R2 today and stop worrying about hosting costs, bandwidth limits, or broken image links.

What image hosting solution are you currently using? Have you tried R2? Let me know in the comments—I'd love to hear about your experience!

Related Resources

Want to explore other image hosting options? Check out my comprehensive guide: Image Hosting for Markdown: The Complete Guide to Picture Beds

Official documentation: Cloudflare R2 Documentation

Tags: Cloud Storage, Cloudflare, Web Development, Blogging, Tutorial

How I Stopped Manually Installing Software on Mac (And You Should Too)

Leon Wong 282 — Wed, 22 Oct 2025 09:11:34 +0000

Last month, I spent three hours setting up my new MacBook. Download Chrome. Wait. Drag to Applications. Open the DMG. Delete the installer. Download VSCode. Repeat. Download Git. Wait, where's the installer? Google "install git mac." Find a sketchy website. Download. Run installer. Click through 12 screens. Repeat this 15 more times.

By hour three, I was exhausted, my Downloads folder was a mess, and I wasn't even sure which versions I'd installed. Then my developer friend saw what I was doing and laughed. "You're doing it the hard way," he said. "Let me show you something."

That something was Homebrew — and it changed everything about how I manage software on my Mac.

In this guide, I'll show you how to install and use Homebrew to install any software with a single command, keep everything updated automatically, and never manually download another .dmg file again. If you spend more than 5 minutes installing software, this is for you.

The Problem: Why Manual Installation is Broken

Before Homebrew, my software installation workflow looked like this:

For every single application:

Google "[app name] download mac"
Hope the first result is the official website (not an ad or malware)
Navigate to the downloads page
Choose the right version (Intel? Apple Silicon? What's the difference?)
Wait for the download
Open the .dmg or .pkg file
Drag the app to Applications (or click through an installer)
Eject the disk image
Delete the installer from Downloads
Remember to check for updates manually later

The real problems:

Time-consuming: 5-10 minutes per application, 15 applications = over an hour
Error-prone: Wrong versions, outdated downloads, missing dependencies
Cluttered: Downloads folder filled with installers I'd forget to delete
Update nightmare: No way to update everything at once; have to check each app individually
No consistency: Every app has a different installation process
Dependency hell: Some tools require other tools first (Python needs Xcode, Node needs specific libraries)

The breaking point came when I tried to install ffmpeg (a video processing tool). The instructions said "install these 12 dependencies first." Each dependency had its own installation process. After an hour of troubleshooting, I still couldn't get it working.

There had to be a better way.

The Solution: Meet Homebrew

What is Homebrew?

Homebrew is a free, open-source package manager for macOS (think of it as an app store for developers, but way more powerful). Instead of hunting down software on websites, you install everything through simple terminal commands.

One command replaces the entire 10-step process above:

brew install visual-studio-code

That's it. Homebrew:

Downloads the software from the official source
Installs it to the right location
Handles all dependencies automatically
Creates shortcuts so it "just works"
Tracks versions for easy updates

The transformation:

Before Homebrew: 15 apps × 7 minutes = 1 hour 45 minutes

After Homebrew: 15 apps × 10 seconds = 2 minutes 30 seconds

That's not an exaggeration — I timed it.

"But I'm not a developer. Isn't the terminal scary?"

I thought so too. But you don't need to be technical to use Homebrew. If you can copy and paste, you can use Homebrew. I'll show you exactly what to do.

Getting Started: Install Homebrew in 5 Minutes

Step 1: Open Terminal

Press Command + Space, type "Terminal", and press Enter. A window with a black background will open. Don't panic — this is where the magic happens.

Step 2: Install Homebrew

Copy this entire command and paste it into Terminal (Command + V), then press Enter:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

What will happen:

You'll be prompted to enter your Mac password (the one you use to log in)
The installation will download and set up Homebrew (takes 2-5 minutes)
You'll see text scrolling by — that's normal!

Important: If you have an Apple Silicon Mac (M1, M2, M3, M4), you'll need to run one more command when installation finishes. Terminal will show you exactly what to paste — it looks like this:

echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' >> ~/.zprofile
eval "$(/opt/homebrew/bin/brew shellenv)"

Step 3: Verify It Works

Type this command and press Enter:

brew --version

If you see something like "Homebrew 4.x.x", congratulations! You're ready to go.

Step 4: Run a Health Check

Homebrew includes a built-in diagnostic tool. Run:

brew doctor

If it says "Your system is ready to brew," you're all set. If it shows warnings, don't worry — it usually suggests how to fix them.

⚠️ Troubleshooting: If you see "brew: command not found," close Terminal completely (Command + Q) and open it again. If it still doesn't work, run the Apple Silicon command from Step 2 again.

Your First Apps: Install Software in Seconds

Now for the fun part. Let's install some popular applications using Homebrew.

Installing Command-Line Tools

These are utilities you run in Terminal:

# Install Git (version control)
brew install git

# Install wget (download files from the internet)
brew install wget

# Install tree (visualize folder structures)
brew install tree

Each installation takes 5-30 seconds. No clicking, no dragging, no mess.

Installing Regular Applications

Homebrew can also install the GUI apps you're used to (browsers, editors, etc.) using something called "casks":

# Install Google Chrome
brew install --cask google-chrome

# Install Visual Studio Code
brew install --cask visual-studio-code

# Install Slack
brew install --cask slack

# Install Firefox
brew install --cask firefox

The --cask flag tells Homebrew you want a graphical application, not a command-line tool.

Install Multiple Apps at Once

Want to set up everything in one shot? Just list them all:

brew install --cask google-chrome firefox visual-studio-code slack rectangle iterm2

What just happened?

In 60 seconds, you installed 6 applications that would've taken 30-45 minutes manually. They're all in your Applications folder, ready to use.

Last week, my friend got a new MacBook. Using a list of Homebrew commands I gave them, they installed everything they needed in under 10 minutes. Compare that to the 2-3 hours it used to take.

The Game-Changer: Updates in One Command

Here's where Homebrew truly shines: keeping software updated.

The old way:

Open Chrome → "Update available" → Download → Install → Restart
Open VSCode → "Update available" → Download → Install → Restart
Repeat for every single application
Total time: 20-30 minutes every few weeks

The Homebrew way:

# Update all software at once
brew upgrade

One command. Every app. Updated simultaneously.

My weekly routine (takes 2 minutes):

# See what's outdated
brew outdated

# Update everything
brew upgrade

# Clean up old versions (free disk space)
brew cleanup

Real results:

Last week, I had 12 outdated apps
brew upgrade updated all of them in 90 seconds
brew cleanup freed 3.2GB of disk space from old installers

Before Homebrew: 30 minutes of manual updates monthly

After Homebrew: 2 minutes, once a week

Essential Commands You'll Actually Use

You don't need to memorize dozens of commands. These five cover 90% of daily use:

1. Search for software

brew search chrome

Not sure if an app is available? Search for it.

2. Install software

brew install git                    # Command-line tool
brew install --cask firefox         # GUI application

3. See what's installed

brew list

4. Update everything

brew update    # Update Homebrew itself
brew upgrade   # Upgrade all apps

5. Remove software

brew uninstall git
brew uninstall --cask firefox

💡 Pro tip: Create a text file with all your favorite apps. When you get a new Mac, run all the install commands at once:

brew install --cask google-chrome firefox visual-studio-code slack zoom rectangle
brew install git wget curl tree htop

Bookmark that file. You'll thank me later.

Common Beginner Questions

"Is Homebrew safe?"

Yes. It's open-source, maintained by thousands of developers, and has been the standard Mac package manager since 2009. It only downloads from official sources.

"Will this break my Mac?"

No. Homebrew installs to its own folder (/opt/homebrew or /usr/local) and doesn't touch system files. You can uninstall it completely anytime.

"Do I need to use Terminal for everything now?"

No! You can still install apps the traditional way. Homebrew is just a faster option. I use both — Homebrew for developer tools and quick installs, Mac App Store for Apple-specific apps.

"What if something goes wrong?"

Run brew doctor. It diagnoses issues and tells you how to fix them. The Homebrew community is also incredibly helpful.

Conclusion

Three months ago, setting up my Mac took hours of downloading, clicking, dragging, and deleting. I dreaded getting a new machine or doing a fresh install. Updates were a monthly chore I'd procrastinate.

Today? I install 20+ applications in under 5 minutes. I update everything with one command every week. My system is cleaner, faster, and I actually know what software I have installed.

Key Takeaways:

Manual installation wastes time: 5-10 minutes per app adds up fast
Homebrew installs anything with one command: brew install [name]
Updates become effortless: brew upgrade handles everything at once
Setup takes 5 minutes: Even if you've never used Terminal before
It's beginner-friendly: Copy, paste, press Enter. That's it.

Next Steps:

Install Homebrew right now (seriously, it takes 5 minutes)
Run brew doctor to make sure it's working
Install your first app: brew install --cask google-chrome
Explore available apps at formulae.brew.sh

The best time to start using Homebrew was when you got your Mac. The second best time is now.

What's the first app you'll install with Homebrew? Drop a comment below — I'd love to hear what tools you're excited to try. And if you found this helpful, consider following me for more Mac productivity tips that'll save you hours every week.

Related Resources

Official Homebrew Website — Installation guide and documentation
Homebrew Formulae Search — Browse all available packages
My Mac Setup Guide — Complete tutorial for new Mac users (coming soon)

DEV Community: Leon Wong 282

The Beginner's Guide to Raycast: Replace Spotlight in 15 Minutes

The Beginner's Guide to Raycast: Replace Spotlight in 15 Minutes

What is Raycast? (And Why Should You Care?)

Installing Raycast

Download and Install

Replacing Spotlight (The Most Important Step)

How to Replace Spotlight:

Your First 5 Minutes with Raycast

1. Launch Apps (Just Like Spotlight)

2. Find Files

3. Do Calculations

4. Understanding the Action Panel (⌘K)

Game-Changing Features You Can Set Up Right Now

Feature 1: Clipboard History

Feature 2: Text Snippets

Feature 3: Window Management

Installing Your First Extension

You're Now a Raycast User

Related Resources

Installing MySQL 8.0 on macOS with Homebrew: A Complete Guide

Installing MySQL 8.0 on macOS with Homebrew: A Complete Guide

Introduction

Prerequisites

Installation Steps

1. Update Homebrew

2. Install MySQL 8.0

3. Start MySQL Service

4. Security Configuration

Verify Installation

Option: DataGrip config

Common Commands

Service Management

Connect to MySQL

Uninstalling MySQL

Conclusion

What I Wish I Knew About Homebrew Before Wasting 2 Hours Troubleshooting

What I Wish I Knew About Homebrew Before Wasting 2 Hours Troubleshooting

Mistake #1: Not Adding Homebrew to Your PATH

Mistake #2: Using sudo with Homebrew (The Fatal Error)

Mistake #3: Ignoring brew doctor Warnings

Mistake #4: Not Understanding Formulae vs Casks

Mistake #5: Skipping the Caveats

Bonus Mistake: Forgetting to Update

The 5-Minute Troubleshooting Checklist

Key Takeaways

Related Resources

Why Your Mac Software Installation is Broken (And How to Fix It in 10 Minutes)

Why Your Mac Software Installation is Broken (And How to Fix It in 10 Minutes)

What "Normal" Installation Actually Costs You

Problem 1: The Security Roulette Game

Problem 2: The Dependency Black Hole

Problem 3: The Update Nightmare

Problem 4: The Version Chaos

Problem 5: The Downloads Folder Graveyard

The Tool Mac Should've Included (But Didn't)

What's a Package Manager?

How to Never Manually Download Software Again

The 10-Minute Setup

Step 1: Open Terminal (1 minute)

Step 2: Install Homebrew (3 minutes)

Step 3: Verify It Works (1 minute)

Step 4: Install Your First Apps (5 minutes)

The Commands You'll Actually Use

What This Actually Fixes

The 10 Minutes That Saves You 30 Hours

Key Takeaways

The Complete Beginner's Guide to Cloudflare R2 Image Hosting (2025)

The Complete Beginner's Guide to Cloudflare R2 Image Hosting (2025)

What Makes R2 Different (And Why It Matters for Your Blog)

How R2 Compares to Alternatives

Prerequisites (Don't Worry—It's Easier Than You Think)

Setting Up Your R2 Image Hosting (The Complete Walkthrough)

Step 1: Create Your Cloudflare Account

Step 2: Enable R2

Step 3: Create Your First Bucket

Step 4: Connect a Custom Domain (Optional but Recommended)

Getting Images Into R2 (Three Easy Methods)

Method 1: Dashboard Upload (Simplest)

Method 2: Using an Upload Tool (Recommended for Regular Use)

Mistake #2: Using `sudo` with Homebrew (The Fatal Error)

Mistake #3: Ignoring `brew doctor` Warnings