Two people. One useless idea. A real Linux terminal that does the opposite of what you ask it to do.
The build started around 8 AM. By 11 AM, after throwing away ideas that were too useful, we finally had something suitably pointless.
We started the hackathon without a solid project idea. We brainstormed, searched, and kept asking the most important question for a useless-project competition: “Is this actually useless?”
One of our early ideas came from an Instagram reel about making a matchmaking/marriage-related webpage. It could have been useful — which was exactly the problem.
We finally settled on a terminal where selected action commands do the opposite. The idea also connected with a terminal project I had wanted to build for a while.
Sreelakshmi started shaping the UI/UX while I focused on the terminal implementation.
Before touching the actual terminal, we turned the UI/UX into a working webpage. By around noon, we had the visual shell of Pookie Terminal.
It looked like a terminal. It just wasn't one yet.
Quick food break. Then back to making the fake terminal become a real one.
An outside suggestion pushed us toward turning the UI into a real terminal rather than stopping at the webpage. I started working on the Python side and the actual terminal behaviour.
The important design decision was to reverse actions, not navigation. Commands such as ls, pwd, and cd remain normal so the terminal is still usable.
The terminal was working. It could interact with the real filesystem instead of being just a fake terminal screen.
We tested navigation, file operations, and the opposite-command behaviour. Some mappings worked; a few, including lock/unlock, did not make it into the working set.
The journal is not a changelog. These are the moments where the project actually fought back.
During testing, terminal formatting/control sequences started appearing as literal characters in the output. Instead of a clean ls, we were getting things that looked like [31m, [0m and other escape-code fragments.
We had to stop building features and clean up the terminal output before moving on.
We explored ways to make the real terminal accessible online, including SSH/Codespaces and server options. We ran into access and payment/account limitations and never got a working server in time.
So the real terminal stayed local. The hosted webpage became the thing we could submit.
The screenshots below are from the real project. No polished fake demo — these are the terminal states we captured while testing.
delete action producing the opposite behaviour.
When it was time to present, connecting the laptop to the projector didn't give us the terminal. The projector showed the wallpaper/background instead.
So the presentation became more hands-on: we brought the laptop closer and showed the project directly.
