What I've Learned From Completing CTFs

Overview

I have been doing CTFs for the past couple of months. Here is what I have learned along the way, and why each lesson matters.

1. The Terminal Is Your Friend

Navigating a Linux terminal is a core skill for CTF competitions. Before starting my cybersecurity journey, the most I had ever done at a command line was run sfc /scannow in Windows to fix a broken system file. Since then, I have become confident navigating the terminal and combining tools to work through problems: chaining commands together with pipes, using grep to search for text inside a folder, or writing a Python script to brute-force a password. Building that fluency has made the terminal feel like a tool I reach for instinctively rather than one I have to think through.

2. It’s Better to Sit With a Problem Than to Rush Past It

I used to fall into a bad habit: the moment I hit a roadblock, I would lean on AI as a teaching assistant to get unstuck. As I have gotten deeper into CTFs, I have deliberately pulled back from that and leaned into patience instead, searching for the right command with --help or -h rather than asking for the answer outright. That discovery-first approach has made me faster and more efficient at solving problems in real time, because I am building my own understanding instead of borrowing someone else’s.

3. Think Like the Person Who Built the Challenge

Before I started thinking like a hacker, I did not know where to begin. I was reasoning from what I had self-taught, what commands might help, but I was not thinking about the person who designed the problem in the first place. If I were working in a SOC, I would need to identify and respond to threats quickly, and there is no shortcut to that without first understanding how an attacker thinks. The moment I started asking “where would I hide this?” or “why does this exist?” is the moment CTFs became noticeably easier.