Making HackTheBox easier to start
The study ideas I'm trying for ADHD, including an Anki deck and a shell setup that help me return to a session.
A captured spark. Unverified, unpolished, possibly wrong.
On HackTheBox, I can lose eleven minutes between deciding to work on a machine and actually typing nmap. By then I’ve often opened another tab, remembered something else I should learn, or started reorganising the setup I was supposed to be using.
Getting started is a recurring difficulty for me with ADHD. Once I’m involved in a problem, I can enjoy the work, but getting to that point isn’t always straightforward. This project is my attempt to make the first few steps easier.
I’ve collected ten ideas across five areas. Some are experiments I’d like to try, while two have become tools I can actually use. I’m keeping that distinction clear because coming up with a study system is much easier than finding out whether it helps me study.
The ideas I’m working with
- Short practice prompts. I called one version “Finsta-of-Doom”: a feed of enumeration questions I could scroll through when I reach for my phone. The related Swipe-to-Pwn idea turns those questions into flashcards, so I have to choose a next step rather than just read an answer.
- Movement during a session. This includes pacing while explaining an attack path and doing a few squats while a scan runs. I’m interested in whether planned movement helps me stay with the task.
- Small challenges. An Ironman-style run would give a session a clear goal, while the “Forfeit Heist” idea adds a consequence for abandoning it. I’m less sure about this one, since adding pressure could make a frustrating session harder.
- A smaller starting task. The “90-Second Terminal Tax” asks me to open the terminal and do one small thing. Leaving a note about the next command or question should also make it easier to resume.
- Familiar cues. A particular playlist, including the 140 BPM music I had in mind, or an object on the desk could help mark the start of a session. These are possibilities to test, rather than things I know will work.
I don’t want to combine all ten and accidentally give myself another complicated routine to maintain. The useful question is whether a particular change helps me begin, continue, or return after getting stuck.
That last part matters because a difficult box can leave me taking the frustration personally. I’d like a way to pause, record what I’ve tried, and come back without treating the session as evidence that I’m bad at this. It connects with looking closely at where a process breaks down.
What I’ve built so far
The Swipe-to-Pwn Anki deck has 54 cards in an .apkg file. Each card starts with a signal I might encounter on a box and asks what I would investigate next. It covers port and service enumeration, web applications, Linux and Windows/Active Directory privilege escalation, and a few questions about approach.
The other tool is htb-operator.bashrc, a shell configuration with a pwn launcher, recon helpers, movement reminders, and a note/next system for recording where I stopped. The resume command and tmux-resurrect notes are there to reduce how much setup I have to repeat when I return.
What comes next
I’d like to add an installer that checks for tools such as ffuf, gobuster, seclists, and evil-winrm. Missing commands are a small annoyance, but they’re also an easy excuse for me to leave the task and start doing something else.
The larger question is whether these changes help over repeated sessions. I’ve built two tools, but that isn’t yet evidence that the whole approach works. I’ll keep the results alongside the rest of my learning notes, including anything that turns out to be more trouble than it’s worth.
Paths that lead here
- Building a chess openings trainer · That pattern is familiar from my attempts to manage attention while studying.
- Feeling behind in cybersecurity · It's the same kind of adjustment I'm exploring in my HackTheBox setup.
- Learning about quant trading · The other constraint is familiar from studying security with ADHD: I need a path I can actually follow.
- Why I keep rereading sentences · This connects with my attempts to make studying easier to start: I keep asking myself to concentrate while leaving plenty of opportunities to stop concentrating.
Where this note points
- Thinking like an attacker · I'm interested in the gap between how a system is supposed to work and what its parts allow it to do.
- Learning in public · Why I'm sharing unfinished notes, even when I'm a little embarrassed by them.
More from these beds
- Getting comfortable sharing my thoughts · I'm trying to make room for mistakes without letting the fear of them stop me from publishing.
- How I think about this site's security · What I want to protect on this site, the choices I've made, and the risks that still need attention.
- How much time should I give a bug hunt? · I'm wondering whether the Kelly criterion can help me think about research time, and where that comparison breaks down.
- Learning to explain things better · Someone told me I wasn't a good explainer, and it made me think about how often I talk past people.