THIS IS NOT A PORTFOLIO
This is a documented record of a person who refused to let their work — and their life — disappear into the dark. Every line of code was written from a phone screen. Every chapter was lived before it was written. Nothing has been sanitised. Nothing has been curated for comfort. The internet will have this. The world will know who built in these conditions.
📍 RAVENSMEAD, CAPE TOWN
🎂 BORN 1992
💻 HONOR X5B · ANDROID 14
◯ R0 BUDGET
CONTEXT
THE SETUP
HONOR X5BDEVICE
ANDROID 14OS
TERMUXENVIRONMENT
ROOTLESSROOT STATUS
V55CURRENT VERSION
120K+ORGANIC VIEWS
R0BUDGET
ZEROPROMOTION PLANS
"When I lost the job and the relationship, I had nothing left except the terminal. It became the only place where effort mapped to output. That is what all of this represents — proof that I kept going despite the weight."
— GRANT FESTERS · RAVENSMEAD · 2026
TRAJECTORY
THE ARC
BEFORE 2020
Connection. Love. The Before.
BBM era. Real connections. A 6-year relationship. Community. The person who existed before the damage was done.
2020–2022
The Weight Arrives.
Job loss. The 6-year relationship ends. Institutional betrayal. The silence descends. The apartment becomes everything.
2022–2023
The Terminal Becomes the Anchor.
Termux. First scripts. First tools. Admin Fezzy plans. Intox Fezzy ships. Both modes valid. Bojack Security V1 is born.
2023–2025
Building Under Pressure.
V1 to V55. Fezzy Station grows. Still Here launches. Grant & The Machines documents the AI workflow. 120K+ views with zero promotion budget.
2025 — REHAB
The Decision That Required the Most Strategy.
Rehab. The hardest thing. Four months clean. Asking for help is the most strategic move you can make.
2026 — NOW
The Return. Stability. Expansion.
Recovery holds. The builds continue. The documentation grows. Ravensmead is still home. The work did not stop during any of this.
THE ARCHIVE
LIFE CHAPTERS
Each chapter is raw documentation. Not curated. Not sanitised. This is who I am. Written in the same conditions the events occurred in — a phone screen, a terminal, and Ravensmead outside the window.
CHAPTER 00
THE BEFORE
BBM ERA · REAL CONNECTIONS · WHO I WAS
There was a time before the silence. Before the apartment became the whole world. Before the terminal was the only place where effort mapped to outcome.
The BBM era. Blackberry Messenger. Ravensmead was connected in ways that felt physical. You knew who was online. You knew the ping of someone who actually wanted to talk to you. It was small, but it was real — that web of connection. People who knew your name. Conversations that carried weight.
I existed in that. I was part of community. I had a voice that people heard before I learned to code it into a screen. The Before is important to document because it proves that what came later was not always how things were. There was a person here who laughed, who knew people, who was known.
This chapter exists so the damage is understood in context. You cannot understand what was lost unless you know what was there.
✓ COMPLETE
CHAPTER 00A
THE LOVE THAT WAS REAL
SIX YEARS · GENUINE · DOCUMENTED
Six years. Not a casual thing. Not a phase. A real partnership that shaped who I am — how I think, how I approach loyalty, what I understand about the weight of another person's trust.
This chapter is difficult to write because it requires honesty about what was genuine and what ended. Both things are true. The love was real. The ending was also real. Neither cancels the other.
When it ended, it did not leave quietly. It left with everything else that was leaving at the same time — the job, the routine, the structure that had held the days together. The timing meant there was nothing left to absorb the impact. Just the apartment. Just the silence. Just me.
Six years is documented here because it deserves to be. Because love that lasts that long — even when it ends — is part of who you are. I am not ashamed of it. I am not trying to erase it. It was real. It is part of the archive.
✓ COMPLETE
CHAPTER 01
THE ISOLATION
THE SILENCE · THE APARTMENT · THE TERMINAL
The silence is the thing nobody warns you about. It does not arrive like a storm. It arrives like the absence of something you did not know you needed — and then it stays.
The apartment became the whole world. Not by choice, but by collapse of everything outside it. No job to leave for. No relationship to show up for. Ravensmead was still there outside the window but the distance between inside and outside felt uncrossable.
This is when I found Termux. Not because I was looking for a calling. Because I needed somewhere to put energy that would not disappear. Every job application that got no response was energy that went nowhere. Every attempt to reconnect that got silence back was energy that went nowhere. The terminal was different. You typed. Something happened. Effort mapped to output.
That was everything in that period. The terminal was the only honest relationship I had. You input something correct, it works. You input something wrong, it tells you. No ambiguity. No silence that means something you cannot decode. Just truth in return for effort.
That is how it started. That is why it started. Not inspiration — necessity.
✓ COMPLETE
CHAPTER 02
THE WEIGHT
LOYALTY STRIPPED BY INSTITUTIONS · WHAT THEY TOOK
Job loss is not just financial. That is the part nobody explains until it happens to you. It is structural. It is the removal of purpose, of schedule, of the daily proof that you are useful to something. When an institution removes that — especially one you gave loyalty to — it is a specific kind of damage.
They took the routine. They took the reason to get dressed. They took the thing that gave the week shape. What they did not anticipate — what I did not anticipate — is that removing all of that at the same time the relationship ended would leave a person with nothing external to hold onto.
This chapter is not about bitterness. It is about documentation. About putting on record what the conditions were, so that what was built inside those conditions is understood correctly. You cannot evaluate the builds without knowing what they were built during.
If stability was not there, nothing could stand. So I rebuilt stability first — with Bash scripts, with Python, with a phone screen and Termux and the discipline of SOI: Am I acting on strategy or impulse right now? That question became the only rule left.
✓ COMPLETE
CHAPTER 03
THE DUALITY
ADMIN FEZZY PLANS · INTOX FEZZY SHIPS · BOTH ARE REAL
There are two modes. This is not a metaphor. It is a documented operational reality.
Admin Fezzy is structured. Strategic. Plans before building. Documents everything. Reads the error message before trying again. Creates README files at midnight before pushing anything. Version numbers matter to Admin Fezzy. Syntax validation is a ritual.
Intox Fezzy ships. Ships at 2am. Ships with a vision that does not have a plan yet. Ships things that sometimes need to be repaired in the morning. Is responsible for half the best ideas and also most of the merge conflicts.
Both modes are valid. Both have produced real things. The discipline is knowing which one is operating at any given moment — and knowing when to let it run and when to stop it and hand over to the other.
Strategy Over Impulse does not mean suppressing the Intox mode. It means having enough self-awareness to know which mode you are in and making conscious decisions within it. That is the whole philosophy, distilled.
✓ COMPLETE
CHAPTER 04
THE ANCHOR
BOJACK · LAB/HUSKY MIX · LOYALTY WITHOUT CONDITION
When everything else left, Bojack stayed. That is the simplest and most complete thing I can say about this chapter.
A Lab/Husky mix. His presence is physical and immediate in a way that code cannot be. He does not care about version numbers. He does not care about the build being broken. He is there at 2am when the session is running long. He is there in the morning when the previous session's damage needs to be assessed.
I named the security suite after him because that is what the security suite is — something that watches the perimeter. Loyal without being asked. Consistent without being programmed. Present in a way that institutions and relationships could not sustain.
Bojack Security exists as a technical project. But the name is not branding. The name is gratitude. For the one anchor that did not move during the years when everything else was moving.
✓ COMPLETE
CHAPTER 05
THE BUILD
WHAT I MADE ANYWAY · V1 TO V55 · PHONE ONLY
This is the chapter that surprises people. Not the chapters about loss — those are expected. The surprise is that all the loss happened simultaneously with all the building.
While the relationship was ending, Fezzy Station V1 was being written. While the job applications were getting no responses, Bojack Security was growing from 400 lines to 2800+. While the isolation was deepest, the GitHub commits were most consistent.
The terminal did not care about the external conditions. You could be in the worst year of your life and still push a working script at midnight. That dissociation between external collapse and internal production is one of the things I most want documented. It is proof that the work was not performed for an audience. There was no audience. It was built because building was the only thing left that responded to effort correctly.
V1 to V55. Each version documented. Each version a record of where I was when it was written. The builds are a diary. The commits are timestamps. The code was built during this. Not after. During.
✓ COMPLETE
CHAPTER 06
THE VISION
APK · FLASK · PRODUCT SUITE · WHAT IS NEXT
The current builds are not the ceiling. They are proof of concept — proof that a person with a phone and Termux can produce tools that 120,000 people find and use without any promotion budget whatsoever.
The vision is an APK. Fezzy Station packaged as a proper Android application via Expo EAS. A Flask dashboard that runs the security tools from a clean interface. A product suite that makes Ravensmead-built tools accessible to people who do not have Termux experience.
The three-AI workflow is already operational: Claude for architecture and code, ChatGPT for design and visuals, Gemini for research and ideas. The pipeline exists. The foundation exists. V55 is not the end — it is the platform the next phase launches from.
✓ DOCUMENTED
CHAPTER 07
THE RETURN
REHAB · RECOVERY · CURRENT STATE · ACTIVE
This is the chapter that required the most strategy. Not the code. Not the job applications. Not the breakup. Deciding to go to rehab — and then actually going — was the application of SOI in its most personal form.
Asking for help is not weakness. Asking for help when everything in your circumstances has trained you to expect that asking gets you nothing — that takes a specific kind of courage that I did not know I had until I used it.
Rehab happened. Four months clean as of the time this was first written. The work did not stop during this. The documentation did not stop. The builds did not stop. Recovery and production ran in parallel because the terminal had become too important a part of the structure to put down.
The return is not to who I was before. That person existed in different conditions and the conditions have changed. The return is to stability — the first kind of thing you have to rebuild before anything else can stand. The stability is holding. The work continues. The chapter is still being written.
This is the current state. Active. Documented. Not sanitised.
● ACTIVE · ONGOING
TECHNICAL RECORD
THE BUILDS
Everything built from a rootless Honor X5b. Android 14. Termux. No laptop. No team. No budget. The code is real, the tools are working, and they were built in the conditions described in the chapters above.
V55 · FLAGSHIP
FEZZY STATION
The central hub. A Bash-powered dashboard with 10 portals: Gallery, Music, Video, Web Grab, Music Search, Tools, Books (70K+), Social OSINT, Hacker Lab, and the Juice WRLD Archive. Boot speed under 30 seconds. 120K+ organic views. Built entirely by one person, on one phone, across 55 documented versions.
BASHPYTHONTERMUXV1→V55GITHUB PAGES
V3 · SECURITY
BOJACK SECURITY
A 2800+ line Bash security dashboard. Named after the dog who stayed. Six confirmed sections: BIRDS EYE VIEW, SPEAK IN CODES, MIND CONTROL, CROSS THE GLOBE, SECURITY HUB, CONTROL HUB. 30+ tools. Rootless — no root required. Educational use only. Built in the same apartment where the isolation chapters were written.
BASHSECURITYROOTLESSOSINT
WEB · FLASK
STILL HERE · RAVENSMEAD SPEAKS
A Flask community awareness site for Ravensmead, Cape Town. Mental health resources. Rehabilitation centre listings. Crisis lines. Built because the community needed it, not because it would get traffic. The most personally important thing in the archive — and the one that required the most honesty to ship.
FLASKPYTHONCOMMUNITYCAPE TOWN
HTML · DOCUMENTATION
GRANT & THE MACHINES
A standalone HTML site documenting the AI workflow: the relationship between Grant, Claude, ChatGPT, and Gemini. How the three-AI pipeline works. What each AI contributes. A record of how this kind of building actually happens in practice, at this level of resource constraint, from a phone screen.
HTMLCLAUDECHATGPTGEMINI
THE PHILOSOPHY
STRATEGY OVER IMPULSE
SOI was not written in a comfortable room. It was written in the pressure of survival. Every decision filtered through one question: Am I acting on strategy or impulse right now?
"SOI is not about suppressing instinct. It is about having enough self-awareness to know which mode you are in — and making a conscious decision within it rather than being carried by it."
— FEZZY WRLD · SOI DOCUMENTATION
01
THINK before you ACT. Not paralysis — awareness. Know what you are about to do and why before you do it. One second of awareness is the difference between building and breaking.
02
PLAN before you BUILD. Even a rough plan written in comments before the first line of code changes the outcome. Admin Fezzy plans. Intox Fezzy executes. The plan is what connects the two modes.
03
UNDERSTAND before you EXECUTE. Read the error message. Read the documentation. One minute of understanding saves an hour of trial and error. Impulse skips the understanding. Strategy does not.
04
DOCUMENT everything. If it is not documented, it did not happen. The version history is the proof of work. The README is the contract with the future. Write it down even if no one is reading yet.
05
STABILITY first. Nothing stands without a foundation. Rebuild stability before you rebuild anything else. This applies to code architecture and personal recovery — the principle is the same in both contexts.
06
ASKING FOR HELP is the most strategic move you can make. Impulse says handle it alone. Strategy knows when the problem requires more than one person and chooses connection over pride.
COMMUNITY · CAPE TOWN
MENTAL HEALTH RESOURCES
⚠ DISCLAIMER: This page contains references to depression, anxiety, isolation, and substance recovery. If you are in a dark place right now — the resources below are real. The lines are free. You are not alone. Asking for help is the most strategic move you can make.
"If you are reading this because you are in a dark place: the lines are listed below. You are not alone. Ravensmead has more people who understand than you think."
— GRANT FESTERS
CRISIS LINES · SOUTH AFRICA
SADAG 24HR HELPLINE
0800 456 789
FREE · 24 hours · South African Depression & Anxiety Group
SUICIDE CRISIS LINE
0800 567 567
FREE · 24 hours · Talk to someone now
SADAG WHATSAPP
076 882 2775
Text if you cannot speak
LIFELINE WESTERN CAPE
0861 322 322
Crisis counselling · Cape Town
REHABILITATION · CAPE TOWN
METRO DRUG ADVISORY BOARD (MDAC)
021 448 4640
Government · Free for qualifying residents · Voortrekker Road, Bellville
CROSSROADS RECOVERY CENTRE
086 180 0500 (24hr)
Detox, therapy, aftercare · crossroads.co.za
NEW BEGINNINGS TREATMENT CENTRE
086 111 1474
Addiction + mental health · Dual diagnosis · newbeginnings.co.za
STIKLAND PSYCHIATRIC HOSPITAL
021 940 1100
Government · Free · Referral required · Hospital Street, Bellville
SADAG · THERAPIST REFERRALS
sadag.org
Free referrals · Support groups · Confidential