Forem: kato Geoffrey

Enterprise Coffee Decisioner

kato Geoffrey — Thu, 02 Apr 2026 09:49:55 +0000

This is a submission for the DEV April Fools Challenge

What I Built

I built Enterprise Coffee Decisioner™, an intentionally useless April Fools web app that decides whether you should drink coffee using corporate nonsense and teapot drama.

Neon “enterprise” UI with fake KPI dashboard (Synergy Index, Caffeine Half-Life, Jitter Probability, Board Alignment).
17-point strategic intake form with absurd entries (Lunar Influence, Manager Proximity, Last Git Commit).
“⬡ FINALIZE DECISION ⬡” includes required repeated confirmation clicks.
HTTP 418 teapot path: the system explicitly returns “I’M A TEAPOT”.
“Download PDF” path requires physical shake (or manual shake button), then shows comedic outcome (page 847 blank, antivirus quarantine, etc.).
Local memo generator (no external API required), but concept idea came from Google Antigravity + Claude Sonnet style prompts in design.

Demo

Run locally in browser:

Open enterprise_coffee_decisioner_april_fools.html from repo.
Fill inputs.
Click “FINALIZE DECISION” until progress pipeline finishes.
Read “Board Recommendation” result and generated memo text.
Click “⬇ Download PDF”, shake twice / click “Manual Shake”, confirm passphrase.
Use “↩ Waste More Time” to rerun.

No deploy required; works offline from file URL.

Code

Repo: https://github.com/geoffkats/descisioner

Primary implementation: enterprise_coffee_decisioner_april_fools.html (single-file HTML/CSS/JS).

Key logic:

UI state transitions and animation overlays
Teapot compliance pipeline + random verdict
Local passphrase generation + physical shake verification
Reset/ reiteration path

How I Built It

HTML + CSS (animated neon, grid layout, status ticks)
JavaScript: controls, randomization, progressive step animation, local memo text.
In early ideation, I used Google AI Antigravity + Claude Sonnet-style prompting to shape tone and jokes.
Final product: no external dependencies, 100% local to keep judging stable.

Prize Category

Primary: Best Ode to Larry Masinter
- RFC 2324 / HTTP 418 is central to the UI and messaging.
- Many “teapot” references in status text, rulings, and failures.
Secondary: Best Google AI Usage
- Google Antigravity + Claude Sonnet style inspired design and naming.
- Final mode is local and offline (robust judge-friendly deliverable).
Bonus: Community Favorite
- High absurdity + shareable meme-ability.

Team

Solo submission: @geoffkats

Notes

This intentionally solves zero real problems and is built to be delightfully ridiculous.
🤣 “Anti-value ranked by design.”
The repo link above is the source code and demo.

well check out my project, i submitted for the contest

kato Geoffrey — Thu, 29 Jan 2026 13:17:01 +0000

GitHub Copilot CLI Challenge Submission

kato Geoffrey

Jan 26

Detective: A Digital Forensics CLI Built with GitHub Copilot CLI

#devchallenge #githubchallenge #cli #githubcopilot

Comments

2 min read

Detective: A Digital Forensics CLI Built with GitHub Copilot CLI

kato Geoffrey — Mon, 26 Jan 2026 09:10:18 +0000

What I Built

I built Detective, a forensic code investigation CLI tool that analyzes software projects the way a detective examines a crime scene.

Instead of only reporting raw metrics, Detective focuses on evidence → inference → reporting. It scans a codebase and its git history, collects concrete signals (file sizes, commit patterns, code markers like TODO/FIXME/HACK), and then translates those signals into meaningful findings such as technical debt indicators, bus-factor risk, and development activity patterns.

The output is a narrative forensic report designed for:

code audits

post-mortems

early-stage project reviews

understanding unfamiliar repositories quickly

The tool is cross-platform (Windows-first), stateless, and produces plain-text reports suitable for terminals, CI logs, or documentation.

This project was built solo by me (@geoffkats).

Demo

Repository:
👉 https://github.com/geoffkats/detective-cli.git

Example command:

detective open . --verbose

Sample output (excerpt):

◼ FINDINGS

[ MEDIUM ] Large File Detected
File exceeds 1MB, may impact repository performance.
Evidence:
- bin/detective.exe: 10,104,320 bytes

[ LOW ] Single Contributor
Project has only one contributor, indicating potential bus factor risk.
Evidence:
- Contributors: 1

The report also includes:

Investigator Notes with human-style reasoning

Overall project health score

Report integrity hash (SHA-256)

Screenshots of the full terminal output are included above to show the tool in action.

My Experience with GitHub Copilot CLI

GitHub Copilot CLI was used throughout the entire development process, directly from the terminal.

I used Copilot CLI to:

Design the overall architecture (evidence collection → inference → reporting)

Generate and refine Go code for file scanning, git analysis, and report formatting

Iterate quickly on CLI UX, flags, and output structure

Refactor logic into clean internal modules without breaking behavior

Instead of switching to a browser or IDE chat, I could stay in the terminal and ask Copilot things like:

“Generate Go code to scan a directory and collect file metrics”

“Refactor this logic to separate evidence collection from inference”

“Suggest a professional CLI output style for a forensic tool”

Copilot CLI felt like a pair programmer inside the command line, which made it especially effective for building a terminal-first tool. It helped me move faster while still keeping the reasoning and design intentional, not autogenerated.

🚀 Elevate Your Code with Some Fun! 🚀

kato Geoffrey — Sat, 25 May 2024 16:28:31 +0000

🚀 Elevate Your Code with Some Fun! 🚀

Hey fellow developers!

Let's take a break from our screens for a moment and inject some fun into our coding journey. Here are a few light-hearted jokes and memes to brighten your day:

Debugging:
- Debugging is like being the detective in a crime movie where you're also the murderer. 😄
Code Comments:
- // TODO: This code is a mess, future me, I'm sorry. 🙈
Programming Languages:
- JavaScript: "I'm the king of the web!"
- Python: "Let's keep it simple and elegant."
- CSS: "I make things look good, but also frustrating."
Meeting Jargon:
- "Let's circle back" = "I have no idea, let's discuss later."
- "Let's take it offline" = "Let's not discuss this here."
Client Requests:
- Client: "Can you just make it pop more?"
- Developer: Adds more pop-up windows 😆

Remember, while coding is serious business, a little humor can go a long way in keeping us sane! Share your favorite coding jokes or memes below and let's keep the fun going!

Happy coding! 🎉

geoffkats

kato Geoffrey — Wed, 16 Sep 2020 22:56:04 +0000

hit it was nice meeting u

geoffkats

kato Geoffrey — Tue, 15 Sep 2020 21:25:13 +0000

My Workflow

Submission Category:

Yaml File or Link to Code

Additional Resources / Info

[Note:] # (Be sure to link to any open source projects that are using your workflow!)